Content Decay Checker for Existing Pages
Paste one public URL after you spot a decline. Use Page Refresh AI to review decay signals: stale sections, weak answers, missing sources, poor internal links, and AI readability issues before assigning edits.
Short answer: diagnose one declining URL before editing
A content decay checker helps you decide whether one existing public page is losing usefulness and what to inspect next. It should combine Search Console evidence, GA4 engagement context, technical eligibility, freshness checks, answer clarity, source context, and internal links before assigning edits.
Start with a GSC comparison window
| Window | Use for | What to watch |
|---|---|---|
| Last 28 days vs previous 28 days | Fast triage when a page looks weaker this month and you need to decide whether to audit it now. | Clicks, impressions, CTR, average position, top queries, and whether the drop is limited to one URL or affects the whole site. |
| Last 3 months vs previous 3 months | Filtering out short-term volatility before assigning refresh work to an older article or landing page. | Query mix changes, average position drift, stale topic coverage, and whether competitors now answer the same intent more completely. |
| Same period year over year | Seasonal topics, annual guides, tax, holidays, product cycles, and other pages where demand naturally moves by calendar period. | Whether the decline is real decay or normal demand timing. Do not rewrite a seasonal page just because the wrong comparison window looks bad. |
Common content decay questions from site owners
| Question | Practical answer | Next step |
|---|---|---|
| My old posts are losing clicks. Should I update all of them? | No. Pick one URL with active impressions, business value, or a clear query decline. Check false positives first, then audit the visible page for missing answers, stale sections, source gaps, and internal links. | Use this page for triage, then run the selected URL through the free content audit tool. |
| Should I refresh an old post or write a new article? | Refresh when the existing URL still matches the search job and mainly needs better answers, examples, sources, or internal links. Write a new article when the new intent is distinct enough that adding it would make the old page unfocused. | Use the content refresh scorecard when several URLs compete for the same editing time. |
| The page still ranks, but traffic is lower. What changed? | Compare query-level CTR, new query impressions, first-screen answer quality, freshness signals, and competing result formats. A page can remain eligible while losing clicks because the answer is weaker or less current. | Use Page Refresh AI after the GSC comparison to turn the diagnosis into an edit queue. |
Content decay signals to check
| Signal | Likely issue | Evidence | Next action |
|---|---|---|---|
| Clicks are down, impressions are still active | Search demand still exists, but the page promise, snippet, first answer, or freshness signal may be weaker than competing results. | Search Console page filter: clicks, impressions, CTR, top queries, and comparison window. | Improve title fit, move the current answer higher, update stale examples, and check whether the page still matches the main query. |
| Impressions and clicks are both down | The query set may have shifted, the page may no longer satisfy intent, or the page may have a technical/indexing issue. | Search Console pages and queries, URL inspection, sitemap, canonical, robots, and visible text check. | Rule out technical issues, then decide whether to refresh, rewrite, consolidate, or leave the page alone. |
| GA4 engagement is weaker than the page role | Readers arrive but do not get enough clarity, proof, next-step routing, or content freshness from the page. | GA4 landing-page sessions, engaged sessions, key events, and next-page path. | Clarify the intro, add internal links, remove stale detours, and align the CTA with the page job. |
| Impressions are up, clicks are flat or down | The page may be appearing for broader or newer queries, but the visible answer, title promise, or snippet-worthy section is not strong enough to earn the click. | Search Console query comparison: new queries, CTR by query, page title, meta description, and first answer. | Split the mixed intent, add a direct answer near the top, and decide whether the new query deserves a supporting section or a separate page. |
| Facts, screenshots, or examples are stale | The page may still rank for the topic, but readers and AI answer systems have less reason to trust or quote it. | Manual review of dates, product names, screenshots, pricing references, external sources, and process steps. | Replace outdated claims, add source links near volatile statements, and remove unsupported details. |
| The answer is hard to extract | Definitions, caveats, entities, and source context are buried across dense paragraphs. | Manual GEO check: direct answer, named entities, descriptive headings, source-backed sections, visible FAQs. | Add a self-contained answer block, split dense sections, add useful FAQs, and link to related guides. |
| The page lost internal support | The page may still be useful, but newer pages no longer link to it, or old internal anchors no longer describe the page job clearly. | Manual internal-link check from the blog hub, related guides, money pages, and recently updated posts. | Add contextual links from related pages, update vague anchors, and route readers to the next step after the old page answers its main question. |
Choose the right next action
| Decision | Use this when |
|---|---|
| Refresh | The URL still matches search intent, has useful impressions or business value, and mainly needs current examples, clearer answers, sources, or internal links. |
| Rewrite | The topic still matters, but the old angle, structure, or audience no longer matches the current search task. |
| Consolidate | Several URLs answer the same job, split links, and would be stronger as one canonical guide. |
| Fix technical first | The page has indexability, canonical, robots, rendering, tracking, or status-code issues. |
| Wait or leave alone | The movement is short-term volatility, seasonality, or a page with no clear search or business reason to edit. |
Rule out false positives
| False decay signal | Check first |
|---|---|
| Seasonal query demand | Compare against the same period last year before assigning refresh work. |
| Recent tracking change | Confirm GA4 tagging, landing-page path, redirects, and consent behavior did not change. |
| Broad ranking volatility | Check whether many unrelated URLs moved together before treating one page as decayed. |
| Technical access issue | Verify 200 status, canonical, robots, noindex, sitemap, and rendered visible text. |
Follow a one-URL decay diagnosis workflow
- 1. Choose one suspect URL: Start from GSC, GA4, or a small content list. Do not diagnose a whole site inside a single page audit.
- 2. Record the pre-refresh evidence: Capture GSC clicks, impressions, CTR, average position, query mix, GA4 sessions, engaged sessions, and the page role.
- 3. Rule out false decay: Check seasonality, tracking changes, redirects, canonical, robots, noindex, status code, sitemap inclusion, and visible content.
- 4. Audit page quality: Review the first answer, stale facts, source gaps, missing FAQs, weak paragraphs, internal links, and AI-readable structure.
- 5. Pick one action: Refresh, rewrite, consolidate, fix technical issues first, or leave the page alone. Then measure the same URL after publishing.
Copy-ready one-URL decay brief
Use this brief before asking a writer, freelancer, or internal editor to refresh the page. It keeps the work tied to evidence instead of turning every traffic dip into a rewrite.
- URL under review:
- Main query or page job:
- Comparison window used: 28 days, 3 months, or year over year
- GSC evidence: clicks, impressions, CTR, average position, and query mix
- GA4 evidence: sessions, engaged sessions, key events, and next-page path
- False positives checked: seasonality, tracking, volatility, redirects, canonical, robots, noindex, sitemap, status code
- Content gaps found: stale examples, missing questions, unsupported claims, weak intro, dense paragraphs, unclear entities
- Internal-link gap:
- Decision: refresh, rewrite, consolidate, fix technical first, or wait
- Measurement date to revisit after publishing:
Where this fits in Page Refresh AI
Page Refresh AI does not crawl an entire site for decay. Use analytics tools to choose the suspect URL, then use this checker path to decide whether the page needs a refresh audit. If the page may be outdated before traffic drops, use the content freshness checker. If you have several candidates, score them with the content refresh scorecard. If you already know which page to edit, use the content refresh tool.
Sources behind the checklist
This page follows Google's traffic drop debugging guide, helpful content guidance, Search Console Performance report guide, and AI features documentation.
Frequently asked questions
What does a content decay checker do?
It reviews one existing public URL for signs that the page is losing usefulness or search performance: declining GSC clicks, weak CTR, stale sections, unsupported claims, weaker engagement, missing follow-up answers, and poor internal links.
Can this guarantee traffic recovery?
No. A content decay check helps you decide what to inspect and edit. Search traffic depends on query demand, competition, technical eligibility, page quality, and factors outside one page refresh.
Does Page Refresh AI check my whole site for decay?
No. Page Refresh AI audits one public URL at a time. Use GA4, Search Console, or a content list to choose the candidate URL first.
Should I refresh every page with lower traffic?
No. Rule out seasonality, tracking changes, technical issues, and broad ranking volatility first. Refresh only when the URL still has a useful job and the page-level evidence points to fixable content gaps.
How is this different from the content refresh scorecard?
The content decay checker diagnoses one URL after you suspect a decline. The scorecard helps compare several old pages before choosing which one deserves a deeper audit first.