Deduplicating Joins Across Citation, Referral, and CRM Data
Website owners comparing citation reports with referrals and customer relationship management (CRM) outcomes need to keep the three record types separate. A…
Categories
How to Diagnose Content Decay Before Rewriting an Article
When an article loses organic search traffic, a rewrite is only one possible response. Content decay is a term for a lasting drop in a page’s search visibility or usefulness. Outdated information, weaker relevance, or a mismatch with what searchers now want may be involved. The term names a problem to investigate, not its cause.
Before editing, identify which measure changed: impressions, clicks, click-through rate, or average position. Then investigate whether search demand shifted, a technical problem occurred, or search results changed. Rewrite only when the evidence points to the article itself.
A traffic drop does not prove content decay
Google lists outdated, incorrect, or less useful content as one possible reason for a lasting drop in search performance. Its traffic-drop guidance also names other causes, including seasonal demand, indexing problems, stronger competing pages, lost links, and changes to search features or reporting.
Those causes call for different fixes. An article with outdated instructions needs editorial work. A page that Google cannot index needs a technical fix. A seasonal decline may need no change at all.
An article can become less relevant when its facts or recommendations are outdated, or when searchers start expecting a different kind of answer. Some searches need recent information; others do not. Google says its freshness systems target searches where people are likely to expect current results, such as a search about a recent earthquake. Older articles do not all need updating. (Google’s ranking systems guide)
Find which search metric fell
In Google Search Console, filter the Performance report to the affected page. Compare the period when performance fell with an earlier period that is comparable. Also check the page’s queries, countries, and devices. Google recommends checking clicks and impressions along with position, rather than relying on average position alone. A canonical URL is the version of a page that Google treats as the main copy when similar URLs exist. (Performance report guidance)
An impression means the page appeared in a Google search result. Click-through rate, or CTR, is the percentage of impressions that led to a click. These measures help show whether fewer people see the result or whether people see it but click less often.
| Performance pattern | What it suggests | What to check next |
|---|---|---|
| Impressions and clicks fall | The page appears less often, or fewer people search for the topic. | Compare query-level trends, seasonality, indexing, and the selected canonical URL. |
| Impressions stay similar, but CTR falls | Searchers still see the result but click it less often. | Review the current results, competing features, and whether the title and snippet describe the page accurately. |
| Average position falls over time | The page may have become less competitive, but position alone does not explain why. | Inspect affected queries, current results, links, and technical status. |
| Search Console stays steady, but analytics visits fall | Search visibility may be stable while measurement, attribution, or post-click behavior has changed. | Check landing-page and traffic-source reporting, tracking changes, and date settings. |
| Many pages decline together | A single article is less likely to explain the whole change. | Investigate sitewide availability, indexing, recent site changes, and Search Console data anomalies. |
Average position combines results across searches. A change may reflect different queries or search contexts, rather than a clear change in position for one search. Treat it as a clue, and check clicks and impressions too. (How Search Console reports performance)
Separate lower demand from weaker rankings
If the topic is seasonal, compare the page’s queries across equivalent periods. A nearby week can show a recent shift, but it can also fall during a normal seasonal low. Google Trends helps compare interest over time, but its numbers are relative, not exact search volumes. Low-volume terms can show as zero. (Google Trends data limitations)
Falling impressions alongside broadly stable position and declining topic interest make lower demand plausible, though they do not establish it. Search Console shows the page’s performance in Google Search. Trends gives a separate, approximate view of interest.
Also check whether the decline affects one page or many. A page-specific drop points toward that page’s queries, content, and technical status. A sitewide decline makes it more useful to investigate broader changes before rewriting an individual article.
Compare the article with today’s searches
For queries that lost visibility, inspect the current results and compare their answers with yours. Look for a specific mismatch. Searchers may now need different information, a key fact may have changed, or the page may no longer answer the question its impressions suggest they are asking.
Google’s traffic-drop guidance recommends checking whether competing results have become more useful, complete, or current. That comparison helps identify gaps, but it cannot prove that a particular competitor caused your decline. Use it to decide whether the article’s answer still fits the search, not to copy the pages currently ranking.
When impressions remain steady but CTR falls, start with the search result itself. Check the title, snippet, and features displayed around the result. A lower CTR does not by itself show that the article’s main text is outdated.
Rule out indexing and reporting problems
Before changing the article, inspect its URL in Search Console. Check whether Google can crawl and index the page and which canonical URL Google selected. A canonical URL is the version Google treats as the main copy when similar URLs exist. If Google selects a different URL or cannot index the intended page, editing the article’s wording will not address that problem.
Check for recent migrations, URL changes, or site availability problems too. If Search Console shows an abrupt change on a particular date, consult its data-anomalies information before treating the chart as a content signal.
Search Console and analytics measure different things. Search Console reports activity in Google Search. Analytics tools record visits after people reach the site. Differences in coverage, privacy filtering, processing, time zones, or tracking can make the totals differ. Search Console also leaves out some queries because of privacy and data limits, so its query table may not show every search behind a page’s performance. (Search Console data limits)
Match the fix to the evidence
A technical issue calls for a technical fix. A seasonal decline calls for a fair comparison period. When impressions stay stable but CTR falls, review the result presentation. Update an article substantively if it contains outdated facts or no longer answers the searches it attracts.
Rewrite the whole article when its main approach no longer meets the reader’s need. If only a few facts or sections are outdated, update those parts and keep the sections that still work. If the evidence does not point to a clear cause, gather more data rather than making a large change based on a small fluctuation.
Do not change a publication date without a meaningful update. Google advises against adding or removing content merely to make a site seem fresh, and says date changes should reflect actual publication or update dates. (People-first content guidance)
A rewrite does not guarantee that rankings will recover. Google says search results change as expectations and competing content change, and site improvements may produce no noticeable effect. After a broad core update ends, Google recommends waiting at least a full week before comparing performance. (Core update guidance)
Check AI search visibility when it matters
Google’s Search Console generative-AI performance reports show a page’s visibility in Google’s AI features. Google announced a worldwide rollout in 2026, and the reports include impressions and affected pages. Compare the reports with regular Search performance to see whether AI-feature visibility changed alongside it. A change in AI-feature impressions does not show that content decay caused the change or that a rewrite will improve it. (Google’s announcement of AI performance reports)
Key Takeaways
- Diagnose the metric first: Separate falling impressions from falling CTR, clicks, or average position before editing.
- Rule out other causes: Check demand and seasonality. Also check indexing, canonical selection, sitewide changes, and reporting differences.
- Compare the current answer: Rewrite when the article is outdated or no longer meets the needs shown by its queries and current search results.
- Make the smallest effective change: Update the affected sections when the rest of the article remains accurate and useful.
- Treat recovery as uncertain: A rewrite does not guarantee improved rankings or AI-search visibility.
What I'm buildingDelegate tasks. Get software.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com