Content Refresh Workflow: Reviving a Decayed Post, Step by Step

This is the per-post execution workflow behind the content refresh strategy. Input: one decayed post that used to perform. Output: a genuinely updated page with honest freshness signals. Time: about 90 minutes with AI doing the labor.

Prerequisites: the post, its performance history, an AI assistant that can browse or accept pasted sources, and edit access to your CMS.

The workflow

Step 1: Snapshot what's working (10 minutes)

Before touching anything, record what the page currently earns: its ranking queries, any AI-answer citations (from your visibility audit if you run one), and its backlinked or frequently-quoted passages. These passages are load-bearing — mark them protected. The cardinal refresh sin is regenerating the exact paragraph that earned the page its authority.

Step 2: AI fact audit (20 minutes)

Extract every factual claim, statistic, date, price, product name,
and external reference in this post. For each: quote it, note where
it appears, and classify — (a) timeless, (b) likely stale, (c) can't
verify. Do NOT correct anything. List only.

The "do not correct" instruction matters: you want a flag list, not silent "fixes" from model memory — that's how hallucinated numbers infiltrate archives. A human verifies every (b) and (c) against current sources and writes the corrections.

Step 3: Gap and intent check (15 minutes)

Ask: what does someone searching this topic in 2026 need that this post doesn't cover? Feed the AI the post plus two or three currently top-performing competitor pieces on the topic:

Compare our post to these current pieces. What questions do they
answer that we don't? What sections do we have that no longer match
what a searcher wants? What's changed in this topic since our
publish date that we don't address?

The output is your addition/removal plan — typically one or two new sections, one retired one.

Step 4: Surgical rewrite (30 minutes)

Work section by section. Corrections from Step 2 get applied verbatim. New sections from Step 3 get drafted by AI with sources provided, then edited to match the post's existing voice. Protected passages from Step 1 are touched only to fix verified errors. The intro usually deserves a fresh human pass — it's where staleness shows first and where generic AI rewrites are most detectable.

Step 5: Structure and schema pass (10 minutes)

Run the GEO content checklist quickly: quotable definition near the top, heading hierarchy clean, FAQ section if genuine questions emerged in Step 3. Update dateModified in your schema and add a visible "Updated [month year]" note — both truthful, since you actually changed things.

Step 6: Log and requeue (5 minutes)

Record what changed and why in your content log, and set the post's next review date (quarterly for defenders, annually for the long tail). Refresh is a loop, not an event.

Failure modes and fixes

• The rewrite virus: AI "improving" every paragraph it touches until the post is new and worse. Fix: paste sections individually with "change only what the correction requires."
• Date theater: updating dateModified after cosmetic edits. Engines cross-check content diffs against date claims; getting caught discounts all your dates.
• Refreshing the unrefreshable: some posts decayed because the topic died. Twenty minutes into a refresh with nothing real to update? Wrong bucket — merge or prune it instead.