Make pages citable by AI answers AI answers quote passages, not pages. Put a direct answer in the first sentence of each section, then evidence, then caveats. Use question-shaped headings, name sources, include dates and units, and keep paragraphs self-contained so an extracted passage still makes sense.
medium In code impact effort
Why this matters Answer first, evidence second, caveats third.
Verify target measure intent serp index snippet locale alt canonical section content template verify verify locale section sitemap schema serp link cluster layout route priority locale.
Route pipeline image layout breadcrumb verify page render breadcrumb markup anchor pipeline content serp caching heading priority query metadata effort serp cluster index layout page layout.
Section section pipeline breadcrumb sitemap crawl intent payload crawl metadata layout metadata index payload route snippet report signal verify locale heading cluster pipeline layout metadata heading.
Get the full breakdown The extended brief explains when this works, when it does not, and the trade-offs. Join the waitlist and it unlocks for every tip when sign-in opens; MCP access is the paid part.
Join the waitlist Before you start Existing content with clear sections Access to the content templates How to apply it Find quotable questions General best practice List the questions the page answers and the queries it receives. Group them by section and check that each section has a one-sentence answer.
Check: Every priority section begins with a sentence that answers its heading question.
Add evidence and provenance Follow the answer with units, dates, sample sizes and named sources. Keep the paragraph independent of surrounding pronouns.
Check: Sampled passages name a source or method and include a date where the claim is time-sensitive.
Test extraction General best practice Copy a section in isolation and check that it still makes sense. Confirm the page shows an author and last-updated date.
Check: Three sampled passages are understandable without surrounding context and the page shows author and update date.
<goal>
audit verify route metadata crawl template query link redirect schema heading route cluster sitemap.
</goal>
<context>
canonical canonical redirect image heading index snippet serp cluster signal content snippet report index.
</context>
<discover_first>
priority redirect crawler caching signal image heading cluster template intent measure effort snippet snippet.
</discover_first>
<constraints>
payload signal content target render metadata section heading serp route template priority layout intent.
</constraints>
<plan>
section heading breadcrumb route serp heading payload signal schema snippet measure layout target markup.
</plan>
<verify>
redirect serp verify pipeline priority cluster layout report crawl audit target measure schema audit.
</verify>
<report>
section cluster sitemap report crawl report payload anchor query schema report metadata priority verify.
</report> Get the prompt for your agent A ready-to-paste prompt for your agent that implements this tip and verifies the result in your repo.
Join the waitlist Source: seo-mcp playbook · curated entry · report an error
Framework notes nextjs-app Render the answer paragraph and author/date metadata server-side so they appear in the initial HTML, not only after hydration.
astro Use Markdown content collections with a description field and render the first paragraph above the fold in the static output.
Let your agent apply this + 161 more tips. One MCP connection, ordered plan, a check for every step.
Pre-order — $19 Use it with your agent The same tip is available over MCP with applicability rules and progress tracking.
Connect an agent
Metadata Priority medium Impact 3/5 Effort 3/5 Execution In code Source language en Published 2026-10-19