Why this signal matters for Google
Content that ages without being reread loses trustworthiness. On fast-moving topics · technology, health, finance, regulation · a page that has not changed says at best that nobody is home, at worst that it is now wrong. A "best email tools" guide still showing 2023 pricing tells the reader everything. That is the Query Deserves Freshness principle: for some searches Google favours recent pages, because the right answer two years ago is not the right answer today.
A page revised regularly and visibly dated tells the reader two things at once. The information is current, and a competent human looks after it. Google's Quality Raters are trained to spot exactly that. They are people paid to grade page quality. Faced with a 2023 price or a screenshot of software that has since changed its interface, your expertise drops, however good the rest of the text is. Active monitoring of your field is what feeds each revision pass.
Updating works in two places. Machine side: Google comes back more often to a page that moves, the page becomes eligible for searches where recency matters, and the date you display finally matches the change Google detects in the code. Human side: a recent "Updated on" in the search results makes people click, and reassures the reader before the first line.
How to update old blog posts, in one rule: prove the freshness instead of announcing it. Replace stale figures, redo screenshots, swap dead sources, then date the pass. No new content to produce and no rare skill to hire · the best result-to-effort ratio on the board, and every pass compounds your main content quality. Every pass starts by reopening your cited sources and checking they still hold. A retracted study or a rate that moved makes your text wrong without you touching a comma.
The NeuroEEAT scoring grid (0-10)
Use this scale to grade your own important pages. Aim for at least 7 out of 10 on YMYL content and on pages that sell.
| Score | Description | Concrete indicators |
|---|---|---|
| 0-2 | Abandoned content | No visible date. Figures and screenshots are out of date, and the sources either no longer open or belong to another era. |
| 3-4 | Freshness on the surface | Only the publication date appears, or the date was changed while nothing moved in the text. |
| 5-6 | Occasional revision | An "Updated on" is visible and a few passages have genuinely been edited, but there is no regular rhythm. |
| 7-8 | Revision cycle in place | A revision calendar is followed, the list of changes is visible, and sources are checked at every pass. |
| 9-10 | Exemplary freshness | Revisions genuinely change the substance, they are dated and archived, the changelog is public, sources are under 12 months old, and your data ships before your competitors'. |
How to audit it on your site
The audit takes five steps. Start with your 10 busiest pages and the pages that sell.
- 01
List the dates on display
Look at each important page: does it show a last-revision date, separate from the publication date? Without a visible date the signal does nothing at all, however good the work behind it.
- 02
Compare the stated date with the real change
Put the displayed date next to the last substantive change, which you can find in your CMS history or on the Wayback Machine, a free site that archives older versions of pages. A gap that shows up every time reads as an attempt to game the system.
- 03
Spot what dates the page
Figures, prices, screenshots, tool names, year mentions such as "in 2024": list everything that ages the page against your will. It is usually three or four items per article, no more.
- 04
Check how old the sources are
References older than 18 months on a fast-moving topic weaken the whole page. Click every outbound link too: a dead link tells the reader nobody has reread this in a long time.
- 05
Score and plan
Give each page a score from 0 to 10, then rank them by traffic against staleness. Busy pages with a low score go first: that is where the refresh pays back the most.
How to activate or improve it
Three levels, depending on the rhythm you can realistically keep today.
A date and a minimal habit
- Display "Updated on [date]" at the top of the article, where the reader sees it straight away.
- Keep the publication date and the revision date separate: they are two different facts.
- Fix stale figures and dead links while you are already on the page.
- Update the existing page address, never a new one.
- Start with your 10 busiest pages, not the easiest ones.
An organised revision cycle
- Book a pass every three months on your important pages, in the calendar.
- Add a short visible list of changes, such as "Added 2026 figures, pricing checked".
- Replace sources older than 12 to 18 months with recent references.
- Redo screenshots and examples whenever the tool or product has changed.
- Fill in dateModified in the Article markup, the block of code that tells engines when the page changed.
Freshness that runs on its own
- Drive the revision queue by weighing each page's traffic against how stale it is.
- Publish and archive the version history, so a reader can see what changed and when.
- Set automatic alerts on data that expires: prices, rates, software versions.
- Systematically revisit your key pages after every Core Update, the major change Google makes to its algorithm.
- Publish your sector data before your competitors: the first version out is the one everybody cites.
5 common mistakes to avoid
Sector specifics
Freshness becomes close to mandatory
Regulations, dosages, rates: outdated information can genuinely harm the reader. Plan a pass every 3 to 6 months at most, reviewed by the expert who signs the article. On these topics a stale page does not just rank badly, it can push someone into a bad decision.
The product moves faster than the docs
Screenshots, pricing, feature names: all of it expires within months. The simplest fix is to hook content revision onto product releases, so the page changes when the software does. Otherwise your documentation describes a tool that no longer exists.
Prices and availability, continuously
Product pages and comparisons have to show real prices and real stock. A comparison with wrong prices does two kinds of damage at once: the reader stops believing you, and they do not buy.
Revise without rewriting everything
Even content that does not date deserves an annual pass: refreshed examples, recent sources, checked links. The revision date reassures the reader without you reworking the whole text.
Signals to activate in parallel
The update amplifies the signals it refreshes. Combine it with:
FAQ
How to update old blog posts without rewriting them from scratch?
Target the perishable 20%: figures, prices, screenshots, dated sources, year mentions. A focused 30 to 45 minute pass per page usually covers it. YMYL or technology content deserves that pass every 3 to 6 months. Timeless content needs it whenever the subject genuinely evolves, with at least one control pass a year.
Is changing only the date enough?
No. Google compares the displayed date with what actually changed on the page. Without a substantive change the effect is nil, and often negative: it looks like an attempt to game the system, and it gets treated as one.
Should you create a new URL for a major overhaul?
No. Update the existing URL so you keep its history and the links other sites have given you. A new URL starts from zero, and you end up with two pages competing on the same subject.
Should the revision date appear in the markup?
Yes. Fill in dateModified, alongside datePublished, in your Article markup. Google cross-checks three things: the date in the code, the date visible on the page and the change it detects itself. All three have to say the same thing.
Does updating really improve rankings?
On searches where recency matters, yes, often within weeks. On the rest the effect builds more slowly: Google comes back more often, the recent date in the results earns clicks, and the reader trusts you more.
Anonymized case study
Before · a page left as it was
After · 90 days of regular revision
Illustrative figures meant to show the typical progression of the signal. They do not come from a real client case and must be replaced with your own measurements before any external communication. The work modelled here: a pass every three months on the 30 busiest pages, a visible list of changes, refreshed sources and dateModified added to the markup, roughly 22 hours spread over a quarter, with no new content written.