Outdated Content: How to Refresh It the Right Way

TL;DR The "Outdated Content" check fires when a page shows visible signs of staleness — old dates, references to years gone by, dead links, superseded tools, or advice that time has overtaken. This is a freshness problem, not a sourcing one: the facts may have had citations, they have simply aged out. The play is almost always to refresh in place, not delete, and to make the update genuine rather than a date swap.

Outdated content is the highest-leverage cheap win in most audits I run. You already rank, you already have links, you just look stale. A real refresh often recovers positions faster than a brand-new page ever earns them.

What this check flags

The crawler looks for staleness markers: a visible "Last updated" or publish date well in the past, body copy naming an old year ("the best tools for 2021"), broken outbound links, screenshots of interfaces that no longer exist, statistics with old vintages, and advice that references deprecated features or defunct products. When enough of these stack up, the issue fires. It is flagging the appearance and substance of age, not whether the page was well-sourced when written — that is a separate concern handled by the unsourced-claims check.

A real example and the fix

A marketing agency had a "Complete Guide to Facebook Ads" that ranked on page one and pulled steady traffic — but it was written in 2020, showed a 2020 date, referenced Power Editor (retired years ago), linked to two dead Facebook help pages, and used screenshots of an Ads Manager UI that had been redesigned twice since. Rankings were slipping quarter over quarter as fresher competitors moved up. The refresh was substantive, not cosmetic: current interface screenshots, the campaign structure updated to the present Ads Manager, dead links replaced with live ones, retired features removed, new sections on Advantage+ and iOS privacy changes, and a genuine "Last updated" date reflecting real editing. The temptation — just change the date to this year — is exactly the move to avoid; a stale page wearing a fresh date is a trust problem the moment a reader notices the 2020 screenshots. After the real refresh, the guide climbed back and held.

Staleness signals and what each one costs

Freshness vs. sourcing — and where E-E-A-T fits

Keep these two straight, because sites confuse them constantly. Outdated content is about age: the information was fine when published and has simply gone stale. Unsourced claims are about provenance: the information never showed where it came from, whatever its age. A page can be perfectly fresh and unsourced, or well-sourced but badly outdated. This check is the first kind. For the sourcing side, see Unsourced Claims.

Freshness connects to E-E-A-T through Trust — visibly stale advice on a money or health topic reads as neglected, and neglect erodes trust. But be precise about the mechanism: "freshness" is not a single ranking factor you dial up. Google's systems reward recency mainly where the query deserves it. On a breaking or fast-moving topic, Query Deserves Freshness favors newer results; on a stable topic, an older evergreen page can hold for years. The universal problem is not the date — it is substance that no longer matches reality. See Content Freshness for the full concept.

How to detect it

1. Sort your pages by publish date and scan the oldest tranche first — that is where staleness concentrates.
2. Search your content for past years ("2020," "2021") in titles and body copy; each hit is a candidate.
3. Run a broken-link check across the site — dead outbound links are a reliable age tell.
4. Spot-check screenshots and step-by-step instructions against the current version of whatever tool they document.
5. Cross-reference with rankings: pages that ranked well and are now sliding are your priority refresh queue.

How to fix it

Refresh in place; do not delete pages that still hold links and rankings. Update the substance first — current screenshots, live links, present-day figures, retired features removed, new developments added. Rewrite year-bound titles to the current year or make them evergreen. Only after real editing should you touch the visible "Last updated" date, and it should reflect genuine work, not a cosmetic bump. For content that is thin as well as stale, enrich it — add depth, examples, and current context rather than pruning it away. Then recrawl and watch the refreshed pages over the following weeks. See this refresh case study for a worked example.

FAQ

Can I just change the date to make a page look fresh?

No, and it can backfire. A fresh date on stale content is a trust problem the moment a reader hits an old screenshot or dead reference. Update the substance, then update the date to reflect real work.

Should I delete outdated pages instead of updating them?

Rarely. If a page still holds rankings and links, refreshing it recovers value far faster than deleting and starting over. Delete only truly obsolete pages with no traffic, no links, and no path to relevance.

How is this different from unsourced claims?

Outdated content is about information that has aged; unsourced claims is about information that never showed its origin. A page can be fresh but unsourced, or well-cited but badly outdated. Fix them with different plays.

Does every page need frequent updating?

No. Fast-moving topics benefit from recency because the query deserves freshness; stable evergreen topics can rank for years untouched. Update on the schedule the subject actually demands, not the calendar.

How often should I refresh a page?

When the substance drifts from reality — a tool changes, a stat updates, a link dies, guidance shifts. That is the trigger, not a fixed interval. Let the topic's pace set the cadence.

Related reading: the Content Freshness Score check quantifies how fresh a page reads, and the HubSpot content-pruning case study shows when refreshing crosses into removal territory.