Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO & SEO Audits

AI can speed up SEO research synthesis, briefing, drafting, technical triage, and reporting—but only when you supply real context and verify the output. Prompts are reusable instructions, not a substitute for keyword tools, crawlers, analytics, or experienced judgment. If you skip context, models fill gaps with fluent guesses that look like research.

This library gives you 110+ practical SEO prompts for strategy, keyword research, intent, topic clusters, content, on-page SEO, internal linking, technical SEO, audits, local SEO, ecommerce SEO, and reporting. Each prompt includes when to use it, what context to provide, a copy-ready instruction block, what good output looks like, and how to validate results before anything reaches production.

Think of prompts as process accelerators inside a human-led SEO system. They help you turn messy exports into cluster sheets, turn cluster sheets into briefs, turn briefs into drafts, and turn crawl notes into developer tickets. They do not “know” your rankings, your crawl budget, or your customers unless you paste evidence.

That distinction matters for people-first SEO. Assistants are good at structuring ambiguous notes, proposing outlines, rewriting for clarity, and listing verification questions. They are weak at inventing trustworthy metrics, judging legal risk without your rules, and deciding which tradeoffs your business should accept. Keep those decisions human.

These prompts work with general assistants such as ChatGPT, Claude, or Gemini. No model is a Google ranking factor, and none replaces people-first editorial standards. Quality still depends on expertise you inject: product specifics, original examples, compliance limits, and honest measurement. For broader AI-assisted search work, see AI SEO expertise and pair prompts with a clear SEO strategy.

Use this page as a working library. Bookmark the categories you touch weekly, keep a saved “context pack” (brand rules, ICP notes, URL inventory, and current goals), and refuse any output that invents volumes, traffic, rankings, reviews, or crawl findings you did not provide. When a prompt asks for missing information, that is a feature—not a failure of the model.

How to Use AI Prompts for SEO Effectively

Paste tool exports, crawl findings, SERP notes, brand rules, and product facts into the prompt. Instruct the model not to invent volumes, rankings, traffic, or crawl results. Ask it to state assumptions, separate observations from recommendations, and request missing data. Those four rules appear inside every prompt block below for a reason: they reduce confident nonsense.

Use AI to structure thinking and first drafts. Use your SEO stack to measure. Use humans to decide what is true, distinctive, and safe to publish. Avoid scaled low-value pages created mainly to manipulate rankings—Google’s people-first guidance still applies whether a human or an assistant typed the sentences. Speed is useful; spam at scale is not a growth plan.

A practical setup that works for most teams:

• Keep a living context pack: ICP, offers, claim limits, glossary, and priority products.
• Export only the columns you need from keyword, analytics, and crawl tools—then paste cleaned subsets.
• Save SERP notes as short bullet evidence (page types, unique sections, gaps)—not as invented “SERP scores.”
• Require [SOURCE NEEDED] markers for factual claims before legal or SME review.
• Ship through CMS with a human approval gate for originality, accuracy, and internal links.
• Measure in Search Console and analytics; feed outcomes back into refresh and reporting prompts.

If you are building durable topical coverage, connect this library to how you build topic clusters for AI search citation readiness and your ongoing content SEO process. Clusters and prompts work best together: prompts create artifacts; clusters keep those artifacts from colliding.

Also decide what “good enough for staging” means before you start. A cluster sheet is done when primaries do not conflict and intent confidence is labeled. A brief is done when sources and open questions are explicit. A draft is done when claims are sourced or marked. A technical ticket is done when acceptance criteria are testable. Prompts accelerate each artifact; standards decide when the artifact moves forward.

One more operating habit: version your context pack. When brand rules, ICP notes, or offer constraints change, update the pack before the next prompt run. Stale context is a common reason assistants produce on-brand-sounding copy that product and legal later reject. Fresh context beats clever prompting.

The table below maps common SEO tasks to prompt categories and the verification a human still owes the work.

SEO Task	Prompt Category	Human Verification Needed
Strategy and prioritization	SEO Strategy	Business goals, capacity, and legal constraints
Keyword clustering and gaps	Keyword Research	Volumes, difficulty, and live SERPs from tools
Intent labeling and page type	Search Intent	SERP sampling and funnel fit
Hub-and-spoke planning	Topic Clusters	Inventory conflicts and SME coverage
Briefs and drafts	SEO Content Writing	Facts, originality, and brand voice
Titles, headings, trust cues	On-Page SEO	Live templates and CTR in Search Console
Contextual links and orphans	Internal Linking	URL existence, relevance, and crawl discovery
Crawl and indexation triage	Technical SEO	Crawler, staging, and Search Console confirmation
Scoped findings and remediation	SEO Audits	Evidence attachments and re-checks after fixes
GBP and location pages	Local SEO	Real NAP, reviews policy, and service capacity
Categories, PDPs, facets	Ecommerce SEO	Catalog truth (price, stock, specs)
Monthly narratives and tests	Reporting and Analysis	Source exports and attribution limits

AI Prompts for SEO Strategy — Prompts 1–10

Start with strategy prompts when stakeholders need clarity on goals, prioritization, ICP mapping, risk, and measurement—before generating more pages. Strong strategy inputs make every later prompt more accurate because writers and developers inherit constraints instead of inventing them.

These prompts help you turn vague “we need more traffic” requests into measurable objectives, sequenced roadmaps, and honest measurement plans. They will not invent baselines or guarantee outcomes. Align outputs with your search visibility priorities and capacity reality.

Use this section at quarter planning, when a new product launches, or when leadership asks for an SEO narrative that stays evidence-based. If strategy is unclear, skip ahead only after you can state the primary conversion and what you will not chase this quarter.

Prompt 1: Clarify Business SEO Goals

Use this when:
You need to turn vague growth goals into measurable SEO objectives without inventing targets.

Provide this context:

• Business model and primary conversion
• Current known constraints (budget, team, tech stack)
• Any existing KPI definitions from stakeholders
• Markets and languages in scope

Prompt:

You are an experienced SEO professional.
Translate the business context below into an SEO goal framework.
Return: primary SEO objective, supporting objectives, leading vs lagging indicators (only if data sources are named), risks, and open questions.
If stakeholders did not define a number, propose a measurement approach—not a fabricated target.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
A goal framework with clear objectives, measurement sources, assumptions, and questions—not invented KPI numbers.

Validate by:
Confirm each metric has a real data source (GSC, analytics, CRM). Reject any invented baseline or target.

Prompt 2: Prioritize SEO Initiatives by Impact and Effort

Use this when:
You have a backlog of SEO ideas and need a transparent prioritization matrix.

Provide this context:

• List of proposed initiatives
• Known resource constraints
• Any historical results you can cite
• Business priorities for the quarter

Prompt:

You are an experienced SEO professional.
Prioritize the SEO initiatives listed below using Impact, Effort, Confidence, and Risk.
Do not invent past results. If impact is unknown, say so and list what evidence would raise confidence.
Output a ranked table with rationale and recommended sequencing.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Ranked initiative list with explicit confidence notes and missing-evidence flags.

Validate by:
Spot-check that high-impact claims are backed by your data or marked as hypotheses.

Prompt 3: Define SEO ICP and Buyer Journey Mapping

Use this when:
You are planning content and landing pages for specific buyer personas.

Provide this context:

• Ideal customer profile notes
• Sales cycle stages
• Known objections and product claims you can support
• Existing page inventory (URLs/titles)

Prompt:

You are an experienced SEO professional.
Map SEO content opportunities to ICP stages using only the notes provided.
For each stage: jobs-to-be-done, likely query themes, page types, and proof needed.
Do not invent market sizes or search volumes.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Stage-by-stage map of themes, page types, and proof requirements tied to supplied ICP notes.

Validate by:
Have sales/CS review that objections and proof points match real conversations.

Prompt 4: Competitive SEO Positioning Brief

Use this when:
You collected competitor notes and need a differentiation brief for SEO content.

Provide this context:

• Your product differentiators
• Competitor page notes you collected
• Claims you are legally allowed to make
• Any tool exports you want compared (paste them)

Prompt:

You are an experienced SEO professional.
Create a competitive SEO positioning brief from my notes.
Do not invent competitor traffic, backlinks, or rankings.
Call out where competitor claims need verification.
Recommend angles we can uniquely own based on supplied differentiators.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Positioning summary, avoid-list of unsupported claims, and content angles grounded in your notes.

Validate by:
Verify competitor claims on their live pages; discard any metric the model added without your export.

Prompt 5: SEO Opportunity Scoring Rubric

Use this when:
You want a reusable rubric to score keyword or page opportunities consistently.

Provide this context:

• Business priorities
• Available data columns from your tools
• Risk tolerances (YMYL, brand, legal)
• Example opportunities to score

Prompt:

You are an experienced SEO professional.
Design an SEO opportunity scoring rubric using only the data columns I can supply.
Define each criterion, weight ranges, and how to handle missing data.
Score the examples I provide without inventing missing metrics.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Documented rubric plus scored examples with missing-data handling.

Validate by:
Apply the rubric manually to 3 items and confirm scores match your judgment.

Prompt 6: Quarterly SEO Roadmap Outline

Use this when:
You need a realistic quarterly roadmap from known capacity and priorities.

Provide this context:

• Team capacity estimates
• Prioritized initiatives
• Dependencies (dev, design, legal)
• Known seasonal or launch dates

Prompt:

You are an experienced SEO professional.
Draft a quarterly SEO roadmap outline from the inputs below.
Sequence work by dependencies and capacity.
Do not promise ranking or traffic outcomes.
Flag risks and decision points that need stakeholders.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Month-by-month workplan with owners placeholders, dependencies, and risk flags.

Validate by:
Confirm capacity assumptions with the team; remove any outcome guarantees if present.

Prompt 7: SEO Risk and Compliance Checklist

Use this when:
You operate in a regulated or sensitive niche and need SEO guardrails.

Provide this context:

• Industry and claim restrictions
• Brand voice and legal review rules
• Examples of past rejected copy
• YMYL considerations if applicable

Prompt:

You are an experienced SEO professional.
Build an SEO content and optimization risk checklist for this niche.
Include claim types that require sources, disclaimer needs, and review gates.
Do not invent legal requirements—flag where counsel must confirm.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Checklist of risk gates, claim types, and review owners with counsel-confirm flags.

Validate by:
Have legal/compliance review the checklist before using it as policy.

Prompt 8: Channel Mix: SEO vs Paid vs Social Roles

Use this when:
Stakeholders blur SEO with paid/social and you need role clarity.

Provide this context:

• Current channel mix notes
• Budget ownership
• Conversion definitions
• Shared landing page inventory

Prompt:

You are an experienced SEO professional.
Clarify how SEO should complement paid and social using the notes below.
Define shared assets, handoffs, and metrics ownership.
Do not invent attribution percentages unless provided.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
RACI-style channel roles, shared asset rules, and measurement ownership.

Validate by:
Align with marketing ops on attribution definitions before publishing the doc.

Prompt 9: Build an SEO Measurement Plan

Use this when:
You need a measurement plan that ties SEO work to analytics without fake baselines.

Provide this context:

• Analytics and GSC access notes
• Conversion events available
• Reporting cadence
• Known tracking gaps

Prompt:

You are an experienced SEO professional.
Create an SEO measurement plan from the tracking notes below.
List primary metrics, supporting diagnostics, and known gaps.
If a metric cannot be measured today, say so and propose instrumentation—not invented numbers.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Metric dictionary, dashboards/cadence, and instrumentation backlog.

Validate by:
Verify each metric exists in your tools; open tickets for gaps.

Prompt 10: Stakeholder SEO Narrative Deck Outline

Use this when:
You need an executive-friendly narrative without overselling AI or rankings.

Provide this context:

• Audience (exec, product, sales)
• Known results and open risks
• Next-quarter asks
• Data tables you will paste

Prompt:

You are an experienced SEO professional.
Outline a stakeholder SEO narrative deck.
Use only facts from my notes/tables.
Separate what happened, why we think it happened (hypothesis), and what we propose next.
No ranking guarantees.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Slide outline with evidence slots, hypothesis labels, and clear asks.

Validate by:
Fill slides only with verified numbers; remove speculative causal language.

AI Prompts for Keyword Research — Prompts 11–25

Keyword prompts help you expand seeds, cluster exports, spot cannibalization, interpret difficulty cautiously, and prepare brief inputs. Always paste tool data for volumes and difficulty. AI should organize, label, and question—not fabricate demand metrics or SERP features.

A healthy keyword workflow is export → clean → cluster → validate in SERPs → brief. Prompts sit in the middle of that chain. If a term is strategically important but shows low or zero volume, use the dedicated prompt to decide with customer-language evidence rather than inventing a volume number.

Before you brief writers, run the QA checklist prompt so cluster sheets do not quietly contain conflicting primaries or missing intent notes. Treat difficulty scores as one input among many, not a verdict.

Prompt 11: Seed Keyword Expansion From Product Notes

Use this when:
You have product/service notes and need seed themes before tool research.

Provide this context:

• Product features and use cases
• Audience language from sales/CS
• Competitors you care about
• Markets/locales

Prompt:

You are an experienced SEO professional.
Generate seed keyword themes and example queries from the product notes below.
Do not invent search volumes or difficulty.
Group by job-to-be-done and flag terms that need tool verification.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Theme clusters with example queries and verification flags—no fabricated metrics.

Validate by:
Run seeds through your keyword tool and discard irrelevant or zero-demand terms.

Prompt 12: Cluster a Keyword Export

Use this when:
You have a CSV/export and need page-level clusters.

Provide this context:

• Keyword export with available columns
• Existing URL map if any
• Business priority themes
• Cannibalization concerns

Prompt:

You are an experienced SEO professional.
Cluster the keyword rows I paste into page targets.
Do not invent missing metrics.
For each cluster: primary term, secondaries, likely intent, suggested URL action (create/merge/optimize), and assumptions.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Cluster table ready for editorial planning with clear primary terms.

Validate by:
Check that primaries are not already ranking on conflicting URLs in GSC.

Prompt 13: Keyword Cannibalization Detector

Use this when:
Multiple URLs may target overlapping terms.

Provide this context:

• Keyword-to-URL mapping
• GSC query report if available
• Page purpose notes

Prompt:

You are an experienced SEO professional.
Identify likely keyword cannibalization from the mapping below.
Do not invent rankings.
Recommend consolidate, differentiate, or monitor—with evidence needed for each.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Conflict list with recommended action types and evidence gaps.

Validate by:
Confirm overlaps in GSC and crawl before consolidating pages.

Prompt 14: Long-Tail Opportunity Filter

Use this when:
You want long-tail ideas that still map to business value.

Provide this context:

• Keyword export
• Conversion relevance criteria
• Support ticket themes
• Content capacity

Prompt:

You are an experienced SEO professional.
Filter long-tail opportunities from my export using business relevance criteria I provide.
Do not invent volumes.
Prioritize terms that match real customer language in my notes.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Filtered long-tail list with relevance rationale and capacity-aware sequencing.

Validate by:
Sample 10 terms in SERPs and CRM language to confirm commercial relevance.

Prompt 15: SERP Feature Opportunity Notes Interpreter

Use this when:
You captured SERP notes and want structured opportunities.

Provide this context:

• SERP screenshots or written notes
• Target queries
• Your current page type
• Available content assets

Prompt:

You are an experienced SEO professional.
Interpret my SERP notes into opportunity hypotheses.
Do not invent feature prevalence beyond what I described.
For each query: dominant page types, possible content formats, and risks.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Per-query SERP interpretation with format hypotheses and risks.

Validate by:
Re-check live SERPs the day you brief writers; features change.

Prompt 16: Keyword-to-Page Type Matcher

Use this when:
You need to decide blog vs landing vs docs vs comparison pages.

Provide this context:

• Keyword clusters
• Product funnel stages
• Existing templates
• Compliance constraints

Prompt:

You are an experienced SEO professional.
Recommend a page type for each cluster using intent cues and my funnel notes.
Do not invent CTR or conversion rates.
Explain when two page types would conflict.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Cluster → page type recommendations with conflict warnings.

Validate by:
Align recommendations with your site IA and sales enablement needs.

Prompt 17: Seasonality and Demand Questions

Use this when:
You suspect seasonal demand but lack full history.

Provide this context:

• Partial historical data if any
• Industry calendar events
• Product launch dates
• Geo scope

Prompt:

You are an experienced SEO professional.
List what seasonal signals I should pull from tools and how to interpret them for planning.
Do not invent seasonality curves.
If my data is incomplete, specify exactly which date ranges I should export.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Research checklist for seasonality plus planning caveats.

Validate by:
Export multi-year trends from your keyword/analytics tools before locking calendar.

Prompt 18: Competitor Keyword Gap Framing

Use this when:
You have competitor keyword exports to compare.

Provide this context:

• Your keyword export
• Competitor exports
• Business exclusion list
• Priority products

Prompt:

You are an experienced SEO professional.
Compare keyword coverage gaps using only the exports I paste.
Do not invent competitor metrics not in the files.
Output: gap themes, likely page opportunities, and low-value terms to ignore.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Gap themes with ignore-list and opportunity candidates grounded in exports.

Validate by:
Validate that gap terms still appear in live SERPs and fit your offer.

Prompt 19: PAA and Question Mining From Notes

Use this when:
You collected People Also Ask / forum questions manually.

Provide this context:

• PAA/forum notes
• Target cluster
• Product facts
• Claims requiring sources

Prompt:

You are an experienced SEO professional.
Organize my question notes into an FAQ and content outline plan.
Do not invent additional PAA questions as if they were observed.
Mark which answers need SME input or sources.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Question map with answer ownership (SME/source) and outline slots.

Validate by:
Confirm questions still appear in SERPs/forums; add only verified new ones.

Prompt 20: Brand vs Non-Brand Keyword Split

Use this when:
You need clearer reporting and content rules for brand queries.

Provide this context:

• Query lists or GSC export
• Brand terms and variants
• Product names
• Partner/competitor brand rules

Prompt:

You are an experienced SEO professional.
Split my queries into brand, non-brand, and ambiguous.
Do not invent volumes.
Propose tagging rules and content ownership for ambiguous terms.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Classification rules plus tagged sample and ambiguous-term playbook.

Validate by:
Apply rules in your reporting tool and spot-check ambiguous buckets.

Prompt 21: International Keyword Localization Brief

Use this when:
You are expanding to another locale and need research questions—not machine-translated keywords as truth.

Provide this context:

• Source-language keyword list
• Target locale
• Terms that must stay English
• Local product differences

Prompt:

You are an experienced SEO professional.
Create a localization research brief for keywords.
Propose how a native researcher should validate meaning and demand.
Do not invent local volumes or treat literal translations as final keywords.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Locale research brief with validation steps and non-translatable terms.

Validate by:
Have a native speaker + local keyword tool confirm before production.

Prompt 22: Keyword Difficulty Interpretation

Use this when:
You have difficulty scores from a tool and need decision guidance.

Provide this context:

• Export with difficulty and other metrics
• Domain strengths you know
• Content/resources available
• Time horizon

Prompt:

You are an experienced SEO professional.
Help me interpret keyword difficulty scores from my export for prioritization.
Do not invent alternative difficulty scores.
Explain limitations of difficulty metrics and what else I must check in SERPs.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Prioritization notes that treat difficulty as one input among many.

Validate by:
Open top SERPs and assess real competitors beyond the difficulty number.

Prompt 23: Zero-Volume and Emerging Query Handling

Use this when:
Some strategically important terms show low/zero volume in tools.

Provide this context:

• List of candidate terms
• Customer language evidence
• Tool volume fields
• Business importance

Prompt:

You are an experienced SEO professional.
Advise how to treat low/zero-volume terms using my customer-language evidence.
Do not invent volumes.
Recommend research next steps and when a page is still justified.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Decision framework for low-volume strategic terms with evidence requirements.

Validate by:
Confirm demand via GSC, sales calls, or paid tests before large investments.

Prompt 24: Keyword Research QA Checklist

Use this when:
You want a QA pass before briefs are written.

Provide this context:

• Draft cluster sheet
• URL map
• Intent notes
• Business exclusions

Prompt:

You are an experienced SEO professional.
Create a QA checklist for my keyword research deliverable.
Then apply it to the draft I paste and list defects.
Do not invent missing metrics while QAing.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
QA checklist plus defect list against your draft sheet.

Validate by:
Fix defects; re-run QA until critical issues are cleared.

Prompt 25: From Keywords to Brief Inputs

Use this when:
Clusters are ready; you need standardized brief input packs.

Provide this context:

• Final clusters
• SERP notes
• Internal link targets
• Brand rules

Prompt:

You are an experienced SEO professional.
Convert each approved cluster into a brief-input pack:
primary/secondaries, intent summary, outline questions, proof needed, and open data gaps.
Do not invent competitor stats.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
One brief-input pack per cluster ready for writers/strategists.

Validate by:
Writers confirm every required field is present before drafting.

AI Prompts for Search Intent — Prompts 26–33

Intent prompts label queries, detect mixed intents, and match formats to user jobs. Low confidence should trigger SERP notes—not invented SERP stories. Intent clarity prevents wasted drafts, wrong templates, and cannibalization between blog posts and landing pages.

Treat intent as a hypothesis you refine with evidence: page types in the results, dominant content formats, and whether commercial investigation language appears. When intent is mixed, splitting URLs is often safer than forcing one page to serve two jobs.

Revisit intent after major SERP changes or product shifts. Historical notes plus current notes beat memory alone. Navigational queries usually belong on official pages—not new content forked for keyword variants.

Prompt 26: Label Intent for a Keyword List

Use this when:
You need consistent intent labels across a research sheet.

Provide this context:

• Keyword list
• Optional SERP notes
• Your intent taxonomy
• Product funnel definitions

Prompt:

You are an experienced SEO professional.
Label search intent for each keyword using my taxonomy.
If SERP evidence is missing, mark confidence low and ask for notes.
Do not invent SERP compositions.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Intent labels with confidence and evidence-needed flags.

Validate by:
Spot-check low-confidence items against live SERPs.

Prompt 27: Detect Mixed-Intent Clusters

Use this when:
A cluster may hide multiple intents that need separate URLs.

Provide this context:

• Cluster terms
• SERP notes if available
• Existing URL purposes

Prompt:

You are an experienced SEO professional.
Evaluate whether this cluster should be one page or split.
Explain mixed-intent signals from my notes only.
Recommend split criteria without inventing traffic forecasts.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Keep vs split recommendation with clear criteria and assumptions.

Validate by:
Confirm with SERP sampling and analytics landing-page behavior.

Prompt 28: Map Intent to Content Format

Use this when:
You know intent but not the best format.

Provide this context:

• Intent labels
• Audience sophistication
• Available media assets
• Conversion goals

Prompt:

You are an experienced SEO professional.
Recommend content formats for each intent group (guide, comparison, calculator concept, docs, etc.).
Do not invent engagement metrics.
Note when format choice depends on SERP norms I have not provided.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Intent → format recommendations with dependency notes.

Validate by:
Compare recommendations to current top results before briefing.

Prompt 29: Commercial Investigation Briefing

Use this when:
Queries look like buyers comparing options.

Provide this context:

• Target queries
• Competitor set
• Differentiators you can prove
• Pricing rules if shareable

Prompt:

You are an experienced SEO professional.
Build a commercial-investigation content brief structure.
Require proof points and comparison dimensions from my inputs only.
Do not invent prices, ratings, or win rates.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Comparison brief structure with proof checklist and claim limits.

Validate by:
Legal/product review of comparison claims before writing.

Prompt 30: Informational Intent Depth Planner

Use this when:
Informational queries need the right depth—not endless fluff.

Provide this context:

• Query list
• Audience expertise level
• SME availability
• Related commercial pages

Prompt:

You are an experienced SEO professional.
Plan depth and section types for informational intents.
Identify what must be original expertise vs summary.
Do not invent word-count ranking rules.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Depth plan with SME touchpoints and internal journey links.

Validate by:
SME confirms sections that need original insight vs commodity explanation.

Prompt 31: Transactional Intent Landing Requirements

Use this when:
You are briefing a landing page for transactional queries.

Provide this context:

• Queries
• Offer details
• Trust elements available
• Form/CTA constraints

Prompt:

You are an experienced SEO professional.
List on-page requirements for transactional intent matching my offer.
Separate must-have trust elements I already have vs missing.
Do not invent conversion rate benchmarks.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Landing requirements checklist tied to your real offer assets.

Validate by:
CRO/design review for feasibility; remove unsupported trust claims.

Prompt 32: Navigational Intent Handling

Use this when:
Brand/navigational queries need careful page targeting.

Provide this context:

• Query list
• Official pages
• Common misspellings
• Support destinations

Prompt:

You are an experienced SEO professional.
Recommend how to handle navigational queries (optimize official pages vs create new).
Do not invent brand search volumes.
Flag risky lookalike/doorway approaches to avoid.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Navigational handling plan with official URL mapping and risk flags.

Validate by:
Ensure no doorway-style pages; align with brand guidelines.

Prompt 33: Intent Change Monitoring Notes

Use this when:
Intent for a query may have shifted; you have historical notes.

Provide this context:

• Past SERP notes
• Current SERP notes
• Page performance summary you provide
• Content changelog

Prompt:

You are an experienced SEO professional.
Compare past vs current SERP notes for intent shift hypotheses.
Do not invent historical rankings.
Recommend content or IA responses as hypotheses to test.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Intent-shift hypotheses with suggested tests—not guaranteed fixes.

Validate by:
Validate with fresh SERPs and segment GSC data before major rewrites.

AI Prompts for Topic Clusters and Content Planning — Prompts 34–43

Cluster prompts turn keyword groups into hub-and-spoke maps, publish order, differentiation matrices, and brief bundles. They support topical depth without encouraging near-duplicate doorway content. Each spoke should own a unique job; if two briefs share the same job, merge before you write.

Use them alongside your cluster practice and Krishan Dev content standards. Pillars should route readers to spokes; spokes should deepen a specific angle and link back with natural anchors. Prompts can draft the map—humans still decide what ships based on demand data and SME capacity.

If you care about clarity for both classic search and AI-mediated discovery, prioritize original evidence and precise entity coverage over keyword stuffing or mass page generation. Citation-worthiness comes from specificity and trust—not from prompt volume.

Prompt 34: Design a Hub-and-Spoke Cluster

Use this when:
You are building topical coverage around a pillar theme.

Provide this context:

• Seed topic
• Keyword clusters
• Existing URLs
• Business priorities

Prompt:

You are an experienced SEO professional.
Design a hub-and-spoke topic cluster map using only my inputs.
Assign pillar vs supporting roles.
Do not invent traffic potential.
Flag cannibalization risks.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Cluster map with URL roles and cannibalization flags.

Validate by:
Review against live inventory; merge overlaps before assigning writers.

Prompt 35: Pillar Page Outline From Cluster

Use this when:
The pillar URL needs an outline that supports spokes.

Provide this context:

• Pillar target queries
• Spoke list
• Unique expertise notes
• Internal link rules

Prompt:

You are an experienced SEO professional.
Outline a pillar page that summarizes the topic and routes to spokes.
Avoid duplicating full spoke content.
Do not invent statistics.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Pillar outline with spoke routing sections and source placeholders.

Validate by:
Ensure each spoke has a distinct angle before drafting the pillar.

Prompt 36: Spoke Differentiation Matrix

Use this when:
Supporting articles risk overlapping.

Provide this context:

• Spoke titles/angles
• Primary keywords
• Audience segments
• Product touches

Prompt:

You are an experienced SEO professional.
Build a differentiation matrix for spokes so each page owns a unique job.
Recommend merges where angles collide.
Do not invent demand metrics.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Matrix of unique angles plus merge recommendations.

Validate by:
Editorial lead signs off that no two briefs share the same job.

Prompt 37: Cluster Publish Order Planner

Use this when:
You need a publish sequence based on dependencies—not fake urgency.

Provide this context:

• Cluster map
• Dependencies (definitions before advanced)
• Capacity
• Known launch dates

Prompt:

You are an experienced SEO professional.
Propose a publish order based on conceptual dependencies and capacity.
Do not promise ranking lift from order alone.
Call out parallelizable work.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Ordered backlog with dependency notes and parallel tracks.

Validate by:
Confirm SME and design bottlenecks before locking dates.

Prompt 38: Cluster Internal Link Blueprint

Use this when:
You want linking rules for a new cluster.

Provide this context:

• Pillar and spoke URLs/titles
• Anchor style guide
• Crawl depth concerns
• Related non-cluster pages

Prompt:

You are an experienced SEO professional.
Create an internal linking blueprint for this cluster using only listed URLs.
Suggest contextual placements.
Do not invent URLs.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Link blueprint with from→to→anchor guidance using real URLs.

Validate by:
Implement in CMS and crawl to confirm links resolve.

Prompt 39: Refresh vs New Page in a Cluster

Use this when:
Unclear whether to update an old URL or create new.

Provide this context:

• Existing URL performance notes
• New keyword targets
• Content overlap summary
• Redirect constraints

Prompt:

You are an experienced SEO professional.
Recommend refresh vs new URL for the scenario below.
Do not invent traffic forecasts.
List evidence still needed to decide.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Decision with evidence gaps and implementation caveats (redirects, canonicals).

Validate by:
Check GSC history and inbound links before creating duplicates.

Prompt 40: Cluster Coverage Gap Audit

Use this when:
You want gaps vs a competitor set you researched.

Provide this context:

• Your cluster map
• Competitor outline notes
• Must-cover entities
• Out-of-scope topics

Prompt:

You are an experienced SEO professional.
Audit topical coverage gaps from my notes.
Do not invent competitor authority metrics.
Separate nice-to-have vs must-cover for our ICP.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Gap list prioritized by ICP relevance with out-of-scope exclusions.

Validate by:
Reject gaps that do not serve your ICP even if competitors cover them.

Prompt 41: Entity and Concept Coverage Planner

Use this when:
You want entity completeness without stuffing.

Provide this context:

• Topic
• Known entities/products
• SME glossary
• Audience level

Prompt:

You are an experienced SEO professional.
Propose which entities/concepts the cluster should explain, define, or merely mention.
Do not invent entity relationships you cannot justify from my notes.
Mark SME-required definitions.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Entity coverage plan with define/mention levels and SME flags.

Validate by:
SME reviews entity list for accuracy and missing critical concepts.

Prompt 42: Cluster Brief Bundle Generator

Use this when:
You need consistent briefs across many spokes.

Provide this context:

• Cluster map
• Brand voice
• Proof library notes
• CTA rules

Prompt:

You are an experienced SEO professional.
Generate a brief template filled for each spoke listed.
Keep uniqueness per spoke.
Do not invent citations or metrics; use [SOURCE NEEDED].

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Per-spoke brief drafts with shared template fields and unique angles.

Validate by:
Human editor checks uniqueness and source markers before assignment.

Prompt 43: AI-Search Citation Readiness for Clusters

Use this when:
You want clusters that are clear, attributable, and useful—not spammy AI bait.

Provide this context:

• Cluster pages list
• Original data/expertise available
• FAQ candidates
• Source policies

Prompt:

You are an experienced SEO professional.
Suggest how to strengthen this cluster for people-first clarity and citation-worthy specificity.
Do not claim AI Overview placement.
Focus on structure, evidence, and uniqueness from my assets.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Action list for clarity, evidence, and unique assets—without citation guarantees.

Validate by:
Ensure every factual claim has a source or SME owner before publish.

AI Prompts for SEO Content Writing — Prompts 44–58

Writing prompts cover briefs, drafts, people-first angles, outline reviews, FAQs, comparison guardrails, refreshes, brand voice, fluff removal, citations, CTAs, multi-author consistency, and publish readiness. Require [SOURCE NEEDED] markers and SME review for expertise-sensitive claims.

AI drafting can be part of a legitimate workflow when humans add experience, examples, and verification. Scaled low-value content created mainly to manipulate rankings is a different—and risky—pattern. Prefer fewer distinctive pages over many interchangeable ones.

Use the publish readiness scorecard before CMS publish so blockers (missing sources, unresolved compliance, broken journey CTAs) stop the ship instead of becoming post-launch debt. If a draft cannot survive an SME read-through, it is not ready—regardless of how polished it sounds.

Prompt 44: SEO Content Brief From Research Pack

Use this when:
Research is ready and you need a writer-ready brief.

Provide this context:

• Brief-input pack
• SERP notes
• Brand voice
• Internal URLs for linking

Prompt:

You are an experienced SEO professional.
Create a complete SEO content brief from the research pack.
Include outline, entities, FAQs, internal links from my URL list only, and [SOURCE NEEDED] markers.
Do not invent statistics or competitor metrics.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Writer-ready brief with sources/assumptions clearly marked.

Validate by:
Strategist approves outline against SERP notes before drafting.

Prompt 45: First Draft in Clean HTML

Use this when:
You have an approved brief and need a first draft.

Provide this context:

• Approved brief
• Source notes
• Examples/SME quotes if any
• HTML constraints

Prompt:

You are an experienced SEO professional.
Write a first draft in clean HTML using p, h2, h3, ul, ol, li, strong, em, a only as needed.
Do not invent metrics, quotes, or case results.
Use [SOURCE NEEDED] placeholders.
Flag assumptions at the top.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Draft HTML with placeholders and assumption list.

Validate by:
SME fact-check all claims; replace placeholders before publish.

Prompt 46: People-First Angle Finder

Use this when:
Drafts feel generic; you need a distinctive angle from real expertise.

Provide this context:

• Topic
• First-hand experience notes
• Customer stories you can share
• Constraints on claims

Prompt:

You are an experienced SEO professional.
Propose people-first angles grounded only in the experience notes I provide.
Reject thin, scaled, or doorway-style approaches.
Do not invent case studies.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Angle options with required proof from your notes.

Validate by:
Pick an angle only if you can supply the promised examples.

Prompt 47: Outline Quality Review

Use this when:
You want to pressure-test an outline before writing.

Provide this context:

• Outline
• Target query
• SERP notes
• Audience

Prompt:

You are an experienced SEO professional.
Review this outline for intent match, redundancy, missing subtopics vs my SERP notes, and fluff risk.
Do not invent SERP features I did not mention.
Separate observations from recommended outline edits.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Critique with specific add/remove/reorder suggestions.

Validate by:
Compare revised outline to live SERP needs once more.

Prompt 48: Expert Quote and Example Insertion Plan

Use this when:
You need to plan where original expertise enters the draft.

Provide this context:

• Draft or outline
• SME availability
• Approved anecdotes
• Data you can publish

Prompt:

You are an experienced SEO professional.
Mark sections that need original examples, screenshots, or SME quotes.
Do not invent expert statements.
Provide interview questions for the SME.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Annotation plan plus SME question list.

Validate by:
Schedule SME interview; do not publish with fabricated quotes.

Prompt 49: Simplify Complex SEO Explanations

Use this when:
Technical explanations are too dense for the audience.

Provide this context:

• Draft section
• Audience level
• Terms that must remain precise
• Examples allowed

Prompt:

You are an experienced SEO professional.
Rewrite the section for clarity without losing accuracy.
Do not add new factual claims.
Call out any simplification that risks technical incorrectness.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Clearer rewrite with accuracy-risk notes.

Validate by:
Technical reviewer confirms no meaning was lost.

Prompt 50: FAQ Draft From Real Questions

Use this when:
You have real customer/SERP questions to answer.

Provide this context:

• Question list with sources
• Product facts
• Legal limits
• Link targets

Prompt:

You are an experienced SEO professional.
Draft FAQ answers from my question list and facts.
Do not invent questions or metrics.
Mark answers needing citations.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
FAQ set with citation flags and suggested internal links from your list.

Validate by:
Verify each question’s origin; remove unverified invented FAQs if any appear.

Prompt 51: Comparison Article Guardrails Draft

Use this when:
You are drafting a comparison/alternative article responsibly.

Provide this context:

• Products in scope
• Criteria you can measure
• Disallowed claims
• Affiliate/disclosure rules if any

Prompt:

You are an experienced SEO professional.
Draft a fair comparison structure and sample sections using only allowed claims.
Do not invent benchmarks or awards.
Insert disclosure placeholders where needed.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Comparison draft sections with disclosure and claim limits observed.

Validate by:
Compliance review before publish; verify every comparative claim.

Prompt 52: Refresh Rewrite With Changelog

Use this when:
An older article needs updating with known changes.

Provide this context:

• Current draft
• Outdated claims list
• New facts
• Performance notes you provide

Prompt:

You are an experienced SEO professional.
Propose a refresh rewrite plan and revise priority sections.
Do not invent performance improvements.
Preserve unique assets worth keeping.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Section-level refresh plan and revised copy for priority parts.

Validate by:
Diff against live page; confirm redirects/canonicals if URL strategy changes.

Prompt 53: Brand Voice Pass

Use this when:
Draft is accurate but off-voice.

Provide this context:

• Draft
• Voice guide
• Examples of on-brand copy
• Words to avoid

Prompt:

You are an experienced SEO professional.
Rewrite for brand voice without changing factual meaning.
List any places where voice and compliance may conflict.
Do not add new claims.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
On-voice rewrite plus conflict flags.

Validate by:
Brand editor spot-checks terminology and tone.

Prompt 54: Eliminate AI Fluff and Repetition

Use this when:
Draft has repetitive filler.

Provide this context:

• Draft HTML
• Required points from brief
• Length guidance if any
• Must-keep examples

Prompt:

You are an experienced SEO professional.
Edit to remove fluff and repetition while keeping required brief points.
Do not delete unique evidence.
Summarize what you removed and why.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Tighter draft with removal log.

Validate by:
Confirm all brief-required points remain after edits.

Prompt 55: Source and Citation Pass

Use this when:
You need claims mapped to sources before legal/editorial review.

Provide this context:

• Draft
• Available sources
• Claim risk levels
• Citation style

Prompt:

You are an experienced SEO professional.
Map factual claims to sources I provided or mark [SOURCE NEEDED].
Do not invent citations.
List high-risk unsupported claims.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Claim–source map and unsupported claim list.

Validate by:
Replace or remove unsupported claims; keep a source log.

Prompt 56: CTA and Journey Alignment Edit

Use this when:
Content should guide next steps without spammy CTAs.

Provide this context:

• Draft
• Desired next step
• Available offers
• Audience stage

Prompt:

You are an experienced SEO professional.
Suggest CTA placements and wording aligned to stage and offer.
Do not invent discount percentages or urgency unless provided.
Avoid manipulative patterns.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
CTA plan with stage-appropriate wording.

Validate by:
Conversion owner approves offers; remove false urgency.

Prompt 57: Multi-Author Consistency Editor

Use this when:
Several writers drafted sections that feel inconsistent.

Provide this context:

• Section drafts
• Glossary
• Style rules
• Primary brief

Prompt:

You are an experienced SEO professional.
Harmonize terminology, structure, and tone across sections.
Do not invent missing facts to fill gaps—flag them.
Preserve distinct examples.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Unified draft with terminology glossary updates and gap flags.

Validate by:
Lead editor confirms consistency; SMEs fill gaps.

Prompt 58: Publish Readiness Scorecard

Use this when:
Final QA before CMS publish.

Provide this context:

• Final draft
• Brief
• Compliance checklist
• Asset list (images, links)

Prompt:

You are an experienced SEO professional.
Score publish readiness across accuracy, intent match, sources, links, and people-first quality.
Do not invent SEO scores from tools.
List blockers vs nice-to-have fixes.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Readiness scorecard with blockers clearly listed.

Validate by:
Do not publish until blockers are resolved by owners.

AI Prompts for On-Page SEO — Prompts 59–70

On-page prompts refine titles, metas, headings, intros, keyword naturalness, alt text, slugs, trust cues, thin-content diagnosis, answer passages, and UX/CTA clarity—without density myths or CTR prophecies. Good on-page work makes the page clearer for people and easier for systems to understand; it does not invent performance.

Measure real CTR and query alignment in Search Console after you ship changes. Keep one clear H1 in the template (the CMS title often becomes H1), and make sure titles and intros match the page promise.

For YMYL or regulated topics, use the E-E-A-T cues prompt only with real credentials and editorial policies—never fabricated author expertise. Clear answer passages help readers; they are not a guarantee of featured snippets.

Prompt 59: Title Tag Options

Use this when:
You need multiple title candidates within your rules.

Provide this context:

• Primary query
• Page angle
• Brand rules
• Character guidance you use

Prompt:

You are an experienced SEO professional.
Write multiple title tag options.
Do not invent CTR predictions.
Avoid unsupported claims and keyword stuffing.
Separate observations about the current title (if provided) from recommendations.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Title variants with notes on tradeoffs—not predicted CTR.

Validate by:
Pick candidates that match on-page H1/promise; test in GSC over time.

Prompt 60: Meta Description Options

Use this when:
You need accurate meta descriptions.

Provide this context:

• Page summary
• Primary query
• CTA allowed
• Compliance limits

Prompt:

You are an experienced SEO professional.
Write meta description options that accurately reflect the page.
Do not invent offers or social proof.
No CTR guarantees.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Description variants aligned to real page content.

Validate by:
Ensure the chosen description matches visible content.

Prompt 61: H1 and Heading Hierarchy Audit

Use this when:
Heading structure may be messy or stuffed.

Provide this context:

• Current headings
• Target intent
• Brief outline
• Brand rules

Prompt:

You are an experienced SEO professional.
Audit heading hierarchy for clarity and intent match.
Propose revised H1/H2/H3 without stuffing.
Do not invent ranking impact.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Heading critique and revised outline.

Validate by:
Implement and verify single clear H1 in the template.

Prompt 62: Intro Rewrite for Clarity

Use this when:
The intro fails to establish relevance quickly.

Provide this context:

• Current intro
• Target audience
• Page promise
• Proof you can state

Prompt:

You are an experienced SEO professional.
Rewrite the introduction for clarity and intent match.
Do not invent statistics.
Keep claims limited to provided proof.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Revised intro with assumption notes.

Validate by:
User-test with a teammate unfamiliar with the draft.

Prompt 63: Keyword Placement Naturalness Check

Use this when:
You want natural language—not stuffing.

Provide this context:

• Draft
• Primary/secondary terms
• Terms to avoid overusing

Prompt:

You are an experienced SEO professional.
Review keyword usage for naturalness.
Suggest edits that preserve meaning.
Do not impose a fake keyword density target.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Edits that reduce stuffing while keeping clarity.

Validate by:
Read aloud; confirm secondaries appear only where useful.

Prompt 64: Image Alt Text Patterning

Use this when:
You need helpful alt text patterns for a page set.

Provide this context:

• Image list with context
• Decorative vs informative flags
• Brand rules
• Accessibility notes

Prompt:

You are an experienced SEO professional.
Draft alt text for informative images and mark decorative ones.
Do not keyword-stuff alt attributes.
Do not invent image contents not described.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Alt text set with decorative exclusions.

Validate by:
Accessibility review; confirm alts describe the image purpose.

Prompt 65: URL Slug Recommendations

Use this when:
You are choosing or refining a slug.

Provide this context:

• Page topic
• Primary term
• Existing URL constraints
• Redirect willingness

Prompt:

You are an experienced SEO professional.
Recommend slug options and discuss change risks if a URL already exists.
Do not invent ranking benefits of short slugs.
Ask for current inbound link notes if missing.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Slug options with change-risk notes.

Validate by:
Avoid unnecessary renames; plan redirects if changing.

Prompt 66: On-Page E-E-A-T Cues Check

Use this when:
You want visible trust cues without fake credentials.

Provide this context:

• Page draft
• Author bio facts
• Editorial policy links
• Reviewer availability

Prompt:

You are an experienced SEO professional.
Suggest on-page trust cues based only on real credentials and policies I provide.
Do not invent author expertise or awards.
Flag YMYL-sensitive sections needing review.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Trust-cue recommendations grounded in real bios/policies.

Validate by:
Verify every credential on the live about/author pages.

Prompt 67: Thin Content Diagnosis

Use this when:
A page may be thin or overlapping others.

Provide this context:

• Page copy
• Related URLs
• Purpose statement
• Performance notes you provide

Prompt:

You are an experienced SEO professional.
Diagnose thin or overlapping content issues from my materials.
Recommend expand, merge, redirect, or noindex hypotheses.
Do not invent indexation counts.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Diagnosis with action hypotheses and evidence still needed.

Validate by:
Confirm with crawl/GSC before merging or noindexing.

Prompt 68: Snippet-Worthy Passage Polish

Use this when:
You want clearer definition/answer passages—not snippet bait spam.

Provide this context:

• Target questions
• Draft sections
• Facts allowed
• HTML constraints

Prompt:

You are an experienced SEO professional.
Polish concise, accurate answer passages for key questions.
Do not guarantee featured snippets.
Keep answers faithful to provided facts.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Clear answer passages with source fidelity notes.

Validate by:
Ensure answers appear on-page and match full context.

Prompt 69: On-Page CTA and UX Copy Audit

Use this when:
SEO copy may conflict with UX clarity.

Provide this context:

• Page copy
• Primary conversion
• Form fields
• Objections

Prompt:

You are an experienced SEO professional.
Audit on-page copy for UX clarity around the conversion.
Separate SEO observations from UX recommendations.
Do not invent conversion benchmarks.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
UX/SEO copy audit with prioritized edits.

Validate by:
Run past design/CRO owners before major layout claims.

Prompt 70: Finalize On-Page Checklist for URL

Use this when:
Pre-publish on-page QA for one URL.

Provide this context:

• Final page content
• Targets
• Assets
• Template limitations

Prompt:

You are an experienced SEO professional.
Produce a final on-page SEO checklist applied to this URL.
Mark pass/fail/unknown.
Do not invent tool scores.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Filled checklist with unknowns called out.

Validate by:
Resolve fails; re-crawl the URL after publish.

AI Prompts for Internal Linking — Prompts 71–78

Internal linking prompts suggest contextual links, rescue orphans, draft hub modules, diversify anchors, refine breadcrumbs, connect clusters, QA after publish, and balance nav vs contextual links—using only URLs you provide. Never let a model invent destinations or link-equity scores.

Strong internal links help users complete journeys and help crawlers discover important URLs. Weak internal links are either missing, irrelevant, or stuffed with awkward exact-match anchors. Provide a URL inventory with titles and topics for best results.

After implementing a blueprint, re-crawl and spot-check in the browser. Orphan fixes are not real until discovery paths exist in HTML navigation or content. Prefer descriptive anchors over generic “click here” text.

Prompt 71: Contextual Link Suggestions for a Draft

Use this when:
You are editing a draft and have a URL inventory.

Provide this context:

• Draft
• URL inventory with titles/topics
• Anchor style rules
• Max links guidance

Prompt:

You are an experienced SEO professional.
Suggest contextual internal links using only my URL inventory.
Provide anchor, target, and placement note.
Do not invent URLs or link-equity metrics.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Link suggestions table constrained to real URLs.

Validate by:
Click each target; remove forced or irrelevant links.

Prompt 72: Orphan Page Rescue Plan

Use this when:
Crawl shows orphan or near-orphan URLs.

Provide this context:

• Orphan URL list
• Topical parents
• Traffic notes you provide
• Navigation constraints

Prompt:

You are an experienced SEO professional.
Propose internal linking and IA fixes for orphan URLs.
Do not invent crawl counts beyond my data.
Prioritize by business relevance using my notes.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Rescue plan with parent pages and link placements.

Validate by:
Implement links and re-crawl to confirm discovery.

Prompt 73: Hub Page Link Module Copy

Use this when:
A hub needs clearer links to supporting pages.

Provide this context:

• Hub draft
• Spoke list
• User journey notes
• Design constraints

Prompt:

You are an experienced SEO professional.
Draft link module copy that helps humans navigate spokes.
Avoid generic 'click here'.
Do not invent popularity rankings for spokes.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Descriptive link module copy mapped to spokes.

Validate by:
UX review for scannability on mobile/desktop.

Prompt 74: Anchor Text Diversity Review

Use this when:
Anchors may be over-optimized or vague.

Provide this context:

• List of existing anchors to a URL
• Target page topic
• Style guide

Prompt:

You are an experienced SEO professional.
Review anchor text patterns and recommend natural diversity.
Do not invent penalty claims.
Flag manipulative exact-match overuse based on the list provided.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Anchor review with rewrite suggestions.

Validate by:
Update highest-risk anchors; avoid automated mass changes blindly.

Prompt 75: Breadcrumb Label Recommendations

Use this when:
Breadcrumb labels need clarity for IA.

Provide this context:

• IA tree
• Current breadcrumb labels
• Primary categories
• Constraints

Prompt:

You are an experienced SEO professional.
Recommend breadcrumb labels that match IA and user language.
Do not invent schema eligibility outcomes.
Ask for missing parent nodes if the tree is incomplete.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Breadcrumb label set aligned to IA.

Validate by:
Implement consistently in templates; validate HTML structure.

Prompt 76: Cross-Cluster Linking Opportunities

Use this when:
Two clusters should connect where journeys overlap.

Provide this context:

• Cluster A map
• Cluster B map
• Shared audience journeys
• URL lists

Prompt:

You are an experienced SEO professional.
Propose selective cross-cluster links that help users—not link spam.
Use only listed URLs.
Explain user-job rationale for each.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Selective cross-links with journey rationale.

Validate by:
Limit to high-relevance pairs; verify in content context.

Prompt 77: Internal Link QA After Publish

Use this when:
A batch of pages shipped and needs link QA.

Provide this context:

• New URLs
• Intended link blueprint
• Crawl snippet or link list
• Known broken links

Prompt:

You are an experienced SEO professional.
QA internal links against the blueprint.
List missing, broken, or low-relevance links from my data.
Do not invent sitewide PageRank effects.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
QA report of missing/broken/low-relevance links.

Validate by:
Fix issues; confirm in crawler and browser.

Prompt 78: Navigation vs Contextual Linking Balance

Use this when:
Stakeholders want everything in global nav.

Provide this context:

• Current nav
• Priority pages
• Analytics nav usage if provided
• Design limits

Prompt:

You are an experienced SEO professional.
Advise what belongs in global nav vs contextual linking.
Do not invent UX best-practice statistics.
Protect usability while supporting discovery of key SEO pages.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Nav vs contextual recommendations with usability rationale.

Validate by:
Align with design system; user-test nav changes.

AI Prompts for Technical SEO — Prompts 79–93

Technical prompts triage crawls, indexation, canonicals, redirects, robots.txt, sitemaps, Core Web Vitals notes, JavaScript rendering risks, facets, hreflang, status-code patterns, schema drafts, log samples, HTTPS issues, and sprint ticket bundles. They translate evidence into prioritized actions—they do not replace crawlers or staging checks.

Pair them with a disciplined technical SEO process: collect samples, triage, ticket, verify on staging, release, re-measure. When CWV or log samples are partial, the prompts should state sampling limits instead of extrapolating sitewide certainty.

Schema drafts must use only real entity fields. Invented ratings, prices, or credentials create trust and compliance problems even if markup validates syntactically. Prefer fewer accurate properties over complete-looking fiction.

Prompt 79: Crawl Issue Triage

Use this when:
You pasted crawl findings and need prioritization.

Provide this context:

• Crawl export or issue list
• Site priorities
• Dev capacity
• Examples of affected URLs

Prompt:

You are an experienced SEO professional.
Triage crawl issues by severity and likely user/bot impact based on my export.
Do not invent issue counts not in the data.
Draft developer tickets with acceptance criteria.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Severity-ranked triage plus ticket drafts.

Validate by:
Verify top issues in browser/crawler before sprint planning.

Prompt 80: Indexation Troubleshooting Guide

Use this when:
Pages are not indexed or are unexpectedly indexed.

Provide this context:

• URL examples
• robots/meta/canonical notes
• GSC coverage notes you provide
• CMS settings

Prompt:

You are an experienced SEO professional.
Build a troubleshooting path for indexation using my notes.
Do not invent coverage counts.
Separate observations from recommended checks.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Step-by-step troubleshooting tree grounded in supplied clues.

Validate by:
Confirm each step in GSC and on live HTML.

Prompt 81: Canonical Strategy Review

Use this when:
Canonicals may conflict across templates.

Provide this context:

• Sample HTML canonicals
• Parameter URL examples
• Duplicate groups
• Desired primary URLs

Prompt:

You are an experienced SEO professional.
Review canonical strategy from samples.
Do not invent sitewide duplicate counts.
Recommend consistent rules and test cases.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Canonical ruleset + test cases.

Validate by:
QA on staging across templates and parameters.

Prompt 82: Redirect Mapping QA

Use this when:
A migration or URL cleanup needs redirect checks.

Provide this context:

• Old→new map
• Known chains/loops list
• Critical URLs
• Analytics notes if any

Prompt:

You are an experienced SEO professional.
QA this redirect map for chains, loops, and risky many-to-one collapses.
Do not invent hit counts.
Propose test plan.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Redirect QA findings and test plan.

Validate by:
Crawl old URLs; verify final status codes and destinations.

Prompt 83: robots.txt Review

Use this when:
You need a careful robots.txt interpretation.

Provide this context:

• Full robots.txt
• Environments (prod/staging)
• Intent for private areas
• Known accidental blocks

Prompt:

You are an experienced SEO professional.
Review robots.txt for risky blocks or overly broad rules.
Do not claim Googlebot behavior beyond documented norms and my file.
Ask clarifying questions about intentional disallows.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Risk review with recommended rule changes and questions.

Validate by:
Test with robots testers and monitor GSC after changes.

Prompt 84: XML Sitemap Recommendations

Use this when:
Sitemaps may include the wrong URLs.

Provide this context:

• Sitemap samples or URL lists
• Indexation goals
• Pagination/facet notes
• Lastmod policy if any

Prompt:

You are an experienced SEO professional.
Recommend sitemap inclusion/exclusion rules from my inputs.
Do not invent sitemap index counts.
Provide QA checks.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Inclusion rules and QA checklist.

Validate by:
Validate sitemap URLs resolve and match canonicals.

Prompt 85: Core Web Vitals Interpretation

Use this when:
You have CWV lab/field summaries to interpret.

Provide this context:

• CWV report excerpts
• Template list
• Recent releases
• Device mix notes

Prompt:

You are an experienced SEO professional.
Interpret CWV summaries and propose investigation hypotheses.
Do not invent lab scores beyond my paste.
Separate observations from remediation ideas.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Interpretation + investigation hypotheses by template.

Validate by:
Confirm with field data and profiling tools before large rebuilds.

Prompt 86: JavaScript Rendering Risk Notes

Use this when:
Critical content may depend on JS rendering.

Provide this context:

• Sample URLs
• What content is JS-dependent
• Framework notes
• Crawl tool rendered HTML snippets

Prompt:

You are an experienced SEO professional.
Assess SEO risks from JS-dependent content using my snippets.
Do not invent rendering outcomes for URLs you cannot see.
Recommend verification steps.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Risk assessment and verification steps.

Validate by:
Compare raw vs rendered HTML in your crawler for key templates.

Prompt 87: Pagination and Faceted Navigation Rules

Use this when:
Filters/facets may create index bloat.

Provide this context:

• Facet examples
• Parameter list
• Desired indexable landing pages
• Current robots/canonical behavior

Prompt:

You are an experienced SEO professional.
Propose indexation rules for pagination and facets from my examples.
Do not invent crawl budget numbers.
Highlight UX vs SEO tradeoffs.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Facet/pagination rules with tradeoff notes.

Validate by:
Implement carefully; monitor index coverage after changes.

Prompt 88: Hreflang Draft Review

Use this when:
International URL pairs need hreflang sanity checks.

Provide this context:

• Locale URL mapping
• Sample hreflang markup
• Known mismatches
• x-default policy

Prompt:

You are an experienced SEO professional.
Review hreflang mapping and samples for common errors.
Do not invent international traffic.
List validation tests.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Error list + validation tests for hreflang.

Validate by:
Validate in GSC international reports and HTML samples.

Prompt 89: Status Code Pattern Explainer

Use this when:
Logs or crawls show confusing status patterns.

Provide this context:

• Status code samples
• URL patterns
• CDN/app notes
• Expected behavior

Prompt:

You are an experienced SEO professional.
Explain likely causes of these status patterns from my notes.
Do not invent log volumes.
Recommend confirmations with ops/dev.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Cause hypotheses and confirmation steps.

Validate by:
Validate with server/CDN owners before content changes.

Prompt 90: Structured Data Draft (JSON-LD)

Use this when:
You want JSON-LD candidates for a page type.

Provide this context:

• Page type
• Visible entity fields
• Disallowed invented fields
• CMS constraints

Prompt:

You are an experienced SEO professional.
Draft JSON-LD using only provided entity fields.
Do not invent ratings, prices, stock, or credentials.
List validation checks before deploy.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
JSON-LD draft + validation checklist.

Validate by:
Test with rich results tools; ensure markup matches visible content.

Prompt 91: Log File Sample Analysis Assist

Use this when:
You have a sample of bot hit lines to interpret.

Provide this context:

• Log sample
• Known bots of interest
• Release timeline
• Suspected problem URLs

Prompt:

You are an experienced SEO professional.
Analyze the log sample for patterns worth investigating.
Do not extrapolate sitewide rates from a small sample without stating limits.
Separate observations from recommendations.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Pattern notes with sampling caveats and next pulls to request.

Validate by:
Request fuller logs for confirmed patterns before major changes.

Prompt 92: Security Header / HTTPS SEO Notes

Use this when:
HTTPS or mixed content issues may affect UX and trust.

Provide this context:

• Issue list
• Affected templates
• CDN/WAF notes
• User impact reports

Prompt:

You are an experienced SEO professional.
Explain SEO-relevant implications of these HTTPS/mixed-content notes.
Do not invent ranking impacts.
Prioritize user-security fixes and verification steps.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Prioritized fix list with verification steps—no ranking promises.

Validate by:
Fix mixed content; verify with browser security tools.

Prompt 93: Technical SEO Ticket Bundle

Use this when:
Engineering needs a clean sprint bundle.

Provide this context:

• Prioritized issues
• Acceptance criteria needs
• Environments
• Rollback notes

Prompt:

You are an experienced SEO professional.
Turn prioritized technical SEO issues into a sprint-ready ticket bundle.
Include test plans and rollback considerations.
Do not invent severity beyond my prioritization.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Ticket bundle with tests and rollback notes.

Validate by:
Eng lead reviews estimates; QA executes test plans on staging.

AI Prompts for SEO Audits — Prompts 94–103

Audit prompts help you scope work, sample large sites intelligently, summarize technical findings for executives, review content inventories, interpret backlink samples cautiously, question tracking reliability, synthesize competitive notes, check multi-location footprints, focus ecommerce template risks, and build remediation roadmaps.

Findings must come from evidence you collected—not from confident-sounding guesses. A good audit separates severity, user impact, and sequencing, then attaches verification steps for each remediation wave.

Use sampling plans on large sites so you do not over-generalize from a handful of blog URLs to every template. Re-audit after waves so “done” means verified, not merely ticketed. Never mass-disavow from an AI summary alone.

Prompt 94: Full SEO Audit Scope Builder

Use this when:
You are starting an audit and need a scoped plan.

Provide this context:

• Site type
• Business goals
• Access available
• Timebox
• Known incidents

Prompt:

You are an experienced SEO professional.
Build a scoped SEO audit plan with workstreams and evidence required.
Do not invent findings before data.
Include out-of-scope boundaries.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Scoped audit plan with evidence checklist and boundaries.

Validate by:
Align scope with stakeholders before crawling or reviewing content.

Prompt 95: Content Audit Framework

Use this when:
You need to audit a content inventory.

Provide this context:

• URL inventory
• Performance exports you provide
• Purpose tags
• Conversion definitions

Prompt:

You are an experienced SEO professional.
Design and apply a content audit framework to my inventory sample.
Do not invent metrics not in exports.
Recommend keep/improve/merge/retire hypotheses.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Audited sample with action hypotheses and data gaps.

Validate by:
Validate retire/merge decisions with analytics and stakeholders.

Prompt 96: Technical Audit Executive Summary

Use this when:
Engineers and execs need a plain-language summary of technical findings.

Provide this context:

• Technical findings list
• Business impact notes
• Capacity
• Timeline constraints

Prompt:

You are an experienced SEO professional.
Write an executive summary of technical SEO findings from my list.
Separate severity, user impact, and recommended sequence.
No traffic guarantees.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Exec summary with sequenced recommendations and assumptions.

Validate by:
Ensure every severity label maps to a verified finding.

Prompt 97: On-Page Audit Sampling Plan

Use this when:
The site is large; you must sample intelligently.

Provide this context:

• Template list
• Traffic tiers you provide
• Risk areas
• Sample size constraints

Prompt:

You are an experienced SEO professional.
Create a sampling plan for on-page audits across templates and tiers.
Do not invent traffic tiers.
Explain how findings will/won't generalize.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Sampling plan with generalization caveats.

Validate by:
Execute sample; avoid over-generalizing to unsampled templates.

Prompt 98: Backlink Profile Review Assist

Use this when:
You exported backlink sample data for review.

Provide this context:

• Backlink export sample
• Disavow policy notes
• Known campaigns
• Risk tolerance

Prompt:

You are an experienced SEO professional.
Review the backlink sample for patterns and risks using only provided data.
Do not invent domain ratings beyond the export.
Recommend investigation steps—not automatic mass disavow.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Pattern/risk notes with investigation steps.

Validate by:
Manually review flagged domains before any disavow action.

Prompt 99: Analytics and Tracking Audit Questions

Use this when:
SEO decisions may be skewed by broken tracking.

Provide this context:

• Tracking setup notes
• Known anomalies
• Conversion list
• Consent mode notes if any

Prompt:

You are an experienced SEO professional.
Generate an analytics/tracking audit question list for SEO reliability.
Do not invent tracking bugs.
Prioritize questions that unblock SEO measurement.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Prioritized tracking QA questions and likely owners.

Validate by:
Analytics owner answers questions with evidence from the property.

Prompt 100: Competitive Audit Synthesis

Use this when:
You collected competitor evidence and need synthesis.

Provide this context:

• Competitor notes
• Your strengths/weaknesses
• SERP screenshots notes
• Business constraints

Prompt:

You are an experienced SEO professional.
Synthesize a competitive SEO audit narrative from my evidence.
Do not invent competitor traffic or link metrics.
List plays that fit our constraints.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Competitive synthesis with constrained play list.

Validate by:
Verify each competitor claim against your saved evidence.

Prompt 101: Local/Multi-Location Audit Checklist

Use this when:
Multi-location sites need specialized audit checks.

Provide this context:

• Location list
• NAP sources
• Landing page samples
• GBP access notes

Prompt:

You are an experienced SEO professional.
Create a multi-location SEO audit checklist and apply it to samples I provide.
Do not invent review scores or rankings.
Flag duplicate/thin location pages.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Checklist + sample findings for locations provided.

Validate by:
Verify NAP consistency in real citations/GBP; fix thin pages carefully.

Prompt 102: Ecommerce SEO Audit Focus Areas

Use this when:
Store SEO audits need catalog-aware focus.

Provide this context:

• Platform notes
• Facet rules
• Indexation samples
• Category/product templates

Prompt:

You are an experienced SEO professional.
Build an ecommerce SEO audit focus list tailored to my platform notes.
Do not invent index bloat counts.
Prioritize template-level risks.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Ecommerce audit focus areas with template risk priorities.

Validate by:
Confirm findings on staging/production samples per template.

Prompt 103: Audit Remediation Roadmap

Use this when:
Findings exist; you need a remediation roadmap.

Provide this context:

• Findings with severities
• Owners available
• Dependencies
• Deadlines if any

Prompt:

You are an experienced SEO professional.
Turn audit findings into a remediation roadmap with waves.
Do not promise ranking recovery dates.
Include verification steps per wave.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Phased remediation roadmap with verification per wave.

Validate by:
Track completion in tickets; re-audit after each wave.

AI Prompts for Local SEO — Prompts 104–113

Local prompts support unique location outlines, GBP posts from real updates, review-theme response templates, citation consistency checklists, service-area page decisions, LocalBusiness schema fields, multi-location differentiation, local SERP note interpretation, monthly local narratives, and spam-avoidance reviews.

Do not invent reviews, map pack rankings, citations, or service areas you do not actually cover. Scaled city pages without unique proof are a classic thin/doorway risk. For location-led growth, see local SEO expertise.

Every local page should answer: why this location, what proof exists here, and how a real customer contacts or visits. If those answers are missing, do not publish yet. Fake locations and review manipulation are out of bounds—prompts in this section refuse that path.

Prompt 104: Local Landing Page Outline

Use this when:
You need a unique local service page outline.

Provide this context:

• NAP
• Services
• Service area
• Local proof points
• Photos/team facts

Prompt:

You are an experienced SEO professional.
Create a local landing page outline using only supplied local proof.
Do not invent reviews, rankings, or citations.
Ensure uniqueness vs generic city spam patterns.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Unique local outline grounded in real proof points.

Validate by:
Reject outlines that could be spun across cities without new proof.

Prompt 105: GBP Post Drafts From Updates

Use this when:
You have real business updates for GBP posts.

Provide this context:

• Updates/offers you can honor
• Dates
• Photos available
• CTA destinations

Prompt:

You are an experienced SEO professional.
Draft GBP posts from real updates only.
Do not invent offers or urgency.
Keep posts accurate and useful.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
GBP post drafts tied to real updates and dates.

Validate by:
Confirm offers/inventory before scheduling posts.

Prompt 106: Review Theme Response Templates

Use this when:
You summarized review themes and need response guidance.

Provide this context:

• Review themes (not fake reviews)
• Tone guide
• Escalation rules
• Privacy constraints

Prompt:

You are an experienced SEO professional.
Create response templates by theme using my rules.
Do not invent review quotes or star ratings.
Include escalation paths.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Theme-based response templates with escalation notes.

Validate by:
Train staff; personalize each response; never fabricate reviews.

Prompt 107: Local Citation Consistency Checklist

Use this when:
NAP consistency needs a practical checklist.

Provide this context:

• Canonical NAP
• Known directories list
• Brand variants
• Phone/hours rules

Prompt:

You are an experienced SEO professional.
Build a citation consistency checklist and cleanup workflow.
Do not invent citation lists beyond what I provide.
Prioritize high-risk mismatches.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Citation QA checklist and cleanup workflow.

Validate by:
Verify each listing manually; track changes in a sheet.

Prompt 108: Service Area Pages Decision Help

Use this when:
Unclear whether service-area pages are justified.

Provide this context:

• True service areas
• Staffing reality
• Existing pages
• Proof available per area

Prompt:

You are an experienced SEO professional.
Advise when service-area pages are justified vs thin doorway risk.
Do not invent local search volumes.
Require proof standards per area.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Decision framework with proof standards and spam-risk warnings.

Validate by:
Only build pages where real service + proof exist.

Prompt 109: Local Schema Fields Assistant

Use this when:
You want LocalBusiness schema fields filled accurately.

Provide this context:

• Business entity details
• Opening hours
• SameAs links
• Departments if any

Prompt:

You are an experienced SEO professional.
Propose LocalBusiness JSON-LD fields from provided details only.
Do not invent ratings or review counts.
List missing required info.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Schema field map + missing info list.

Validate by:
Validate markup; ensure it matches visible NAP.

Prompt 110: Multi-Location Page Differentiation

Use this when:
Location pages are too similar.

Provide this context:

• Location-specific facts
• Shared boilerplate
• Services differences
• Team/photos

Prompt:

You are an experienced SEO professional.
Rewrite differentiation guidance so each location page has unique substance.
Do not invent local awards or stats.
Identify boilerplate to cut.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Per-location unique content plan and boilerplate cuts.

Validate by:
Publish only when each page has real unique details.

Prompt 111: Local Competitor SERP Notes Interpreter

Use this when:
You saved map pack / local SERP notes.

Provide this context:

• SERP/map notes
• Your GBP categories
• Services
• Differentiators

Prompt:

You are an experienced SEO professional.
Interpret local SERP notes into action hypotheses.
Do not invent map pack rankings.
Separate pack vs organic observations.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Local SERP interpretation with testable hypotheses.

Validate by:
Re-check pack results by location/device before acting.

Prompt 112: Local SEO Reporting Narrative

Use this when:
Monthly local metrics need a careful narrative.

Provide this context:

• GBP insights you export
• GSC local pages data
• Call/direction metrics if any
• Changes shipped

Prompt:

You are an experienced SEO professional.
Write a local SEO monthly narrative from my metrics only.
Do not invent calls or direction counts.
Label hypotheses about cause.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Narrative with cited metrics and labeled hypotheses.

Validate by:
Reconcile numbers to source exports before sending to clients.

Prompt 113: Local Spam Avoidance Review

Use this when:
Someone proposed scaled city pages or keyword-stuffed GBP categories.

Provide this context:

• Proposed tactics
• Business reality
• Policy concerns you know
• Existing footprint

Prompt:

You are an experienced SEO professional.
Review proposed local tactics for spam/doorway risk and people-first issues.
Do not provide advice that encourages fake locations or review gating abuse.
Recommend safer alternatives based on real service capacity.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Risk review with safer alternatives grounded in real operations.

Validate by:
Reject tactics that create fake locations or manipulative reviews.

AI Prompts for Ecommerce SEO — Prompts 114–121

Ecommerce prompts improve category and PDP copy from real attributes, facet indexation rules, out-of-stock handling options, collection linking, product schema field audits, PDP vs editorial boundaries, and experiment backlogs—always tied to catalog truth.

Stores fail SEO when filters explode indexable URLs, manufacturer copy is duplicated at scale, or schema disagrees with price and availability. Prompts can propose rules and copy; commerce systems remain the source of truth. Learn more via ecommerce SEO.

Treat experiments as hypotheses with stop conditions. Do not ship “AI category intros” that invent specs shoppers cannot verify on the PDP. Keep editorial guides and product pages complementary, not competing for the same primary job.

Prompt 114: Category Page Copy From Product Data

Use this when:
Category copy is thin or manufacturer-duplicated.

Provide this context:

• Category purpose
• Product attributes
• Audience
• Facets available
• Prohibited claims

Prompt:

You are an experienced SEO professional.
Draft category copy from product/category data.
Do not invent specs, prices, or stock.
Support shoppers without duplicating every facet URL.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Helpful category copy with assumption/source notes.

Validate by:
Merchandising review for accuracy; check duplicate content risk.

Prompt 115: Product Description Enrichment

Use this when:
PDP content is sparse but you have attributes.

Provide this context:

• Attribute table
• Brand voice
• Compliance limits
• Unique selling points you can prove

Prompt:

You are an experienced SEO professional.
Enrich product description using attributes and approved USPs only.
Do not invent certifications or performance claims.
Mark missing attributes to request from vendors.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Enriched PDP copy + missing attribute requests.

Validate by:
Compare to physical product/specs sheet before publish.

Prompt 116: Faceted Navigation SEO Ruleset

Use this when:
Filters create many URLs.

Provide this context:

• Facet list
• Indexable landing needs
• Platform capabilities
• Current canonical/robots behavior

Prompt:

You are an experienced SEO professional.
Propose a faceted navigation SEO ruleset for this catalog.
Do not invent crawl budget figures.
Include examples of allow vs noindex vs canonical.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Facet ruleset with examples and tradeoffs.

Validate by:
Implement with eng; monitor indexation after release.

Prompt 117: Out-of-Stock SEO Handling Options

Use this when:
SKU availability changes and SEO handling is unclear.

Provide this context:

• OOS policies possible
• Similar product linking
• Seasonality notes
• Platform constraints

Prompt:

You are an experienced SEO professional.
Compare SEO handling options for OOS products using my constraints.
Do not invent revenue impacts.
Recommend UX-first approaches.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
OOS handling options with UX/SEO tradeoffs.

Validate by:
Pick a policy; document redirects/canonicals; test templates.

Prompt 118: Collection Internal Linking for Catalogs

Use this when:
Collections need smarter cross-links.

Provide this context:

• Collection list
• Top products
• Affinity notes from merchandising
• URL inventory

Prompt:

You are an experienced SEO professional.
Suggest collection and PDP internal links from my inventory and merchandising notes.
Do not invent bestseller ranks unless provided.
Keep links helpful for shoppers.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Link suggestions aligned to merchandising reality.

Validate by:
Merch confirms affinities; avoid irrelevant cross-sell spam.

Prompt 119: Ecommerce Schema Field Audit

Use this when:
Product schema may be incomplete or inaccurate.

Provide this context:

• Sample product fields
• Current JSON-LD
• Pricing source of truth
• Review policy

Prompt:

You are an experienced SEO professional.
Audit product schema fields against provided data.
Do not invent aggregate ratings.
List mismatches and safe fixes.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Schema mismatch list and safe fix recommendations.

Validate by:
Validate with testing tools; sync price/availability to feed/CMS.

Prompt 120: PDP vs Blog Content Boundaries

Use this when:
Content team overlaps commercial PDPs and editorial guides.

Provide this context:

• PDP goals
• Editorial goals
• Shared keywords
• IA constraints

Prompt:

You are an experienced SEO professional.
Clarify content boundaries between PDPs and editorial to reduce cannibalization.
Do not invent traffic splits.
Propose internal linking between the two.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Boundary rules + linking patterns for PDP vs editorial.

Validate by:
Apply to overlapping URLs; adjust targets in the keyword map.

Prompt 121: Ecommerce SEO Experiment Backlog

Use this when:
You want test ideas—not guaranteed wins.

Provide this context:

• Current issues
• Platform limits
• Analytics capability
• Past test notes

Prompt:

You are an experienced SEO professional.
Propose an ecommerce SEO experiment backlog with hypotheses and required metrics.
Do not promise uplift.
Include stop conditions.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Experiment backlog with hypotheses and stop conditions.

Validate by:
Run tests with proper measurement; document outcomes honestly.

AI Prompts for SEO Reporting and Analysis — Prompts 122–129

Reporting prompts turn exports into executive narratives, anomaly investigations, channel posture sections, experiment write-ups, KPI trees, audit follow-ups, query deep dives, and quarterly strategy review outlines—without inventing metrics or promising outcomes.

Honest reporting compounds better decisions than optimistic storytelling. Cite only numbers you pasted, label hypotheses clearly, and state attribution limits. Stakeholders trust SEO programs that admit uncertainty and show verification plans.

Close every month with actions that feed the next sprint: refreshes, technical tickets, cluster gaps, or tests—not vanity screenshots alone. A useful report answers what changed, what we think caused it, what we will do next, and what we still cannot know.

Prompt 122: Monthly SEO Executive Narrative

Use this when:
You have monthly tables and need a clear story.

Provide this context:

• GSC/analytics tables
• Shipped changes
• Known incidents
• Goals

Prompt:

You are an experienced SEO professional.
Turn my monthly SEO tables into an executive narrative.
Cite only provided numbers.
Label hypotheses vs facts.
No ranking promises.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Executive narrative with cited metrics and labeled hypotheses.

Validate by:
Reconcile every number to the source export before sending.

Prompt 123: Anomaly Detection Notes

Use this when:
A metric moved unexpectedly.

Provide this context:

• Metric time series you provide
• Release calendar
• Seasonality notes
• Tracking changes

Prompt:

You are an experienced SEO professional.
List plausible anomaly causes from my context.
Do not invent external events I did not mention.
Rank investigations by likelihood given provided clues.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Investigation list ranked by likelihood with evidence needed.

Validate by:
Prove/disprove top causes with logs, GSC, and release notes.

Prompt 124: Channel Posture Report Section

Use this when:
SEO must be reported beside paid/social carefully.

Provide this context:

• Channel metrics you provide
• Shared landing pages
• Attribution notes
• Caveats

Prompt:

You are an experienced SEO professional.
Write a channel posture section that respects attribution limits in my notes.
Do not invent assisted-conversion math.
State uncertainty clearly.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Balanced channel section with uncertainty stated.

Validate by:
Marketing ops reviews attribution language.

Prompt 125: Experiment Results Write-Up

Use this when:
An SEO test concluded and needs honest documentation.

Provide this context:

• Hypothesis
• Design
• Results table
• Confounders
• Decision

Prompt:

You are an experienced SEO professional.
Write an experiment results document from my inputs.
Do not overclaim causality.
Include limitations and next steps.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Results write-up with limitations and decision recorded.

Validate by:
Store in knowledge base; share raw data with stakeholders.

Prompt 126: KPI Tree and Diagnostic Metrics

Use this when:
Leadership wants fewer vanity metrics.

Provide this context:

• Business goal
• Available metrics
• Leading activities
• Data gaps

Prompt:

You are an experienced SEO professional.
Propose a KPI tree linking activities → diagnostics → outcomes using available metrics only.
Do not invent benchmarks.
Highlight gaps.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
KPI tree with diagnostics and gap list.

Validate by:
Agree definitions in writing; instrument gaps.

Prompt 127: Client-Friendly Audit Follow-Up Report

Use this when:
After an audit, clients need progress reporting.

Provide this context:

• Original findings
• Completed fixes
• Open items
• Verification evidence

Prompt:

You are an experienced SEO professional.
Draft a follow-up report showing progress against audit findings.
Do not claim ranking recovery.
Show verification evidence placeholders for me to fill.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Progress report structure with evidence slots.

Validate by:
Attach real screenshots/crawl proofs before delivery.

Prompt 128: Search Console Query Deep Dive

Use this when:
A query set needs interpretation.

Provide this context:

• Query table
• Landing pages
• Changes shipped
• Cannibalization notes

Prompt:

You are an experienced SEO professional.
Deep-dive my GSC query table into insights and action hypotheses.
Do not invent impressions not in the table.
Separate brand vs non-brand if I labeled them.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Query insights with action hypotheses tied to pages.

Validate by:
Validate page changes in staging/prod; re-measure later.

Prompt 129: Quarterly SEO Strategy Review Deck Outline

Use this when:
Quarter end needs a strategy review outline.

Provide this context:

• Quarter goals
• Results tables
• Learnings
• Next-quarter proposals
• Risks

Prompt:

You are an experienced SEO professional.
Outline a quarterly SEO strategy review deck.
Use only my results.
Include learnings, stops, and asks without guarantees.

Rules:
- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.
- State assumptions clearly.
- Separate observations from recommendations.
- Ask for missing information when needed.

Expected output:
Deck outline with evidence slots and clear asks.

Validate by:
Fill with verified data; remove speculative slides.

How to Combine These Prompts Into an SEO Workflow

Use a simple loop: define the job (strategy prompts) → export data from tools → cluster and label intent → build or refine topic clusters → brief and draft with sources → on-page and internal links → technical checks → ship → report and refresh. Skip steps only when you already have verified artifacts sitting in your project folder.

Teams get stuck when they start at drafting. Drafting without clusters creates cannibalization. Clusters without keyword exports create guesswork. Technical fixes without measurement create busywork. The prompt order below mirrors how durable SEO programs actually run.

1. Lock goals and constraints with strategy prompts so success definitions are shared.
2. Run keyword and intent prompts on real exports; freeze primary page targets.
3. Plan clusters before scaling content production; remove overlapping spokes early.
4. Brief, draft, and fact-check with writing prompts; keep [SOURCE NEEDED] visible.
5. Apply on-page and internal linking prompts before publish using a real URL inventory.
6. Triage technical risks with crawl and Search Console evidence; ticket what engineering must own.
7. Audit periodically; remediate in waves with verification after each wave.
8. Report with cited numbers; feed learnings into refreshes and the next roadmap.

For local or ecommerce programs, insert the specialized prompts after cluster planning and before scale publishing. Location and catalog work introduce template risks that blog-only workflows miss: NAP consistency, facet indexation, out-of-stock handling, and product schema accuracy. Handle those before you multiply pages.

For model-specific workflow tips, read the practical guide to using Claude for SEO—the same validation rules apply across assistants. Swap models if you like; do not swap away evidence requirements.

Document your team’s “definition of done” for each artifact (cluster sheet, brief, draft, ticket, report). Prompts produce drafts of those artifacts; your definition of done decides when they leave the sandbox. Store approved examples so future prompt runs have on-brand references.

Common Mistakes When Using AI SEO Prompts

Most failures are process failures, not model failures. The model will happily invent a tidy answer if you ask for certainty without data. Guard against these patterns:

• Asking for keyword volumes without pasting tool data
• Treating invented SERP analysis as fact
• Publishing first drafts without SME or compliance review
• Generating near-duplicate location or affiliate pages at scale
• Ignoring technical debt while only producing more content
• Letting the model invent URLs, citations, reviews, or ratings
• Confusing schema or meta tweaks with guaranteed rich results or CTR
• Skipping measurement after publishing
• Assuming one AI tool ranks content better than another
• Using prompts to replace strategy instead of accelerating it
• Automating publish pipelines without originality and accuracy gates
• Copying competitor outlines blindly without differentiation or proof

When you catch a mistake, fix the prompt pack and the checklist—not only the single page. Libraries improve when teams record failure modes.

If an output includes numbers, URLs, reviews, ratings, or crawl counts you did not supply, discard those claims immediately. Ask again with the missing export attached, or proceed without the invented detail. Fluency is not evidence.

Frequently Asked Questions

How many SEO prompts do I need day to day?

Most teams reuse a core set: clustering, intent, brief, draft QA, internal links, technical triage, and monthly reporting. Keep the rest as a library for specialized projects like migrations, local rollouts, or ecommerce facet cleanups. Depth beats collecting prompts you never run with real data.

Do AI SEO prompts work with ChatGPT, Claude, and Gemini?

Yes—these prompts are written for general assistants. Results vary by model and by the quality of context you provide. No assistant is a ranking factor, and none should be treated as a source of keyword volumes or live crawl truth unless you connect verified tools and still double-check outputs.

Can prompts replace Ahrefs, Semrush, or Screaming Frog?

No. Those tools measure the web and your site: crawls, keyword databases, rank tracking, and more. Prompts help you analyze exports and produce work product such as briefs, outlines, and ticket drafts. The winning loop is tool export → AI analysis → human decision → implementation → measurement again.

Will using these prompts guarantee rankings or traffic?

No. Prompts improve process quality when paired with data and expertise. Outcomes still depend on competition, demand, implementation quality, site constraints, and time. Anyone promising guaranteed rankings from prompts is selling certainty the web does not offer.

Is AI-generated content allowed for SEO?

Helpful, reliable, people-first content can perform whether or not an assistant helped write it. Scaled low-value content created mainly to manipulate rankings can violate spam policies. Verify facts, add original experience, and avoid doorway-style mass generation.

How do I validate AI SEO output quickly?

Check numbers against exports, open live SERPs, confirm URLs exist, require sources for claims, and have an SME review expertise-sensitive sections before publish. If the output cannot point to your evidence, treat it as a draft hypothesis—not a finding.

Should I automate publishing from prompts?

Prefer human approval gates for accuracy, originality, and compliance. Light automation for formatting or ticket creation can help. Automation that floods the index with thin pages is a risk—not a growth plan.

Where should beginners start in this library?

Start with strategy goal clarity, keyword clustering, intent labeling, a single topic cluster map, one brief, and one draft QA pass. Add technical triage once you can paste a real crawl sample. Expand into local or ecommerce prompts only when those business models apply.

How should agencies adapt these prompts for clients?

Keep a client-specific context pack (brand voice, claim limits, CMS constraints, and approved competitors). Run prompts in a shared workspace, attach exports to every recommendation, and present observations separately from recommendations in deliverables. Clients should see evidence, not unexplained AI prose.

Final Takeaway

A strong SEO prompt library makes AI useful without pretending it replaces research tools or expert judgment. Feed real context, forbid invented metrics, separate observations from recommendations, and validate before you ship. That discipline is what keeps assistants helpful instead of noisy.

Use these 110+ prompts to accelerate strategy, research, content, on-page work, technical triage, audits, local and ecommerce tasks, and reporting—while keeping people-first standards at the center of your search visibility program.

The teams that win with AI SEO prompts are not the teams that generate the most text. They are the teams that attach evidence, protect uniqueness, fix technical blockers, and measure honestly. Keep this library next to your exports—and let humans remain accountable for what goes live.

If you only remember one operating rule: never ask an assistant to invent the numbers your tools already exist to measure. Ask it to organize what you know, challenge what is missing, and draft work you can verify.