First decide whether a page should be created
Many weak content programs begin with a title and skip the question of whether the site already has the answer.
| Decision | Use it when | Required action |
|---|---|---|
| Create | A distinct audience need and page job are not adequately covered | Define the new page's relationship to existing commercial and educational pages |
| Update | The correct page exists but is incomplete, unclear, outdated, or poorly connected | Preserve useful equity while improving answers, evidence, structure, and conversion |
| Consolidate | Several pages overlap and none provides a strong complete answer | Choose the best destination, merge unique value, update links, and redirect retired URLs |
| Retire | The page has no current audience or business purpose and cannot be improved responsibly | Remove it with the appropriate status or redirect based on whether a relevant replacement exists |
Copy this content brief structure
Complete each field with enough specificity that a writer, expert, designer, and reviewer can make the same page—not four different interpretations.
Page purpose
State the job in one sentence: “Help [audience] understand or decide [specific need] so they can [useful next action].”
Audience and situation
Describe who is reading, what they already know, the trigger that brought them here, and any industry, role, or location context.
Primary intent and page type
Classify the need—learn, compare, buy, find locally, troubleshoot, validate—and choose the page type that naturally serves it.
Primary answer
Write the concise answer or value proposition the page should make clear near the beginning. Include conditions and limits.
Required questions
List the follow-up questions, objections, comparisons, process details, costs or timing context, and exceptions that help the reader decide.
Evidence plan
Name the subject-matter experts, first-hand examples, original data, methodology, screenshots, photos, calculations, customer-safe proof, and primary sources.
Search language
Document the primary topic, meaningful variations, entities, and related questions. Explain how they map to sections instead of setting repetition quotas.
Structure
Outline the H1, H2s, supporting H3s, direct-answer placement, comparison or checklist components, and intended reading sequence.
Internal relationships
Identify the parent or commercial page, supporting guides, relevant proof, author or expert pages, tools, and pages that should link back.
Visual and interaction plan
Specify real photographs, diagrams, screenshots, tables, calculators, forms, alt-text purpose, captions, and mobile behavior.
Conversion path
Define the reader's sensible next step and any qualification or expectation-setting required before a call, form, purchase, or tool.
Technical and publishing notes
Include URL, title, description, canonical, schema eligibility, social preview, author, reviewer, accessibility checks, analytics events, and maintenance owner.
Illustrative brief: a local kitchen remodeling service page
This example shows how business context changes the brief. It is not a claim about a TeamSoda client.
| Field | Illustrative entry |
|---|---|
| Purpose | Help San Diego County homeowners evaluate whether the company fits a full kitchen remodel and request a project conversation |
| Primary intent | Find and evaluate a local kitchen remodeling contractor |
| Primary answer | The company manages design and construction for complete kitchen remodels; project fit depends on scope, property, budget, permitting, and desired timeline |
| Required detail | Service scope, design process, construction phases, materials, permits, homeowner responsibilities, realistic timing factors, service area, warranties, communication |
| Evidence | Approved project photos, designer and contractor review, documented process, permit links, customer-approved example, license information where applicable |
| Internal links | Design-build overview, bathroom remodeling, project gallery, service area, process, reviews, contact |
| Conversion | Request a project consultation with property location, scope, timing, and contact details |
Add AEO and GEO fields responsibly
Answer readiness comes from page clarity and evidence—not from adding a collection of AI acronyms to the brief.
Write the direct answer the page should provide in one or two paragraphs.
List the questions a customer is likely to ask next.
Identify important entities and the approved names and relationships for each.
Separate factual claims from opinions, estimates, and scenario-dependent guidance.
Name the primary sources or internal experts needed to support the claims.
Document external profiles or references that should remain consistent with the page.
Specify structured data only when the page visibly contains eligible information.
Define a representative question set if the page will be monitored in answer systems.
Explain what the page should help a human do after receiving the answer.
If AI assists the content workflow
The brief should make the allowed role, approved source set, and review responsibility explicit.
Allowed support
Examples include clustering research, summarizing approved notes, identifying missing questions, formatting tables, checking consistency, and proposing alternatives for human review.
Prohibited shortcuts
Do not invent interviews, examples, clients, statistics, citations, local experience, test results, or performance claims. Do not paste confidential customer or company data into an unapproved system.
Human accountability
Name the writer, subject expert, editor, legal or compliance reviewer where needed, and final publisher. “AI reviewed it” is not an accountable approval step.
Fact and source record
Keep a simple ledger connecting consequential claims to approved evidence and note which details require future review.
Editorial and publishing quality check
A completed draft is not a completed page.
The opening answers the primary question without unnecessary scene-setting.
The headings form a logical outline and do not skip levels for styling.
Every consequential claim is accurate, supported, and approved.
Examples are real or explicitly labeled illustrative.
The page adds value beyond the current search results and internal site content.
Internal and external links are accurate, descriptive, and useful.
Images are relevant, rights-cleared, compressed, and given appropriate alternative text.
The page works with keyboard navigation, zoom, mobile screens, and readable contrast.
Metadata and structured data match the visible content.
The call to action matches the reader's stage and lands at the exact next action.
Analytics events and form notifications are tested.
The page has an owner and a reason to be reviewed or retired.
What to review after publication
Evaluate whether the page is doing its assigned job before changing it to chase isolated fluctuations.
| Signal | Question | Possible response |
|---|---|---|
| Indexing and crawl | Can search systems access and retain the intended canonical page? | Resolve technical or duplication problems before rewriting |
| Query and result fit | Is the page appearing for the audience and intent defined in the brief? | Clarify purpose, title, headings, content, or page relationships |
| Engagement | Do visitors continue to relevant sections, pages, tools, or actions? | Improve answer order, navigation, media, proof, or next steps |
| Conversion quality | Are actions legitimate and commercially relevant? | Adjust qualification, offer clarity, audience targeting, or sales follow-up |
| Maintenance | Have facts, examples, links, platform behavior, or business details changed? | Update the source and note the review responsibility |
Primary sources and further reading
Platform behavior can change. These official sources support the platform-specific statements in this guide and provide the best place to verify current requirements.
Frequently asked questions
How long should an SEO content brief be?
Long enough to remove important ambiguity. A simple service-page update may need one focused page; a regulated, technical, or research-led guide may need substantially more evidence and review detail.
Should a brief prescribe an exact word count?
Usually not as the primary requirement. Define the questions, evidence, comparisons, examples, and user task. An estimated range can help planning, but completeness and clarity matter more than reaching a number.
Who should approve the brief?
The strategist should confirm purpose and search intent, a subject expert should confirm accuracy and evidence, and the person responsible for the business outcome should approve the conversion path. Technical, design, legal, or compliance review may also be needed.
Can the same brief support SEO, GEO, and AEO?
Yes. A useful brief can define discoverability, direct answers, entity clarity, evidence, source relationships, and the next human action in one connected plan.