Citation Decay: Why Your AEO Content Fades After a Few Weeks – and How a Refresh Calendar Fights Back
Citation decay describes the phenomenon where AI search engines like ChatGPT and Perplexity cite a source less and less over time – even though nothing about the content itself has changed. AI citations have a kind of half-life: the median sits at around 4.5 weeks, varying by platform (ChatGPT ~3.4 weeks, Perplexity ~5.8 weeks). Roughly half of all AI citations come from content younger than about 13 weeks, and content under 30 days old gets cited significantly more often (a benchmark of about 3.2x). What this means for you: freshness is no guarantee, but it is a real lever – and a systematic refresh process keeps your most important pages measurably citable for longer.
TL;DR
- AI citations decay over time. Median half-life ~4.5 weeks; ChatGPT ~3.4 weeks, Perplexity ~5.8 weeks.
- Around 50% of all AI citations come from content younger than ~13 weeks. Content under 30 days old gets cited ~3.2x more often.
- Regular updates plus distribution can noticeably extend citation persistence – a benchmark of about 2.1x.
- Freshness is no magic word: outdated content that you merely re-date does not become citable. Substance remains the foundation.
- In practice, what helps is a monthly refresh cycle with clear prioritization of your most important pages, a visible update date, and current figures.
What is citation decay?
Citation decay is the gradual decline in how often AI answer engines cite an existing source as it gets older. Imagine you’ve published a genuinely strong guide. In the first few weeks it shows up in Perplexity answers, ChatGPT points to it, everything’s working. Three months later: same question, same page – but it’s barely mentioned anymore. Not because it got worse. But because these systems favor newer sources for time-sensitive topics and discount older ones.
That’s the decisive difference from classic SEO. A well-ranked article can hold position one for years if nobody delivers anything better. With AI citations, that stable state simply doesn’t exist. There’s a built-in transience – a half-life after which half of the citation probability has evaporated. If you want to understand why citability is the right target metric in the first place, it’s worth reading our foundational article What is AEO first. Here we assume you already know the playing field, and we focus on the time factor.
How fast does an AI citation decay?
The median half-life of an AI citation is around 4.5 weeks – but the platforms differ significantly. That’s not a cosmetic nuance; it determines how often you need to top things up.
| Platform | Approximate half-life | Practical consequence |
|---|---|---|
| ChatGPT | ~3.4 weeks | Decays fastest – short refresh intervals |
| Median across platforms | ~4.5 weeks | A solid rule of thumb for planning |
| Perplexity | ~5.8 weeks | A bit more patient, but freshness still counts here |
Don’t read the table as a law of nature, but as an order of magnitude. The message is clear: we’re talking weeks, not years. With ChatGPT, content that was fresh two months ago has already dropped a fair way in citation probability. Anyone who “updates the blog” once a year is working completely out of step with these systems.
In the interest of honesty: these figures are averages across many topics. A timeless foundational topic (“What is HTTPS?”) decays more slowly than a fast-moving one (“best AI tools 2026”). But the direction holds for both – and the more current the topic, the harder the decay hits.
Why do AI search engines prefer fresh content?
AI answer engines prefer fresh content because recency is a strong signal of reliability – especially for questions that change over time. A system that cites a two-year-old source in response to a question about current prices, versions, or regulations risks giving a wrong answer. And an answer engine that serves up outdated information burns user trust. So retrieval layers simply weight newer sources higher for many queries.
The numbers back this up. Around 50% of all AI citations come from content younger than about 13 weeks. That’s remarkable: half of the cited knowledge is essentially “from last quarter.” And it gets even clearer at the lower end – content younger than 30 days gets cited around 3.2x more often. Freshness, then, isn’t a minor adjustment knob; it shifts the probability dramatically.
Behind this sits not a single lever but a bundle: crawlers re-fetch updated pages, visible date stamps are read as a signal, and new content gets re-linked and discussed through distribution – which in turn raises perceived relevance. Freshness is therefore part technical, part editorial, part distribution phenomenon.
Is freshness a guarantee of citations?
No. And that’s the most important honest caveat in this entire article. Outdated, thin, or vague content does not become citable just because you bump the date. Freshness is a multiplier, not a foundation. It amplifies an already good, clear, evidence-backed source – it doesn’t turn a bad one into a good one.
Concretely, this means: if your page doesn’t cleanly answer the question in a citable paragraph, no amount of fresh dating will help. Substance comes first – answer-first, clear structure, evidence-backed statements – and only then does freshness extend its effect. Anyone who flips that around and slaps a “last updated: today” on mediocre text is doing cosmetics. Worse still: in audits we regularly see pure date bumping – dateModified changes, the text stays identical. That’s risky in the long run, because crawlers can indeed detect whether the content has actually changed.
So the honest framing is this: freshness is a real, measurable lever – and at the same time worthless without the content underneath it. The two together work. One without the other doesn’t.
What does regular updating actually deliver?
Regular updating combined with distribution can noticeably extend citation persistence – as a rough benchmark, by a factor of about 2.1. That’s the real point of the whole exercise. You can’t switch decay off, but you can flatten its curve. A page you maintain regularly and put back into circulation drops out of citations more slowly than one you publish once and then leave to sit.
The “combined with distribution” part is no afterthought here. It’s rarely enough to quietly edit a file. Impact comes when the update also becomes visible – a re-crawl, a shared or linked version, a mention in a newsletter or on social channels. Update and distribution are two halves of the same lever.
Still, set your expectations realistically: ~2.1x longer persistence is a benchmark, not a promise for your specific page. Effects vary by topic, competition, and platform. What holds is the direction – and it’s clear enough to build a process on.
What does a practical refresh calendar look like?
A working refresh calendar is a monthly cycle that prioritizes your most important pages and reworks each one on a fixed rhythm – not a frantic “everything at once.” With the median half-life of ~4.5 weeks, a monthly cadence is the natural unit. Here’s a pragmatic setup.
1. Prioritize instead of spraying. You won’t be able to touch every page every month – and you don’t have to. Sort by importance:
- Tier 1 – revenue- and visibility-critical: your five to ten most important pages (core services, top blog articles, anything where you want to show up in AI answers). These get done every month.
- Tier 2 – relevant but more stable: supporting content, more timeless topics. Quarterly is enough.
- Tier 3 – archive: everything else. On an as-needed basis, e.g. when a fact goes out of date.
2. Define the monthly run. For each Tier 1 page, a short, always-identical sequence:
- Check figures, statistics, and year references and bring them up to date.
- Add at least one new, concrete example or insight – real substance, not filler.
- Remove or correct outdated statements (tools, versions, regulations).
- Set the visible update date – and only when something has genuinely changed in the content.
- Distribute the refresh: re-link, share, mention it in an active channel.
3. Lock in ownership and cadence. Define who maintains which pages and on which day of the month the run happens. A refresh calendar that nobody owns simply doesn’t happen. A simple spreadsheet with columns for page, tier, last update, next due update, and owner is entirely enough – you don’t need a specialized tool for this.
4. Factor in platform cadence. If ChatGPT visibility matters especially to you, you’ll pace Tier 1 pages more tightly (ChatGPT decays fastest at ~3.4 weeks). If your focus is Perplexity (~5.8 weeks), you can afford to be a bit more patient. You build the calendar around your most important platform, not around an average.
What you shouldn’t do
Avoid three mistakes we see again and again in content audits at Rocket-Monkeys. First: empty date bumping. Changing dateModified without touching the text is, in the long run, ineffective to counterproductive. Second: refreshing only a handful of pages that happen to be on your radar, while the pages that actually matter go stale – which is exactly why you need clean tier prioritization. Third: ignoring the decay and running one big “content update” as a project once a year. With half-lives measured in weeks, a yearly rhythm is simply the wrong cadence.
And once more, because it’s central: the refresh calendar does not replace content quality. It’s the maintenance layer on top of citable content, not a trick that rescues weak content. If the page doesn’t answer the question independently and clearly, start there – not with the calendar.
Where we’d start
If you want to get going today, you don’t need new software – you need a list and a date in the calendar. Take your five to ten most important pages, enter them as Tier 1 in a spreadsheet, fix a set day of the month, and run the same refresh sequence every time: update figures, add one new example, set a visible date, distribute. It’s unspectacular – and that’s exactly why it works, because it’s repeatable.
At Rocket-Monkeys, we build precisely these kinds of processes: technically clean Astro sites, citable content, and a maintenance cadence that works against citation decay instead of suffering it. If you want to know which of your pages are currently dropping out of AI answers and where a refresh calendar would deliver the most, we’re happy to look at it together. Write to us at info@rocket-monkeys.com for a no-obligation initial conversation – we’ll tell you honestly where the biggest lever is.