A content refresh brief tells a writer what an existing page needs and what should stay. Without one, a request to “improve this for SEO” can turn into an unnecessary rewrite, remove useful details or introduce claims the business cannot support. Start with one page and one clearly stated reader problem.
Record the page and the reason for reviewing it
Copy the live URL, page title and review date into the brief. Save a reference copy through your normal backup or version process. Describe the trigger in a sentence: an outdated process, a changed service, repeated customer confusion or a section that no longer answers the intended question.
A traffic change can prompt investigation, but it does not identify the cause by itself. Record the reporting period and relevant changes before deciding that a rewrite is the answer. Separate what you observed from what you think may explain it.
Define the reader’s task
Write down who uses the page and what they should be able to do after reading it. “A local business owner can prepare the information needed for an initial SEO consultation” is more useful than “target more keywords.” Check whether the current page serves that task before adding sections.
If the purpose is unclear, use our search-intent content brief to clarify the audience first. A refresh should have a reason beyond making the document longer.
Divide the page into keep, update and remove
Review the existing headings and give each section a decision. Keep accurate material that answers the reader’s question. Update facts, examples and explanations that need work. Remove repetition or irrelevant material only after checking that it is not needed elsewhere on the page.
- Keep: a clear description of the service process that still reflects how the business works.
- Update: an old delivery timeframe, after the service owner confirms the current wording.
- Remove: a repeated introduction that adds no new information.
- Add: a missing preparation checklist that helps the reader take the next step.
These are illustrative decisions. Put the exact section name and proposed action in your real brief so the writer does not have to infer the scope.
Give every factual change a source and an owner
Link to the source that supports a revised claim. For business-specific facts, name the person who can approve them. Do not invent prices, testimonials, turnaround times, credentials or performance figures to make the updated copy sound more convincing.
Use a small evidence table with columns for the claim, source, date checked and approver. Mark open questions as unresolved. Our service-page proof checklist can help distinguish supported detail from promotional language.
Specify the limits of the update
Tell the writer whether the work includes the introduction, headings, examples, title, description, images or internal links. State any elements that require a separate technical decision, such as changing the URL or redirecting another page. Do not let a copy update silently become a site migration.
Ask for descriptive internal links where they help the reader continue a task. Verify the destinations. Avoid a quota for repeated keywords or links; the brief should explain the purpose of each proposed addition.
Write acceptance checks before drafting
- The page answers the agreed reader question.
- Changed facts have a checked source and business approval where needed.
- Useful existing information remains easy to find.
- Headings describe the actual sections.
- Links lead to the intended pages.
- The live layout works on a narrow screen.
- The change is recorded with its publication date and owner.
After publishing, use an SEO change log to record what actually changed. Set a review date appropriate to the page and your reporting cycle, without promising that a refresh will produce a particular ranking or traffic result.
A reusable brief outline
Copy these fields into your working document: page URL; review trigger; reader task; sections to keep; sections to update; proposed additions; evidence and approvers; work excluded; acceptance checks; owner; review date. A good brief makes the update small enough to manage and clear enough to verify.