How to Audit Content Decay Without Ahrefs: 51 Posts (2026)

A Search Console audit gives you four things per page across two aligned windows: clicks, impressions, average position, and the actual queries behind each of them. That is enough to compute a decay rate, to catch a query mix that has quietly rotated, and to catch a click-through collapse while position holds steady — which usually means something above the result is absorbing the clicks, not that the page got worse.

What it cannot tell you is why. You will not see a competitor rewriting their page, a backlink disappearing, a site-wide technical regression, or whether an AI assistant now recommends someone else for your query. Those signals live in other tools, and it is worth knowing the entry prices before deciding a free audit is enough: Screpy lists its monitoring plans from $6/month under a 60%-off welcome offer, with the Pro tier listed at $19/month month-to-month or $16/month billed yearly at $192/year (screpy.com/pricing, checked 13 September 2026); Ahrefs Starter is $29/month, and its AI citation product, Brand Radar, starts at $199/month (ahrefs.com/pricing, checked the same day).

Two limits are structural rather than financial, and both change how you read your own export. First, rows below roughly 50 impressions per window are noise: a page can look 100% down because it moved from two clicks to one. Second, clicks are a lagging indicator on any query type where AI answers sit above the results — the Ahrefs freshness figure is one of the few public attempts to size that shift, and it is an average, not a per-page truth. Write your impression floor down before you sort anything, or you will spend the sprint on pages that never had traffic to lose.

The method needs three things: two exports of the same length, aligned to the same part of the week, joined in a spreadsheet with one calculated column. Everything else is sorting.

This is the loop we ran on our own archive, written so the input and the output of every step are checkable. Total working time lands near 90 minutes for a site under 500 pages, and the first ten minutes are the part people skip and then regret.

We ran the first two steps of this method on our own site before writing the rest. The archive holds 51 posts published between 2 June and 12 September 2026: 15 from June, 7 from July, 17 from August, and 12 from September. The oldest is 103 days old today. There is no year-over-year window to compare against and no 90-day window either, because the site is barely older than that itself — a live example of the fallback case rather than a hypothetical one.

The method still produces a queue. The June and July cohort — 22 posts, many of them listicle-format pages aimed at head terms — sorts first, because those are the pages whose impressions sit furthest from a click and whose content is old enough to have drifted away from the queries that now reach them. The 12 September posts are excluded from this sprint on principle: they have not completed a single full data cycle, so any verdict on them would be a guess dressed as analysis. Five pages get tickets this month, not twenty-two.

What we are not doing is publishing per-page click figures from the Search Console export. The property is ours; that does not make the numbers ours to decorate, and building a before-and-after table out of data we cannot reproduce for you would contradict the entire reason this page exists. What we will publish is the method, the thresholds, and the recheck date — the parts your team can run on its own property tonight. If you would rather watch the same evidence rules applied to a paid stack, our Surfer SEO alternatives piece runs a 30-day switch test under the same constraints.

Nearly every failed refresh project is one of these five, and all five are avoidable before you edit a single page.

Q: How fast does content decay? A: On freshness-sensitive queries — anything shaped like “best X” or “how to Y” — a page can lose ground within months rather than years, which is why a quarterly cadence is the standard recommendation. The commonly cited trigger is a 20% year-over-year traffic drop, but that assumes you have the history to calculate it. On a younger property, compare 28-day windows spaced 90 days apart and treat a 30–40% drop as your trigger instead.

Q: Is Search Console enough, or do I need Ahrefs? A: For detection, Search Console is genuinely enough: it is the only free source for the impressions, clicks, and query mix of your own pages. What you give up is context — lost backlinks, competitor page changes, and AI citation counts. A complete free stack is the two exports above plus Rank Revival, which reads your Search Console data and surfaces the pages declining most in clicks with year-over-year trends, and currently invites you to sign up free with no credit card. Add Ahrefs at $29/month when you need link data, and prompt tracking from $199/month only when you need it.

Q: Should I refresh a decaying page or delete it? A: Update it first if the page still matches the intent behind the query. Consolidate when two pages split the same intent, redirect when the intent has moved to a different page, and prune only when a page has neither links nor impressions left to protect. Deleting a page that still earns impressions hands the query to a competitor and gives you nothing in return.

Q: Do refreshes work on pages stuck at positions 11 to 30? A: That is where most of the return sits on a young site. Our own average position is 27 across 9,208 impressions in 28 days, which means the realistic win is moving a page from 27 to 12, not from 3 to 2. Pages in that band already have impressions and topic relevance; they usually lack fresher evidence, a clearer answer near the top, and internal links — three things a refresh can actually supply.

Q: Can I make AI assistants cite my page instead of a competitor’s? A: Only indirectly. There is no switch, and the public evidence is correlational: Ahrefs’ research points to recency as one factor in which URLs get cited. What you control is whether the page still answers the query in its opening lines, whether its statistics carry dated sources, and whether it is crawlable and linked. Those are also the first things a decay audit puts back.