BlogContent Marketing

How to Write an SEO Content Brief

Amplify Team 3 August 2026 15 min read

A weak SEO content brief hands a writer a keyword, three competitor links, a word count and a deadline. The writer still has to guess who the page serves, what it must prove, which URL owns the topic and how the editor will judge the result.

A useful brief removes those strategic guesses before drafting begins.

It records the decisions that must remain true while giving the writer enough freedom to improve the explanation. That means specifying the page's task, evidence, boundaries, ownership, links, assets and acceptance criteria rather than prescribing every heading or sentence.

This guide starts after you approve the content opportunity. If you still need to select and sequence work, use How to Build an SEO Content Plan. If you have not yet found and mapped the search terms, begin with How to Do Keyword Research for a Kenyan Business.

The brief is a decision record for one page

A content plan answers “What should we work on next?” The brief answers “What must this one page accomplish, and what does the creator need to accomplish it?”

A complete brief connects five layers:

Layer

Decision

Reader

Who needs the page, and what are they trying to do?

Page

Which format and canonical URL should own the task?

Evidence

Which facts, sources, examples and reviewers make the answer credible?

Experience

How should the structure, links, media and next step help the reader finish?

Acceptance

What must the finished page contain and pass before publication?

These decisions matter more than a target word count. Google explicitly says it has no preferred word count. Write enough to complete the task, then remove repetition.

1) Do not open the brief until the page decision exists

Before briefing, confirm these inputs:

  • one customer task;

  • one approved query cluster;

  • one page type;

  • one existing or planned canonical owner;

  • one action: keep, improve, merge or create; and

  • one useful next step for the reader.

If any input remains uncertain, return the item to planning or intent research. A detailed outline cannot repair an unresolved page decision.

Suppose “office cleaning cost Nairobi” might belong inside the main service page or on a separate guide. Do not tell a writer to produce the guide until you inspect current results, customer questions and the service page. If a concise price section can satisfy the need, creating another URL may split one task across two pages.

Record the approved input at the top of the brief:

Task: Help an office manager understand which factors change recurring cleaning cost in Nairobi and prepare for an accurate quotation.
Page type: Pricing guide.
Action: Create.
Canonical: /blog/office-cleaning-cost-nairobi/.
Next step: Review the service scope and request a site visit.

That block gives every later decision a test. If a proposed section does not help the budgeting task, provide necessary evidence or support the next step, question its place.

2) Describe the reader's decision in plain language

“Informational intent” remains too broad for a writer. Describe what the reader knows, what remains uncertain and what they should be able to decide afterward.

Use four fields:

  1. Primary reader: Name the role or situation, not a demographic invented from the keyword.

  2. Starting point: State what the reader probably knows and what they still need.

  3. Decision or task: Write the practical outcome in one sentence.

  4. Next step: Choose an action that follows naturally from the answer.

For the hypothetical cost guide:

  • Primary reader: An office manager, operations lead or business owner planning a cleaning budget in Nairobi.

  • Starting point: They know the office location and approximate size but may not know how frequency, scope, staffing, supplies or access conditions change the quote.

  • Decision: Decide what service scope to request and which information to prepare for comparable quotations.

  • Next step: Read the provider's service page and request a site assessment.

Avoid invented customer quotations. If sales calls, Search Console queries, enquiry forms or support records contain recurring language, cite the internal source in the working brief without exposing private information in the public article.

Kenyan context belongs where it changes the answer. A price brief may need KES, VAT status, service area, transport, local procurement language or relevant regulator sources. A stable technical definition may not need “Kenya” repeated in every heading.

3) Build the evidence pack before the outline

The evidence pack tells the writer which claims the page can make and who owns them.

Divide inputs into four groups:

Evidence type

Examples

Owner

Business facts

Service scope, locations, process, price units, availability, warranties

Product or service owner

First-party evidence

Approved examples, screenshots, tests, customer questions, original calculations

Named internal owner

External authority

Law, regulator guidance, standards, platform documentation, official datasets

Writer or researcher, then reviewer

Market context

Current result formats, competitor coverage, terminology, gaps

SEO researcher; never a factual source by itself

For every material claim, record:

  • the claim the page needs;

  • the preferred source;

  • the access or verification date;

  • any limitation or conflict;

  • the person who confirms it; and

  • what to do when evidence remains unavailable.

“Research current prices” leaves too much ambiguity. A stronger instruction says:

Obtain the company's current quotation inputs from the service owner. Record the charging unit, minimum scope, inclusions, exclusions and VAT status. Do not publish a sample figure until the owner approves it and the editor records the verification date.

Search-result pages can reveal likely format and missing questions, but they do not verify facts. Competitor copy does not prove a price, law, feature or result.

For financial, legal, medical, safety or regulated content, assign a qualified reviewer before drafting. If no reviewer or authoritative source exists, narrow or postpone the page rather than bury uncertainty in a disclaimer.

4) State the answer and its boundaries

Write one promise the finished page must keep:

After reading, the office manager can identify the main cost drivers, prepare the information a provider needs and compare quotations on the same scope.

Then define three sets of boundaries.

Must answer

List questions essential to the task, such as:

  • Which inputs change the quotation?

  • Which services sit inside or outside the base scope?

  • Which units allow useful comparisons?

  • What information should the reader prepare before requesting a quote?

  • What can the provider price publicly, and what requires a site assessment?

May support

Allow closely related information when it improves the same decision. A short explanation of service frequency may help the reader understand cost. A brief link to the main cleaning service may clarify the next step.

Exclude or link elsewhere

Protect the page from neighbouring topics:

  • a full guide to choosing a cleaning company;

  • an operational office-cleaning checklist;

  • job applications;

  • a location page for every Nairobi neighbourhood; and

  • claims about being the cheapest or best without evidence.

Boundaries prevent a “complete guide” from swallowing a cluster. They also give the writer permission to link rather than duplicate.

5) Derive the outline from the reader's decisions

Do not paste the headings from the first five results and call the average an outline. Those pages may target different audiences, carry unsupported sections or repeat each other.

Build the outline by asking what the reader must understand in sequence:

  1. What answer or orientation prevents an early misunderstanding?

  2. Which inputs change the decision?

  3. How does the reader compare options or complete the task?

  4. Which exception or constraint could change the recommendation?

  5. What should the reader do next?

For the hypothetical cost guide, the reasoning might produce:

  1. Explain why a useful quote starts with scope rather than one universal price.

  2. Show the variables that change recurring cost.

  3. Separate inclusions, optional services and exclusions.

  4. Give the reader a worksheet for requesting comparable quotations.

  5. Explain when a site visit changes the estimate.

  6. Link to the service page and quotation route.

The outline should specify the job of each section, not the exact prose:

Section job: Help the reader compare quotations on the same basis.
Required content: Frequency, area, labour, supplies, specialist tasks, access and VAT status.
Format: Compact comparison table followed by interpretation.
Evidence: Approved quotation inputs from the service owner.
Avoid: An invented “average Nairobi price.”

This format gives the writer a reason for the section and room to find the clearest explanation.

6) Specify original value, examples and media

A brief should explain why the page deserves to exist beyond summarising current results.

Choose the original contribution before drafting:

  • an approved process that the business actually uses;

  • an original calculation with visible assumptions;

  • a comparison framework the reader can apply;

  • a checklist built from real operating requirements;

  • first-party screenshots or product data;

  • expert commentary with named ownership; or

  • local examples that change the decision.

Do not write “add expert insight” unless you name the expert, question and approval route. Do not request a case study when the business lacks permission to publish one.

Every numerical example needs a source or a hypothetical label. For a hypothetical cost calculation, show the inputs and operation rather than presenting the output as a market average.

Give every image an editorial job. The brief can request:

  • a scope diagram that separates base and optional services;

  • a screenshot that proves the current interface;

  • a comparison table that reduces repeated prose; or

  • a featured image that attracts and orients without embedding claims.

Record source, rights, alt text, dimensions and review needs. Decorative dashboards and fake growth charts do not strengthen the answer.

7) Add SEO and publishing requirements without superstition

The SEO block should make the page identity and discovery path explicit.

Include:

  • working H1;

  • working title element;

  • working meta description;

  • slug and self-referencing canonical;

  • page type and category;

  • featured-image filename and alt text;

  • existing pages that should link in;

  • contextual internal links from the new page;

  • structured data only when the content and site qualify; and

  • technical or template requirements.

Treat title and description text as editorial inputs, not guaranteed search-result wording. Google recommends descriptive, concise titles. Google primarily creates snippets from page content and may use the meta description when it describes the page more accurately.

Do not turn the brief into a keyword-placement ritual. The primary phrase should help the writer keep the page focused, but the page must use the natural vocabulary the subject requires. Set no density target.

For internal links, record both destination and purpose:

Link

Editorial purpose

Anchor idea

Office-cleaning service page

Let a budgeting reader assess the actual service

office cleaning services in Nairobi

Quotation route

Let a prepared reader request an assessment

request a site visit or quotation

Cleaning checklist

Help a reader who needs to define operational scope

office cleaning checklist

Google's link guidance recommends crawlable links and descriptive, reasonably concise anchor text. It publishes no magical ideal number of links. Include the links that help readers and site structure.

8) Assign ownership and review gates

A brief fails when everyone assumes someone else will verify the difficult part.

Name the roles:

  • Brief owner: Resolves strategy questions and approves scope.

  • Writer: Produces the draft and documents unresolved evidence.

  • Subject reviewer: Confirms product, service, technical or high-stakes facts.

  • Editor: Tests reasoning, sources, voice, structure and reader usefulness.

  • Designer: Produces approved media with source and rights records.

  • Publisher: Implements metadata, links, redirects, media and layout.

  • Maintenance owner: Responds when facts or performance trigger a review.

One person may hold several roles in a small business. Keep the responsibilities explicit.

Set gates around the real risks:

  1. Evidence ready: Required business facts and primary sources exist.

  2. Brief approved: Page owner, task, boundaries and acceptance criteria have agreement.

  3. Subject review passed: A qualified owner confirms material claims.

  4. Editorial review passed: The page answers the task without repetition or unsupported authority.

  5. Publishing QA passed: URL, metadata, images, links, forms and mobile layout work.

Do not use “SEO approved” as a vague final gate. State what the reviewer checked.

9) Define done before the writer starts

Acceptance criteria prevent the editor from changing the assignment after the draft arrives.

Use observable criteria:

  • The introduction identifies the reader's budgeting problem and the page's practical outcome.

  • Every published price or cost claim has an approved source, unit, inclusion, VAT status and verification date.

  • The page distinguishes recurring base scope from optional services.

  • The comparison worksheet helps readers request quotations on the same basis.

  • The page links to the correct service owner and quotation route.

  • The draft invents no customer, ranking, saving, average price or provider result.

  • The title, description and image describe the actual page.

  • The final page passes desktop and mobile review.

Add rejection conditions when a common shortcut would break the page:

  • reject a market-average figure without a defensible dataset;

  • reject copied competitor wording or structure;

  • reject a sales claim disguised as independent advice;

  • reject citations that point only to search snippets or secondary summaries when primary evidence exists; and

  • reject a separate location section for places the business does not serve.

The criteria should evaluate the finished outcome, not force one writing style.

10) Preserve writer judgement

A brief should control truth, purpose and boundaries. It should not reduce the writer to filling boxes.

Mark three instruction levels:

  • Fixed: Reader, task, page owner, factual constraints, required evidence, links, legal or brand rules and acceptance criteria.

  • Preferred: Working title, suggested order, example formats and likely subtopics.

  • Open: Hook, transitions, exact wording, section rhythm and better explanations discovered during research.

Invite the writer to challenge the brief with evidence. They may find that a required section duplicates another page, a source conflicts with the premise or the planned example cannot receive approval. The brief owner should resolve the decision rather than insist on an obsolete outline.

This freedom also prevents every article in a cluster from using the same template. A tutorial, service page, comparison and evidence review require different structures even when one editor briefs them.

11) Brief AI-assisted work with the same ownership standard

An AI prompt can carry a brief, but it cannot own facts, experience or approval.

Google's current generative AI content guidance says AI can help with research and structure while publishers remain responsible for accuracy, quality and relevance across content and metadata.

For AI-assisted drafting, add:

  • source material the system may use;

  • facts it must not infer;

  • first-party claims that require human confirmation;

  • prohibited fabricated quotations, examples and results;

  • required uncertainty or calculation labels;

  • reviewer names and gates;

  • the site's voice and ownership rules; and

  • whether readers would reasonably expect a creation-method disclosure.

Do not ask an AI system to “research current Kenyan prices” and accept unsourced output. Supply verified inputs or require a research stage that records each source for human review.

Glarify can carry keyword, content-type, current-page and planning context into the assignment. It cannot provide private operational facts or approve a claim. Use the tool to organise the handoff, then complete the evidence and ownership fields yourself.

12) Assemble the complete worked brief

Here is the condensed brief for the hypothetical office-cleaning topic.

Page identity

  • Working H1: Office Cleaning Cost in Nairobi: What Changes Your Quote?

  • Page type: Pricing guide

  • Canonical: /blog/office-cleaning-cost-nairobi/

  • Action: Create only after confirming that the service page cannot satisfy the full budgeting task

  • Primary cluster: office cleaning cost Nairobi and close variants that share the same task

  • Reader: Office manager, operations lead or owner planning a recurring-cleaning budget

  • Decision: Define scope and request comparable quotations

  • Next step: Review the Nairobi service page and request a site assessment

Evidence

  • Service owner supplies current quotation inputs, charging units, base scope, optional work, exclusions and VAT status.

  • Writer records verification dates and avoids a market-average price without a defensible dataset.

  • Editor checks Kenyan currency, terminology and service-area claims.

  • Any calculation uses visible hypothetical assumptions unless the company approves current first-party data.

Required answer

  1. Explain why scope prevents one useful universal figure.

  2. Show which variables change recurring cost.

  3. Separate base service, optional work and exclusions.

  4. Give the reader a quotation-comparison worksheet.

  5. Explain when a site visit changes an estimate.

  6. Provide the correct service and quotation links.

Boundaries

  • Do not rank cleaning companies.

  • Do not turn the page into a complete cleaning checklist.

  • Do not target jobs or employment searches.

  • Do not create neighbourhood pages from the same copy.

  • Do not claim cheapest, best or guaranteed savings.

Media

  • Featured image: scope and quote inputs becoming a clear comparison, without prices or performance claims.

  • Optional in-article table: base scope versus optional service versus information required.

  • Alt text describes the visual function rather than repeating the keyword.

Acceptance criteria

  • A reader can prepare the details needed for a comparable quote.

  • Every cost statement has an approved source and context.

  • The page serves a distinct job from the main service page.

  • Internal links lead to the live canonical service and quotation routes.

  • The finished page passes factual, editorial, desktop and mobile checks.

This brief does not tell the writer how many words to produce. It tells them what the page must enable and what evidence earns the answer.

Use a final brief QA before drafting

Read the brief once as the writer and once as the approver.

As the writer, ask:

  • Can I identify the reader and their decision?

  • Do I know which URL and page type own the task?

  • Can I access the facts, sources, expert and assets I need?

  • Do the required sections have clear jobs?

  • Do I know what belongs elsewhere?

As the approver, ask:

  • Does the page deserve to exist separately?

  • Does the brief protect against unsupported claims and duplicate intent?

  • Does every difficult fact have an owner?

  • Will the proposed links move readers through a useful path?

  • Can I judge the finished page against observable criteria?

If either reader still has to guess, the brief is not ready.

A strong SEO content brief creates alignment before expensive work begins. It preserves the reason the page entered the plan, gives the writer verified inputs and lets the editor approve the result against the same decision.

If your team keeps rewriting drafts because page ownership, evidence or acceptance criteria remain unclear, request an SEO audit from Amplify SEO. The audit should resolve the page map and priorities before you scale production. For ongoing briefs, publishing and optimisation, review Amplify's current SEO packages.


Written by

Amplify Team

SEO Strategist

Amplify SEO is a Nairobi growth studio building organic engines for Kenyan brands — technical SEO, local map-pack dominance, editorial content and visibility inside AI answer engines like ChatGPT, Gemini and Perplexity. Everything we publish comes from live client campaigns across real estate, finance, education and e-commerce.