Turn search evidence into a content refresh brief
Create a focused editorial brief with an audience, problem, evidence and acceptance criteria.
A refresh brief translates a reporting observation into a better answer for the reader. It should tell an editor what is missing or wrong, not just request more words. Preserve the useful parts of the existing page and name the specific decision the revision should help.
Work through it, step by step.
Select a page and query group with a clear reason for review. Record its purpose, current evidence and any sustained loss or new relevant exposure.
Read the existing answer and list factual gaps, obsolete steps and confusing sections. Separate required corrections from optional presentation improvements.
Define acceptance criteria and a sensible evaluation window. Include internal links and examples only where they help complete the reader’s task.
Make it concrete.
A guide still describes a retired interface and omits the replacement workflow. The brief should specify the steps to correct and how to verify them, rather than prescribing an arbitrary word count.
What to keep in mind.
A new date and a longer introduction do not establish that the content became more useful. Avoid claiming a refresh will produce a specific ranking or traffic gain.
Your next useful step.
Give the editor a small, reviewable task and preserve the release date in the reporting note. Evaluate accuracy first, then observe the relevant search evidence.
Working with this in Liftaven
Choose a single business question before requesting data. Write down the accounts, dates and definitions that make the answer reproducible. Liftaven provides the reporting workspace and authenticated MCP access; decisions and changes remain with you.
Explore the AI workflowSources & context
This note combines original practical guidance with the reporting references below. Follow provider documentation for current definitions and availability; suggested investigations are not guarantees of a particular result.