A content decay audit helps you find blog posts that have lost visibility, become outdated, or no longer satisfy the reader’s search intent. This repeatable workflow shows what to compare, how to prioritize fixes, and when to refresh, consolidate, redirect, or retire an article.
Overview
Older posts do not always fail because they were poorly written. A topic may have changed, competing pages may have improved, links may have broken, or the search intent may have shifted. A content decay audit separates those possibilities so you can make an editorial decision instead of updating every article in the same way.
Start by creating a list of published posts with their URLs, publication dates, last updated dates, topic, primary query, and intended audience. Then compare a recent measurement period with an earlier period of similar length. For example, compare the most recent 28 or 90 days with the preceding 28 or 90 days. Longer periods can reduce the effect of short-term fluctuations, while shorter periods can help you identify a sudden decline.
Use your site analytics for visits, engaged sessions, conversions, and other business goals. Use your search platform’s performance reporting for impressions, clicks, click-through rate, and average position where available. Treat these figures as signals rather than verdicts: a traffic decline can come from lower demand, seasonality, technical problems, or a change in the way search results are displayed.
For a broader production process, pair this audit with the blog post production checklist and republish workflow. The audit identifies the work; the workflow helps you complete and document it.
What to track
A useful content audit combines performance data with a manual review. Add one row for each article and record the following fields:
- Traffic change: Compare visits or engaged sessions in the recent period with the previous period. Record both the numbers and the percentage change, but do not rely on percentage change alone when the starting volume is very small.
- Search visibility: Note changes in impressions, clicks, click-through rate, and average position. A fall in impressions may indicate reduced demand or visibility; a fall in clicks with stable impressions may point to a title, snippet, or intent problem.
- Ranking changes: Check the article’s main query as well as related queries. Look for important terms that moved from the first page to lower results, or queries for which the page no longer appears.
- Outdated claims: Mark statistics, product details, screenshots, dates, regulations, software instructions, and recommendations that may no longer be accurate. If you cannot verify a time-sensitive statement, rewrite it with a clear date or remove it.
- Search-intent shifts: Review the current results for the main query. Ask whether readers now expect a tutorial, comparison, checklist, definition, template, or case-based explanation. An article can be well written and still be mismatched to the query.
- Internal links: Check whether the post links to newer, more useful pages and whether other relevant pages link back to it. Replace vague anchor text and remove links that lead to deleted or unrelated content.
- Broken resources: Test external references, downloads, embedded media, forms, and calls to action. A broken tool link or missing example can make an otherwise useful article difficult to follow.
- Thin sections: Identify headings that answer a question only briefly, repeat nearby material, or no longer support the reader’s task. Improve the specific section rather than adding length everywhere.
- Engagement and outcomes: Where relevant, record scroll depth, clicks to a template or tool, email signups, downloads, or other meaningful actions. A post with modest traffic may still be valuable if it supports a clear audience goal.
Use a simple scorecard to decide what deserves attention first. Give each category a score from zero to three: zero means no issue, one means minor, two means meaningful, and three means urgent. Score traffic loss, ranking loss, outdated information, intent mismatch, internal-link weakness, broken resources, thin sections, and business value. Prioritize articles with several high scores and a realistic opportunity to improve.
| Audit signal | What it may indicate | First action |
|---|---|---|
| Traffic and impressions both declined | Lower demand, weaker visibility, or increased competition | Compare current search results and verify technical access |
| Impressions are stable but clicks declined | Title, snippet, or intent mismatch | Review the title and opening against the query |
| Rankings declined for important queries | Relevance, quality, freshness, or internal-link weakness | Compare the page with current competing results |
| Claims and resources are outdated | Reduced trust and practical usefulness | Verify, replace, date, or remove affected material |
| Several pages target the same intent | Overlapping coverage and unclear page purpose | Consider consolidation and one primary URL |
Cadence and checkpoints
Run a light content decay check monthly if you publish frequently or depend heavily on organic traffic. Review a smaller set of priority pages: posts with sudden declines, important conversion paths, seasonal deadlines, or time-sensitive recommendations. The monthly pass should identify problems, not become a full rewrite session.
Run a deeper audit quarterly. Export or record the same metrics each time, using comparable date ranges. Keep a change log with the URL, issue found, action taken, editor, publication date, and review date. This makes it easier to tell whether a later performance change followed an actual update or merely reflected normal variation.
Add special checkpoints after a major site redesign, a change to navigation, a large batch of new content, or a noticeable traffic decline. Also review posts before their relevant season. A guide about annual planning, tax preparation, conference attendance, or holiday publishing should be checked before readers begin searching for it.
Reporting interfaces change over time, so document the report names and filters you use rather than relying on memory. The exact labels in analytics and search platforms may differ, but the method remains consistent: select comparable periods, segment by URL, record the main signals, and inspect the page itself.
How to interpret changes
Do not refresh a post solely because its traffic fell. First identify the likely cause and choose the smallest effective intervention.
Refresh
Refresh when the page still serves a distinct purpose but contains stale details, weak examples, missing steps, or outdated links. Preserve useful sections, improve the introduction, update the title when appropriate, add relevant internal links, and make substantial changes visible in the revision record. A readability review can help with structure and clarity; see this blog readability checklist and scorecard for a practical review method.
Consolidate
Consolidate when two or more pages address nearly the same question and neither has a clear reason to exist separately. Choose the strongest URL, combine the genuinely useful material, remove duplication, and redirect the weaker page when that is appropriate for your site setup. Update internal links so they point to the surviving article.
Redirect
Redirect when an old URL has a clear, closely related replacement. A redirect should guide readers to a relevant destination, not simply send every retired page to the homepage. Confirm that the replacement fulfills the same general need and update links, navigation, and promotional references.
Retire
Retire a post when it has no continuing audience, no useful replacement, outdated information that cannot be responsibly maintained, or no meaningful role in your content strategy. Before removing it, check links from other pages, saved campaign references, and any conversions it generated. Record the reason for the decision.
After an update, measure the result against the same type of comparison used in the audit. Allow enough time for meaningful data to accumulate, and evaluate more than traffic: examine relevant queries, clicks, engagement, and the action the page is meant to support. When revising a draft, a text comparison tool can help you document what changed; the revision workflow for comparing two texts explains how to use that check.
When to revisit
Use this content decay audit template quarterly as a baseline, then revisit individual posts sooner when their signals change. A sudden traffic drop, an important ranking loss, a broken resource, a product or platform change, or a shift in reader questions is a reason to investigate immediately. Recheck seasonal posts before their active period rather than waiting for the next general audit.
End each audit with a short action list divided into three groups: update now, monitor, and leave unchanged. For every update-now item, assign a specific fix, owner, target date, and success measure. For monitor items, record the next review date and the signal that would trigger action. For unchanged items, note why the current version remains fit for purpose.
- Export or record comparable recent and previous-period data.
- Filter for meaningful traffic, impression, click, or ranking declines.
- Manually review intent, accuracy, links, resources, and thin sections.
- Score each issue by severity and strategic value.
- Choose refresh, consolidate, redirect, retire, or monitor.
- Document the change and schedule a follow-up measurement.
Repeat this process consistently and your content library becomes easier to manage. Instead of treating old posts as permanent assets or automatic liabilities, you can maintain them according to reader need, editorial purpose, and evidence from your own site.