Content Refresh & Decay Auditor: Find Stale Posts Before They Sink
Import your published-content list, flag posts that are decaying, aging, or going stale, and build a prioritized refresh queue your content lead approves — one task per page, no duplicates.
A web tool where you import your content list, decay and staleness rules flag refresh candidates, the tool ranks them by priority, your content lead approves which posts enter the queue and assigns owners, refresh tasks are created, and everything exports to CSV.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- A CSV export of your content (URL, publish date, last-updated, traffic/clicks over time)
- Your team's 'stale' thresholds
- Claude Code or any AI coding agent
The problem this kills
You have hundreds of published posts. Some were great two years ago and are now quietly bleeding traffic. Some still say "best tools for 2023" in the title. Some link to pages that no longer exist. And somewhere in that pile are five posts that, if you refreshed them this month, would win back real traffic — but you have no system for finding them, so you keep writing new posts instead while the old ones decay in the dark.
Content decay is the slow leak of content marketing. Google rewards freshness, competitors update their pages, and your once-ranking article slides from position 3 to position 12 without anyone noticing. The frustrating part is that the evidence is already in your hands: your publish dates, your last-updated dates, your clicks over time. You just need something that reads all of it, applies your team's rules for "stale," and hands you a ranked list of what to fix first. You do not need to be a developer to build that something.
What you'll build
A simple internal web tool for your content team. You import a CSV of your published content — URL, publish date, last-updated date, and traffic or clicks over time. The tool applies your decay and staleness rules: too old since last update, traffic dropped more than your threshold, an outdated year sitting in the title, and (optionally) broken links found by a quick URL check. It scores and ranks every flagged page so the biggest, most fixable losses float to the top, each with a plain-English reason. Your content lead reviews the candidates, approves which ones enter the refresh queue, and assigns an owner. Only then are refresh tasks created. Everything exports to a clean CSV — the refresh queue in the exact columns your project tracker or spreadsheet expects.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — your current content process and who runs it, the systems and spreadsheets you use (Search Console, GA4, your CMS, a tracker), the exact columns and naming in your content export, your typical and peak post counts, and your real thresholds for what counts as "stale" or "decaying." It reads a short spec back to you for a thumbs-up, then builds the tool around your answers instead of a generic template. From there it walks the agent through the data model, the CSV import, the decay-and-staleness scoring engine, the optional link checker, the ranked review screen, the human approval gate, owner assignment, and the refresh-queue CSV export. Every step ends with a ready-to-copy prompt.
The governance it includes (this is the point)
This isn't a toy. The plan builds in the controls a real marketing operation needs: login so only your team can use it, row-level security so people only see their own organization's content, a complete audit trail of every approve/skip decision and owner assignment (who, what, when, and why), a hard human-approval gate so nothing enters the refresh queue until your content lead decides, and a duplicate guard keyed on the canonical URL so one page can only ever have one open refresh task — even if you re-import the same export twice.
Who it's for
Content managers, SEO leads, and marketing-ops folks sitting on a back-catalog of hundreds of posts with no system for keeping them current. If you can describe what makes a post "stale" in your world, you can build this.
You've got this — open the plan, paste the first prompt, and you'll be ranking your first real refresh queue this weekend.