What content decay is
A post ranks, earns traffic for a year or two, then slides. Competitors publish fresher versions, the facts in it age, the search intent drifts, and Google's preference for recency does the rest. Because the decline is gradual and spread across dozens of posts, the total traffic chart looks like a gentle plateau while the pages that built the site quietly stop working.
The posts that decay are also the cheapest wins you have. A page that once ranked has the links, the history and the topical authority; it usually needs an afternoon of updating, not a rewrite. The trick is knowing which ones, early.
Connect GA4
Install Dragon Content Decay, open Tools, then Content Decay, then Settings, and press Connect Google Analytics. The plugin asks for read-only Analytics access; the tokens are stored encrypted in your database and the traffic data is fetched from your own property and cached locally. Nothing is shared with anyone. Pick the GA4 property for this site.
The first scan compares each post's recent traffic against its own baseline and classifies it as Decaying, Stable or Growing.
Add Search Console for the earliest signal
Pageviews lag. By the time sessions fall, the page has already been losing impressions and clicks in search for weeks. Tick Search Console in Settings, enable the Search Console API in the same Google Cloud project as your client ID, reconnect to grant the extra read-only permission, and choose the verified property. The dashboard gains a Search Clicks column with the change against the previous period. Search Console data lags real time by two or three days, which is still far ahead of the traffic chart.
Reading the dashboard: what to refresh first
Every decaying post is a candidate; not every candidate is worth the time. Sort by two things at once:
- Steepness of decline. A post down 60% is bleeding; a post down 8% may be seasonal noise.
- Historical traffic. A post that used to bring 2,000 visits a month and now brings 800 is worth a day. One that went from 40 to 15 is not.
The posts high on both are recoverable rankings. Take the top five. Each row links straight to the editor.
Before opening the editor, search for the post's main phrase yourself and look at what now outranks it. That tells you what the refresh needs to add.
What a refresh that works looks like
Bumping the date does nothing. A refresh that recovers rankings changes the page:
- Update every fact, number, screenshot and product name. Anything dated is the reason the reader, and Google, moved on.
- Answer what the top-ranking pages now answer and you did not. Usually a missing section, sometimes a missing format (a table, a checklist, a short video).
- Cut what is dead. Sections about a tool that no longer exists, a policy that changed, a trend that ended.
- Rewrite the title and intro for the intent as it is now, not as it was.
- Add internal links from newer posts to this one, and from this one to your newer coverage. Dragon Internal Links finds those opportunities ranked by relevance; the workflow is in internal linking that actually helps.
- Republish with an updated date that reflects the real edit. Then resubmit the URL in Search Console.
Expect the effect four to eight weeks later, and confirm it on the same dashboard: the row should move from Decaying to Stable or Growing.
Make it a habit
Once a month, open the dashboard, take the top few decaying posts by lost traffic, refresh them, and note the date. Ten refreshed posts a quarter is a modest amount of work and, on most content sites, a larger traffic gain than the same effort spent on new posts.
Troubleshooting
- Connect fails after approving. The Google account must have access to the GA4 property for this domain. Check the property picker.
- Numbers differ from the GA4 interface. The plugin reads sessions per page path; GA4's own reports are often filtered or modelled.
- Search Console shows nothing. Confirm the API is enabled in the Cloud project and that you reconnected after ticking the option.