Make Old Content Earn Again

You published it. It ranked. Then it slipped, and nobody told you. The page that used to bring people in is still sitting there, a year out of date, quietly losing ground while you write something new to replace it. That's the tax on publish-and-forget: you keep paying for new content because the old content stopped working, and you never went back to find out why.

This is a maintenance system for content you already own. It removes the guesswork about which pages deserve your time, what's actually wrong with them, and what to do about it in an hour.

Read This First: Your Content Compounding Map is a six-page orientation. Four short chapters — What You're Holding, The Order That Works, Your First Hour, and How To Get Real Results — plus a five-item checklist that sets your sequence before you touch a single page. Five minutes here decides whether the rest of this becomes published results or another download.

Make Old Content Earn Again is the twenty-page core guide, and it's the system itself. It opens with The Publish-and-Forget Tax, then walks the five moves: Anchor (decide what deserves maintenance), Watch (catch drift before it costs you), Rework (fix the weakness, not the whole page), Reissue (get eight assets out of one), and Resend (put old work back in front of people). It closes with The Maintenance Calendar, Keeping the Loop Alive, and Your First Seven Days. Seventeen checklist items and an exercise turn the reading into decisions you've actually made.

The Content Rescue Checklist is the fourteen-page working document — the one you open when a page is slipping. Six phases: find the page that's slipping, diagnose before you touch a word, run the 45-minute rescue, and prove it worked. It ends with The Rescue Scorecard and Your Maintenance Rhythm. Twenty-nine checklist items, so you're never guessing what comes next mid-repair.

The 7-Day Content Revival Sprint is eleven pages and thirty-nine checklist items, built for thirty-minute sessions. One day per step: find the slippage, score and choose one page, diagnose before you edit, make the repairs, set the tracking, put the page back to work, and turn one sprint into a system. A 30-Day Verdict section tells you how to read what happened. You pick one decaying page and prove the system on it before you scale it.

This is for anyone with a back catalog they stopped looking at — a blog, a resource library, a set of landing pages that used to pull. Fifty-one pages across four documents. At the end you have one rescued page with tracking on it, a scorecard that tells you whether the fix held, and a maintenance calendar that keeps the rest of your library from going the same way.