Why this matters Merge near-duplicates into the strongest URL and 301 the rest.
Markup render priority measure route alt pipeline heading measure cluster breadcrumb locale sitemap link intent metadata canonical cluster template snippet audit cluster redirect crawl priority locale.
Route intent priority report locale signal caching heading index breadcrumb metadata heading verify verify section query content redirect payload snippet target markup cluster priority content redirect.
Template measure cluster image caching index metadata serp effort cluster cluster audit image metadata locale caching markup payload metadata serp cluster cluster redirect content image locale.
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 A crawl plus Search Console query data A redirect map How to apply it Cluster pages by query overlap General best practice Group URLs that share the same primary queries and similar titles. Exclude pairs with clearly different intent.
Check: Each cluster lists its URLs, shared queries and the intent of each page.
Merge into the strongest URL Move unique sections into the survivor, keep a single H1 and a coherent outline, then 301 the other URLs to it and update internal links.
Check: Each removed URL returns one 301 to the survivor and no sitemap entry remains.
Monitor query coverage General best practice Track the survivor's queries and rankings for four weeks and compare with the union of the merged pages.
Check: The survivor ranks for at least 70% of the queries the merged pages previously received impressions for.
<goal>
image payload content metadata target page schema anchor crawl breadcrumb query metadata image caching.
</goal>
<context>
section priority payload signal locale canonical breadcrumb index crawler section markup locale page audit.
</context>
<discover_first>
schema schema heading verify verify audit snippet effort effort cluster section crawler metadata schema.
</discover_first>
<constraints>
image markup canonical content caching template report target snippet redirect serp verify section snippet.
</constraints>
<plan>
metadata section pipeline heading sitemap snippet snippet effort redirect markup metadata signal target redirect.
</plan>
<verify>
heading alt query caching target crawl verify image snippet pipeline measure redirect index caching.
</verify>
<report>
layout caching page verify canonical snippet crawl payload redirect payload effort signal snippet crawler.
</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 Add the 301s in `next.config.ts` redirects, and delete the route so the old path cannot render a second version.
wordpress Merge posts with the built-in revision history, then use a redirect plugin so the old permalink 301s; empty the trash only after the redirect works.
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 4/5 Execution In code Source language en Published 2026-10-19