Citation Decay Half-Life: How to Time Page Refreshes by Watching Citation Trends
Pages get cited, peak, and fade. Learn to read ramp-up days, peak rate, and decay half-life so refreshes happen before the drop.
Most content calendars treat a published page as finished. Publish, promote, move on, and revisit when someone notices traffic is down. AI citations make that habit expensive. A page can be cited heavily for a few weeks and then fade without any visible change on your site. By the time you notice, a competitor's fresher page has taken the slot.
The fix is to treat citation behavior as a life cycle you can measure, and to schedule work by the shape of that curve instead of by the calendar.
The four numbers
Promptwatch's Citation Trends reports four values per page. Together they describe the curve.
First cited. The date the page first appeared as a source in tracked responses. If it never appears, the page may have an access or relevance problem, not a decay problem.
Ramp-up days. How long it took from first citation to peak. A short ramp means the engines picked it up quickly. A long ramp suggests it needed time to be discovered or trusted.
Peak rate. The highest citation rate the page reached. It tells you the page's ceiling for the prompts you track.
Decay half-life. How long it takes for the citation rate to fall to half of its peak. This is the number to watch. A short half-life means the page loses its position fast. A long one means it holds.
Why half-life beats a single snapshot
A snapshot says the page is cited in twelve percent of responses today. It cannot tell you whether that is a climb, a plateau, or a slide. The half-life, read next to the peak, tells you which. A page at half its peak after three weeks is a very different asset from a page at half its peak after three months.
How to use the numbers
Plan refreshes by half-life. Sort pages by short half-life and high peak. These earned a lot and lose it fast. They are the best candidates for an early refresh.
Compare ramp-up across content types. Citation Trends classifies each citation by content type and source type. If comparison pages ramp faster than guides on your site, that tells you which format the engines pull sooner for your topics.
Spot pages that never ramped. If a page was published weeks ago and has no first-cited date, go to crawler logs before touching the content. Agent Analytics shows whether the page was fetched at all and whether any request failed.
Set a floor. Choose a peak rate below which a page is not worth refreshing, and a half-life above which it can wait. Two rules like that keep the queue short.
A worked example
Imagine three pages on the same topic, described by their reported numbers.
Page A has a high peak and a short half-life. It was cited a lot, and it fades. Refresh it first: update the data, tighten the opening, and add anything new competitors now cover.
Page B has a modest peak and a long half-life. It holds a steady position. Leave it alone, or give it a light update at the next quarterly pass.
Page C has no first-cited date. Check access. If crawlers fetch it and it is never cited, rewrite it to answer a specific question more directly than the competitor page that is cited. Page Tracker lets you pin that competitor page and compare.
The numbers here are illustrative, not from a customer, but the logic is the part to copy.
What a refresh should contain
A good refresh is not a date change. It should add something an engine could use: a corrected fact, a new example, a clearer answer to the question in the first paragraph, or a new section that matches a query fan-out you were missing. Content Refresh in Promptwatch proposes diff-style update suggestions for existing pages, so an editor can accept or reject specific changes instead of rewriting the page from scratch.
If you run a knowledge base, keep the facts there current. The Knowledge Base in Promptwatch, available from Professional, feeds the content agents with your own material, so a refreshed fact can flow into new drafts.
Measuring whether the refresh worked
After the refresh, watch two things. First, does the citation rate recover toward the earlier peak? Second, does the half-life lengthen the next cycle? If the rate recovers and then fades just as fast, the update fixed the facts but not the underlying reason the page loses ground, which may be competitors or sources outside your site.
For outside sources, use Reddit, YouTube, and LinkedIn citation reports and offsite mentions to see whether third-party pages are taking over the topic.
A cadence that works
- Weekly: scan for pages with falling rate and short half-life.
- Monthly: refresh the top two or three.
- Quarterly: review pages that never ramped and decide to fix or retire them.
The Action Board can hold these items in a queue with owners, and its Discovery agent proposes up to five evidence-backed actions per weekly run. For brands on the Business plan, the Content Agent can plan and publish refresh work on a schedule, with a review inbox in front of it.
The recommendation
Stop treating published pages as finished. Read the four citation numbers, schedule refreshes by half-life, and verify the effect. Promptwatch is where those numbers live, per page, next to crawler logs and the action queue. Start by listing your ten most-cited pages and noting each one's half-life, then pick the shortest one and refresh it this week.