Workflows / Templates / Publisher: find decaying posts
The publisher decaying posts template: on the 1st of every month, for free.
Old posts lose clicks quietly. This workflow template finds decaying posts once a month from your own Search Console data: it compares the last 28 days with the 28 before, keeps the posts that lost more than a quarter of their clicks, and sends Managers a CSV. It fetches nothing, so it costs nothing in provider fees.
Every template asks before it spends and never publishes.
Who it is for, and what starts a run.
Who it is for
Publishers and content teams with a big archive, where nobody has time to check hundreds of posts by hand.
Anyone who wants a refresh list on a fixed day instead of in a quarterly review. The project needs Search Console connected.
What starts it
Schedule: the 1st of every month at 06:00 UTC by default. You can change the day, the time and the time zone.
If last month's run is still going, the new one is skipped.
How it finds decaying posts, block by block.
Each block is a step you can open in the editor. Every step keeps a receipt: inputs, outputs, evidence, provider, cost and timings.
Search Console data
Reads the last 28 days per page and compares them with the 28 days before. Pages with fewer than 10 impressions are left out.
Filter
Keeps posts whose clicks fell by more than 25%, and only those that had at least 100 clicks before. Small posts with noisy numbers stay out.
If/else
Carries on only when at least one post decayed. A quiet month sends no email.
Export CSV
One row per post: URL, clicks before, clicks now and average position.
Notify by email
Emails Owners, Admins and Managers that posts in the project are losing clicks.
Change the line in the Filter block if 25% is too loose or too strict for your archive. The CSV is a list to review, not a verdict: seasonal posts lose clicks every year.
Before it spends, it asks.
Approvals
No spending block, so nothing to approve on spend. The run reads data you already sync from Search Console.
If you add a spending block later, such as a SERP fetch, the run then needs a standing approval from an Owner or Admin, and publishing that version clears any old one.
What it costs
No provider cost. Search Console data comes from your own connection, and the template calls no DataForSEO or AI provider block.
Refreshing a post is a separate step that a person starts, and that step shows its own estimate.
What you get when the run finishes.
- A CSV of decaying posts: URL, clicks before, clicks now, average position.
- An email to Managers on months when posts decayed, and silence when none did.
- A receipt in Runs for every month, so you can see when a post first showed up.
No workflow can publish to a site. Drafts and tasks wait for a person. Spending waits for an approval, and every run checks your monthly cap first.
Related. Templates and pages that pair with this one.
Content decay
How SerpDad spots decay and lines up refreshes.
SerpDad for publishers
Plans and refreshes for big archives.
Content refresh
Turn the list into refreshes a person approves.
Search Console
What SerpDad reads from your Search Console.
Monthly re-run
The other monthly template: re-plan the whole list.
Content audit template
A free sheet for sorting pages by what they need.
Catch the slide
before the quarterly review.
Your first plan is free up to 1,000 keywords, with briefs for the top 5 pages. No card needed.