Website Content Refresh Brief Template

A refresh brief keeps an old page from becoming a series of uncoordinated edits. It should explain why the page matters, what evidence needs review, what changes are in scope, and how the team will know the update helped.

Record the current page

Capture URL, title, intent, audience, traffic, queries, conversions, links, backlinks, freshness, and known issues. Note the page's role in the site so a rewrite does not remove a useful bridge to another topic.

Define the customer question

Write the primary question, related questions, decision stage, and expected next action. Use actual search, form, sales, and support language instead of a keyword list detached from the customer.

List evidence and claims

For pricing, timelines, outcomes, service scope, credentials, locations, and examples, record source, date, owner, limitations, and approval. The content claim source checklist helps identify unsupported or stale statements.

Set the update boundary

Decide whether the work is copy, structure, design, technical SEO, internal links, form routing, images, schema, redirect, or consolidation. State what is explicitly out of scope to prevent a refresh from becoming an unplanned rebuild.

Define acceptance checks

Include accuracy, reading level, headings, links, accessibility, mobile layout, metadata, analytics, form behavior, and approval. Add a rollback or archived version when the page has meaningful search or business value.

Measure after publishing

Compare qualified traffic, engagement, search refinements, form starts, conversions, and support questions over an appropriate period. Use the content refresh prioritization guide to decide what should be reviewed next.