Content refresh audit checklist

A content refresh is not a new date on an old page. It is a documented decision to keep, correct, expand, combine, redirect, or retire a URL after checking what people search for and whether the page still deserves to answer.

Start with evidence by URL. Then read the page. A spreadsheet can identify candidates, but it cannot tell you whether the recommendation, screenshot, price, regulation, source, or product behavior is still true.

Choose candidates from page and query evidence

Export at least the page, query, clicks, impressions, click-through rate, and average position from Google Search Console. Compare equivalent periods and note seasonality, campaigns, migrations, and tracking changes before calling a movement meaningful.

Google recommends looking at trends in impressions and clicks rather than treating average position as the main result. Search Console also assigns most performance data to the canonical URL. Check the canonical before comparing a URL that may redirect or duplicate another page.

Useful candidates include:

• a page with declining clicks or impressions for queries it previously served;
• a page receiving impressions for a useful query it answers only partially;
• two pages appearing for the same query with overlapping intent;
• a commercial guide with an outdated price, feature, rule, screenshot, or source;
• a page with strong impressions and weak CTR whose title or description no longer describes the answer;
• a page that still attracts visits but sends them to dead or irrelevant next steps.

Low traffic alone is not a deletion rule. A narrow page can be useful to a qualified buyer even when volume is small. Likewise, a high-traffic page may need urgent correction if the facts are wrong.

Record the reason for opening the audit. “Old” is not enough.

Identify the query the page actually serves

Read the queries beside the landing page. Group close variants by the job they represent: learn, compare, calculate, troubleshoot, choose a vendor, or take an action. Do not create a separate page for every wording.

Check whether the page's promise, heading, answer, and CTA still match that job. If the dominant query changed because Google began showing the page for a different need, decide whether that new need belongs on this URL. Do not force it in merely to preserve impressions.

Search Console omits some anonymized queries and stores only the most important rows. Treat its query table as evidence, not a complete record of demand.

Audit claims line by line

Mark every statement that could expire or be challenged. Prices, product capabilities, policies, laws, statistics, deadlines, availability, and vendor instructions need a current source or removal.

For each material claim, record:

• the sentence or section where it appears;
• the source URL and source owner;
• the date the source was checked;
• whether the source directly supports the claim;
• the person responsible for approval;
• the next review trigger.

Prefer the organization that owns the fact. Use product documentation for product behavior, an agency for its rule, and the original dataset for a statistic. A search result snippet is not a source.

If the old article cited a secondary summary and the primary source now exists, replace it. If sources disagree, narrow the claim or explain the disagreement. A confident paragraph does not repair weak evidence.

Decide what changes and what stays

Preserve accurate material that still helps the reader. Rewrite only where the answer, evidence, order, or next step improves.

The audit should end with one action:

• Keep: the page remains accurate and aligned; record the review without changing its public date.
• Correct: fix a specific error and note a correction when the mistake could have affected a decision.
• Refresh: materially improve facts, examples, structure, sources, or buyer guidance.
• Consolidate: merge overlapping pages into the strongest URL and redirect the weaker URLs.
• Reposition: change the query and promise only when the page can serve a distinct need without cannibalizing another page.
• Retire: remove a page that no longer has a valid purpose, then return the correct status or redirect to a genuinely equivalent destination.

Do not expand a short answer simply to make it longer. Add the missing decision criteria, evidence, boundary, example, or procedure. Delete repetition that has no job.

Recheck title, description, and opening answer

Google creates title links and snippets from several sources and may replace what you write. That is not a reason to ignore the title or meta description.

Make the title unique, specific, and consistent with the visible heading. Write a description that accurately summarizes the particular page. Google says snippets are primarily drawn from page content and may use the meta description when it describes the page better.

Read the first screen without the navigation. It should answer enough of the query to prove the page is relevant. Do not bury the actual answer behind a history lesson, a generic definition, or a sales pitch.

If CTR is weak, compare the query, title, snippet, and competing result types before changing copy. A low CTR can reflect intent mismatch, a SERP feature, brand familiarity, or a result that answers the question without a click. It does not prove the title is bad.

Repair internal links and the next action

Check links into the page as well as links out. A refreshed guide that remains buried is still hard to discover.

• Link from the relevant product, category, or hub page using descriptive anchor text.
• Replace links to redirected, removed, or obsolete resources.
• Add a next step that matches the page's intent: another guide, a calculator, a product detail, or a diagnostic.
• Remove CTAs for services, offers, or forms that no longer exist.
• Confirm that important content and links appear in the rendered HTML and work on mobile.

Keep a small link map in the audit record: sources into the page, destinations out, and the commercial next step. It makes future reviews faster.

Use an honest modified date

Change the visible “last updated” date only after a significant update. Google asks publishers to keep visible dates consistent with `datePublished` and `dateModified` structured data and says those dates must describe publication or substantial page updates.

Fixing a typo, changing a CTA color, or rerunning the build does not make the article new. Keep the original publication date. When the answer changes materially, show the modified date and preserve the publication date in structured data.

Keep a change log outside the article even when readers do not need a public list. Record the old and new claim, source, reviewer, publication commit, and date. That is more useful than a vague “updated for 2026” label.

Verify the refreshed page in production

Review the public URL, not only the draft. Confirm:

• HTTP response, canonical URL, indexability, title, description, and structured data;
• visible publication and modified dates;
• headings, lists, forms, images, alt text, and mobile layout;
• source links, internal links, and redirects;
• inclusion in the hub, sitemap, and any machine-readable content map;
• analytics and Search Console tracking where access is available.

Take a baseline before deployment. After publication, annotate the change and compare the same URL and query group. Check indexing in the first few days, early query movement after about a week, title and description behavior after two weeks, and contribution against baseline after four weeks. Those checkpoints are observations, not a promise that a refresh caused the movement.

The DATIK Content Engine keeps the source record, editorial review, build, publishing, and measurement in one operating cycle. The original research guide covers evidence other sites can reuse. A free diagnostic can audit one live page and produce the keep, refresh, consolidate, or retire decision before a larger content project starts.

Sources and review limits

• Google Search Console: performance report dimensions and data groupings
• Google Search Console: common performance-report tasks
• Google Search Central: control snippets
• Google Search Central: influence byline dates
• Google Search Central: helpful, reliable, people-first content

Sources were checked on October 16, 2026. Search Console data can be incomplete, delayed, anonymized, or aggregated to a canonical URL. This checklist does not promise that refreshing a page will improve rankings, traffic, citations, or conversions.