SEO Report
SEO Performance Report
Explain ranking and traffic movement with queries, pages, and actions - no vanity charts.
The Prompt
seo-performance-report.md
Write an SEO report from the data I paste. Property / site: {{site}} Period: {{period}} Data (Search Console, rankings, notes): {{data}} Changes we shipped: {{changes}} Include: 1. Executive summary (traffic, top movers, one risk) 2. Query and page tables (top 10) using only my data 3. What we did that might explain movement 4. Technical / content issues mentioned in the data 5. 5 actions for next period, ordered by effort vs likely impact Do not invent rankings or click counts. If GSC data is partial, say so.
Negative prompt
Included when you copy the prompt
Do not invent rankings, CTR, impressions, or click counts. Do not present partial GSC exports as complete without saying so. Do not fill tables with queries or pages not present in {{data}}. Do not recommend generic "create more content" without tying to movers, issues, or shipped changes. Do not use vanity chart language instead of query/page tables and concrete next actions. Do not blame algorithm updates without evidence in the notes.
Fill in your details below - this prompt updates as you type, then copy it.
Fill in your details
0 of 4 filled. Preview updates as you type - then copy the finished prompt (negative prompt included when present).
seo-performance-report.md
Prompt preview
Write an SEO report from the data I paste. Property / site: {{site}} Period: {{period}} Data (Search Console, rankings, notes): {{data}} Changes we shipped: {{changes}} Include: 1. Executive summary (traffic, top movers, one risk) 2. Query and page tables (top 10) using only my data 3. What we did that might explain movement 4. Technical / content issues mentioned in the data 5. 5 actions for next period, ordered by effort vs likely impact Do not invent rankings or click counts. If GSC data is partial, say so.
Examples
Example input
Property / site: docs.northstar.app Period: 2026-07-01 to 2026-07-31 vs 2026-06-01 to 2026-06-30 Data (Search Console, rankings, notes): Clicks: 12,400 (June 10,800) Impressions: 310,000 (June 295,000) Avg CTR: 4.0% (June 3.7%) Avg position: 18.2 (June 19.1) Top queries by clicks: "northstar api auth" 920; "northstar webhook retry" 610; "northstar sso setup" 540; "northstar rate limits" 410; "northstar csv export" 380 (only 5 queries exported - GSC partial) Top pages by clicks: /docs/auth 2,100; /docs/webhooks 1,640; /docs/sso 1,200; /docs/api/rate-limits 890; /blog/onboarding-checklist 720 Notes: /docs/sso climbed from ~pos 24 → ~14 for "northstar sso setup". Blog post ranking for non-brand generics still weak (pos 40+). Crawl: 14 soft 404s on old /guides/* URLs after IA move. Changes we shipped: Rewrote /docs/sso + internal links (Jul 8). Fixed webhook example code (Jul 15). Added FAQ schema on /docs/auth (Jul 22).
What you should get
1. Executive summary Organic clicks rose 12,400 vs 10,800 (+14.8%) with CTR 4.0% vs 3.7% and average position 18.2 vs 19.1. Top mover: SSO docs/query after the Jul 8 rewrite. Risk: 14 soft 404s on legacy /guides/* may waste crawl budget and confuse referrers. Note: query export is partial (5 queries only). 2. Queries (provided) | Query | Clicks | | northstar api auth | 920 | | northstar webhook retry | 610 | | northstar sso setup | 540 | | northstar rate limits | 410 | | northstar csv export | 380 | Pages (provided) | Page | Clicks | | /docs/auth | 2,100 | | /docs/webhooks | 1,640 | | /docs/sso | 1,200 | | /docs/api/rate-limits | 890 | | /blog/onboarding-checklist | 720 | 3. Likely explanations - /docs/sso rewrite + internal links aligns with SSO query/position improvement. - Webhook example fix may support webhook query clicks. - FAQ schema on /docs/auth may aid CTR on auth query (hypothesis; not proven in data). 4. Issues in data - Soft 404s on old /guides/* after IA move (14 URLs) - Blog still weak on non-brand generics (pos 40+) - Partial GSC query export - do not treat top 5 as full head terms 5. Next actions (effort → impact) 1. 301 /guides/* soft 404s to new docs (low effort, high crawl hygiene) 2. Export full query + page CSVs for August baseline (low effort, enables real prioritization) 3. Add "SSO setup" screenshot steps + troubleshooting on /docs/sso (med, doubles down on mover) 4. Refresh /docs/webhooks with retry/backoff snippet matching top query (med) 5. One non-brand comparison/outline only if capacity - else defer blog generics (higher effort, weaker near-term)
When to use this prompt
Use it when
- You need help with seo leads.
- You need help with agencies.
- You need help with marketers.
Skip it when
- You only need a one-line ask with no constraints, format, or context.
- You cannot supply the fill-in details the template asks for.
- A different category or tool-specific workflow fits the job better.
How to get a good result
Done when
1. Executive summary Organic clicks rose 12,400 vs 10,800 (+14.8%) with CTR 4.0% vs 3.7% and average position 18.2 vs 19.1. Top mover: SSO docs/query after the Jul 8 rewrite. Risk: 14 soft 404s on legacy /guides/* may waste crawl budget and confuse referrers. Note: query export is partial (5 queries only). 2. Queries (provided) | Query | Clicks | | northstar api auth | 920 | | northstar webhook retry | 610 | | northstar sso setup | 540 | | northstar rate limits | 410 | | northstar csv export | 380 | Pages (provided) | Page | Clicks | | /docs/auth | 2,100 | | /docs/webhooks | 1,640 | | /docs/sso | 1,200 | | /docs/api/rate-limits | 890 | | /blog/onboarding-checklist | 720 | 3. Likely explanations - /docs/sso rewrite + internal links aligns with SSO query/position improvement. - Webhook example fix may support webhook query clicks. - FAQ schema on /docs/auth may aid CTR on auth query (hypothesis; not proven in data). 4. Issues in data - Soft 404s on old /guides/* after IA move (14 URLs) - Blog still weak on non-brand generics (pos 40+) - Partial GSC query export - do not treat top 5 as full head terms 5. Next actions (effort → impact) 1. 301 /guides/* soft 404s to new docs (low effort, high crawl hygiene) 2. Export full query + page CSVs for August baseline (low effort, enables real prioritization) 3. Add "SSO setup" screenshot steps + troubleshooting on /docs/sso (med, doubles down on mover) 4. Refresh /docs/webhooks with retry/backoff snippet matching top query (med) 5. One non-brand comparison/outline only if capacity - else defer blog generics (higher effort, weaker near-term)
Common mistakes
- Leaving site, period, data vague - the model then invents placeholders.
- Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules.
- Stopping when the first draft appears instead of checking it against the success criteria below.
FAQ
- What do I fill in before I copy this prompt?
- Replace these placeholders with your details: site, period, data, changes. Required fields are marked on the page. The prompt text updates as you type.
- Which AI tools is this prompt written for?
- It works best with ChatGPT, Claude, Gemini. Copy the filled prompt and paste it into the tool you already use.
- What should a good result look like?
- 1. Executive summary Organic clicks rose 12,400 vs 10,800 (+14.8%) with CTR 4.0% vs 3.7% and average position 18.2 vs 19.1. Top mover: SSO docs/query after the Jul 8 rewrite. Risk: 14 soft 404s on legacy /guides/* may waste crawl budget and confuse referrers. Note: query export is partial (5 queries only). 2. Queries (provided) | Query | Clicks | | northstar api auth | 920 | | northstar webhook retry | 610 | | northstar sso setup | 540 | | northstar rate limits | 410 | | northstar csv export…
- What are common mistakes with this prompt?
- Leaving site, period, data vague - the model then invents placeholders. Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules. Stopping when the first draft appears instead of checking it against the success criteria below.
Best for
- SEO leads
- Agencies
- Marketers
Related Prompts
More prompts like this — same topic and style.