Search intent is the job behind a query. Mapping it in the brief helps the writer answer the reader's real question instead of assembling a collection of related phrases.
Name the job
Complete this sentence: “The reader wants to…” Use a verb such as compare, plan, fix, learn, or choose. Then describe the reader's situation and what would make the answer actionable.
Choose the article shape
A checklist suits a repeatable task. A comparison suits a decision with meaningful tradeoffs. A guide suits a process that needs ordered steps. Do not force every query into the same format.
Plan supporting evidence
List the claims that need authoritative support and the examples that can be explained from the team's own workflow. If the answer depends on current information, mark the source and review date. Pair the plan with the content brief QA checklist.
Define the next step
The reader should know what to do after finishing. That may be another article, a service overview, or a simple internal task. The next step must follow naturally from the article and should not promise a public price or rate.
Intent mapping gives the draft a spine. It also makes weak or overlapping topics easier to reject before writing begins. +## Pressure-test the interpretation
“Content brief example” may need a usable structure, while “content brief versus editorial brief” needs a decision. Shared words do not guarantee shared intent. Review support questions, sales calls, and site search, then note why this article differs from existing pages.
Make the brief executable
Give the writer a primary question, audience, evidence, exclusions, links, and completion test. A daily publishing guide might require a repeatable morning workflow and a recovery path when a topic is rejected. Clear briefs prevent guessing.
