Loading...
The playbook Moonrank's SEO Agent uses to find pages losing traffic year over year, name the cause, and give each one a single verdict: refresh, consolidate, or retire.
Download the methodology, see how the agent classifies decay, or run it live inside the SEO Agent.
The Content Decay skill is how Moonrank's SEO Agent audits an ageing content library: which pages are slipping, why each one is slipping, and what to do about it — without refreshing pages that were never going to recover.
It's written as a SKILL.md, a plain-language instruction format that people and AI agents can both follow. Read it to audit your own archive, or let the SEO Agent run the year-over-year comparison and return a verdict per URL.
Downloading the playbook is free with a Moonrank account. Running it on a schedule, and shipping the refreshes and redirects it calls for, is what the SEO Agent does for you.
“We publish more than ever and traffic is flat. Where is it going?”
Forty-two URLs are down year over year, and eighteen of them are cannibalizing each other — you have four separate posts targeting the same query, none of which wins it. Consolidate those into one page and redirect the rest. Nine more are stale rather than beaten: the answer changed, the page didn't. The remaining fifteen are seasonal and need nothing.
Twelve months minimum, so decay can be measured year over year instead of month to month.
The agent compares the last 90 days to the same period last year and flags real declines.
Seasonal, competitive, stale, cannibalized, or an intent shift — each needs a different response.
Refresh, consolidate, or retire, with the specific change and the redirect target.
The only comparison that separates real decay from a seasonal dip.
Seasonal, competitive, stale, cannibalized, or intent shift — named, not guessed.
Groups of your own URLs competing for one query, with a canonical winner picked.
Catches the queries where the result type changed and copy edits won't help.
One verdict per page, with the redirect target when a page is being retired.
Refreshes that haven't moved get re-judged instead of quietly forgotten.