Rewrite decaying posts → Webflow drafts

The problem this solves

Content decay is the quietest leak in organic. Posts that earned their rankings two years ago slip a position at a time as SERPs shift, competitors refresh, and answers age. No alarm goes off. The traffic graph erodes so gradually that nobody owns the problem, and by the time someone notices, the post that once drove signups is on page two and the aggregate loss across the blog is substantial.

The fix is well understood and almost never executed, because it means someone digging through Search Console exports, comparing each declining post against what ranks today, diagnosing whether the problem is freshness, depth, or intent drift, and then actually rewriting - work that always loses to net-new content on the roadmap. Refreshes routinely outperform new posts for effort invested, and they are still the first thing cut.

How the mission runs

1. Pull the decay list from Search Console. The mission queries Search Console for the last quarter and isolates posts losing clicks and impressions against their prior baseline. The output is a ranked decay list - which URLs are bleeding, how fast, and which queries they are losing - built from your actual data.
2. Diagnose each loser against the live SERP. For each declining post, the SERP tool pulls what ranks for its core queries today. The agent compares: has intent shifted, did competitors go deeper, is the format wrong now, or is the content simply stale? Each post gets a specific diagnosis rather than a generic refresh label.
3. Pick the three biggest recoverable losers. Decline alone does not decide priority. The mission weighs traffic at stake against how fixable the diagnosis is, and selects the three posts where a rewrite most plausibly recovers position. The rest of the decay list is documented for future cycles.
4. Rewrite against the diagnosis. Each of the three posts is rewritten to fix its specific failure: restructured for shifted intent, deepened where competitors out-covered it, updated where it aged. What still works in the original is preserved - a rewrite that discards earned relevance would be a fresh gamble.
5. Stage the updates as Webflow drafts. The rewritten versions land as drafts in Webflow alongside a summary of what changed in each and why. Your team reviews the diffs against the diagnosis, edits where judgment says otherwise, and publishes on their own schedule. Live pages stay untouched until then.

The prompt

This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.

What comes back

Three fully rewritten posts staged as Webflow drafts, each with a diagnosis note explaining what was losing, why, and what the rewrite changed - plus the complete ranked decay list from Search Console so you know what the next cycle should tackle. Your live site is untouched until a human reviews and publishes each draft.

Make it yours

• Widen the window: run the decay scan over the trailing year instead of a quarter to catch slow, deep decline on older pillar content.
• Rewrite five instead of three, or restrict the scan to one content cluster - like your product-adjacent posts - where recovery matters most.
• Make it a loop: run monthly so decay is caught within weeks and the rewrite queue never grows past a handful of posts.

Frequently asked questions

Go deeper

• Playbook: the content refresh and decay system
• Use case: reviving a stalled organic channel
• Editorial QA for AI content: catching what models get wrong