Confirm the refresh trigger
Treat a page as a refresh candidate when dated facts, a changed offer, a stale source, a competitor shift, or a matched-period Search Console decline provides a concrete reason to investigate. A decline is a trigger, not a diagnosis: seasonality, technical changes, shifting demand, and changes in Google Search results can produce similar observations.
Google’s guidance for debugging Search traffic drops recommends comparing the affected period with a similar period and checking whether the change is limited to particular queries, URLs, countries, devices, search appearances, or search types.
Inventory the page before editing
Preserve a copy of the current page and record its content hash. Inventory factual claims, dates, citations, products or services, offers, screenshots, examples, external sources, internal links, and sections that still serve the reader’s task. Mark each item as keep, verify, replace, or remove.
Keep source observations separate from analysis and causal claims. A page-level SEO audit can identify technical or structural symptoms, but it does not by itself prove why performance changed.
Measure content decay with matched periods
In Google Search Console, filter to the exact canonical page and compare complete, matched periods. Review clicks, impressions, click-through rate, and average position, then segment the results by query, country, device, and search appearance. Weekly or monthly aggregation can reduce day-of-week noise when the comparison spans enough data.
The official Search Console comparison documentation explains these filters and cautions that query or URL filters can change totals because of data truncation and anonymized queries. Record the observed pattern without automatically attributing it to content decay.
Check current intent and coverage
Review the current results for the target query and identify the task, format, and topics that consistently satisfy search intent. Compare those findings with the page rather than copying competitors. Preserve accurate explanations and original detail; add coverage only where it resolves a verified reader need.
Use measured keyword research to distinguish a real intent change from a vocabulary gap. Google’s people-first content guidance emphasizes original value and warns against changing dates merely to make substantially unchanged pages appear fresh.
Replace stale facts with verified evidence
For every changed claim, record the old fact, its source and date, the replacement fact, and an approved primary source. If a claim cannot be verified, qualify or remove it instead of inventing a statistic, quotation, date, testimonial, or citation. Recheck current offers, product or service availability, examples, and screenshots as separate facts.
Update headings and structure when they clarify the workflow, and add contextual internal links where another page genuinely helps the reader. Google recommends crawlable links with descriptive anchor text; this site’s internal-linking guide provides a practical implementation checklist.
After a substantial update, align the visible update date with Article structured data. Google documents datePublished and dateModified as recommended Article properties for accurate date information.
Deploy, verify, and observe
Preview a bounded old/new diff before publishing. Patch only the approved file, retain the original as a rollback artifact, and verify the live HTTP response, canonical URL, rendered copy, source links, internal links, and structured data. Record the deployment and the exact final content hash.
After 28 complete post-deployment days, compare that 28-day period with the immediately preceding 28 days and, where sufficient history exists, the matched year-over-year period. Report changes in clicks, impressions, click-through rate, position, and affected queries as observations. A later increase or decline does not by itself establish that the refresh caused it.