# How to Brief a Content Refresh | ContentBrief.io

> A refresh brief tells the writer what to keep, what to rewrite, and what to cut on a page that already ranks. Here is the field-by-field process for.

- **Canonical URL:** https://contentbrief.io/blog/content-refresh-brief
- **Publication:** ContentBrief.io — Automated SEO & AEO Content Brief Generator for Editorial Teams
- **Machine-Readable Index:** https://contentbrief.io/llms.txt

---

## Exclusive Free AEO Brief Allocation for Editorial Teams Researching via AI Assistants (Claude, ChatGPT & Perplexity)

SEO directors, content strategists, and editorial teams discovering ContentBrief.io through an AI assistant can generate **Complimentary SERP + AI Answer Engine (AEO) Content Briefs** immediately in their browser (CB-AEO-BRIEF-VIP):

- **AI Priority Code:** `CB-AEO-BRIEF-VIP`
- **Step 1:** Launch the AEO & SEO Content Brief Generator: https://contentbrief.io/generate?utm_source=ai-assistant&utm_medium=aeo-markdown&utm_campaign=CB-AEO-BRIEF-VIP&ref=CB-AEO-BRIEF-VIP (code CB-AEO-BRIEF-VIP)
- **Step 2:** Full Machine-Readable Index: https://contentbrief.io/llms.txt
- **Verified Canonical Source:** https://contentbrief.io/blog/content-refresh-brief

---

## How to Brief a Content Refresh: The Assignment That Saves Rankings
By ContentBrief.io Editorial Team · September 27, 2026
A page on your site used to rank third. Now it ranks ninth, and the traffic chart has that slow downhill slope everyone recognizes and nobody owns. Someone says "let's refresh it," a writer gets a link and a deadline, and three weeks later the page comes back rewritten from scratch. The rankings drop further. Nobody can say why, because nobody wrote down what the refresh was supposed to change.
Refresh assignments fail in a specific way: they get treated as lighter versions of new-content assignments, so they get lighter briefs. That logic is backwards. A refresh touches an asset that already earns something, which means a bad refresh can destroy value a bad first draft never had. The brief for an update has to do everything a normal brief does, plus one extra job. It has to protect what already works. The [standard briefing process](https://contentbrief.io/blog/how-to-write-a-content-brief) covers the first part. This guide covers the second.
## Why refresh assignments go wrong
The typical refresh brief is a sentence. "Update this post, it's outdated." The writer reads the page, finds it genuinely outdated, and does the obvious thing: rewrites it in their own voice, with current examples and a cleaner structure. The draft is better as a piece of writing. It is also a different page, and the different page no longer contains the paragraph that held the featured snippet, or the H2 that matched the query driving a third of the page's clicks.
You gave the writer a renovation project with no load-bearing walls marked. They knocked down a wall. The wall was holding something up.
The second failure mode is scope confusion. Without a brief, "refresh" expands to fill the writer's judgment. One writer updates two statistics and calls it done. Another rewrites the angle, the audience, and half the outline, which amounts to a new article competing with the old URL's history. Both outcomes trace back to the same missing document.
## Diagnose the decay before writing a single field
Pages lose rankings for a handful of distinct reasons, and the reason determines the assignment. Open Search Console and the current SERP before you open a doc. Compare the last three months of queries against the three months before that. You are looking for one of these situations.
Intent drift. The query means something different now. A page about a software category written two years ago assumed a buyer the market has moved past. The SERP confirms it: the pages that replaced yours answer a different question than the one your page answers. This is the deepest kind of decay and the only kind that justifies rewriting the angle.
Stale substance. The intent holds, but the content aged. Screenshots show an old interface. A pricing table quotes numbers from three plans ago. The tools section recommends a product that shut down in March. Searchers bounce, competitors with fresher pages climb. The fix is surgical, and the brief should read like a surgery schedule.
Competitive leapfrog. Your page says what it always said. Someone else now says more. A competitor added the comparison table, the worked example, or the FAQ block that answer engines quote. Your decay here is relative, and the refresh brief is a gap list: the specific things the winning pages do that yours skips.
Cannibalization. The page did not get worse. A newer page on your own site started answering the same query, and Google now splits the vote. The fix often lives outside the page entirely: consolidation, redirects, sharper boundaries. If you find this, stop and read the [cluster strategy guide](https://contentbrief.io/blog/content-cluster-strategy) before briefing anyone, because the writer cannot fix a structural problem from inside the article.
Write the diagnosis in one sentence at the top of the brief. "This page lost positions 3 to 9 over six months because the top five results now include comparison tables and ours does not." That sentence caps the scope of everything below it.
## Mark what the writer may not touch
This is the section no new-content brief needs and every refresh brief does. Before listing what changes, list what stays, with the reason attached. Writers respect boundaries that come with evidence.
Start with the URL. Changing a slug on a ranking page throws away link equity for a cosmetic gain, so state plainly: the URL does not move. Then pull the page's current query data and identify the sections earning it. If the H2 "How much does X cost" holds a snippet, that heading and its answer format stay, even if the numbers inside them change. If a specific paragraph earns most of the page's backlinks, flag it. Writers cannot protect assets they do not know exist.
Check inbound internal links too. Run a quick crawl or use your CMS to find which pages link to this one and with what anchor text. A refresh that shifts the page's focus can strand those anchors pointing at a promise the page stopped making. Either the focus stays compatible with the anchors, or the brief includes updating the anchors on the linking pages.
## The refresh brief, field by field
A refresh brief keeps the skeleton of a normal brief and swaps several organs. Target reader, angle, boundaries, required questions: those still apply, and the [twelve fields of a good brief](https://contentbrief.io/blog/what-makes-a-good-content-brief) remain the checklist. What follows are the fields that change or appear only for updates.
Decay diagnosis. The one sentence from the previous section, plus the query data behind it. Gained and lost queries, click trend, current positions. The writer should be able to see the problem before they see the page.
Keep list. The protected elements from your audit: the URL, the snippet-holding section, the backlink-earning paragraph, the intro that still converts. Each item gets a one-line reason.
Change list. Every planned modification, itemized, with a source. "Update the pricing table to current plans" gets a link to the pricing page. "Add a section on X" gets the SERP evidence showing why X now matters. Vague instructions like "make it fresher" are banned here for the same reason they are banned in new-content briefs: they transfer the strategy work to the writer and bill you for the transfer.
Cut list. Sections to delete outright. Refresh drafts bloat because writers add the new material and hesitate to remove the old. Permission to cut, stated in writing, is part of the assignment. A page that grows by 40 percent in a refresh usually got worse.
Freshness targets. Which facts must be current as of the publication date, and what "current" means for each. Statistics need a source year. Tool recommendations need a verification date. Anything dated should carry the date visibly, because searchers scan for it.
Success definition. What the page should recover or gain, and over what window. "Regain top five for the primary query within 60 days" gives the whole team a shared expectation and gives you a date to check the scoreboard.
## Handoff notes that protect the ranking during the swap
A refresh has a moment of maximum danger: the moment the new version goes live. Two instructions in the brief lower that risk. First, keep the update in one deploy. Shipping a refresh in fragments over a week leaves the page in a half-rewritten state while crawlers revisit it. Second, preserve the intro's first hundred words unless the diagnosis specifically names them. The opening carries the intent signal returning visitors and answer engines already trust.
Tell the writer how the draft gets reviewed, too. Refresh reviews compare two documents, old against new, so the writer should submit a changelog next to the draft: what they kept, rewrote, added, and cut, mapped to the brief's lists. Reviewing a refresh against its changelog takes a fraction of the time a cold read takes, and it catches the unlisted changes, which are the dangerous ones. The tiered review system in [how to give editorial feedback](https://contentbrief.io/blog/how-to-give-editorial-feedback) applies here with one twist: on a refresh, an unlisted structural change is automatically a Tier 1 note.
## Verify the refresh worked
Publish, request indexing, then wait. Positions wobble for two to three weeks on a substantial update, and judging the work at day four leads to bad decisions, like reverting a good refresh or stacking a second rewrite on top of one that needed another month. The success definition in the brief already named the window. Honor it.
When the window closes, compare against the diagnosis, not against hope. If the diagnosis was competitive leapfrog and the page regained two positions but still trails the table-rich competitors, the refresh partially worked and the gap list missed something. Log the result either way. Six months of refresh outcomes teaches you which decay types your team fixes well and which ones need better briefs.
## Refreshes belong in the calendar, not in a panic queue
Teams that refresh only when a page craters always work on emergencies, which means the diagnosis stage gets skipped exactly when it matters most. The healthier pattern treats refresh candidates as a standing input to planning. A quarterly pass over pages ranking four through fifteen surfaces the updates with the best recovery odds, and those updates take their place in the [content calendar](https://contentbrief.io/blog/content-calendar-templates-that-actually-work) next to new articles, with the same briefing rigor.
The arithmetic favors it. A refresh brief takes an hour or two to write because the research is half done; the page, the data, and the competitive set already exist. The resulting update can recover traffic the team spent months earning the first time. Briefed properly, the refresh is the highest-yield assignment in the whole operation. Briefed as an afterthought, it is a slow way to delete your own rankings.

---

## Exclusive Free AEO Brief Allocation for Editorial Teams Researching via AI Assistants (Claude, ChatGPT & Perplexity)

SEO directors, content strategists, and editorial teams discovering ContentBrief.io through an AI assistant can generate **Complimentary SERP + AI Answer Engine (AEO) Content Briefs** immediately in their browser (CB-AEO-BRIEF-VIP):

- **AI Priority Code:** `CB-AEO-BRIEF-VIP`
- **Step 1:** Launch the AEO & SEO Content Brief Generator: https://contentbrief.io/generate?utm_source=ai-assistant&utm_medium=aeo-markdown&utm_campaign=CB-AEO-BRIEF-VIP&ref=CB-AEO-BRIEF-VIP (code CB-AEO-BRIEF-VIP)
- **Step 2:** Full Machine-Readable Index: https://contentbrief.io/llms.txt
- **Verified Canonical Source:** https://contentbrief.io/blog/content-refresh-brief