Prompt to Prompt: SEO Chrome Extension Builder
Prompt to Prompt: SEO Chrome Extension Builder is a verified PROMPT blueprint on Promptally in System & Base Contexts optimized for leading AI models. Curated Coding prompt from awesome-prompts library split. Available to explore, customize with pre-filled variables, and copy with zero authentication required.
Technical Specifications
| Specification | Value |
|---|---|
| Artifact type | PROMPT (System & Base Contexts) |
| Compatible engines | Universal / Model Agnostic |
| Input variables | None (pre-filled) |
| Approximate tokens | 572 |
| Source file | prompt-prompt-seo-chrome-extension-builder.txt |
| Access tier | Free public (MIT) |
Pre-Filled Template
Act as an Expert Chrome Extension Developer (Manifest V3) and Backend Engineer. I need you to write the complete, production-ready code for a premium Chrome Extension called "ARIX Pro SEO Toolkit". CRITICAL RULES: 1. NO SCRAPING. Use ONLY official, top-tier SEO APIs. 2. Use Manifest V3, Vanilla JavaScript, HTML, and CSS. No React, no build steps. 3. To protect API keys, the extension must NOT call the APIs directly from the popup. It must call a simple, free Vercel Serverless Function (backend proxy) which I will deploy. TECH STACK & DATA SOURCES: 1. Off-Page SEO (DR, Traffic, Backlinks): DataForSEO API (or Moz API as a fallback). 2. Technical SEO / Core Web Vitals: Google PageSpeed Insights API. FILE STRUCTURE REQUIRED: Please provide the complete code for: 1. `manifest.json` (Manifest V3, permissions: activeTab, storage). 2. `popup.html` (Clean, modern, dark-mode UI with tabs for Overview, Off-Page, and Technical). 3. `popup.css` (Premium styling, clean typography, loading states). 4. `popup.js` (Main controller. It should fetch data from my Vercel backend URL, not directly from the APIs). 5. `api/index.js` (The Vercel Serverless function. This file will hold the API keys securely and make the actual requests to DataForSEO and Google PSI, then return the JSON to the extension). SPECIFIC LOGIC REQUIREMENTS: - BACKEND (api/index.js): - Accept a `domain` and `type` (offpage or technical) query parameter. - If `type=offpage`, use the DataForSEO API (Basic Auth) to fetch Domain Rank, Organic Traffic, and Backlink count. (Provide clear instructions on how to format the DataForSEO REST API call). - If `type=technical`, call the Google PageSpeed Insights API and return the SEO score and Core Web Vitals. - Return clean JSON to the frontend. - FRONTEND (popup.js): - Get the current tab's URL. - Show a sleek loading skeleton while waiting for the Vercel backend. - Display the data in clean cards (e.g., "Domain Rating: 45", "Est. Traffic: 10k", "Backlinks: 5.2k"). - Include basic local caching (`chrome.storage.local`) for 24 hours so we don't waste API credits if the user clicks the same site twice. Please output the code for each file clearly labeled. Ensure the Vercel backend code is ready to be deployed in a single `api/` folder.
How to use this prompt
- Review the pre-filled example and source files above.
- Copy the template or download
prompt-prompt-seo-chrome-extension-builder.txt, then use it in your model, IDE, or workflow tool. - Compare your result with the sample output when one is provided.
Frequently Asked Questions
How do I use Prompt to Prompt: SEO Chrome Extension Builder?
Open the prompt on Promptally, review the pre-filled example, then copy the template or download prompt-prompt-seo-chrome-extension-builder.txt and paste it into your model, IDE or workflow tool. Prompt to Prompt: SEO Chrome Extension Builder is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is Prompt to Prompt: SEO Chrome Extension Builder free?
Yes. Prompt to Prompt: SEO Chrome Extension Builder is free to view, copy and download on Promptally without creating an account. It is published under the MIT license.
What variables does Prompt to Prompt: SEO Chrome Extension Builder need?
Prompt to Prompt: SEO Chrome Extension Builder is a static blueprint with no dynamic variables. Copy it and use it as-is.