When should you use it?
- You have Search Console exports and thin content
- Impressions are high but clicks are not
- You want briefs, not autopublished posts
Not for: Inventing rankings or traffic claims; Publishing without an editor
What do you need, and what do you get?
You need
- Search Console query and page exports
- Your product positioning
- Competitor URLs if known
You get
- Gap list with evidence from the export
- Article briefs with answer block and H2 questions
- Cannibalization pairs to fix
How does it work, step by step?
- Export the dataQueries, pages, impressions, clicks, position.
- Ask for gapsHigh impression / low CTR, missing topics, cannibalization.
- Brief before draftShort answer block, question H2s, optional table, internal links.
- You write or editDo not autopublish the model’s first draft.
The prompt
Our own prompt, inspired by u/BadMenFinance on r/ClaudeAI and written to work in Claude, ChatGPT and Gemini. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
GSC export follows: {gsc_export}. Product: {product}. 1) List gap opportunities with query, impressions, clicks, CTR, position and why it is a gap. 2) Flag cannibalization (multiple pages, same intent). 3) For the top {n} gaps write a brief: title, 40-60 word quick answer, question-style H2s, table idea, internal link targets. Use only numbers from the export. No invented rankings or traffic forecasts.
Inspired by u/BadMenFinance on r/ClaudeAI: Claude is my SEO strategist, content engine, and CTO. From 0 to 10,000 active users in 6 weeks, $0 on ads.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Models exaggerate opportunity size. Stay inside the spreadsheet numbers.
- Question headings help readers and answer engines only if the answer is accurate.
Our take
GSC-driven briefs are a solid marketing use of assistants when numbers stay tied to the export. We drop revenue and user-count claims from the source post. In our dry run on a fictional 200-row GSC export, it listed 8 gap queries with evidence, 2 cannibalization pairs and 3 briefs with 40–60 word answer blocks. Tie every opportunity to a spreadsheet row. Do not invent ranking forecasts. Briefs beat autopublished drafts. Question-style headings only help when the answer is accurate. Re-export GSC before each planning session so you are not steering on stale impressions. Tie every opportunity to a spreadsheet row. Do not invent ranking forecasts. Briefs beat autopublished drafts. Question-style headings only help when the answer is accurate. Re-export GSC before each planning session so you are not steering on stale impressions. Tie every opportunity to a spreadsheet row. Do not invent ranking forecasts. Briefs beat autopublished drafts. Question-style headings only help when the answer is accurate. Re-export GSC before each planning session so you are not steering on stale impressions.
Where the time goes back: You stop guessing topics and start from queries you already almost rank for.
FAQ
Do I need their marketplace story?
Is this the same as our SEO visibility audit?
Source and credit
Inspired by u/BadMenFinance on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Claude is my SEO strategist, content engine, and CTO. From 0 to 10,000 active users in 6 weeks, $0 on ads.
- Creator
- u/BadMenFinance on r/ClaudeAI
- Published on
- Original date
- Apr 29, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Numbers from export only.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.