{"id":102,"date":"2026-09-18T12:27:44","date_gmt":"2026-09-18T12:27:44","guid":{"rendered":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/"},"modified":"2026-09-18T12:27:44","modified_gmt":"2026-09-18T12:27:44","slug":"complete-seo-prompts","status":"publish","type":"post","link":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/","title":{"rendered":"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO &#038; SEO Audits"},"content":{"rendered":"<p>AI can speed up SEO research synthesis, briefing, drafting, technical triage, and reporting\u2014but 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.<\/p>\n<p>This library gives you <strong>110+ practical SEO prompts<\/strong> 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.<\/p>\n<p>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 \u201cknow\u201d your rankings, your crawl budget, or your customers unless you paste evidence.<\/p>\n<p>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.<\/p>\n<p>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 <a href=\"https:\/\/www.krishandev.com\/expertise\/ai-seo\">AI SEO expertise<\/a> and pair prompts with a clear <a href=\"https:\/\/www.krishandev.com\/solutions\/seo-strategy\">SEO strategy<\/a>.<\/p>\n<p>Use this page as a working library. Bookmark the categories you touch weekly, keep a saved \u201ccontext pack\u201d (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\u2014not a failure of the model.<\/p>\n<h2>How to Use AI Prompts for SEO Effectively<\/h2>\n<p>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.<\/p>\n<p>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\u2014Google\u2019s 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.<\/p>\n<p>A practical setup that works for most teams:<\/p>\n<ul>\n<li>Keep a living context pack: ICP, offers, claim limits, glossary, and priority products.<\/li>\n<li>Export only the columns you need from keyword, analytics, and crawl tools\u2014then paste cleaned subsets.<\/li>\n<li>Save SERP notes as short bullet evidence (page types, unique sections, gaps)\u2014not as invented \u201cSERP scores.\u201d<\/li>\n<li>Require [SOURCE NEEDED] markers for factual claims before legal or SME review.<\/li>\n<li>Ship through CMS with a human approval gate for originality, accuracy, and internal links.<\/li>\n<li>Measure in Search Console and analytics; feed outcomes back into refresh and reporting prompts.<\/li>\n<\/ul>\n<p>If you are building durable topical coverage, connect this library to how you <a href=\"https:\/\/www.krishandev.com\/blog\/how-to-build-topic-clusters-that-get-cited-in-ai-search\/\">build topic clusters for AI search citation readiness<\/a> and your ongoing <a href=\"https:\/\/www.krishandev.com\/solutions\/content-seo\">content SEO<\/a> process. Clusters and prompts work best together: prompts create artifacts; clusters keep those artifacts from colliding.<\/p>\n<p>Also decide what \u201cgood enough for staging\u201d 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.<\/p>\n<p>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.<\/p>\n<p>The table below maps common SEO tasks to prompt categories and the verification a human still owes the work.<\/p>\n<table>\n<thead>\n<tr>\n<th>SEO Task<\/th>\n<th>Prompt Category<\/th>\n<th>Human Verification Needed<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Strategy and prioritization<\/td>\n<td>SEO Strategy<\/td>\n<td>Business goals, capacity, and legal constraints<\/td>\n<\/tr>\n<tr>\n<td>Keyword clustering and gaps<\/td>\n<td>Keyword Research<\/td>\n<td>Volumes, difficulty, and live SERPs from tools<\/td>\n<\/tr>\n<tr>\n<td>Intent labeling and page type<\/td>\n<td>Search Intent<\/td>\n<td>SERP sampling and funnel fit<\/td>\n<\/tr>\n<tr>\n<td>Hub-and-spoke planning<\/td>\n<td>Topic Clusters<\/td>\n<td>Inventory conflicts and SME coverage<\/td>\n<\/tr>\n<tr>\n<td>Briefs and drafts<\/td>\n<td>SEO Content Writing<\/td>\n<td>Facts, originality, and brand voice<\/td>\n<\/tr>\n<tr>\n<td>Titles, headings, trust cues<\/td>\n<td>On-Page SEO<\/td>\n<td>Live templates and CTR in Search Console<\/td>\n<\/tr>\n<tr>\n<td>Contextual links and orphans<\/td>\n<td>Internal Linking<\/td>\n<td>URL existence, relevance, and crawl discovery<\/td>\n<\/tr>\n<tr>\n<td>Crawl and indexation triage<\/td>\n<td>Technical SEO<\/td>\n<td>Crawler, staging, and Search Console confirmation<\/td>\n<\/tr>\n<tr>\n<td>Scoped findings and remediation<\/td>\n<td>SEO Audits<\/td>\n<td>Evidence attachments and re-checks after fixes<\/td>\n<\/tr>\n<tr>\n<td>GBP and location pages<\/td>\n<td>Local SEO<\/td>\n<td>Real NAP, reviews policy, and service capacity<\/td>\n<\/tr>\n<tr>\n<td>Categories, PDPs, facets<\/td>\n<td>Ecommerce SEO<\/td>\n<td>Catalog truth (price, stock, specs)<\/td>\n<\/tr>\n<tr>\n<td>Monthly narratives and tests<\/td>\n<td>Reporting and Analysis<\/td>\n<td>Source exports and attribution limits<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>AI Prompts for SEO Strategy \u2014 Prompts 1\u201310<\/h2>\n<p>Start with strategy prompts when stakeholders need clarity on goals, prioritization, ICP mapping, risk, and measurement\u2014before generating more pages. Strong strategy inputs make every later prompt more accurate because writers and developers inherit constraints instead of inventing them.<\/p>\n<p>These prompts help you turn vague \u201cwe need more traffic\u201d requests into measurable objectives, sequenced roadmaps, and honest measurement plans. They will not invent baselines or guarantee outcomes. Align outputs with your <a href=\"https:\/\/www.krishandev.com\/solutions\/search-visibility\">search visibility<\/a> priorities and capacity reality.<\/p>\n<p>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.<\/p>\n<h3>Prompt 1: Clarify Business SEO Goals<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need to turn vague growth goals into measurable SEO objectives without inventing targets.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Business model and primary conversion<\/li>\n<li>Current known constraints (budget, team, tech stack)<\/li>\n<li>Any existing KPI definitions from stakeholders<\/li>\n<li>Markets and languages in scope<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nTranslate the business context below into an SEO goal framework.\nReturn: primary SEO objective, supporting objectives, leading vs lagging indicators (only if data sources are named), risks, and open questions.\nIf stakeholders did not define a number, propose a measurement approach\u2014not a fabricated target.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nA goal framework with clear objectives, measurement sources, assumptions, and questions\u2014not invented KPI numbers.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm each metric has a real data source (GSC, analytics, CRM). Reject any invented baseline or target.<\/p>\n<h3>Prompt 2: Prioritize SEO Initiatives by Impact and Effort<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have a backlog of SEO ideas and need a transparent prioritization matrix.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>List of proposed initiatives<\/li>\n<li>Known resource constraints<\/li>\n<li>Any historical results you can cite<\/li>\n<li>Business priorities for the quarter<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPrioritize the SEO initiatives listed below using Impact, Effort, Confidence, and Risk.\nDo not invent past results. If impact is unknown, say so and list what evidence would raise confidence.\nOutput a ranked table with rationale and recommended sequencing.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nRanked initiative list with explicit confidence notes and missing-evidence flags.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nSpot-check that high-impact claims are backed by your data or marked as hypotheses.<\/p>\n<h3>Prompt 3: Define SEO ICP and Buyer Journey Mapping<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou are planning content and landing pages for specific buyer personas.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Ideal customer profile notes<\/li>\n<li>Sales cycle stages<\/li>\n<li>Known objections and product claims you can support<\/li>\n<li>Existing page inventory (URLs\/titles)<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nMap SEO content opportunities to ICP stages using only the notes provided.\nFor each stage: jobs-to-be-done, likely query themes, page types, and proof needed.\nDo not invent market sizes or search volumes.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nStage-by-stage map of themes, page types, and proof requirements tied to supplied ICP notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nHave sales\/CS review that objections and proof points match real conversations.<\/p>\n<h3>Prompt 4: Competitive SEO Positioning Brief<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou collected competitor notes and need a differentiation brief for SEO content.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Your product differentiators<\/li>\n<li>Competitor page notes you collected<\/li>\n<li>Claims you are legally allowed to make<\/li>\n<li>Any tool exports you want compared (paste them)<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate a competitive SEO positioning brief from my notes.\nDo not invent competitor traffic, backlinks, or rankings.\nCall out where competitor claims need verification.\nRecommend angles we can uniquely own based on supplied differentiators.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPositioning summary, avoid-list of unsupported claims, and content angles grounded in your notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nVerify competitor claims on their live pages; discard any metric the model added without your export.<\/p>\n<h3>Prompt 5: SEO Opportunity Scoring Rubric<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want a reusable rubric to score keyword or page opportunities consistently.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Business priorities<\/li>\n<li>Available data columns from your tools<\/li>\n<li>Risk tolerances (YMYL, brand, legal)<\/li>\n<li>Example opportunities to score<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDesign an SEO opportunity scoring rubric using only the data columns I can supply.\nDefine each criterion, weight ranges, and how to handle missing data.\nScore the examples I provide without inventing missing metrics.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDocumented rubric plus scored examples with missing-data handling.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nApply the rubric manually to 3 items and confirm scores match your judgment.<\/p>\n<h3>Prompt 6: Quarterly SEO Roadmap Outline<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need a realistic quarterly roadmap from known capacity and priorities.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Team capacity estimates<\/li>\n<li>Prioritized initiatives<\/li>\n<li>Dependencies (dev, design, legal)<\/li>\n<li>Known seasonal or launch dates<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDraft a quarterly SEO roadmap outline from the inputs below.\nSequence work by dependencies and capacity.\nDo not promise ranking or traffic outcomes.\nFlag risks and decision points that need stakeholders.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nMonth-by-month workplan with owners placeholders, dependencies, and risk flags.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm capacity assumptions with the team; remove any outcome guarantees if present.<\/p>\n<h3>Prompt 7: SEO Risk and Compliance Checklist<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou operate in a regulated or sensitive niche and need SEO guardrails.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Industry and claim restrictions<\/li>\n<li>Brand voice and legal review rules<\/li>\n<li>Examples of past rejected copy<\/li>\n<li>YMYL considerations if applicable<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nBuild an SEO content and optimization risk checklist for this niche.\nInclude claim types that require sources, disclaimer needs, and review gates.\nDo not invent legal requirements\u2014flag where counsel must confirm.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nChecklist of risk gates, claim types, and review owners with counsel-confirm flags.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nHave legal\/compliance review the checklist before using it as policy.<\/p>\n<h3>Prompt 8: Channel Mix: SEO vs Paid vs Social Roles<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nStakeholders blur SEO with paid\/social and you need role clarity.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Current channel mix notes<\/li>\n<li>Budget ownership<\/li>\n<li>Conversion definitions<\/li>\n<li>Shared landing page inventory<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nClarify how SEO should complement paid and social using the notes below.\nDefine shared assets, handoffs, and metrics ownership.\nDo not invent attribution percentages unless provided.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nRACI-style channel roles, shared asset rules, and measurement ownership.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nAlign with marketing ops on attribution definitions before publishing the doc.<\/p>\n<h3>Prompt 9: Build an SEO Measurement Plan<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need a measurement plan that ties SEO work to analytics without fake baselines.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Analytics and GSC access notes<\/li>\n<li>Conversion events available<\/li>\n<li>Reporting cadence<\/li>\n<li>Known tracking gaps<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate an SEO measurement plan from the tracking notes below.\nList primary metrics, supporting diagnostics, and known gaps.\nIf a metric cannot be measured today, say so and propose instrumentation\u2014not invented numbers.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nMetric dictionary, dashboards\/cadence, and instrumentation backlog.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nVerify each metric exists in your tools; open tickets for gaps.<\/p>\n<h3>Prompt 10: Stakeholder SEO Narrative Deck Outline<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need an executive-friendly narrative without overselling AI or rankings.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Audience (exec, product, sales)<\/li>\n<li>Known results and open risks<\/li>\n<li>Next-quarter asks<\/li>\n<li>Data tables you will paste<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nOutline a stakeholder SEO narrative deck.\nUse only facts from my notes\/tables.\nSeparate what happened, why we think it happened (hypothesis), and what we propose next.\nNo ranking guarantees.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nSlide outline with evidence slots, hypothesis labels, and clear asks.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nFill slides only with verified numbers; remove speculative causal language.<\/p>\n<h2>AI Prompts for Keyword Research \u2014 Prompts 11\u201325<\/h2>\n<p>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\u2014not fabricate demand metrics or SERP features.<\/p>\n<p>A healthy keyword workflow is export \u2192 clean \u2192 cluster \u2192 validate in SERPs \u2192 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.<\/p>\n<p>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.<\/p>\n<h3>Prompt 11: Seed Keyword Expansion From Product Notes<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have product\/service notes and need seed themes before tool research.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Product features and use cases<\/li>\n<li>Audience language from sales\/CS<\/li>\n<li>Competitors you care about<\/li>\n<li>Markets\/locales<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nGenerate seed keyword themes and example queries from the product notes below.\nDo not invent search volumes or difficulty.\nGroup by job-to-be-done and flag terms that need tool verification.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nTheme clusters with example queries and verification flags\u2014no fabricated metrics.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nRun seeds through your keyword tool and discard irrelevant or zero-demand terms.<\/p>\n<h3>Prompt 12: Cluster a Keyword Export<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have a CSV\/export and need page-level clusters.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Keyword export with available columns<\/li>\n<li>Existing URL map if any<\/li>\n<li>Business priority themes<\/li>\n<li>Cannibalization concerns<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCluster the keyword rows I paste into page targets.\nDo not invent missing metrics.\nFor each cluster: primary term, secondaries, likely intent, suggested URL action (create\/merge\/optimize), and assumptions.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nCluster table ready for editorial planning with clear primary terms.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nCheck that primaries are not already ranking on conflicting URLs in GSC.<\/p>\n<h3>Prompt 13: Keyword Cannibalization Detector<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nMultiple URLs may target overlapping terms.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Keyword-to-URL mapping<\/li>\n<li>GSC query report if available<\/li>\n<li>Page purpose notes<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nIdentify likely keyword cannibalization from the mapping below.\nDo not invent rankings.\nRecommend consolidate, differentiate, or monitor\u2014with evidence needed for each.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nConflict list with recommended action types and evidence gaps.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm overlaps in GSC and crawl before consolidating pages.<\/p>\n<h3>Prompt 14: Long-Tail Opportunity Filter<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want long-tail ideas that still map to business value.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Keyword export<\/li>\n<li>Conversion relevance criteria<\/li>\n<li>Support ticket themes<\/li>\n<li>Content capacity<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nFilter long-tail opportunities from my export using business relevance criteria I provide.\nDo not invent volumes.\nPrioritize terms that match real customer language in my notes.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nFiltered long-tail list with relevance rationale and capacity-aware sequencing.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nSample 10 terms in SERPs and CRM language to confirm commercial relevance.<\/p>\n<h3>Prompt 15: SERP Feature Opportunity Notes Interpreter<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou captured SERP notes and want structured opportunities.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>SERP screenshots or written notes<\/li>\n<li>Target queries<\/li>\n<li>Your current page type<\/li>\n<li>Available content assets<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nInterpret my SERP notes into opportunity hypotheses.\nDo not invent feature prevalence beyond what I described.\nFor each query: dominant page types, possible content formats, and risks.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPer-query SERP interpretation with format hypotheses and risks.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nRe-check live SERPs the day you brief writers; features change.<\/p>\n<h3>Prompt 16: Keyword-to-Page Type Matcher<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need to decide blog vs landing vs docs vs comparison pages.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Keyword clusters<\/li>\n<li>Product funnel stages<\/li>\n<li>Existing templates<\/li>\n<li>Compliance constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRecommend a page type for each cluster using intent cues and my funnel notes.\nDo not invent CTR or conversion rates.\nExplain when two page types would conflict.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nCluster \u2192 page type recommendations with conflict warnings.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nAlign recommendations with your site IA and sales enablement needs.<\/p>\n<h3>Prompt 17: Seasonality and Demand Questions<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou suspect seasonal demand but lack full history.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Partial historical data if any<\/li>\n<li>Industry calendar events<\/li>\n<li>Product launch dates<\/li>\n<li>Geo scope<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nList what seasonal signals I should pull from tools and how to interpret them for planning.\nDo not invent seasonality curves.\nIf my data is incomplete, specify exactly which date ranges I should export.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nResearch checklist for seasonality plus planning caveats.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nExport multi-year trends from your keyword\/analytics tools before locking calendar.<\/p>\n<h3>Prompt 18: Competitor Keyword Gap Framing<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have competitor keyword exports to compare.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Your keyword export<\/li>\n<li>Competitor exports<\/li>\n<li>Business exclusion list<\/li>\n<li>Priority products<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCompare keyword coverage gaps using only the exports I paste.\nDo not invent competitor metrics not in the files.\nOutput: gap themes, likely page opportunities, and low-value terms to ignore.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nGap themes with ignore-list and opportunity candidates grounded in exports.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nValidate that gap terms still appear in live SERPs and fit your offer.<\/p>\n<h3>Prompt 19: PAA and Question Mining From Notes<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou collected People Also Ask \/ forum questions manually.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>PAA\/forum notes<\/li>\n<li>Target cluster<\/li>\n<li>Product facts<\/li>\n<li>Claims requiring sources<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nOrganize my question notes into an FAQ and content outline plan.\nDo not invent additional PAA questions as if they were observed.\nMark which answers need SME input or sources.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nQuestion map with answer ownership (SME\/source) and outline slots.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm questions still appear in SERPs\/forums; add only verified new ones.<\/p>\n<h3>Prompt 20: Brand vs Non-Brand Keyword Split<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need clearer reporting and content rules for brand queries.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Query lists or GSC export<\/li>\n<li>Brand terms and variants<\/li>\n<li>Product names<\/li>\n<li>Partner\/competitor brand rules<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nSplit my queries into brand, non-brand, and ambiguous.\nDo not invent volumes.\nPropose tagging rules and content ownership for ambiguous terms.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nClassification rules plus tagged sample and ambiguous-term playbook.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nApply rules in your reporting tool and spot-check ambiguous buckets.<\/p>\n<h3>Prompt 21: International Keyword Localization Brief<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou are expanding to another locale and need research questions\u2014not machine-translated keywords as truth.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Source-language keyword list<\/li>\n<li>Target locale<\/li>\n<li>Terms that must stay English<\/li>\n<li>Local product differences<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate a localization research brief for keywords.\nPropose how a native researcher should validate meaning and demand.\nDo not invent local volumes or treat literal translations as final keywords.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nLocale research brief with validation steps and non-translatable terms.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nHave a native speaker + local keyword tool confirm before production.<\/p>\n<h3>Prompt 22: Keyword Difficulty Interpretation<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have difficulty scores from a tool and need decision guidance.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Export with difficulty and other metrics<\/li>\n<li>Domain strengths you know<\/li>\n<li>Content\/resources available<\/li>\n<li>Time horizon<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nHelp me interpret keyword difficulty scores from my export for prioritization.\nDo not invent alternative difficulty scores.\nExplain limitations of difficulty metrics and what else I must check in SERPs.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPrioritization notes that treat difficulty as one input among many.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nOpen top SERPs and assess real competitors beyond the difficulty number.<\/p>\n<h3>Prompt 23: Zero-Volume and Emerging Query Handling<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nSome strategically important terms show low\/zero volume in tools.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>List of candidate terms<\/li>\n<li>Customer language evidence<\/li>\n<li>Tool volume fields<\/li>\n<li>Business importance<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nAdvise how to treat low\/zero-volume terms using my customer-language evidence.\nDo not invent volumes.\nRecommend research next steps and when a page is still justified.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDecision framework for low-volume strategic terms with evidence requirements.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm demand via GSC, sales calls, or paid tests before large investments.<\/p>\n<h3>Prompt 24: Keyword Research QA Checklist<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want a QA pass before briefs are written.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Draft cluster sheet<\/li>\n<li>URL map<\/li>\n<li>Intent notes<\/li>\n<li>Business exclusions<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate a QA checklist for my keyword research deliverable.\nThen apply it to the draft I paste and list defects.\nDo not invent missing metrics while QAing.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nQA checklist plus defect list against your draft sheet.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nFix defects; re-run QA until critical issues are cleared.<\/p>\n<h3>Prompt 25: From Keywords to Brief Inputs<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nClusters are ready; you need standardized brief input packs.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Final clusters<\/li>\n<li>SERP notes<\/li>\n<li>Internal link targets<\/li>\n<li>Brand rules<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nConvert each approved cluster into a brief-input pack:\nprimary\/secondaries, intent summary, outline questions, proof needed, and open data gaps.\nDo not invent competitor stats.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nOne brief-input pack per cluster ready for writers\/strategists.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nWriters confirm every required field is present before drafting.<\/p>\n<h2>AI Prompts for Search Intent \u2014 Prompts 26\u201333<\/h2>\n<p>Intent prompts label queries, detect mixed intents, and match formats to user jobs. Low confidence should trigger SERP notes\u2014not invented SERP stories. Intent clarity prevents wasted drafts, wrong templates, and cannibalization between blog posts and landing pages.<\/p>\n<p>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.<\/p>\n<p>Revisit intent after major SERP changes or product shifts. Historical notes plus current notes beat memory alone. Navigational queries usually belong on official pages\u2014not new content forked for keyword variants.<\/p>\n<h3>Prompt 26: Label Intent for a Keyword List<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need consistent intent labels across a research sheet.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Keyword list<\/li>\n<li>Optional SERP notes<\/li>\n<li>Your intent taxonomy<\/li>\n<li>Product funnel definitions<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nLabel search intent for each keyword using my taxonomy.\nIf SERP evidence is missing, mark confidence low and ask for notes.\nDo not invent SERP compositions.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nIntent labels with confidence and evidence-needed flags.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nSpot-check low-confidence items against live SERPs.<\/p>\n<h3>Prompt 27: Detect Mixed-Intent Clusters<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nA cluster may hide multiple intents that need separate URLs.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Cluster terms<\/li>\n<li>SERP notes if available<\/li>\n<li>Existing URL purposes<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nEvaluate whether this cluster should be one page or split.\nExplain mixed-intent signals from my notes only.\nRecommend split criteria without inventing traffic forecasts.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nKeep vs split recommendation with clear criteria and assumptions.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm with SERP sampling and analytics landing-page behavior.<\/p>\n<h3>Prompt 28: Map Intent to Content Format<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou know intent but not the best format.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Intent labels<\/li>\n<li>Audience sophistication<\/li>\n<li>Available media assets<\/li>\n<li>Conversion goals<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRecommend content formats for each intent group (guide, comparison, calculator concept, docs, etc.).\nDo not invent engagement metrics.\nNote when format choice depends on SERP norms I have not provided.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nIntent \u2192 format recommendations with dependency notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nCompare recommendations to current top results before briefing.<\/p>\n<h3>Prompt 29: Commercial Investigation Briefing<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nQueries look like buyers comparing options.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Target queries<\/li>\n<li>Competitor set<\/li>\n<li>Differentiators you can prove<\/li>\n<li>Pricing rules if shareable<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nBuild a commercial-investigation content brief structure.\nRequire proof points and comparison dimensions from my inputs only.\nDo not invent prices, ratings, or win rates.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nComparison brief structure with proof checklist and claim limits.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nLegal\/product review of comparison claims before writing.<\/p>\n<h3>Prompt 30: Informational Intent Depth Planner<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nInformational queries need the right depth\u2014not endless fluff.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Query list<\/li>\n<li>Audience expertise level<\/li>\n<li>SME availability<\/li>\n<li>Related commercial pages<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPlan depth and section types for informational intents.\nIdentify what must be original expertise vs summary.\nDo not invent word-count ranking rules.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDepth plan with SME touchpoints and internal journey links.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nSME confirms sections that need original insight vs commodity explanation.<\/p>\n<h3>Prompt 31: Transactional Intent Landing Requirements<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou are briefing a landing page for transactional queries.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Queries<\/li>\n<li>Offer details<\/li>\n<li>Trust elements available<\/li>\n<li>Form\/CTA constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nList on-page requirements for transactional intent matching my offer.\nSeparate must-have trust elements I already have vs missing.\nDo not invent conversion rate benchmarks.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nLanding requirements checklist tied to your real offer assets.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nCRO\/design review for feasibility; remove unsupported trust claims.<\/p>\n<h3>Prompt 32: Navigational Intent Handling<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nBrand\/navigational queries need careful page targeting.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Query list<\/li>\n<li>Official pages<\/li>\n<li>Common misspellings<\/li>\n<li>Support destinations<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRecommend how to handle navigational queries (optimize official pages vs create new).\nDo not invent brand search volumes.\nFlag risky lookalike\/doorway approaches to avoid.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nNavigational handling plan with official URL mapping and risk flags.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nEnsure no doorway-style pages; align with brand guidelines.<\/p>\n<h3>Prompt 33: Intent Change Monitoring Notes<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nIntent for a query may have shifted; you have historical notes.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Past SERP notes<\/li>\n<li>Current SERP notes<\/li>\n<li>Page performance summary you provide<\/li>\n<li>Content changelog<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCompare past vs current SERP notes for intent shift hypotheses.\nDo not invent historical rankings.\nRecommend content or IA responses as hypotheses to test.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nIntent-shift hypotheses with suggested tests\u2014not guaranteed fixes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nValidate with fresh SERPs and segment GSC data before major rewrites.<\/p>\n<h2>AI Prompts for Topic Clusters and Content Planning \u2014 Prompts 34\u201343<\/h2>\n<p>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.<\/p>\n<p>Use them alongside your cluster practice and <a href=\"https:\/\/www.krishandev.com\/\">Krishan Dev<\/a> 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\u2014humans still decide what ships based on demand data and SME capacity.<\/p>\n<p>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\u2014not from prompt volume.<\/p>\n<h3>Prompt 34: Design a Hub-and-Spoke Cluster<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou are building topical coverage around a pillar theme.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Seed topic<\/li>\n<li>Keyword clusters<\/li>\n<li>Existing URLs<\/li>\n<li>Business priorities<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDesign a hub-and-spoke topic cluster map using only my inputs.\nAssign pillar vs supporting roles.\nDo not invent traffic potential.\nFlag cannibalization risks.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nCluster map with URL roles and cannibalization flags.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nReview against live inventory; merge overlaps before assigning writers.<\/p>\n<h3>Prompt 35: Pillar Page Outline From Cluster<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nThe pillar URL needs an outline that supports spokes.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Pillar target queries<\/li>\n<li>Spoke list<\/li>\n<li>Unique expertise notes<\/li>\n<li>Internal link rules<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nOutline a pillar page that summarizes the topic and routes to spokes.\nAvoid duplicating full spoke content.\nDo not invent statistics.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPillar outline with spoke routing sections and source placeholders.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nEnsure each spoke has a distinct angle before drafting the pillar.<\/p>\n<h3>Prompt 36: Spoke Differentiation Matrix<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nSupporting articles risk overlapping.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Spoke titles\/angles<\/li>\n<li>Primary keywords<\/li>\n<li>Audience segments<\/li>\n<li>Product touches<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nBuild a differentiation matrix for spokes so each page owns a unique job.\nRecommend merges where angles collide.\nDo not invent demand metrics.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nMatrix of unique angles plus merge recommendations.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nEditorial lead signs off that no two briefs share the same job.<\/p>\n<h3>Prompt 37: Cluster Publish Order Planner<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need a publish sequence based on dependencies\u2014not fake urgency.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Cluster map<\/li>\n<li>Dependencies (definitions before advanced)<\/li>\n<li>Capacity<\/li>\n<li>Known launch dates<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose a publish order based on conceptual dependencies and capacity.\nDo not promise ranking lift from order alone.\nCall out parallelizable work.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nOrdered backlog with dependency notes and parallel tracks.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm SME and design bottlenecks before locking dates.<\/p>\n<h3>Prompt 38: Cluster Internal Link Blueprint<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want linking rules for a new cluster.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Pillar and spoke URLs\/titles<\/li>\n<li>Anchor style guide<\/li>\n<li>Crawl depth concerns<\/li>\n<li>Related non-cluster pages<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate an internal linking blueprint for this cluster using only listed URLs.\nSuggest contextual placements.\nDo not invent URLs.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nLink blueprint with from\u2192to\u2192anchor guidance using real URLs.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nImplement in CMS and crawl to confirm links resolve.<\/p>\n<h3>Prompt 39: Refresh vs New Page in a Cluster<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nUnclear whether to update an old URL or create new.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Existing URL performance notes<\/li>\n<li>New keyword targets<\/li>\n<li>Content overlap summary<\/li>\n<li>Redirect constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRecommend refresh vs new URL for the scenario below.\nDo not invent traffic forecasts.\nList evidence still needed to decide.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDecision with evidence gaps and implementation caveats (redirects, canonicals).<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nCheck GSC history and inbound links before creating duplicates.<\/p>\n<h3>Prompt 40: Cluster Coverage Gap Audit<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want gaps vs a competitor set you researched.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Your cluster map<\/li>\n<li>Competitor outline notes<\/li>\n<li>Must-cover entities<\/li>\n<li>Out-of-scope topics<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nAudit topical coverage gaps from my notes.\nDo not invent competitor authority metrics.\nSeparate nice-to-have vs must-cover for our ICP.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nGap list prioritized by ICP relevance with out-of-scope exclusions.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nReject gaps that do not serve your ICP even if competitors cover them.<\/p>\n<h3>Prompt 41: Entity and Concept Coverage Planner<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want entity completeness without stuffing.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Topic<\/li>\n<li>Known entities\/products<\/li>\n<li>SME glossary<\/li>\n<li>Audience level<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose which entities\/concepts the cluster should explain, define, or merely mention.\nDo not invent entity relationships you cannot justify from my notes.\nMark SME-required definitions.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nEntity coverage plan with define\/mention levels and SME flags.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nSME reviews entity list for accuracy and missing critical concepts.<\/p>\n<h3>Prompt 42: Cluster Brief Bundle Generator<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need consistent briefs across many spokes.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Cluster map<\/li>\n<li>Brand voice<\/li>\n<li>Proof library notes<\/li>\n<li>CTA rules<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nGenerate a brief template filled for each spoke listed.\nKeep uniqueness per spoke.\nDo not invent citations or metrics; use [SOURCE NEEDED].\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPer-spoke brief drafts with shared template fields and unique angles.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nHuman editor checks uniqueness and source markers before assignment.<\/p>\n<h3>Prompt 43: AI-Search Citation Readiness for Clusters<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want clusters that are clear, attributable, and useful\u2014not spammy AI bait.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Cluster pages list<\/li>\n<li>Original data\/expertise available<\/li>\n<li>FAQ candidates<\/li>\n<li>Source policies<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nSuggest how to strengthen this cluster for people-first clarity and citation-worthy specificity.\nDo not claim AI Overview placement.\nFocus on structure, evidence, and uniqueness from my assets.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nAction list for clarity, evidence, and unique assets\u2014without citation guarantees.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nEnsure every factual claim has a source or SME owner before publish.<\/p>\n<h2>AI Prompts for SEO Content Writing \u2014 Prompts 44\u201358<\/h2>\n<p>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.<\/p>\n<p>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\u2014and risky\u2014pattern. Prefer fewer distinctive pages over many interchangeable ones.<\/p>\n<p>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\u2014regardless of how polished it sounds.<\/p>\n<h3>Prompt 44: SEO Content Brief From Research Pack<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nResearch is ready and you need a writer-ready brief.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Brief-input pack<\/li>\n<li>SERP notes<\/li>\n<li>Brand voice<\/li>\n<li>Internal URLs for linking<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate a complete SEO content brief from the research pack.\nInclude outline, entities, FAQs, internal links from my URL list only, and [SOURCE NEEDED] markers.\nDo not invent statistics or competitor metrics.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nWriter-ready brief with sources\/assumptions clearly marked.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nStrategist approves outline against SERP notes before drafting.<\/p>\n<h3>Prompt 45: First Draft in Clean HTML<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have an approved brief and need a first draft.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Approved brief<\/li>\n<li>Source notes<\/li>\n<li>Examples\/SME quotes if any<\/li>\n<li>HTML constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nWrite a first draft in clean HTML using p, h2, h3, ul, ol, li, strong, em, a only as needed.\nDo not invent metrics, quotes, or case results.\nUse [SOURCE NEEDED] placeholders.\nFlag assumptions at the top.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDraft HTML with placeholders and assumption list.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nSME fact-check all claims; replace placeholders before publish.<\/p>\n<h3>Prompt 46: People-First Angle Finder<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nDrafts feel generic; you need a distinctive angle from real expertise.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Topic<\/li>\n<li>First-hand experience notes<\/li>\n<li>Customer stories you can share<\/li>\n<li>Constraints on claims<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose people-first angles grounded only in the experience notes I provide.\nReject thin, scaled, or doorway-style approaches.\nDo not invent case studies.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nAngle options with required proof from your notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nPick an angle only if you can supply the promised examples.<\/p>\n<h3>Prompt 47: Outline Quality Review<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want to pressure-test an outline before writing.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Outline<\/li>\n<li>Target query<\/li>\n<li>SERP notes<\/li>\n<li>Audience<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nReview this outline for intent match, redundancy, missing subtopics vs my SERP notes, and fluff risk.\nDo not invent SERP features I did not mention.\nSeparate observations from recommended outline edits.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nCritique with specific add\/remove\/reorder suggestions.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nCompare revised outline to live SERP needs once more.<\/p>\n<h3>Prompt 48: Expert Quote and Example Insertion Plan<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need to plan where original expertise enters the draft.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Draft or outline<\/li>\n<li>SME availability<\/li>\n<li>Approved anecdotes<\/li>\n<li>Data you can publish<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nMark sections that need original examples, screenshots, or SME quotes.\nDo not invent expert statements.\nProvide interview questions for the SME.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nAnnotation plan plus SME question list.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nSchedule SME interview; do not publish with fabricated quotes.<\/p>\n<h3>Prompt 49: Simplify Complex SEO Explanations<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nTechnical explanations are too dense for the audience.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Draft section<\/li>\n<li>Audience level<\/li>\n<li>Terms that must remain precise<\/li>\n<li>Examples allowed<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRewrite the section for clarity without losing accuracy.\nDo not add new factual claims.\nCall out any simplification that risks technical incorrectness.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nClearer rewrite with accuracy-risk notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nTechnical reviewer confirms no meaning was lost.<\/p>\n<h3>Prompt 50: FAQ Draft From Real Questions<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have real customer\/SERP questions to answer.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Question list with sources<\/li>\n<li>Product facts<\/li>\n<li>Legal limits<\/li>\n<li>Link targets<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDraft FAQ answers from my question list and facts.\nDo not invent questions or metrics.\nMark answers needing citations.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nFAQ set with citation flags and suggested internal links from your list.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nVerify each question\u2019s origin; remove unverified invented FAQs if any appear.<\/p>\n<h3>Prompt 51: Comparison Article Guardrails Draft<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou are drafting a comparison\/alternative article responsibly.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Products in scope<\/li>\n<li>Criteria you can measure<\/li>\n<li>Disallowed claims<\/li>\n<li>Affiliate\/disclosure rules if any<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDraft a fair comparison structure and sample sections using only allowed claims.\nDo not invent benchmarks or awards.\nInsert disclosure placeholders where needed.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nComparison draft sections with disclosure and claim limits observed.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nCompliance review before publish; verify every comparative claim.<\/p>\n<h3>Prompt 52: Refresh Rewrite With Changelog<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nAn older article needs updating with known changes.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Current draft<\/li>\n<li>Outdated claims list<\/li>\n<li>New facts<\/li>\n<li>Performance notes you provide<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose a refresh rewrite plan and revise priority sections.\nDo not invent performance improvements.\nPreserve unique assets worth keeping.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nSection-level refresh plan and revised copy for priority parts.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nDiff against live page; confirm redirects\/canonicals if URL strategy changes.<\/p>\n<h3>Prompt 53: Brand Voice Pass<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nDraft is accurate but off-voice.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Draft<\/li>\n<li>Voice guide<\/li>\n<li>Examples of on-brand copy<\/li>\n<li>Words to avoid<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRewrite for brand voice without changing factual meaning.\nList any places where voice and compliance may conflict.\nDo not add new claims.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nOn-voice rewrite plus conflict flags.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nBrand editor spot-checks terminology and tone.<\/p>\n<h3>Prompt 54: Eliminate AI Fluff and Repetition<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nDraft has repetitive filler.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Draft HTML<\/li>\n<li>Required points from brief<\/li>\n<li>Length guidance if any<\/li>\n<li>Must-keep examples<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nEdit to remove fluff and repetition while keeping required brief points.\nDo not delete unique evidence.\nSummarize what you removed and why.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nTighter draft with removal log.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm all brief-required points remain after edits.<\/p>\n<h3>Prompt 55: Source and Citation Pass<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need claims mapped to sources before legal\/editorial review.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Draft<\/li>\n<li>Available sources<\/li>\n<li>Claim risk levels<\/li>\n<li>Citation style<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nMap factual claims to sources I provided or mark [SOURCE NEEDED].\nDo not invent citations.\nList high-risk unsupported claims.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nClaim\u2013source map and unsupported claim list.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nReplace or remove unsupported claims; keep a source log.<\/p>\n<h3>Prompt 56: CTA and Journey Alignment Edit<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nContent should guide next steps without spammy CTAs.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Draft<\/li>\n<li>Desired next step<\/li>\n<li>Available offers<\/li>\n<li>Audience stage<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nSuggest CTA placements and wording aligned to stage and offer.\nDo not invent discount percentages or urgency unless provided.\nAvoid manipulative patterns.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nCTA plan with stage-appropriate wording.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConversion owner approves offers; remove false urgency.<\/p>\n<h3>Prompt 57: Multi-Author Consistency Editor<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nSeveral writers drafted sections that feel inconsistent.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Section drafts<\/li>\n<li>Glossary<\/li>\n<li>Style rules<\/li>\n<li>Primary brief<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nHarmonize terminology, structure, and tone across sections.\nDo not invent missing facts to fill gaps\u2014flag them.\nPreserve distinct examples.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nUnified draft with terminology glossary updates and gap flags.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nLead editor confirms consistency; SMEs fill gaps.<\/p>\n<h3>Prompt 58: Publish Readiness Scorecard<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nFinal QA before CMS publish.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Final draft<\/li>\n<li>Brief<\/li>\n<li>Compliance checklist<\/li>\n<li>Asset list (images, links)<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nScore publish readiness across accuracy, intent match, sources, links, and people-first quality.\nDo not invent SEO scores from tools.\nList blockers vs nice-to-have fixes.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nReadiness scorecard with blockers clearly listed.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nDo not publish until blockers are resolved by owners.<\/p>\n<h2>AI Prompts for On-Page SEO \u2014 Prompts 59\u201370<\/h2>\n<p>On-page prompts refine titles, metas, headings, intros, keyword naturalness, alt text, slugs, trust cues, thin-content diagnosis, answer passages, and UX\/CTA clarity\u2014without 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.<\/p>\n<p>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.<\/p>\n<p>For YMYL or regulated topics, use the E-E-A-T cues prompt only with real credentials and editorial policies\u2014never fabricated author expertise. Clear answer passages help readers; they are not a guarantee of featured snippets.<\/p>\n<h3>Prompt 59: Title Tag Options<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need multiple title candidates within your rules.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Primary query<\/li>\n<li>Page angle<\/li>\n<li>Brand rules<\/li>\n<li>Character guidance you use<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nWrite multiple title tag options.\nDo not invent CTR predictions.\nAvoid unsupported claims and keyword stuffing.\nSeparate observations about the current title (if provided) from recommendations.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nTitle variants with notes on tradeoffs\u2014not predicted CTR.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nPick candidates that match on-page H1\/promise; test in GSC over time.<\/p>\n<h3>Prompt 60: Meta Description Options<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need accurate meta descriptions.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Page summary<\/li>\n<li>Primary query<\/li>\n<li>CTA allowed<\/li>\n<li>Compliance limits<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nWrite meta description options that accurately reflect the page.\nDo not invent offers or social proof.\nNo CTR guarantees.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDescription variants aligned to real page content.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nEnsure the chosen description matches visible content.<\/p>\n<h3>Prompt 61: H1 and Heading Hierarchy Audit<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nHeading structure may be messy or stuffed.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Current headings<\/li>\n<li>Target intent<\/li>\n<li>Brief outline<\/li>\n<li>Brand rules<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nAudit heading hierarchy for clarity and intent match.\nPropose revised H1\/H2\/H3 without stuffing.\nDo not invent ranking impact.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nHeading critique and revised outline.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nImplement and verify single clear H1 in the template.<\/p>\n<h3>Prompt 62: Intro Rewrite for Clarity<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nThe intro fails to establish relevance quickly.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Current intro<\/li>\n<li>Target audience<\/li>\n<li>Page promise<\/li>\n<li>Proof you can state<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRewrite the introduction for clarity and intent match.\nDo not invent statistics.\nKeep claims limited to provided proof.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nRevised intro with assumption notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nUser-test with a teammate unfamiliar with the draft.<\/p>\n<h3>Prompt 63: Keyword Placement Naturalness Check<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want natural language\u2014not stuffing.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Draft<\/li>\n<li>Primary\/secondary terms<\/li>\n<li>Terms to avoid overusing<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nReview keyword usage for naturalness.\nSuggest edits that preserve meaning.\nDo not impose a fake keyword density target.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nEdits that reduce stuffing while keeping clarity.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nRead aloud; confirm secondaries appear only where useful.<\/p>\n<h3>Prompt 64: Image Alt Text Patterning<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need helpful alt text patterns for a page set.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Image list with context<\/li>\n<li>Decorative vs informative flags<\/li>\n<li>Brand rules<\/li>\n<li>Accessibility notes<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDraft alt text for informative images and mark decorative ones.\nDo not keyword-stuff alt attributes.\nDo not invent image contents not described.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nAlt text set with decorative exclusions.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nAccessibility review; confirm alts describe the image purpose.<\/p>\n<h3>Prompt 65: URL Slug Recommendations<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou are choosing or refining a slug.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Page topic<\/li>\n<li>Primary term<\/li>\n<li>Existing URL constraints<\/li>\n<li>Redirect willingness<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRecommend slug options and discuss change risks if a URL already exists.\nDo not invent ranking benefits of short slugs.\nAsk for current inbound link notes if missing.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nSlug options with change-risk notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nAvoid unnecessary renames; plan redirects if changing.<\/p>\n<h3>Prompt 66: On-Page E-E-A-T Cues Check<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want visible trust cues without fake credentials.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Page draft<\/li>\n<li>Author bio facts<\/li>\n<li>Editorial policy links<\/li>\n<li>Reviewer availability<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nSuggest on-page trust cues based only on real credentials and policies I provide.\nDo not invent author expertise or awards.\nFlag YMYL-sensitive sections needing review.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nTrust-cue recommendations grounded in real bios\/policies.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nVerify every credential on the live about\/author pages.<\/p>\n<h3>Prompt 67: Thin Content Diagnosis<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nA page may be thin or overlapping others.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Page copy<\/li>\n<li>Related URLs<\/li>\n<li>Purpose statement<\/li>\n<li>Performance notes you provide<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDiagnose thin or overlapping content issues from my materials.\nRecommend expand, merge, redirect, or noindex hypotheses.\nDo not invent indexation counts.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDiagnosis with action hypotheses and evidence still needed.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm with crawl\/GSC before merging or noindexing.<\/p>\n<h3>Prompt 68: Snippet-Worthy Passage Polish<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want clearer definition\/answer passages\u2014not snippet bait spam.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Target questions<\/li>\n<li>Draft sections<\/li>\n<li>Facts allowed<\/li>\n<li>HTML constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPolish concise, accurate answer passages for key questions.\nDo not guarantee featured snippets.\nKeep answers faithful to provided facts.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nClear answer passages with source fidelity notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nEnsure answers appear on-page and match full context.<\/p>\n<h3>Prompt 69: On-Page CTA and UX Copy Audit<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nSEO copy may conflict with UX clarity.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Page copy<\/li>\n<li>Primary conversion<\/li>\n<li>Form fields<\/li>\n<li>Objections<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nAudit on-page copy for UX clarity around the conversion.\nSeparate SEO observations from UX recommendations.\nDo not invent conversion benchmarks.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nUX\/SEO copy audit with prioritized edits.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nRun past design\/CRO owners before major layout claims.<\/p>\n<h3>Prompt 70: Finalize On-Page Checklist for URL<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nPre-publish on-page QA for one URL.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Final page content<\/li>\n<li>Targets<\/li>\n<li>Assets<\/li>\n<li>Template limitations<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nProduce a final on-page SEO checklist applied to this URL.\nMark pass\/fail\/unknown.\nDo not invent tool scores.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nFilled checklist with unknowns called out.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nResolve fails; re-crawl the URL after publish.<\/p>\n<h2>AI Prompts for Internal Linking \u2014 Prompts 71\u201378<\/h2>\n<p>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\u2014using only URLs you provide. Never let a model invent destinations or link-equity scores.<\/p>\n<p>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.<\/p>\n<p>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 \u201cclick here\u201d text.<\/p>\n<h3>Prompt 71: Contextual Link Suggestions for a Draft<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou are editing a draft and have a URL inventory.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Draft<\/li>\n<li>URL inventory with titles\/topics<\/li>\n<li>Anchor style rules<\/li>\n<li>Max links guidance<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nSuggest contextual internal links using only my URL inventory.\nProvide anchor, target, and placement note.\nDo not invent URLs or link-equity metrics.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nLink suggestions table constrained to real URLs.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nClick each target; remove forced or irrelevant links.<\/p>\n<h3>Prompt 72: Orphan Page Rescue Plan<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nCrawl shows orphan or near-orphan URLs.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Orphan URL list<\/li>\n<li>Topical parents<\/li>\n<li>Traffic notes you provide<\/li>\n<li>Navigation constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose internal linking and IA fixes for orphan URLs.\nDo not invent crawl counts beyond my data.\nPrioritize by business relevance using my notes.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nRescue plan with parent pages and link placements.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nImplement links and re-crawl to confirm discovery.<\/p>\n<h3>Prompt 73: Hub Page Link Module Copy<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nA hub needs clearer links to supporting pages.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Hub draft<\/li>\n<li>Spoke list<\/li>\n<li>User journey notes<\/li>\n<li>Design constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDraft link module copy that helps humans navigate spokes.\nAvoid generic 'click here'.\nDo not invent popularity rankings for spokes.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDescriptive link module copy mapped to spokes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nUX review for scannability on mobile\/desktop.<\/p>\n<h3>Prompt 74: Anchor Text Diversity Review<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nAnchors may be over-optimized or vague.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>List of existing anchors to a URL<\/li>\n<li>Target page topic<\/li>\n<li>Style guide<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nReview anchor text patterns and recommend natural diversity.\nDo not invent penalty claims.\nFlag manipulative exact-match overuse based on the list provided.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nAnchor review with rewrite suggestions.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nUpdate highest-risk anchors; avoid automated mass changes blindly.<\/p>\n<h3>Prompt 75: Breadcrumb Label Recommendations<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nBreadcrumb labels need clarity for IA.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>IA tree<\/li>\n<li>Current breadcrumb labels<\/li>\n<li>Primary categories<\/li>\n<li>Constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRecommend breadcrumb labels that match IA and user language.\nDo not invent schema eligibility outcomes.\nAsk for missing parent nodes if the tree is incomplete.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nBreadcrumb label set aligned to IA.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nImplement consistently in templates; validate HTML structure.<\/p>\n<h3>Prompt 76: Cross-Cluster Linking Opportunities<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nTwo clusters should connect where journeys overlap.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Cluster A map<\/li>\n<li>Cluster B map<\/li>\n<li>Shared audience journeys<\/li>\n<li>URL lists<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose selective cross-cluster links that help users\u2014not link spam.\nUse only listed URLs.\nExplain user-job rationale for each.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nSelective cross-links with journey rationale.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nLimit to high-relevance pairs; verify in content context.<\/p>\n<h3>Prompt 77: Internal Link QA After Publish<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nA batch of pages shipped and needs link QA.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>New URLs<\/li>\n<li>Intended link blueprint<\/li>\n<li>Crawl snippet or link list<\/li>\n<li>Known broken links<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nQA internal links against the blueprint.\nList missing, broken, or low-relevance links from my data.\nDo not invent sitewide PageRank effects.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nQA report of missing\/broken\/low-relevance links.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nFix issues; confirm in crawler and browser.<\/p>\n<h3>Prompt 78: Navigation vs Contextual Linking Balance<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nStakeholders want everything in global nav.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Current nav<\/li>\n<li>Priority pages<\/li>\n<li>Analytics nav usage if provided<\/li>\n<li>Design limits<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nAdvise what belongs in global nav vs contextual linking.\nDo not invent UX best-practice statistics.\nProtect usability while supporting discovery of key SEO pages.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nNav vs contextual recommendations with usability rationale.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nAlign with design system; user-test nav changes.<\/p>\n<h2>AI Prompts for Technical SEO \u2014 Prompts 79\u201393<\/h2>\n<p>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\u2014they do not replace crawlers or staging checks.<\/p>\n<p>Pair them with a disciplined <a href=\"https:\/\/www.krishandev.com\/expertise\/technical-seo\">technical SEO<\/a> 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.<\/p>\n<p>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.<\/p>\n<h3>Prompt 79: Crawl Issue Triage<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou pasted crawl findings and need prioritization.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Crawl export or issue list<\/li>\n<li>Site priorities<\/li>\n<li>Dev capacity<\/li>\n<li>Examples of affected URLs<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nTriage crawl issues by severity and likely user\/bot impact based on my export.\nDo not invent issue counts not in the data.\nDraft developer tickets with acceptance criteria.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nSeverity-ranked triage plus ticket drafts.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nVerify top issues in browser\/crawler before sprint planning.<\/p>\n<h3>Prompt 80: Indexation Troubleshooting Guide<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nPages are not indexed or are unexpectedly indexed.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>URL examples<\/li>\n<li>robots\/meta\/canonical notes<\/li>\n<li>GSC coverage notes you provide<\/li>\n<li>CMS settings<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nBuild a troubleshooting path for indexation using my notes.\nDo not invent coverage counts.\nSeparate observations from recommended checks.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nStep-by-step troubleshooting tree grounded in supplied clues.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm each step in GSC and on live HTML.<\/p>\n<h3>Prompt 81: Canonical Strategy Review<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nCanonicals may conflict across templates.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Sample HTML canonicals<\/li>\n<li>Parameter URL examples<\/li>\n<li>Duplicate groups<\/li>\n<li>Desired primary URLs<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nReview canonical strategy from samples.\nDo not invent sitewide duplicate counts.\nRecommend consistent rules and test cases.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nCanonical ruleset + test cases.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nQA on staging across templates and parameters.<\/p>\n<h3>Prompt 82: Redirect Mapping QA<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nA migration or URL cleanup needs redirect checks.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Old\u2192new map<\/li>\n<li>Known chains\/loops list<\/li>\n<li>Critical URLs<\/li>\n<li>Analytics notes if any<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nQA this redirect map for chains, loops, and risky many-to-one collapses.\nDo not invent hit counts.\nPropose test plan.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nRedirect QA findings and test plan.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nCrawl old URLs; verify final status codes and destinations.<\/p>\n<h3>Prompt 83: robots.txt Review<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need a careful robots.txt interpretation.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Full robots.txt<\/li>\n<li>Environments (prod\/staging)<\/li>\n<li>Intent for private areas<\/li>\n<li>Known accidental blocks<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nReview robots.txt for risky blocks or overly broad rules.\nDo not claim Googlebot behavior beyond documented norms and my file.\nAsk clarifying questions about intentional disallows.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nRisk review with recommended rule changes and questions.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nTest with robots testers and monitor GSC after changes.<\/p>\n<h3>Prompt 84: XML Sitemap Recommendations<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nSitemaps may include the wrong URLs.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Sitemap samples or URL lists<\/li>\n<li>Indexation goals<\/li>\n<li>Pagination\/facet notes<\/li>\n<li>Lastmod policy if any<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRecommend sitemap inclusion\/exclusion rules from my inputs.\nDo not invent sitemap index counts.\nProvide QA checks.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nInclusion rules and QA checklist.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nValidate sitemap URLs resolve and match canonicals.<\/p>\n<h3>Prompt 85: Core Web Vitals Interpretation<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have CWV lab\/field summaries to interpret.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>CWV report excerpts<\/li>\n<li>Template list<\/li>\n<li>Recent releases<\/li>\n<li>Device mix notes<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nInterpret CWV summaries and propose investigation hypotheses.\nDo not invent lab scores beyond my paste.\nSeparate observations from remediation ideas.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nInterpretation + investigation hypotheses by template.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm with field data and profiling tools before large rebuilds.<\/p>\n<h3>Prompt 86: JavaScript Rendering Risk Notes<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nCritical content may depend on JS rendering.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Sample URLs<\/li>\n<li>What content is JS-dependent<\/li>\n<li>Framework notes<\/li>\n<li>Crawl tool rendered HTML snippets<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nAssess SEO risks from JS-dependent content using my snippets.\nDo not invent rendering outcomes for URLs you cannot see.\nRecommend verification steps.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nRisk assessment and verification steps.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nCompare raw vs rendered HTML in your crawler for key templates.<\/p>\n<h3>Prompt 87: Pagination and Faceted Navigation Rules<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nFilters\/facets may create index bloat.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Facet examples<\/li>\n<li>Parameter list<\/li>\n<li>Desired indexable landing pages<\/li>\n<li>Current robots\/canonical behavior<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose indexation rules for pagination and facets from my examples.\nDo not invent crawl budget numbers.\nHighlight UX vs SEO tradeoffs.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nFacet\/pagination rules with tradeoff notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nImplement carefully; monitor index coverage after changes.<\/p>\n<h3>Prompt 88: Hreflang Draft Review<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nInternational URL pairs need hreflang sanity checks.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Locale URL mapping<\/li>\n<li>Sample hreflang markup<\/li>\n<li>Known mismatches<\/li>\n<li>x-default policy<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nReview hreflang mapping and samples for common errors.\nDo not invent international traffic.\nList validation tests.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nError list + validation tests for hreflang.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nValidate in GSC international reports and HTML samples.<\/p>\n<h3>Prompt 89: Status Code Pattern Explainer<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nLogs or crawls show confusing status patterns.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Status code samples<\/li>\n<li>URL patterns<\/li>\n<li>CDN\/app notes<\/li>\n<li>Expected behavior<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nExplain likely causes of these status patterns from my notes.\nDo not invent log volumes.\nRecommend confirmations with ops\/dev.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nCause hypotheses and confirmation steps.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nValidate with server\/CDN owners before content changes.<\/p>\n<h3>Prompt 90: Structured Data Draft (JSON-LD)<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want JSON-LD candidates for a page type.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Page type<\/li>\n<li>Visible entity fields<\/li>\n<li>Disallowed invented fields<\/li>\n<li>CMS constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDraft JSON-LD using only provided entity fields.\nDo not invent ratings, prices, stock, or credentials.\nList validation checks before deploy.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nJSON-LD draft + validation checklist.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nTest with rich results tools; ensure markup matches visible content.<\/p>\n<h3>Prompt 91: Log File Sample Analysis Assist<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have a sample of bot hit lines to interpret.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Log sample<\/li>\n<li>Known bots of interest<\/li>\n<li>Release timeline<\/li>\n<li>Suspected problem URLs<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nAnalyze the log sample for patterns worth investigating.\nDo not extrapolate sitewide rates from a small sample without stating limits.\nSeparate observations from recommendations.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPattern notes with sampling caveats and next pulls to request.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nRequest fuller logs for confirmed patterns before major changes.<\/p>\n<h3>Prompt 92: Security Header \/ HTTPS SEO Notes<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nHTTPS or mixed content issues may affect UX and trust.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Issue list<\/li>\n<li>Affected templates<\/li>\n<li>CDN\/WAF notes<\/li>\n<li>User impact reports<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nExplain SEO-relevant implications of these HTTPS\/mixed-content notes.\nDo not invent ranking impacts.\nPrioritize user-security fixes and verification steps.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPrioritized fix list with verification steps\u2014no ranking promises.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nFix mixed content; verify with browser security tools.<\/p>\n<h3>Prompt 93: Technical SEO Ticket Bundle<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nEngineering needs a clean sprint bundle.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Prioritized issues<\/li>\n<li>Acceptance criteria needs<\/li>\n<li>Environments<\/li>\n<li>Rollback notes<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nTurn prioritized technical SEO issues into a sprint-ready ticket bundle.\nInclude test plans and rollback considerations.\nDo not invent severity beyond my prioritization.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nTicket bundle with tests and rollback notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nEng lead reviews estimates; QA executes test plans on staging.<\/p>\n<h2>AI Prompts for SEO Audits \u2014 Prompts 94\u2013103<\/h2>\n<p>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.<\/p>\n<p>Findings must come from evidence you collected\u2014not from confident-sounding guesses. A good audit separates severity, user impact, and sequencing, then attaches verification steps for each remediation wave.<\/p>\n<p>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 \u201cdone\u201d means verified, not merely ticketed. Never mass-disavow from an AI summary alone.<\/p>\n<h3>Prompt 94: Full SEO Audit Scope Builder<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou are starting an audit and need a scoped plan.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Site type<\/li>\n<li>Business goals<\/li>\n<li>Access available<\/li>\n<li>Timebox<\/li>\n<li>Known incidents<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nBuild a scoped SEO audit plan with workstreams and evidence required.\nDo not invent findings before data.\nInclude out-of-scope boundaries.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nScoped audit plan with evidence checklist and boundaries.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nAlign scope with stakeholders before crawling or reviewing content.<\/p>\n<h3>Prompt 95: Content Audit Framework<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need to audit a content inventory.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>URL inventory<\/li>\n<li>Performance exports you provide<\/li>\n<li>Purpose tags<\/li>\n<li>Conversion definitions<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDesign and apply a content audit framework to my inventory sample.\nDo not invent metrics not in exports.\nRecommend keep\/improve\/merge\/retire hypotheses.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nAudited sample with action hypotheses and data gaps.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nValidate retire\/merge decisions with analytics and stakeholders.<\/p>\n<h3>Prompt 96: Technical Audit Executive Summary<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nEngineers and execs need a plain-language summary of technical findings.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Technical findings list<\/li>\n<li>Business impact notes<\/li>\n<li>Capacity<\/li>\n<li>Timeline constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nWrite an executive summary of technical SEO findings from my list.\nSeparate severity, user impact, and recommended sequence.\nNo traffic guarantees.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nExec summary with sequenced recommendations and assumptions.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nEnsure every severity label maps to a verified finding.<\/p>\n<h3>Prompt 97: On-Page Audit Sampling Plan<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nThe site is large; you must sample intelligently.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Template list<\/li>\n<li>Traffic tiers you provide<\/li>\n<li>Risk areas<\/li>\n<li>Sample size constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate a sampling plan for on-page audits across templates and tiers.\nDo not invent traffic tiers.\nExplain how findings will\/won't generalize.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nSampling plan with generalization caveats.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nExecute sample; avoid over-generalizing to unsampled templates.<\/p>\n<h3>Prompt 98: Backlink Profile Review Assist<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou exported backlink sample data for review.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Backlink export sample<\/li>\n<li>Disavow policy notes<\/li>\n<li>Known campaigns<\/li>\n<li>Risk tolerance<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nReview the backlink sample for patterns and risks using only provided data.\nDo not invent domain ratings beyond the export.\nRecommend investigation steps\u2014not automatic mass disavow.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPattern\/risk notes with investigation steps.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nManually review flagged domains before any disavow action.<\/p>\n<h3>Prompt 99: Analytics and Tracking Audit Questions<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nSEO decisions may be skewed by broken tracking.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Tracking setup notes<\/li>\n<li>Known anomalies<\/li>\n<li>Conversion list<\/li>\n<li>Consent mode notes if any<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nGenerate an analytics\/tracking audit question list for SEO reliability.\nDo not invent tracking bugs.\nPrioritize questions that unblock SEO measurement.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPrioritized tracking QA questions and likely owners.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nAnalytics owner answers questions with evidence from the property.<\/p>\n<h3>Prompt 100: Competitive Audit Synthesis<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou collected competitor evidence and need synthesis.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Competitor notes<\/li>\n<li>Your strengths\/weaknesses<\/li>\n<li>SERP screenshots notes<\/li>\n<li>Business constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nSynthesize a competitive SEO audit narrative from my evidence.\nDo not invent competitor traffic or link metrics.\nList plays that fit our constraints.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nCompetitive synthesis with constrained play list.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nVerify each competitor claim against your saved evidence.<\/p>\n<h3>Prompt 101: Local\/Multi-Location Audit Checklist<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nMulti-location sites need specialized audit checks.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Location list<\/li>\n<li>NAP sources<\/li>\n<li>Landing page samples<\/li>\n<li>GBP access notes<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate a multi-location SEO audit checklist and apply it to samples I provide.\nDo not invent review scores or rankings.\nFlag duplicate\/thin location pages.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nChecklist + sample findings for locations provided.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nVerify NAP consistency in real citations\/GBP; fix thin pages carefully.<\/p>\n<h3>Prompt 102: Ecommerce SEO Audit Focus Areas<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nStore SEO audits need catalog-aware focus.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Platform notes<\/li>\n<li>Facet rules<\/li>\n<li>Indexation samples<\/li>\n<li>Category\/product templates<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nBuild an ecommerce SEO audit focus list tailored to my platform notes.\nDo not invent index bloat counts.\nPrioritize template-level risks.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nEcommerce audit focus areas with template risk priorities.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm findings on staging\/production samples per template.<\/p>\n<h3>Prompt 103: Audit Remediation Roadmap<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nFindings exist; you need a remediation roadmap.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Findings with severities<\/li>\n<li>Owners available<\/li>\n<li>Dependencies<\/li>\n<li>Deadlines if any<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nTurn audit findings into a remediation roadmap with waves.\nDo not promise ranking recovery dates.\nInclude verification steps per wave.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPhased remediation roadmap with verification per wave.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nTrack completion in tickets; re-audit after each wave.<\/p>\n<h2>AI Prompts for Local SEO \u2014 Prompts 104\u2013113<\/h2>\n<p>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.<\/p>\n<p>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 <a href=\"https:\/\/www.krishandev.com\/expertise\/local-seo\">local SEO expertise<\/a>.<\/p>\n<p>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\u2014prompts in this section refuse that path.<\/p>\n<h3>Prompt 104: Local Landing Page Outline<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou need a unique local service page outline.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>NAP<\/li>\n<li>Services<\/li>\n<li>Service area<\/li>\n<li>Local proof points<\/li>\n<li>Photos\/team facts<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate a local landing page outline using only supplied local proof.\nDo not invent reviews, rankings, or citations.\nEnsure uniqueness vs generic city spam patterns.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nUnique local outline grounded in real proof points.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nReject outlines that could be spun across cities without new proof.<\/p>\n<h3>Prompt 105: GBP Post Drafts From Updates<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have real business updates for GBP posts.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Updates\/offers you can honor<\/li>\n<li>Dates<\/li>\n<li>Photos available<\/li>\n<li>CTA destinations<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDraft GBP posts from real updates only.\nDo not invent offers or urgency.\nKeep posts accurate and useful.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nGBP post drafts tied to real updates and dates.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nConfirm offers\/inventory before scheduling posts.<\/p>\n<h3>Prompt 106: Review Theme Response Templates<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou summarized review themes and need response guidance.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Review themes (not fake reviews)<\/li>\n<li>Tone guide<\/li>\n<li>Escalation rules<\/li>\n<li>Privacy constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCreate response templates by theme using my rules.\nDo not invent review quotes or star ratings.\nInclude escalation paths.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nTheme-based response templates with escalation notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nTrain staff; personalize each response; never fabricate reviews.<\/p>\n<h3>Prompt 107: Local Citation Consistency Checklist<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nNAP consistency needs a practical checklist.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Canonical NAP<\/li>\n<li>Known directories list<\/li>\n<li>Brand variants<\/li>\n<li>Phone\/hours rules<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nBuild a citation consistency checklist and cleanup workflow.\nDo not invent citation lists beyond what I provide.\nPrioritize high-risk mismatches.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nCitation QA checklist and cleanup workflow.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nVerify each listing manually; track changes in a sheet.<\/p>\n<h3>Prompt 108: Service Area Pages Decision Help<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nUnclear whether service-area pages are justified.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>True service areas<\/li>\n<li>Staffing reality<\/li>\n<li>Existing pages<\/li>\n<li>Proof available per area<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nAdvise when service-area pages are justified vs thin doorway risk.\nDo not invent local search volumes.\nRequire proof standards per area.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDecision framework with proof standards and spam-risk warnings.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nOnly build pages where real service + proof exist.<\/p>\n<h3>Prompt 109: Local Schema Fields Assistant<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want LocalBusiness schema fields filled accurately.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Business entity details<\/li>\n<li>Opening hours<\/li>\n<li>SameAs links<\/li>\n<li>Departments if any<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose LocalBusiness JSON-LD fields from provided details only.\nDo not invent ratings or review counts.\nList missing required info.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nSchema field map + missing info list.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nValidate markup; ensure it matches visible NAP.<\/p>\n<h3>Prompt 110: Multi-Location Page Differentiation<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nLocation pages are too similar.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Location-specific facts<\/li>\n<li>Shared boilerplate<\/li>\n<li>Services differences<\/li>\n<li>Team\/photos<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nRewrite differentiation guidance so each location page has unique substance.\nDo not invent local awards or stats.\nIdentify boilerplate to cut.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nPer-location unique content plan and boilerplate cuts.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nPublish only when each page has real unique details.<\/p>\n<h3>Prompt 111: Local Competitor SERP Notes Interpreter<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou saved map pack \/ local SERP notes.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>SERP\/map notes<\/li>\n<li>Your GBP categories<\/li>\n<li>Services<\/li>\n<li>Differentiators<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nInterpret local SERP notes into action hypotheses.\nDo not invent map pack rankings.\nSeparate pack vs organic observations.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nLocal SERP interpretation with testable hypotheses.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nRe-check pack results by location\/device before acting.<\/p>\n<h3>Prompt 112: Local SEO Reporting Narrative<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nMonthly local metrics need a careful narrative.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>GBP insights you export<\/li>\n<li>GSC local pages data<\/li>\n<li>Call\/direction metrics if any<\/li>\n<li>Changes shipped<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nWrite a local SEO monthly narrative from my metrics only.\nDo not invent calls or direction counts.\nLabel hypotheses about cause.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nNarrative with cited metrics and labeled hypotheses.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nReconcile numbers to source exports before sending to clients.<\/p>\n<h3>Prompt 113: Local Spam Avoidance Review<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nSomeone proposed scaled city pages or keyword-stuffed GBP categories.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Proposed tactics<\/li>\n<li>Business reality<\/li>\n<li>Policy concerns you know<\/li>\n<li>Existing footprint<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nReview proposed local tactics for spam\/doorway risk and people-first issues.\nDo not provide advice that encourages fake locations or review gating abuse.\nRecommend safer alternatives based on real service capacity.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nRisk review with safer alternatives grounded in real operations.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nReject tactics that create fake locations or manipulative reviews.<\/p>\n<h2>AI Prompts for Ecommerce SEO \u2014 Prompts 114\u2013121<\/h2>\n<p>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\u2014always tied to catalog truth.<\/p>\n<p>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 <a href=\"https:\/\/www.krishandev.com\/expertise\/ecommerce-seo\">ecommerce SEO<\/a>.<\/p>\n<p>Treat experiments as hypotheses with stop conditions. Do not ship \u201cAI category intros\u201d that invent specs shoppers cannot verify on the PDP. Keep editorial guides and product pages complementary, not competing for the same primary job.<\/p>\n<h3>Prompt 114: Category Page Copy From Product Data<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nCategory copy is thin or manufacturer-duplicated.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Category purpose<\/li>\n<li>Product attributes<\/li>\n<li>Audience<\/li>\n<li>Facets available<\/li>\n<li>Prohibited claims<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDraft category copy from product\/category data.\nDo not invent specs, prices, or stock.\nSupport shoppers without duplicating every facet URL.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nHelpful category copy with assumption\/source notes.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nMerchandising review for accuracy; check duplicate content risk.<\/p>\n<h3>Prompt 115: Product Description Enrichment<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nPDP content is sparse but you have attributes.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Attribute table<\/li>\n<li>Brand voice<\/li>\n<li>Compliance limits<\/li>\n<li>Unique selling points you can prove<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nEnrich product description using attributes and approved USPs only.\nDo not invent certifications or performance claims.\nMark missing attributes to request from vendors.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nEnriched PDP copy + missing attribute requests.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nCompare to physical product\/specs sheet before publish.<\/p>\n<h3>Prompt 116: Faceted Navigation SEO Ruleset<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nFilters create many URLs.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Facet list<\/li>\n<li>Indexable landing needs<\/li>\n<li>Platform capabilities<\/li>\n<li>Current canonical\/robots behavior<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose a faceted navigation SEO ruleset for this catalog.\nDo not invent crawl budget figures.\nInclude examples of allow vs noindex vs canonical.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nFacet ruleset with examples and tradeoffs.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nImplement with eng; monitor indexation after release.<\/p>\n<h3>Prompt 117: Out-of-Stock SEO Handling Options<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nSKU availability changes and SEO handling is unclear.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>OOS policies possible<\/li>\n<li>Similar product linking<\/li>\n<li>Seasonality notes<\/li>\n<li>Platform constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nCompare SEO handling options for OOS products using my constraints.\nDo not invent revenue impacts.\nRecommend UX-first approaches.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nOOS handling options with UX\/SEO tradeoffs.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nPick a policy; document redirects\/canonicals; test templates.<\/p>\n<h3>Prompt 118: Collection Internal Linking for Catalogs<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nCollections need smarter cross-links.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Collection list<\/li>\n<li>Top products<\/li>\n<li>Affinity notes from merchandising<\/li>\n<li>URL inventory<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nSuggest collection and PDP internal links from my inventory and merchandising notes.\nDo not invent bestseller ranks unless provided.\nKeep links helpful for shoppers.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nLink suggestions aligned to merchandising reality.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nMerch confirms affinities; avoid irrelevant cross-sell spam.<\/p>\n<h3>Prompt 119: Ecommerce Schema Field Audit<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nProduct schema may be incomplete or inaccurate.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Sample product fields<\/li>\n<li>Current JSON-LD<\/li>\n<li>Pricing source of truth<\/li>\n<li>Review policy<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nAudit product schema fields against provided data.\nDo not invent aggregate ratings.\nList mismatches and safe fixes.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nSchema mismatch list and safe fix recommendations.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nValidate with testing tools; sync price\/availability to feed\/CMS.<\/p>\n<h3>Prompt 120: PDP vs Blog Content Boundaries<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nContent team overlaps commercial PDPs and editorial guides.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>PDP goals<\/li>\n<li>Editorial goals<\/li>\n<li>Shared keywords<\/li>\n<li>IA constraints<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nClarify content boundaries between PDPs and editorial to reduce cannibalization.\nDo not invent traffic splits.\nPropose internal linking between the two.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nBoundary rules + linking patterns for PDP vs editorial.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nApply to overlapping URLs; adjust targets in the keyword map.<\/p>\n<h3>Prompt 121: Ecommerce SEO Experiment Backlog<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou want test ideas\u2014not guaranteed wins.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Current issues<\/li>\n<li>Platform limits<\/li>\n<li>Analytics capability<\/li>\n<li>Past test notes<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose an ecommerce SEO experiment backlog with hypotheses and required metrics.\nDo not promise uplift.\nInclude stop conditions.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nExperiment backlog with hypotheses and stop conditions.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nRun tests with proper measurement; document outcomes honestly.<\/p>\n<h2>AI Prompts for SEO Reporting and Analysis \u2014 Prompts 122\u2013129<\/h2>\n<p>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\u2014without inventing metrics or promising outcomes.<\/p>\n<p>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.<\/p>\n<p>Close every month with actions that feed the next sprint: refreshes, technical tickets, cluster gaps, or tests\u2014not 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.<\/p>\n<h3>Prompt 122: Monthly SEO Executive Narrative<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nYou have monthly tables and need a clear story.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>GSC\/analytics tables<\/li>\n<li>Shipped changes<\/li>\n<li>Known incidents<\/li>\n<li>Goals<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nTurn my monthly SEO tables into an executive narrative.\nCite only provided numbers.\nLabel hypotheses vs facts.\nNo ranking promises.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nExecutive narrative with cited metrics and labeled hypotheses.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nReconcile every number to the source export before sending.<\/p>\n<h3>Prompt 123: Anomaly Detection Notes<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nA metric moved unexpectedly.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Metric time series you provide<\/li>\n<li>Release calendar<\/li>\n<li>Seasonality notes<\/li>\n<li>Tracking changes<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nList plausible anomaly causes from my context.\nDo not invent external events I did not mention.\nRank investigations by likelihood given provided clues.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nInvestigation list ranked by likelihood with evidence needed.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nProve\/disprove top causes with logs, GSC, and release notes.<\/p>\n<h3>Prompt 124: Channel Posture Report Section<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nSEO must be reported beside paid\/social carefully.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Channel metrics you provide<\/li>\n<li>Shared landing pages<\/li>\n<li>Attribution notes<\/li>\n<li>Caveats<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nWrite a channel posture section that respects attribution limits in my notes.\nDo not invent assisted-conversion math.\nState uncertainty clearly.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nBalanced channel section with uncertainty stated.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nMarketing ops reviews attribution language.<\/p>\n<h3>Prompt 125: Experiment Results Write-Up<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nAn SEO test concluded and needs honest documentation.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Hypothesis<\/li>\n<li>Design<\/li>\n<li>Results table<\/li>\n<li>Confounders<\/li>\n<li>Decision<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nWrite an experiment results document from my inputs.\nDo not overclaim causality.\nInclude limitations and next steps.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nResults write-up with limitations and decision recorded.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nStore in knowledge base; share raw data with stakeholders.<\/p>\n<h3>Prompt 126: KPI Tree and Diagnostic Metrics<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nLeadership wants fewer vanity metrics.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Business goal<\/li>\n<li>Available metrics<\/li>\n<li>Leading activities<\/li>\n<li>Data gaps<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nPropose a KPI tree linking activities \u2192 diagnostics \u2192 outcomes using available metrics only.\nDo not invent benchmarks.\nHighlight gaps.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nKPI tree with diagnostics and gap list.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nAgree definitions in writing; instrument gaps.<\/p>\n<h3>Prompt 127: Client-Friendly Audit Follow-Up Report<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nAfter an audit, clients need progress reporting.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Original findings<\/li>\n<li>Completed fixes<\/li>\n<li>Open items<\/li>\n<li>Verification evidence<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDraft a follow-up report showing progress against audit findings.\nDo not claim ranking recovery.\nShow verification evidence placeholders for me to fill.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nProgress report structure with evidence slots.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nAttach real screenshots\/crawl proofs before delivery.<\/p>\n<h3>Prompt 128: Search Console Query Deep Dive<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nA query set needs interpretation.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Query table<\/li>\n<li>Landing pages<\/li>\n<li>Changes shipped<\/li>\n<li>Cannibalization notes<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nDeep-dive my GSC query table into insights and action hypotheses.\nDo not invent impressions not in the table.\nSeparate brand vs non-brand if I labeled them.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nQuery insights with action hypotheses tied to pages.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nValidate page changes in staging\/prod; re-measure later.<\/p>\n<h3>Prompt 129: Quarterly SEO Strategy Review Deck Outline<\/h3>\n<p><strong>Use this when:<\/strong><br \/>\nQuarter end needs a strategy review outline.<\/p>\n<p><strong>Provide this context:<\/strong><\/p>\n<ul>\n<li>Quarter goals<\/li>\n<li>Results tables<\/li>\n<li>Learnings<\/li>\n<li>Next-quarter proposals<\/li>\n<li>Risks<\/li>\n<\/ul>\n<p><strong>Prompt:<\/strong><\/p>\n<pre><code>You are an experienced SEO professional.\nOutline a quarterly SEO strategy review deck.\nUse only my results.\nInclude learnings, stops, and asks without guarantees.\n\nRules:\n- Do not invent keyword volumes, rankings, traffic, or crawl findings unless data is provided.\n- State assumptions clearly.\n- Separate observations from recommendations.\n- Ask for missing information when needed.<\/code><\/pre>\n<p><strong>Expected output:<\/strong><br \/>\nDeck outline with evidence slots and clear asks.<\/p>\n<p><strong>Validate by:<\/strong><br \/>\nFill with verified data; remove speculative slides.<\/p>\n<h2>How to Combine These Prompts Into an SEO Workflow<\/h2>\n<p>Use a simple loop: define the job (strategy prompts) \u2192 export data from tools \u2192 cluster and label intent \u2192 build or refine topic clusters \u2192 brief and draft with sources \u2192 on-page and internal links \u2192 technical checks \u2192 ship \u2192 report and refresh. Skip steps only when you already have verified artifacts sitting in your project folder.<\/p>\n<p>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.<\/p>\n<ol>\n<li>Lock goals and constraints with strategy prompts so success definitions are shared.<\/li>\n<li>Run keyword and intent prompts on real exports; freeze primary page targets.<\/li>\n<li>Plan clusters before scaling content production; remove overlapping spokes early.<\/li>\n<li>Brief, draft, and fact-check with writing prompts; keep [SOURCE NEEDED] visible.<\/li>\n<li>Apply on-page and internal linking prompts before publish using a real URL inventory.<\/li>\n<li>Triage technical risks with crawl and Search Console evidence; ticket what engineering must own.<\/li>\n<li>Audit periodically; remediate in waves with verification after each wave.<\/li>\n<li>Report with cited numbers; feed learnings into refreshes and the next roadmap.<\/li>\n<\/ol>\n<p>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.<\/p>\n<p>For model-specific workflow tips, read the practical guide to <a href=\"https:\/\/www.krishandev.com\/blog\/claude-for-seo\/\">using Claude for SEO<\/a>\u2014the same validation rules apply across assistants. Swap models if you like; do not swap away evidence requirements.<\/p>\n<p>Document your team\u2019s \u201cdefinition of done\u201d 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.<\/p>\n<h2>Common Mistakes When Using AI SEO Prompts<\/h2>\n<p>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:<\/p>\n<ul>\n<li>Asking for keyword volumes without pasting tool data<\/li>\n<li>Treating invented SERP analysis as fact<\/li>\n<li>Publishing first drafts without SME or compliance review<\/li>\n<li>Generating near-duplicate location or affiliate pages at scale<\/li>\n<li>Ignoring technical debt while only producing more content<\/li>\n<li>Letting the model invent URLs, citations, reviews, or ratings<\/li>\n<li>Confusing schema or meta tweaks with guaranteed rich results or CTR<\/li>\n<li>Skipping measurement after publishing<\/li>\n<li>Assuming one AI tool ranks content better than another<\/li>\n<li>Using prompts to replace strategy instead of accelerating it<\/li>\n<li>Automating publish pipelines without originality and accuracy gates<\/li>\n<li>Copying competitor outlines blindly without differentiation or proof<\/li>\n<\/ul>\n<p>When you catch a mistake, fix the prompt pack and the checklist\u2014not only the single page. Libraries improve when teams record failure modes.<\/p>\n<p>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.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How many SEO prompts do I need day to day?<\/h3>\n<p>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.<\/p>\n<h3>Do AI SEO prompts work with ChatGPT, Claude, and Gemini?<\/h3>\n<p>Yes\u2014these 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.<\/p>\n<h3>Can prompts replace Ahrefs, Semrush, or Screaming Frog?<\/h3>\n<p>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 \u2192 AI analysis \u2192 human decision \u2192 implementation \u2192 measurement again.<\/p>\n<h3>Will using these prompts guarantee rankings or traffic?<\/h3>\n<p>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.<\/p>\n<h3>Is AI-generated content allowed for SEO?<\/h3>\n<p>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.<\/p>\n<h3>How do I validate AI SEO output quickly?<\/h3>\n<p>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\u2014not a finding.<\/p>\n<h3>Should I automate publishing from prompts?<\/h3>\n<p>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\u2014not a growth plan.<\/p>\n<h3>Where should beginners start in this library?<\/h3>\n<p>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.<\/p>\n<h3>How should agencies adapt these prompts for clients?<\/h3>\n<p>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.<\/p>\n<h2>Final Takeaway<\/h2>\n<p>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.<\/p>\n<p>Use these 110+ prompts to accelerate strategy, research, content, on-page work, technical triage, audits, local and ecommerce tasks, and reporting\u2014while keeping people-first standards at the center of your <a href=\"https:\/\/www.krishandev.com\/solutions\/search-visibility\">search visibility<\/a> program.<\/p>\n<p>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\u2014and let humans remain accountable for what goes live.<\/p>\n<p>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.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Get 100+ practical AI SEO prompts for keyword research, content, on-page SEO, technical SEO, local SEO, ecommerce audits, and reporting\u2014with guidance on when to use each prompt and how to validate output.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,9],"tags":[],"class_list":["post-102","post","type-post","status-publish","format-standard","hentry","category-ai-seo","category-seo","category-technical-seo"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO &amp; SEO Audits - Krishan Dev<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO &amp; SEO Audits - Krishan Dev\" \/>\n<meta property=\"og:description\" content=\"Get 100+ practical AI SEO prompts for keyword research, content, on-page SEO, technical SEO, local SEO, ecommerce audits, and reporting\u2014with guidance on when to use each prompt and how to validate output.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/\" \/>\n<meta property=\"og:site_name\" content=\"Krishan Dev\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-18T12:27:44+00:00\" \/>\n<meta name=\"author\" content=\"admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"90 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/complete-seo-prompts\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/complete-seo-prompts\\\/\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/#\\\/schema\\\/person\\\/9d33ce274ad83f0cb7022a00a9f42afe\"},\"headline\":\"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO &#038; SEO Audits\",\"datePublished\":\"2026-09-18T12:27:44+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/complete-seo-prompts\\\/\"},\"wordCount\":10119,\"commentCount\":0,\"articleSection\":[\"AI SEO\",\"SEO\",\"Technical SEO\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/complete-seo-prompts\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/complete-seo-prompts\\\/\",\"url\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/complete-seo-prompts\\\/\",\"name\":\"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO & SEO Audits - Krishan Dev\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/#website\"},\"datePublished\":\"2026-09-18T12:27:44+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/#\\\/schema\\\/person\\\/9d33ce274ad83f0cb7022a00a9f42afe\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/complete-seo-prompts\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/complete-seo-prompts\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/complete-seo-prompts\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO &#038; SEO Audits\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/\",\"name\":\"Krishan Dev\",\"description\":\"AI SEO Expert | Technical SEO | Digital Marketing\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/#\\\/schema\\\/person\\\/9d33ce274ad83f0cb7022a00a9f42afe\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/055f02e024ca34dba0f2cd0ca37cff0b7ecdb52a09aacc58acab7e6022fe3267?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/055f02e024ca34dba0f2cd0ca37cff0b7ecdb52a09aacc58acab7e6022fe3267?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/055f02e024ca34dba0f2cd0ca37cff0b7ecdb52a09aacc58acab7e6022fe3267?s=96&d=mm&r=g\",\"caption\":\"admin\"},\"sameAs\":[\"https:\\\/\\\/www.krishandev.com\\\/blog\"],\"url\":\"https:\\\/\\\/www.krishandev.com\\\/blog\\\/author\\\/admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO & SEO Audits - Krishan Dev","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/","og_locale":"en_US","og_type":"article","og_title":"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO & SEO Audits - Krishan Dev","og_description":"Get 100+ practical AI SEO prompts for keyword research, content, on-page SEO, technical SEO, local SEO, ecommerce audits, and reporting\u2014with guidance on when to use each prompt and how to validate output.","og_url":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/","og_site_name":"Krishan Dev","article_published_time":"2026-09-18T12:27:44+00:00","author":"admin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"admin","Est. reading time":"90 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/#article","isPartOf":{"@id":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/"},"author":{"name":"admin","@id":"https:\/\/www.krishandev.com\/blog\/#\/schema\/person\/9d33ce274ad83f0cb7022a00a9f42afe"},"headline":"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO &#038; SEO Audits","datePublished":"2026-09-18T12:27:44+00:00","mainEntityOfPage":{"@id":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/"},"wordCount":10119,"commentCount":0,"articleSection":["AI SEO","SEO","Technical SEO"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/","url":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/","name":"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO & SEO Audits - Krishan Dev","isPartOf":{"@id":"https:\/\/www.krishandev.com\/blog\/#website"},"datePublished":"2026-09-18T12:27:44+00:00","author":{"@id":"https:\/\/www.krishandev.com\/blog\/#\/schema\/person\/9d33ce274ad83f0cb7022a00a9f42afe"},"breadcrumb":{"@id":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.krishandev.com\/blog\/complete-seo-prompts\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.krishandev.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Complete SEO Prompts: 100+ AI Prompts for Keyword Research, Content, Technical SEO, On-Page SEO, Local SEO &#038; SEO Audits"}]},{"@type":"WebSite","@id":"https:\/\/www.krishandev.com\/blog\/#website","url":"https:\/\/www.krishandev.com\/blog\/","name":"Krishan Dev","description":"AI SEO Expert | Technical SEO | Digital Marketing","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.krishandev.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.krishandev.com\/blog\/#\/schema\/person\/9d33ce274ad83f0cb7022a00a9f42afe","name":"admin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/055f02e024ca34dba0f2cd0ca37cff0b7ecdb52a09aacc58acab7e6022fe3267?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/055f02e024ca34dba0f2cd0ca37cff0b7ecdb52a09aacc58acab7e6022fe3267?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/055f02e024ca34dba0f2cd0ca37cff0b7ecdb52a09aacc58acab7e6022fe3267?s=96&d=mm&r=g","caption":"admin"},"sameAs":["https:\/\/www.krishandev.com\/blog"],"url":"https:\/\/www.krishandev.com\/blog\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.krishandev.com\/blog\/wp-json\/wp\/v2\/posts\/102","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.krishandev.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.krishandev.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.krishandev.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.krishandev.com\/blog\/wp-json\/wp\/v2\/comments?post=102"}],"version-history":[{"count":0,"href":"https:\/\/www.krishandev.com\/blog\/wp-json\/wp\/v2\/posts\/102\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.krishandev.com\/blog\/wp-json\/wp\/v2\/media?parent=102"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.krishandev.com\/blog\/wp-json\/wp\/v2\/categories?post=102"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.krishandev.com\/blog\/wp-json\/wp\/v2\/tags?post=102"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}