SourceCited / Content freshness
Strategy · Maintenance
A stale statistic is worse than none — AI engines favor current, verifiable figures and can cite an outdated claim with your name on it. Keeping facts fresh is an ongoing discipline, not a one-time signal.
Facts, statistics, prices, and version claims decay, and in AI search a confidently stale figure is worse than none — engines favor recent, verifiable numbers and can cite an outdated claim as current. Keep content factually fresh, not just signal-fresh: date time-sensitive claims, audit for aging figures quarterly, update in place (keeping the URL), and refresh honestly — date-gaming without real changes backfires.
A page is not finished when you publish it. Facts, statistics, prices, version numbers, and "as of" claims all decay, and in AI search a confidently stale figure is worse than no figure: engines increasingly favor recent, specific, verifiable numbers, and a page that states a 2023 statistic as current fact is exactly what gets filtered, demoted, or — worse — cited wrong, putting an outdated claim about your topic into an AI answer with your name on it. Freshness is not just a ranking signal to game; it is the ongoing discipline of keeping your content true.
Signal freshness is telling engines the page is current (honest dateModified, a visible "last updated" date). Factual freshness is the page actually being current. This guide is mostly about the second — because the first without the second is just date-gaming, which the March 2026 core update specifically demoted.
Not everything ages at the same rate. Knowing what rots fastest tells you what to audit first:
| Content type | Decay speed | Watch for |
|---|---|---|
| Statistics & percentages | Fast | Any figure with a year; "X% of" claims; anything vendor-published |
| Prices & costs | Fast | Tool pricing, API rates, plan tiers — these move monthly |
| Product/version names & features | Fast | "The latest version is…", model names, deprecated features |
| People & roles | Medium | "CEO of", "led by", team/company facts |
| Laws, policies, standards | Medium | Platform rules, regulations, "as of" compliance claims |
| Best practices & recommendations | Medium | "Currently the best way…" — the field moves |
| Core concepts & definitions | Slow | Usually safe, but check that the framing hasn’t shifted |
A dated statistic with no date on it. "68% of searches are zero-click" is useful with a source and a year attached and a liability without — a reader (or an engine) cannot tell if it is current, and when it ages it silently becomes misinformation you are publishing.
You cannot fix decay you cannot see. Run a periodic pass that hunts the fast-decaying items specifically, rather than re-reading everything. Claude is good at this against your files:
Review the page(s) I'm pasting (or point Claude Code at my content) for anything that may have
gone stale. Produce a table: claim/figure | why it may be outdated | how to check it | priority.
Flag specifically:
- Any statistic or percentage, especially with a year, or vendor-published
- Prices, plan tiers, API rates, and cost claims
- Version numbers, product/model names, and "latest" / "newest" claims
- "As of", "currently", "recently", "now" phrasing that anchors to a moment
- People-and-role claims ("CEO of", "led by") and legal/policy statements
Do NOT rewrite yet — just give me the prioritized list of what to verify, most time-sensitive first.Run this quarterly, and after any major change in your field. It is the cheapest way to keep a growing site honest.
Once you find an aging page, the move depends on how far gone it is:
| Situation | Do this |
|---|---|
| A few figures are stale, the page is still sound | Update in place: fix the numbers, re-date honestly, note what changed |
| The framing has shifted but the topic is still yours | Rewrite the affected sections; keep the URL so you keep the equity |
| Something material changed in the field | Add a dated "recent developments" section rather than silently editing |
| The page is obsolete with no replacement | Retire it — 301 to the nearest live page, or 410 (see URL cleanup) |
| Two pages now overlap after updates | Consolidate into one canonical page so you don’t split signals |
Keeping the URL stable through an update is what preserves the citations and links a page has already earned — update the content, not the address.
There is a real difference between a freshness signal and a freshness lie, and engines are getting better at telling them apart:
| Honest freshness | Date-gaming (backfires) |
|---|---|
You changed real content, then updated dateModified | Bumping the date with no content change |
| A dated "recent developments" section with genuinely new information | Adding "2026" to a title that wasn’t updated |
| Fixing a figure and citing the new source | Find-replacing the year on an old stat without checking it |
Rolling the date forward to look fresh. The 2026 core update demoted exactly this, and AI engines can compare a page across crawls. A real, smaller update beats a fake, bigger date every time.
Freshness is a habit, not a project. A light, repeatable rhythm keeps a growing site honest without drowning you:
Every figure here is dated and marked directional, with a standing "re-verify quarterly" rule — because a GEO site that published a stale citation stat would refute its own method. Freshness maintenance is not overhead; it is what keeps a site citable as the field moves under it.
Yes, in two ways. As a signal, AI engines (ChatGPT especially) skew toward recently updated pages. More importantly, as substance: engines favor current, specific, verifiable figures, and a stale statistic can be filtered, demoted, or cited as if current — putting an outdated claim about your topic into an AI answer attributed to you. Keeping facts true is the real freshness work.
Ship a dated update the same week your field moves; run an aging-claims audit on your key pages quarterly; and do a full sweep annually to retire obsolete pages and refresh first-party data. Fast-decaying items — statistics, prices, version names — need the most attention; core definitions rarely do.
No — it backfires. Bumping dateModified or adding a year to a title without real content changes is date-gaming, which the 2026 core update specifically demoted, and AI engines can compare a page across crawls. A smaller genuine update beats a fake bigger date every time.
Update in place when the page is still sound but some figures are stale — and keep the URL, which preserves the links and citations it already earned. Rewrite affected sections if the framing shifted; add a dated 'recent developments' section for material changes; and retire (301 or 410) a page that's obsolete with no replacement.
Because they are, and because pretending otherwise would break the method this site teaches. Vendor-published statistics in this field move monthly, so we date them, mark them directional, and re-verify quarterly — modelling the exact freshness discipline the guide describes rather than presenting aging numbers as permanent truth.