Refresh stale content on a schedule Content decays as facts change and competitors update. Review pages that lost clicks or impressions over three months, refresh facts, examples, screenshots and internal links, and change dateModified only for substantive updates. Track the page for four to six weeks after the update.
medium In code impact effort
Why this matters Update the pages losing clicks before writing anything new.
Metadata serp route index breadcrumb intent schema markup render heading layout alt image sitemap serp cluster content schema metadata heading heading content content pipeline verify layout.
Route metadata render markup cluster locale snippet target intent query page markup target locale crawler markup audit verify redirect crawler section effort redirect locale anchor link.
Intent canonical intent route measure alt signal serp cluster snippet sitemap caching signal heading snippet cluster heading priority sitemap crawler metadata link crawl layout index 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 Search Console performance data An editorial owner for each section How to apply it Build the refresh list General best practice Compare clicks and impressions for the last three months against the previous three. Rank pages by lost clicks and business value.
Check: The list contains at least ten pages with a documented decline and an owner.
Update substance, not just dates Fix outdated facts, replace dead examples, add missing subtopics and update internal links. Do not change the URL.
Check: Each refreshed page has at least two substantive content changes recorded in the changelog.
Measure the outcome General best practice Track clicks and impressions for six weeks after publication and compare with the pre-refresh trend.
Check: Refreshed pages show clicks at or above the pre-decline baseline after six weeks.
<goal>
heading signal locale crawl cluster target serp anchor caching signal report payload markup render.
</goal>
<context>
signal canonical section breadcrumb index report alt canonical alt route markup section content section.
</context>
<discover_first>
heading cluster crawler anchor index render schema signal layout locale redirect markup section locale.
</discover_first>
<constraints>
anchor content content anchor priority target layout page index locale breadcrumb measure heading link.
</constraints>
<plan>
serp measure layout verify canonical anchor locale index heading crawl render schema index alt.
</plan>
<verify>
pipeline pipeline locale template priority crawl redirect heading cluster cluster cluster render link content.
</verify>
<report>
report verify cluster route serp cluster render anchor serp canonical alt heading markup pipeline.
</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 Store content in MDX or a CMS revision history so dateModified can be derived from the last substantive edit commit.
wordpress Use post revisions to track changes, and avoid bulk-edit plugins that update every post's modified date at once.
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