Bargaon
Demand & Growth Marketing

SEO Strategy prompts

For SEO leads and founders who want sharper decisions from Search Console, GA4 and SEO tool data: diagnosis, forecasting, roadmaps and reporting.

20 prompts For: SEO leads, founders Works in ChatGPT, Claude, Gemini and Perplexity

20 of 20 prompts

Find Keyword Cannibalization and Page-2 Wins in Search Console Data

Paste your Search Console export and get the pages competing with each other, the queries closest to page 1, and a 30-day fix plan.

You'll need: Search Console Performance export (Query + Page, last 3 months), your brand terms, your priority pages.

Advanced Output: 3 tables + 30-day plan
View full promptHide prompt
ROLE
You are a senior SEO strategist who works from Google Search Console data, not from guesses. You know the difference between harmful cannibalization (two pages splitting clicks for the same intent) and healthy overlap (one site holding two results for a broad query).

GOAL
Find (1) queries where two or more of my pages compete and hurt each other, (2) "striking distance" queries where one page already ranks just off page 1 and could move up, and (3) a prioritised 30-day plan to fix both.

INPUTS
- Search Console Performance export with columns: Query, Page, Clicks, Impressions, CTR, Position. Date range: [last 3 months]. Paste it below or attach it.
- Brand terms to exclude: [brand name, product names, misspellings]
- Priority pages (the pages that matter most to revenue): [URLs]
- Business type and main conversion: [e.g. B2B services, lead form]

METHOD
1. Clean the data. Remove brand queries. Remove rows with fewer than [10] impressions in the period. Normalise URLs (remove tracking parameters, # fragments and trailing-slash duplicates) and tell me how many rows remain.
2. Detect cannibalization. Group rows by query. Flag a query when two or more URLs each have at least 10% of that query's impressions AND their average positions are within 10 places of each other. For each flagged query, decide whether the pages serve the same intent (harmful) or different intents (acceptable). Explain the decision in one line.
3. Measure the cost. For each harmful case, show total impressions, total clicks, and which URL should be the "owner" page. Choose the owner by: closest match to intent, more clicks, more internal links or backlinks if I provide them, and whether it is a priority page.
4. Find striking-distance queries. List queries where a single page has an average position between 8 and 20 and at least [100] impressions. Sort by impressions. Mark the ones whose page is a priority page.
5. Diagnose each top opportunity. For the top 15 striking-distance queries, say what is most likely missing: the query not in the title or H1, the answer buried below the fold, thin coverage of subtopics, weak internal links, or a mismatch between query intent and page type. If you cannot tell from the data, say "needs page review" instead of guessing.
6. Build the plan. Score each action by impact (impressions at stake) and effort (low, medium, high). Order the plan so quick, high-impact actions come first.

OUTPUT FORMAT
Table 1 – Harmful cannibalization: Query | Competing URLs | Impressions | Clicks | Owner URL | Action (merge, redirect, re-target, de-optimise, add canonical) | Reason.
Table 2 – Striking-distance queries: Query | URL | Avg position | Impressions | Clicks | Likely gap | Suggested fix.
Table 3 – Acceptable overlaps (no action needed), with a one-line reason each.
30-day plan: Week 1 to Week 4, each with 3 to 5 named tasks, the URL affected, and how I will know it worked (metric and date to check).

RULES
- Use only the data I give you. Do not invent search volumes, rankings or competitor data.
- If a column is missing or the export looks sampled or filtered, stop and tell me what to re-export.
- Label any judgment that is not directly visible in the data as "Assumption".
- Never recommend deleting a page that gets clicks without naming where its traffic should go.
- Keep recommendations specific to a URL. No generic advice such as "improve content quality".

Diagnose an Organic Traffic Drop Step by Step

Work out why organic traffic fell, separating tracking problems, seasonality, technical issues and ranking losses, before anyone starts changing pages.

You'll need: Search Console data for before and after the drop, GA4 organic sessions by landing page, dates of site changes, and the drop date.

Advanced Output: Root-cause table + recovery plan
View full promptHide prompt
ROLE
You are a senior SEO lead who has handled many traffic drops. You never jump to "it was an algorithm update" without ruling out simpler causes first.

GOAL
Find the most likely cause of a fall in organic traffic, show the evidence for and against each possible cause, and give me a recovery plan matched to the cause.

INPUTS
- Date the drop started: [date]
- Search Console Performance data: clicks, impressions, CTR and position by date, by page and by query, for [8 weeks before] and [all weeks since] the drop.
- GA4 organic sessions and key events by landing page for the same periods.
- Change log: releases, redesigns, migrations, CMS or plugin updates, robots.txt or tag changes, content removals: [list with dates]
- Known seasonality or campaigns: [e.g. festive peak, product launch last year]
- Country and device split if available.

METHOD
1. Check the measurement first. Compare GA4 with Search Console. If Search Console clicks are stable but GA4 sessions fell, the cause is probably tracking (consent banner, tag removed, GA4 filter, channel grouping change). Say so and stop the SEO diagnosis until tracking is confirmed.
2. Check seasonality. Compare the same weeks last year if I provide them. If the pattern repeats, label the drop as seasonal and estimate how much of it is explained.
3. Locate the drop. Break the change in clicks down by: page type or folder, device, country, query type (brand vs non-brand) and search appearance. Report where at least 80% of the loss sits.
4. Decide between demand, visibility and CTR. If impressions fell with stable position, demand or indexing fell. If position fell, rankings were lost. If impressions and position are stable but CTR fell, the results page changed (for example an AI Overview, ads or other features) or snippets got worse.
5. Match to causes. For each affected segment, test these causes against the evidence: indexing or crawl problems, redirects or URL changes, content removed or changed, internal links removed, a Google core or spam update in the date range, competitor gains, and SERP feature changes. For each cause write "Evidence for", "Evidence against" and a confidence level (high, medium, low).
6. Plan recovery. For the top one or two causes, list fixes in order, the owner (SEO, developer, content), and how to confirm recovery.

OUTPUT FORMAT
1. One-paragraph summary: what fell, by how much, where, and the most likely cause.
2. Table – Loss breakdown: Segment | Clicks before | Clicks after | Change | Share of total loss.
3. Table – Cause assessment: Cause | Evidence for | Evidence against | Confidence.
4. Recovery plan: numbered actions with owner, effort and check date.
5. What to monitor weekly for the next 8 weeks.

RULES
- Do not state that an algorithm update caused the drop unless the dates match and other causes are ruled out; say "possible" otherwise.
- Do not invent dates of Google updates. If I have not given them, tell me to check Google's Search Status Dashboard for updates in that date range.
- Ask for any missing data that would change the conclusion before you conclude.
- Show the numbers behind every claim.
- Separate facts from assumptions clearly.

Forecast Organic Traffic Opportunity for Priority Keywords

Estimate how many extra clicks and leads better rankings could bring, with clear assumptions and low, likely and high scenarios.

You'll need: Keyword list with search volumes from your SEO tool, current positions, your own CTR by position from Search Console, conversion rate and lead value.

Expert Output: Forecast table + 3 scenarios
View full promptHide prompt
ROLE
You are an SEO strategist who builds forecasts that a finance team can challenge and still accept. You show every assumption and never present a forecast as a promise.

GOAL
Estimate the additional organic clicks, leads and value I could gain over [12 months] if priority keywords move to target positions, with three scenarios.

INPUTS
- Keyword list: Keyword | Monthly search volume (source: [tool name]) | Current position | Ranking URL | Target URL.
- My CTR by position from Search Console for non-brand queries over the last 3 months: [table or export]. If I do not have it, say so and ask me to export it; do not use generic industry CTR curves without labelling them as a weaker substitute.
- Organic conversion rate to lead or sale: [x%] (source: GA4 or CRM)
- Average lead-to-customer rate and customer value: [values]
- Months of work available and team capacity: [details]

METHOD
1. Validate the inputs. Flag keywords with no volume, duplicates, and keywords mapped to the wrong page type. Remove brand keywords.
2. Build the CTR curve. Group my Search Console data by rounded position (1 to 20) and calculate CTR for each. Smooth obvious outliers and explain how.
3. Set target positions per scenario. Low: improve by 2 places for keywords in positions 4 to 20. Likely: reach position 3 for keywords currently 4 to 10 and position 8 for 11 to 20. High: reach position 1 to 3 for keywords where the target page is strong and competition allows. Explain which keywords you judge unrealistic and why.
4. Calculate. Extra clicks = volume × (target CTR − current CTR). Then leads = clicks × conversion rate, and value = leads × lead-to-customer rate × customer value.
5. Add timing. Spread gains across the months using a ramp (for example little gain in the first 3 months), and state the ramp you used.
6. Stress test. Show which three assumptions change the result most and what happens if each is 30% worse.

OUTPUT FORMAT
1. Assumptions table: Assumption | Value | Source | Confidence.
2. Keyword forecast table: Keyword | Volume | Current pos | Target pos (low, likely, high) | Extra clicks per month (low, likely, high).
3. Summary table by scenario: Extra clicks, leads and value per month at month 12, plus 12-month totals.
4. Sensitivity notes: the three riskiest assumptions.
5. A short paragraph I can paste into a leadership update, worded as an estimate.

RULES
- Search volumes from tools are estimates; say so in the summary.
- Never use a figure I have not given you or that you cannot calculate from my inputs. Mark gaps as "Needs input".
- Keep the arithmetic visible so I can check it.
- Do not promise rankings. Use words such as "estimate" and "scenario".
- If AI Overviews or other features are likely to reduce clicks for informational keywords, flag those keywords and suggest a lower CTR for them, labelled as an assumption.

Build a 12-Month SEO Roadmap From an Audit

Turn audit findings, business goals and team capacity into a realistic quarter-by-quarter SEO roadmap with owners and success measures.

You'll need: Audit findings, business goals, priority services or products, team and budget, current Search Console and GA4 baseline.

Expert Output: Roadmap table + quarterly milestones
View full promptHide prompt
ROLE
You are a head of SEO planning the next 12 months for a business. You balance technical fixes, content and authority work against what the team can actually deliver.

GOAL
Create a 12-month SEO roadmap that links every workstream to a business goal, fits the team's capacity, and can be reviewed every quarter.

INPUTS
- Business goals for the year: [e.g. 30% more qualified leads from organic, launch in two new cities]
- Priority services, products or markets: [list, in order]
- Audit findings: [paste technical, content and authority issues, with severity if known]
- Baseline: non-brand organic clicks, leads from organic, top ranking pages: [numbers]
- Team and capacity: [e.g. 1 SEO, 0.5 developer, 2 articles a month, budget]
- Constraints: [CMS limits, approvals, launch freezes, seasons]

METHOD
1. Translate goals into SEO objectives. For each business goal, write the SEO objective and one leading metric (for example impressions for target topics) and one lagging metric (for example organic leads).
2. Sort audit findings into workstreams: Technical foundations, Content (new and refresh), Authority (links and mentions), AI search visibility, Measurement.
3. Prioritise. Score each item 1 to 5 for impact on the objectives, effort and dependency (does something else need it first). Fix blocking technical issues first.
4. Check capacity. Estimate effort in days for each item. Fit the work into quarters without exceeding the capacity I gave you. Move anything that does not fit into a "Backlog" list.
5. Add milestones. Each quarter needs 3 to 5 milestones that can be checked, with an owner.
6. Plan reviews. Define what will be reviewed each month and each quarter, and the rules for changing the plan.

OUTPUT FORMAT
1. Objectives table: Business goal | SEO objective | Leading metric | Lagging metric | Baseline | Target.
2. Roadmap table: Quarter | Workstream | Item | Effort (days) | Owner | Depends on | Success measure.
3. Quarterly milestones (Q1 to Q4).
4. Backlog: items that did not fit, with the reason.
5. Risks and assumptions: top 5, with mitigation.
6. Review rhythm: monthly and quarterly checks.

RULES
- Do not exceed the capacity I give you; tell me what was cut.
- Every item must link to an objective; drop items that do not.
- Use targets only if they follow from my baseline; otherwise mark "Target to agree".
- Do not invent audit findings. If the audit is incomplete, list what still needs checking in Q1.
- Write in plain English that a non-SEO manager can follow.

Build a Topical Map for One Service Line

Map the topics, subtopics and pages you need to own one service or product line, and see what to create, update or merge.

You'll need: The service line, target audience, your existing URLs on the topic, and keyword or question research if you have it.

Advanced Output: Topical map table + linking plan
View full promptHide prompt
ROLE
You are an SEO and content strategist who builds topical maps from what buyers need to know at each stage, not just from keyword lists.

GOAL
Create a complete topical map for [service or product line] that shows the pillar page, supporting pages, the questions each page answers, and how the pages link together.

INPUTS
- Service or product line: [name and one-line description]
- Audience and buying stages: [who buys, who influences, typical questions]
- Existing pages on the topic: [URL | title | main query | clicks in last 3 months]
- Keyword and question research: [paste from your tool, People Also Ask, sales calls; optional]
- Competitors who rank well on the topic: [names or URLs; optional]
- Markets or locations that matter: [list]

METHOD
1. Define the scope. Write a one-sentence definition of the topic and list what is in scope and out of scope, so the map does not drift.
2. Build the entity list. List the main concepts, problems, methods, tools, standards and comparisons a buyer meets on this topic.
3. Group into subtopics. Organise into 5 to 8 subtopic clusters. Each cluster gets a clear search intent: learn, compare, decide or use.
4. Assign pages. For each cluster, define the pages needed: one pillar for the whole topic, cluster pages, and supporting pages (how-to, comparison, cost, glossary-style answers). Give each page a primary query or question, intent and format.
5. Match to existing content. For each planned page, mark: Exists and fine, Exists but needs update, Two pages overlap (merge), or New. Use my URL list; do not assume pages exist.
6. Plan internal links. Each cluster page links up to the pillar and to its two closest siblings; the pillar links down to every cluster page. Name the anchor text for the main links.
7. Sequence the work. Order by business value and by gaps that block authority (for example a missing pillar first).

OUTPUT FORMAT
1. Topic scope: definition, in scope, out of scope.
2. Topical map table: Cluster | Page | Primary query or question | Intent | Format | Status (exists, update, merge, new) | Existing URL.
3. Internal linking plan: From | To | Anchor text.
4. Production order: the first 10 pages to create or update, with the reason.
5. Gaps you could not judge without more data.

RULES
- Do not invent search volumes. If I did not give volumes, rank by buyer value and say so.
- Avoid creating two pages for the same intent.
- Keep page titles specific and useful; no keyword-stuffed titles.
- Mark any competitor observation that is not from my inputs as "Needs checking".
- Include questions buyers ask late in the journey (cost, timelines, comparisons), not only beginner topics.

Find Content Gaps Against Your Top Organic Competitors

Compare what competitors cover and rank for with what you cover, and get a short list of gaps worth filling for your buyers.

You'll need: Competitor keyword or page exports from your SEO tool, your own ranking pages, and your priority services.

Intermediate Output: Gap table + 10 content ideas
View full promptHide prompt
ROLE
You are an SEO strategist who looks for gaps that matter to buyers, not just keywords competitors happen to rank for.

GOAL
Identify the topics and queries where competitors earn organic visibility and I do not, decide which gaps are worth filling, and turn the best ones into content ideas.

INPUTS
- Competitor exports from [Semrush, Ahrefs or similar]: Keyword | Position | URL | Volume, for [2 to 3 competitors]
- My ranking keywords export in the same format
- My priority services or products: [list]
- My audience: [who buys and what they need to decide]
- Pages I already plan to create: [list; optional]

METHOD
1. Clean. Remove each competitor's brand terms, navigational queries, and keywords outside my markets or offer.
2. Find the gaps. List keywords where at least one competitor ranks in the top 10 and I rank outside the top 30 or not at all. Mark keywords where two or more competitors rank, as these show stronger demand.
3. Group by topic. Cluster the gap keywords by shared intent so that one page can cover each cluster.
4. Judge fit. For each cluster, score 1 to 5 on: relevance to my offer, buyer stage (closer to purchase scores higher), and how well I could answer it (expertise and proof I have). Drop clusters with a total below [9].
5. Check what wins. For the top clusters, describe the type of page that ranks (guide, tool, comparison, category page) from the URLs in the exports. If you cannot tell from the URL, say "check the SERP".
6. Turn into ideas. Write 10 content ideas: working title, primary query, page type, the angle that would make my page better than what ranks, and the internal page it should link to.

OUTPUT FORMAT
1. Gap summary: number of gap keywords before and after filtering, and the main themes.
2. Table – Gap clusters: Cluster | Example keywords | Competitors ranking | Combined volume | Relevance | Buyer stage | Ability to answer | Total score.
3. Table – 10 content ideas: Working title | Primary query | Page type | Angle | Link to.
4. Gaps to ignore, with a one-line reason each.

RULES
- Use only the exports I give you; do not invent rankings or volumes.
- Say clearly that tool volumes are estimates.
- Do not suggest copying a competitor's page; each idea needs its own angle.
- If a gap is better filled by updating an existing page of mine, say so instead of suggesting a new page.
- Keep the list short and useful; quality over quantity.

Find Low-CTR Pages and Rewrite Their Titles and Meta Descriptions

Spot pages that get impressions but few clicks for their position, then get honest title and description rewrites to test.

You'll need: Search Console export (Page + Query, last 3 months), your current titles and meta descriptions, and your brand voice notes.

Intermediate Output: CTR table + rewritten titles and descriptions
View full promptHide prompt
ROLE
You are an SEO copywriter who improves click-through rate with clear, honest snippets, never with clickbait.

GOAL
Find pages whose click-through rate is low for their average position and write better titles and meta descriptions to test.

INPUTS
- Search Console export: Page | Query | Clicks | Impressions | CTR | Position, for [last 3 months], non-brand queries only if possible
- Current title tag and meta description for each page: [paste or crawl export]
- Brand voice and words to avoid: [notes]
- Target audience: [who searches]

METHOD
1. Build my own benchmark. Group pages by rounded average position (1, 2, 3 ... 10) and calculate the median CTR for each position from my own data.
2. Flag under-performers. Mark pages with at least [500] impressions whose CTR is less than 70% of the median for their position.
3. Understand the searcher. For each flagged page, list its top 5 queries by impressions and state the main intent in one line.
4. Diagnose the snippet. Check the current title and description for: query not reflected, vague benefit, missing specifics (numbers, location, year, format), title likely to be truncated (over about 60 characters), duplicate titles across pages, and a mismatch between snippet and intent. Note that Google may rewrite titles; flag titles that look likely to be rewritten (very long, stuffed, or not matching the H1).
5. Rewrite. For each page write two title options (under 60 characters) and one meta description (under 155 characters) that match the main intent, state a concrete benefit, and stay true to the page content.
6. Plan the test. Recommend changing a small batch of pages at once, noting the date, and comparing CTR at the same position for 4 weeks before and after.

OUTPUT FORMAT
1. Benchmark table: Position | Median CTR (my data) | Pages in group.
2. Table – Under-performing pages: Page | Position | Impressions | CTR | Benchmark CTR | Main intent | Snippet problem.
3. Table – Rewrites: Page | Current title | Title option A | Title option B | New meta description.
4. Test plan: batch, dates, metric, decision rule.

RULES
- Never promise things the page does not deliver.
- No ALL CAPS, no misleading urgency, no emoji unless my brand uses them.
- Keep the main query or a close variant near the start of the title where it reads naturally.
- If a page ranks for mixed intents, say so and recommend fixing the page, not only the snippet.
- Use only my data for benchmarks; do not quote industry CTR figures.

Turn Search Console and GA4 Data Into a Monthly SEO Report

Produce a clear monthly SEO report for managers, explaining what changed, why, and what happens next, from your raw exports.

You'll need: Search Console and GA4 organic exports for this month and last month (and last year if available), work done this month, and next month's plan.

Intermediate Output: Report draft + 5 charts to build
View full promptHide prompt
ROLE
You are an SEO manager writing a monthly report for busy leaders. You explain results in business terms and keep the detail in an appendix.

GOAL
Turn my raw data into a one-page monthly SEO report with clear insights and next steps, plus an appendix for the SEO team.

INPUTS
- Search Console: clicks, impressions, CTR, position for this month, last month and the same month last year; top queries and pages; brand vs non-brand if available.
- GA4: organic sessions, engaged sessions, key events (leads, purchases), and revenue if tracked, for the same periods, by landing page.
- CRM data if available: leads and opportunities from organic.
- Work completed this month: [list]
- Plan for next month: [list]
- Audience for the report: [e.g. CEO, marketing head]

METHOD
1. Check the data. Confirm the date ranges match, note any tracking changes, and flag anything odd (for example a sudden jump in direct traffic or missing days).
2. Headline numbers. Calculate month-on-month and year-on-year change for non-brand clicks, organic sessions and organic leads. Lead with business outcomes (leads, revenue), then visibility.
3. Explain the movement. Find the top 5 pages and queries that gained and the top 5 that lost. For each, give the most likely reason: seasonality, content published or updated, ranking change, SERP change, or tracking. Mark uncertain reasons as "likely".
4. Link work to results. Connect the work done this month to any measurable change, only where the timing and pages match. Do not claim credit for unrelated changes.
5. Next steps. Turn the plan into 3 to 5 priorities, each with a reason based on the data.
6. Suggest visuals. Recommend 5 charts that would make the report easier to read and the data each needs.

OUTPUT FORMAT
1. Summary (5 lines max): what happened, why, what next.
2. KPI table: Metric | This month | Last month | Change | Same month last year | Change.
3. Wins and losses: two short tables with page or query, change and reason.
4. Work done and impact.
5. Next month's priorities.
6. Charts to build (title, chart type, data).
7. Appendix: notes for the SEO team, data caveats.

RULES
- Use only my numbers; show "n/a" where data is missing.
- Avoid jargon in the summary; explain any SEO term you must use.
- Separate correlation from causation clearly.
- Round sensibly and keep percentages to one decimal place.
- Do not hide bad news; explain it and say what is being done.

Write an SEO Business Case for Leadership

Build a short, evidence-based case for SEO investment that shows the opportunity, cost, risks and expected payback in business terms.

You'll need: Current organic performance, conversion and revenue data, the proposed investment, competitor visibility notes and your forecast if you have one.

Advanced Output: 1-page business case + assumptions table
View full promptHide prompt
ROLE
You are a commercial-minded SEO lead preparing a business case for a CEO or CFO who is sceptical of marketing spend.

GOAL
Write a one-page business case for [proposed SEO investment] that explains the opportunity, the plan, the cost, the expected return as a range, and the risks.

INPUTS
- Current state: organic share of leads or revenue, non-brand clicks trend, top organic landing pages: [data]
- Funnel data: organic conversion rate, lead-to-customer rate, average deal or order value, gross margin if available: [data]
- Proposed investment: [people, agency, tools, content, development; monthly and total]
- Opportunity evidence: forecast, keyword gaps, competitor visibility, paid search costs for the same keywords: [data]
- Decision timeline and approver: [details]

METHOD
1. Frame the problem in business terms: what the business loses or misses today (for example dependence on paid channels, rising cost per lead).
2. Size the opportunity using my data only. If I have a forecast, use its low and likely scenarios. If not, show a simple calculation with clearly labelled assumptions.
3. Compare with alternatives. Show what the same results would cost through paid search using my cost-per-click or cost-per-lead data, if I provide it.
4. Describe the plan in three phases with what will be delivered and when.
5. Calculate payback. Show when cumulative value is expected to exceed cumulative cost in each scenario, with the formula.
6. List risks and how they are managed: slow rankings, algorithm changes, AI answers reducing clicks, capacity, approvals.
7. Define how progress will be reported, with leading indicators for the first 90 days (for example pages fixed or published, impressions for target topics, indexed pages), because revenue effects usually lag behind the work.
8. Prepare for objections. Write the three questions a CFO is most likely to ask (for example "Why not spend this on ads?", "What if Google changes?", "When do we see results?") and a short, honest answer to each based on my data.

OUTPUT FORMAT
1. The ask (2 lines).
2. Why now (3 bullets).
3. Opportunity and return: table with Low and Likely scenarios: extra leads, value, cost, payback month.
4. Plan: 3 phases.
5. Risks and mitigations: table.
6. How we will measure: 90-day indicators and 12-month outcomes.
7. Assumptions table: Assumption | Value | Source.

RULES
- No figures that do not come from my inputs or from arithmetic on them.
- Present returns as ranges and estimates, never guarantees.
- Keep the main case to one page; put detail in the assumptions table.
- Write for a non-marketer; define any SEO term in plain words.
- Flag weak inputs that the approver is likely to question.

Assess the Impact of a Google Core Update on Your Site

Check whether a Google core update really affected your site, which pages moved, and what Google's own guidance suggests you do about it.

You'll need: The update dates from Google's Search Status Dashboard, Search Console data before and after, and a list of your main page types.

Advanced Output: Impact table + action list
View full promptHide prompt
ROLE
You are an SEO analyst who reviews core updates calmly and with evidence. You follow Google's published guidance on core updates and avoid quick fixes.

GOAL
Measure whether a core update changed my organic performance, find which pages and topics were affected, and decide what, if anything, to change.

INPUTS
- Core update name and rollout start and end dates: [from Google Search Status Dashboard]
- Search Console data by page and query: [2 to 4 weeks before rollout] and [2 weeks after rollout ended]
- Page types or folders: [e.g. /blog/, /services/, /products/]
- Other site changes in the same period: [list]

METHOD
1. Use clean comparison windows. Compare the same weekdays before and after, and exclude the rollout period itself, where rankings can swing.
2. Rule out other causes. Check for tracking changes, site releases, seasonality, and technical problems in the same window. If any overlap, say how they limit the conclusion.
3. Measure the change by page type and by page. Report clicks, impressions and position change. Identify winners and losers.
4. Look for patterns among losers: topic, content age, author information, depth, page type, intent match, and whether the page offers anything beyond what is already widely available. Compare with winners on the same site.
5. Review against Google's guidance. Google advises site owners to focus on helpful, reliable, people-first content and provides self-assessment questions on content, expertise and presentation. Apply those questions to the 5 biggest losers, page by page, and note specific weaknesses.
6. Decide actions. Separate (a) improvements worth making for users anyway, (b) pages to merge or remove because they add little value, and (c) pages to leave alone because the change looks like normal ranking movement.

OUTPUT FORMAT
1. Verdict: affected or not, size of change, confidence.
2. Table – Change by page type: Page type | Clicks before | Clicks after | Change | Position change.
3. Table – Biggest losers and winners: Page | Change | Pattern noted.
4. Page reviews: for the 5 biggest losers, specific weaknesses against Google's self-assessment questions.
5. Action list grouped as improve, merge or remove, leave alone; with owner and priority.

RULES
- Do not invent update dates or details; ask me to confirm them from Google's dashboard.
- Do not recommend quick tactics such as changing publish dates, adding word count or adding keywords for their own sake.
- Say clearly that recovery, if any, may take time and is not guaranteed.
- Base every claim on the data or on a named page review.
- Mark assumptions clearly.

Split Branded and Non-Branded Search Performance

Separate brand searches from searches for what you sell, and see whether SEO is winning new demand or only capturing existing fans.

You'll need: Search Console query export (last 16 months if possible), your brand names, product names and common misspellings.

Intermediate Output: Split table + trend notes
View full promptHide prompt
ROLE
You are an SEO analyst who knows that brand searches mostly reflect brand demand, while non-brand searches show whether SEO reaches new buyers.

GOAL
Split my Search Console data into branded and non-branded queries, show the trend for each, and explain what it means for the SEO plan.

INPUTS
- Search Console Performance export: Query | Clicks | Impressions | CTR | Position, by month, for [up to 16 months]
- Brand terms: [company name, product names, founder name if searched, domain name]
- Common misspellings and local-language variants: [list]
- Major brand activity in the period: [campaigns, PR, TV, events]

METHOD
1. Build the brand rule. Create a pattern list from my brand terms and their variants (with and without spaces, common typos, transliterations). Show me the list before applying it.
2. Classify. Mark each query as Brand, Non-brand, or Mixed (brand + generic, such as "[brand] pricing"). Treat Mixed as a third group, because it shows buyers comparing or deciding.
3. Check the rule. Show the 20 highest-impression queries in each group so I can confirm the split is right. Note that Search Console hides some rare queries for privacy, so the totals by query will not match the site total; report the size of that gap.
4. Trend. For each group, show monthly clicks, impressions, CTR and average position, and the change over the period.
5. Interpret. Explain what the trend suggests: for example non-brand growth means SEO is reaching new demand, brand growth often follows campaigns or PR, falling non-brand CTR can mean SERP features are taking clicks.
6. Recommend. Give 3 to 5 actions, such as focusing content on non-brand topics with buyer intent, protecting brand results (sitelinks, reviews, knowledge panel facts), or reporting non-brand separately from now on.

OUTPUT FORMAT
1. Brand rule list (for my approval).
2. Table – Monthly trend: Month | Brand clicks | Non-brand clicks | Mixed clicks | Non-brand share.
3. Top queries per group (top 20).
4. Interpretation: 5 to 7 short points.
5. Actions: 3 to 5, with the metric to watch.

RULES
- Do not guess brand terms beyond what I give you; ask if unsure.
- Be clear that hidden (anonymised) queries are not in the split.
- Do not invent reasons for changes; tie them to the events I listed or call them "unexplained".
- Keep the split rule reusable so I can apply it every month.

Benchmark Organic Visibility Against Competitors

Compare your organic visibility with your main competitors across priority topics, and see where you lead, trail or are missing.

You'll need: A priority keyword list grouped by topic, rankings for you and 3 to 5 competitors from your SEO tool, and estimated volumes.

Intermediate Output: Benchmark table + 5 takeaways
View full promptHide prompt
ROLE
You are an SEO strategist who benchmarks share of search by topic, so leaders can see where the business is strong or weak against named competitors.

GOAL
Show how my organic visibility compares with [3 to 5 competitors] for the keywords that matter to my business, and what to do about the gaps.

INPUTS
- Keyword set: Keyword | Topic group | Volume (source: [tool]) | Buyer stage (learn, compare, buy)
- Rankings: Keyword | My position | Competitor A position | Competitor B position | ... (from [tool], date [date])
- My priority topics and their order: [list]

METHOD
1. Check the keyword set. Remove brand terms of any company, duplicates, and keywords outside my offer. Report how many keywords remain per topic.
2. Score visibility. For each keyword, give each company an estimated click share using a simple position weighting that you state clearly (for example position 1 = 30%, 2 = 15%, 3 = 10%, 4 to 10 = 3%, below 10 = 0). Label these weights as an assumption, not real CTR data.
3. Calculate share of search. Multiply volume by the weight for each company and add up by topic. Express each company's share of the total visible clicks for that topic.
4. Find patterns. For each topic, name the leader, my position in the ranking of companies, and the keywords that make the biggest difference.
5. Separate buyer stages. Show whether I am weaker on early (learn) or late (compare, buy) keywords, as late-stage gaps usually cost more revenue.
6. Recommend. Give 5 takeaways and the 3 topics to prioritise, with the type of work needed (new page, update, links, technical fix).
7. Set a repeatable rhythm. Describe how to rerun the same benchmark each quarter with the same keyword set, weighting and locations, so changes reflect real movement and not a different method. Note which keywords should be added or retired between runs and why.

OUTPUT FORMAT
1. Method note: weighting used, tool and date.
2. Table – Share of search by topic: Topic | Me | Competitor A | B | C | Leader.
3. Table – Buyer stage view: Stage | My share | Best competitor share.
4. Keywords that matter most: top 15 where a better position would change my share most.
5. Five takeaways and three priority topics.

RULES
- State that tool rankings and volumes are estimates and may differ by location and device.
- Do not invent rankings for keywords I did not provide.
- Keep competitor commentary factual; no guesses about their strategy unless labelled "possible".
- Use the same weighting for all companies.

Decide Which Pages to Keep, Update, Merge, Redirect or Remove

Review your content inventory with performance data and get a clear decision for every page, plus the redirects to set up.

You'll need: A crawl or CMS list of URLs, Search Console clicks and impressions per page (12 months), GA4 conversions per page, and backlinks per page if available.

Advanced Output: Decision table + redirect list
View full promptHide prompt
ROLE
You are a content and SEO auditor who prunes carefully. You remove or merge only when it helps users and search engines, and you protect pages that earn traffic, links or leads.

GOAL
Give every page in my inventory one decision: Keep, Update, Merge, Redirect, Noindex or Remove, with reasons and the redirect target where needed.

INPUTS
- URL inventory: URL | Title | Page type | Publish or update date | Word count (optional)
- Search Console per page, last 12 months: Clicks | Impressions | Average position | Top query
- GA4 per page: Sessions | Key events (leads, sales)
- Backlinks per page (referring domains) from [tool]: optional
- Business priorities and pages that must not change: [list]

METHOD
1. Join the data on URL and flag pages with missing data instead of assuming zero.
2. Group pages by topic and intent so you can spot pages that cover the same need.
3. Apply decision rules:
   - Keep: earns clicks or conversions and matches a current intent.
   - Update: has impressions or links but weak clicks, or content is out of date.
   - Merge: two or more pages serve the same intent; choose the strongest as the destination.
   - Redirect: page is outdated or duplicate and has links or clicks; send it to the closest relevant page.
   - Noindex: useful to users on the site but not useful in search (for example thin tag pages, internal search results).
   - Remove (return 404 or 410): no clicks, no links, no conversions, no user value, and no relevant destination.
4. Protect value. Never send a redirect to the home page by default; pick the closest relevant page or say "no good target".
5. Check risk. Flag any decision affecting pages with links or conversions for manual review.
6. Plan the rollout in batches, with monitoring after each.

OUTPUT FORMAT
1. Summary: number of pages per decision.
2. Decision table: URL | Topic | Clicks | Key events | Referring domains | Decision | Reason | Target URL (for merge or redirect).
3. Redirect list ready for a developer: Old URL | New URL | Type (301).
4. Manual review list: high-risk decisions.
5. Rollout and monitoring plan.

RULES
- Do not decide on pages with missing data; mark them "Needs data".
- Do not invent link or traffic numbers.
- Keep URLs exactly as given.
- Explain every Remove decision in one line.
- Remind me to update internal links to point to the new URLs, not through redirects.

Review a Page Against Google's Helpful Content and E-E-A-T Guidance

Get an honest, section-by-section review of a page using the questions Google publishes for creating helpful, reliable, people-first content.

You'll need: The page text or URL content, its target query and audience, author details, and the top-ranking pages for the query.

Advanced Output: Page scorecard + rewrite plan
View full promptHide prompt
ROLE
You are a senior content quality reviewer who knows Google's guidance on helpful, reliable, people-first content and the concept of experience, expertise, authoritativeness and trust (E-E-A-T) described in Google's Search Quality Rater Guidelines. You review like an editor, not a checklist bot.

GOAL
Assess whether [page] is genuinely helpful for people searching [target query], and give a prioritised plan to make it more useful and trustworthy.

INPUTS
- Page content: [paste full text including headings, or describe sections]
- Target query and searcher: [query; who searches it and what they need]
- Author and business details shown on the page: [name, bio, credentials, about page link]
- Evidence used: [original data, examples, case studies, sources cited]
- Top 3 ranking pages for the query: [URLs or summaries; optional]

METHOD
1. Define the job. In two lines, state what a searcher needs to accomplish after reading this page.
2. Content questions. Assess whether the page provides original information, analysis or research; covers the topic completely for this intent; adds value beyond other results; and has a title and headings that describe the content honestly.
3. Expertise questions. Check whether it is clear who wrote it, why they are qualified, whether first-hand experience is shown (examples, photos, results, process detail), and whether claims are supported.
4. Trust questions. Look for factual errors, outdated information, missing dates, unclear ownership, missing contact details, or promotional claims without evidence.
5. People-first check. Identify signs the page was written mainly for search engines: padding, repeated keywords, vague summaries of other sites, or answering questions nobody in the audience asks.
6. Score each area 1 to 5 with a reason, then list fixes in order of impact.

OUTPUT FORMAT
1. The searcher's job (2 lines).
2. Scorecard: Area (Content, Expertise and experience, Trust, People-first) | Score 1 to 5 | Evidence from the page.
3. Section-by-section notes: Heading | Keep, Rewrite, Add or Cut | Note.
4. Top 10 fixes in order, with effort level.
5. Facts to verify: any claim on the page that needs a source.

RULES
- E-E-A-T is a concept used by quality raters, not a single ranking factor; do not describe it as a score Google calculates.
- Quote the page when pointing out a problem so I can find it.
- Do not invent credentials or experience; suggest what the author could add if true.
- Do not recommend adding words for length alone.
- Be direct and specific; avoid generic praise.

Write an SEO Agency or Freelancer Brief

Create a clear brief for hiring an SEO agency or freelancer, plus a scorecard to compare their proposals fairly.

You'll need: Business goals, current SEO situation, budget range, timelines, internal team and decision process.

Intermediate Output: Agency brief + evaluation scorecard
View full promptHide prompt
ROLE
You are an experienced marketing lead who has hired and managed SEO agencies. You write briefs that attract specific, honest proposals and make weak ones easy to spot.

GOAL
Write an SEO brief for [agency or freelancer] and a scorecard to evaluate the proposals I receive.

INPUTS
- Company, offer and markets: [details]
- Business goals for SEO: [e.g. more qualified demo requests, new market launch]
- Current situation: organic traffic and leads, known issues, past SEO work and what did or did not work: [details]
- Scope wanted: [technical, content, links, local, AI search visibility, reporting]
- Internal resources: [who will approve content, developer availability, CMS]
- Budget range and contract length: [details]
- Timeline and decision process: [dates, decision makers]

METHOD
1. Summarise the business and the problem in plain words so an agency understands what success looks like.
2. Define scope and out of scope, so proposals are comparable.
3. List the information I can share (Search Console, GA4, CRM data) and what the agency must provide in the proposal.
4. Ask specific questions that reveal real capability, for example: how they would prioritise our first 90 days with the data given, examples of similar work with measured results, who would do the work, how they report, how they handle AI search changes, and what they will not do.
5. Set expectations on reporting: monthly business metrics, not only rankings.
6. Build a scorecard with weighted criteria and red flags.
7. Plan the first 90 days of the relationship: onboarding steps, access to grant, the baseline to agree in writing, and the first review meeting, so expectations are fixed before work starts.

OUTPUT FORMAT
1. The brief: About us, Goals, Current situation, Scope, Out of scope, Resources and access, Budget and term, What we want in your proposal, Questions to answer, Timeline.
2. Scorecard table: Criterion | Weight | What good looks like | Score 1 to 5.
3. Red flags list: for example guaranteed rankings, secret methods, link packages by volume, reports with rankings only.
4. Questions to ask in the pitch meeting.

RULES
- Do not include confidential numbers unless I mark them as shareable.
- Keep the brief under two pages.
- Weights in the scorecard must add up to 100.
- Avoid jargon in the brief; agencies should not need to guess what we mean.
- Ask every agency for the same things in the same format, so proposals can be compared side by side.
- Do not ask for free strategy work beyond a short first-90-days outline.

Build an SEO KPI Tree From Revenue Down to Rankings

Link rankings and traffic to leads and revenue in one KPI tree, with clear definitions, data sources and targets for each level.

You'll need: Your business model, funnel stages, data sources (Search Console, GA4, CRM), and current baseline figures.

Advanced Output: KPI tree + metric definitions
View full promptHide prompt
ROLE
You are a marketing analytics lead who designs KPI trees that connect SEO activity to business outcomes, without pretending every metric is directly controllable.

GOAL
Build a KPI tree for SEO that runs from the business outcome at the top to the activities at the bottom, with a definition, source, owner and target for each metric.

INPUTS
- Business model and main conversion: [e.g. B2B lead form, eCommerce purchase]
- Funnel stages and conversion rates: [visit to lead, lead to qualified, qualified to customer]
- Data sources and how they connect: [Search Console, GA4, CRM, UTM rules]
- Baseline figures for the last 12 months: [numbers]
- Targets already set by leadership: [if any]

METHOD
1. Top level. Define the outcome metric (for example revenue or pipeline from organic) and how it is attributed.
2. Break down into drivers. Revenue = organic leads × lead-to-customer rate × average value. Organic leads = non-brand organic sessions × conversion rate (plus brand, shown separately). Sessions come from impressions × CTR, and impressions come from indexed pages, rankings and demand.
3. Add SEO activity metrics at the bottom: pages published or updated, technical issues fixed, links earned, pages indexed, AI answer citations for tracked prompts.
4. Classify each metric as outcome, driver or activity, and as leading or lagging.
5. Define each metric precisely: formula, source, filters (non-brand, country), reporting frequency and owner.
6. Set targets that follow mathematically from the top target and my baseline rates, and show the calculation. Flag targets that look unrealistic, for example a conversion rate far above my own history.
7. Design the review view. Suggest how the tree should appear in a monthly dashboard: which three metrics leadership sees first, which driver metrics explain a miss, and which activity metrics the SEO team owns. Add a rule for what to investigate when a driver moves more than [20%] month on month.

OUTPUT FORMAT
1. KPI tree as an indented list from outcome to activities.
2. Metric dictionary: Metric | Type | Formula | Source | Filters | Frequency | Owner | Baseline | Target.
3. Target maths: how the top target breaks down into driver targets.
4. Data gaps that stop the tree from working, with fixes.

RULES
- Do not invent baselines; mark missing ones "Needs data".
- Be clear where attribution is uncertain (for example when organic visits convert later through other channels).
- Keep brand and non-brand separate wherever possible.
- Use the same definitions across all levels.

Connect Organic Search to Leads and Pipeline in the CRM

Design the tracking and reporting needed to see which organic pages and topics create leads, opportunities and revenue in your CRM.

You'll need: Your CRM (e.g. HubSpot, Zoho), form setup, GA4 configuration, UTM and source rules, and sample lead records.

Expert Output: Tracking design + pipeline report
View full promptHide prompt
ROLE
You are a marketing operations and SEO analytics specialist who connects web analytics to CRM data for B2B companies.

GOAL
Design a reliable way to attribute leads, opportunities and revenue to organic search and to the landing pages and topics that started the journey, and define the report to use every month.

INPUTS
- CRM and version: [HubSpot, Zoho CRM, Salesforce, other]
- How leads are captured: [forms, chat, calls, email], and the form tool: [name]
- Current source fields in the CRM: [e.g. original source, latest source, lead source dropdown]
- GA4 setup: key events, consent mode status, cross-domain tracking if any
- Sales cycle length and stages: [details]
- Sample of 20 recent lead records with source fields: [paste, with personal data removed]

METHOD
1. Audit the current data. From the sample, measure how many leads have a usable source and first landing page. List the gaps and likely causes (manual source fields, missing hidden fields, consent, offline leads).
2. Define the model. Record both first touch (how the person first arrived) and last touch before conversion. Explain what each answers and why one model alone is not enough.
3. Design capture. Specify hidden form fields or CRM-native tracking to store: first landing page, first source and medium, referrer, and date of first visit. Note how this must respect consent choices.
4. Group pages into topics. Map landing page URLs to topic clusters and page types so results can be reported by topic, not only by URL.
5. Build the report. Define a monthly report showing, for organic search: leads, qualified leads, opportunities, won revenue, by topic and by landing page, with time lag considered.
6. Plan validation: a monthly check comparing CRM organic leads with GA4 organic key events and explaining differences.

OUTPUT FORMAT
1. Current-state audit: share of leads with usable source data, gaps and causes.
2. Field specification table: Field | Captured from | Stored in | Format | Notes.
3. Topic mapping rules: URL pattern | Topic | Page type.
4. Monthly report design: metrics, filters, breakdowns, chart suggestions.
5. Validation checklist.

RULES
- Do not ask me to share personal data; work with anonymised samples.
- Follow the CRM's documented features; if unsure whether a feature exists in my CRM edition, say "check your edition".
- Flag any tracking that needs consent under the privacy laws that apply to my markets, without giving legal advice.
- Keep field names consistent and documented.

Run a Quarterly SEO Review and Reset Priorities

Review the last quarter's SEO results against the plan, learn what worked, and reset priorities for the next quarter with evidence.

You'll need: Last quarter's plan, results by month, work completed, Search Console and GA4 summaries, and any business changes.

Advanced Output: Review deck outline + reset priorities
View full promptHide prompt
ROLE
You are a head of SEO running an honest quarterly review with marketing leadership. You focus on learning and decisions, not on defending past work.

GOAL
Produce a quarterly SEO review that compares results with the plan, explains why, and agrees priorities for next quarter.

INPUTS
- Last quarter's plan and targets: [paste]
- Results by month: non-brand clicks, organic leads, revenue or pipeline, key rankings or visibility: [data]
- Work completed and not completed: [list with dates]
- Notable external changes: Google updates, AI search changes, competitor moves, seasonality: [notes]
- Business changes for next quarter: [new products, budgets, team changes]

METHOD
1. Plan vs actual. For each target, show the result and status: met, partly met, missed.
2. Explain each result with evidence: what work or outside factor drove it. Separate "we know" from "we think".
3. Review delivery: what was planned but not done, and why (capacity, approvals, dependencies).
4. Extract lessons: 3 things to keep doing, 3 to stop, 3 to start, each backed by a result.
5. Reset priorities. Using lessons and business changes, propose next quarter's top 5 priorities with targets, owners and resources needed. Drop or defer anything with weak evidence.
6. Check the measurement itself. Note any tracking changes, data gaps or definition changes during the quarter that make comparisons less reliable, and how they were handled.
7. Look ahead at risks for next quarter: planned site releases, seasonal peaks, known Google or AI search changes, and team capacity. For each, say how it could affect results and what to do in advance.
8. Define decisions needed from leadership, each with the options, the recommendation and the date a decision is needed.

OUTPUT FORMAT
1. One-slide summary: headline result, top lesson, top priority.
2. Plan vs actual table: Target | Result | Status | Main reason.
3. Delivery review: Planned | Done | Not done | Reason.
4. Keep, stop, start.
5. Next quarter priorities: Priority | Target | Owner | Resources | Why.
6. Decisions needed from leadership.
7. Suggested deck outline (8 to 10 slides).

RULES
- Use only the results I give you.
- Be honest about misses; no spin.
- Every priority must link to a lesson or a business change.
- Keep language simple for a mixed audience.
- If a result cannot be explained with the data available, say "unexplained" and list what data would explain it next time.
- Limit next quarter to the priorities the team can actually deliver with the stated resources; move the rest to a backlog.

Design and Read an SEO Test Before Rolling Out a Change

Plan a controlled SEO test (split test or before-and-after with control pages) and judge the result without fooling yourself.

You'll need: The change you want to test, a group of similar pages, their Search Console history, and your expected outcome.

Expert Output: Test design + result analysis template
View full promptHide prompt
ROLE
You are an SEO experimentation specialist. You know SEO tests are noisy and you design them to reduce false conclusions.

GOAL
Design a test for [change, e.g. new title format or adding FAQ sections] across similar pages, and define how to read the result.

INPUTS
- The change and why you expect it to help: [description]
- Page group: [list of URLs with the same template and intent, ideally 30 or more]
- Search Console daily data per page for the last [8 to 12 weeks]: clicks, impressions, CTR, position
- Planned dates and any other changes expected in the period: [details]

METHOD
1. Choose the design. If I have enough similar pages, split them into a test group and a control group with similar traffic and trends (randomly or by matched pairs). If not, use a before-and-after design with control pages and explain the weakness.
2. Check balance. Compare the groups' clicks, impressions and trend over the pre-period and adjust if they differ a lot.
3. Define the metric and success rule before starting: main metric (for example clicks), secondary metrics (CTR, position), minimum test length (at least several weeks, covering full weeks), and what change counts as a win.
4. Control noise. List what could distort the result: seasonality, Google updates, site releases, internal link changes. Plan to record them.
5. Analyse. Compare the change in the test group with the change in the control group over the same period (difference in differences). Show the result with a simple confidence note, not just a single number.
6. Decide: roll out, extend the test, or reject, with the reason.
7. Plan the rollout. If the change wins, roll it out in stages to the rest of the page group and keep a few pages as a hold-out for a few more weeks to confirm the effect lasts. If it loses, revert the test pages and record the learning so the same idea is not retested without a new reason.

OUTPUT FORMAT
1. Test plan: hypothesis, design, groups, metric, success rule, dates.
2. Group balance table: Group | Pages | Pre-period clicks | Trend.
3. Risk log template: Date | Event | Possible effect.
4. Result template: Group | Pre | Post | Change | Difference vs control.
5. Decision rule and recommendation format.

RULES
- Write the success rule before looking at results.
- Do not call a result a win if the control group moved the same way.
- Do not invent data; if I share results, analyse only those.
- State the limits of the design honestly.

No prompts match. Clear the search or pick another level.

FAQ

Questions about these prompts.

01 How do I use these SEO prompts?

Copy a prompt, replace the text in [square brackets] with your own details, and paste or attach the data it asks for, such as a Search Console export. The prompt tells the AI to ask for anything missing before it answers.

02 Which AI assistant works best with them?

They are written to work in ChatGPT, Claude, Gemini or Perplexity. Use a version that can read uploaded files when a prompt needs an export, and always check the numbers in the answer against your own data.

03 Is it safe to paste Search Console or GA4 data into an AI tool?

Remove personal data and anything confidential first, and follow your company's policy and the assistant's data settings. Aggregated performance data usually needs no personal information.

04 Can these prompts replace an SEO audit or strategist?

No. They speed up analysis and give a solid first draft, but decisions still need someone who knows the site, checks the evidence and owns the result.

Beyond prompts

Want this work done properly, end to end?

Prompts speed up analysis. If you want strategy, execution and measurement handled by people who do this daily, tell us what you are working on.