Find usefulness decay, not merely traffic decay
Usefulness decay is the gap between what a page now provides and what its intended visitor needs. It can come from changed facts, regulations, pricing, interfaces, screenshots, availability, terminology, or decision criteria. An older evergreen explanation may still be accurate and satisfying, so age alone is not a reason to edit. In Search Console, compare a seasonally comparable period and inspect page clicks, impressions, click-through rate, and associated queries. Combine that with conversion friction, support questions, broken-link reports, and owner knowledge. Each signal is a lead, not a verdict: search data varies by view and user context.
Review incorrect instructions, broken destinations, risky claims, and pages affecting high-value decisions before optimizing modest traffic losses.
Capture the URL, audience job, baseline dates and metrics, evidence to check, proposed action, reviewer, and release owner.
Preserve intent before rewriting
Search intent is the job a person is trying to complete: learn a process, compare options, solve an error, or reach a specific destination. State the page’s question, decision, and promised outcome in one sentence before editing. Inspect the queries and landing-page context that bring visitors, but do not turn one page into every related topic. Keep the central answer near the top and retain sections that still serve the job. If the topic has truly changed, create a new page or consolidate deliberately rather than forcing a different intent into a familiar URL.
Title, introductory answer, calls to action, and internal anchor text should set the same expectation.
Ask someone outside the draft to attempt the intended task and identify the first missing or confusing step.
Replace stale evidence and improve the next step
Inventory every date-sensitive claim, statistic, quote, screenshot, product detail, link, and procedural step. Open the original or official source for each material claim; replace, qualify, or remove what you cannot support. Add current prerequisites, decision criteria, precise steps, and examples that match the present experience. Do not pad the page to a supposed ideal length. Google’s guidance emphasizes original value, accurate facts, clear sourcing, and expertise rather than a preferred word count. Financial, legal, health, security, privacy, and payment content needs review by appropriately qualified owners; an SEO edit is not a compliance review.
Confirm images depict the described state, test key destinations, and replace dead or needlessly redirected links with direct relevant sources.
Keep an internal record of factual, editorial, design, and technical changes so later diagnosis and rollback are possible.
Keep the URL unless architecture requires a change
When the page still answers the same core need, retain its preferred URL. Check that it has a self-referencing canonical, internal links point directly to it, and the sitemap reflects the desired version. If two pages substantially duplicate one another, choose the stronger destination, move unique useful material into it, and retire the duplicate. If a durable new taxonomy or consolidation really requires a URL change, map every old URL to the closest equivalent destination and use a server-side permanent redirect where possible. Update internal links and canonical annotations, avoid redirect chains, and monitor both old and new URLs.
Canonical hints and sitemaps express a preference; use permanent redirects when deprecating a duplicate or moving a destination.
Plan a rollback owner and restore path for shared template, navigation, or routing changes. This is proactive uptime optimization, not outage monitoring.
Publish honestly and measure cautiously
Change a visible last-updated label and Article dateModified markup only for a substantive revision that makes currency useful to readers; retain the original publication date where appropriate. Google recommends datePublished and dateModified in ISO 8601 format with time-zone information for applicable article markup, but markup does not guarantee a search feature or ranking result. Preflight the rendered page, canonical, key links, forms, media, and sources before release. For a few changed URLs, URL Inspection can request recrawling; for many, submit a sitemap. Google says crawling may take days to weeks and neither route guarantees indexing or visibility.
Record the original page, intended change, page and query metrics, task or conversion measure, date range, and confounders such as seasonality or campaigns.
Compare comparable periods and look for coherent change in qualified clicks, relevant click-through rate, task completion, or support friction. Average position is not a promise, and rankings are dynamic.