How to Write an SEO Content Brief (with a Worked Example)

A useful SEO content brief tells a writer what the reader needs to accomplish, what the existing page or search results already provide, and what evidence this page can add. It also settles a decision that is easy to skip: should you create a new URL at all?

A target keyword and an outline are only the beginning. A writer still needs to know whom the page serves, which claims need checking, what the finished piece must contain, and how you will judge it. This guide gives you a copyable brief and a filled example from a real editorial plan. It starts where our Search Console content map ends: with a proposed topic that needs to become a clear assignment.

1. Decide whether this is a new page or an update

Before opening a blank document, write the reader's task as a sentence: “I need to ___ so I can ___.” Then name the closest existing URL on your site. If that page already promises the same outcome, improving it is usually a clearer assignment than publishing a second near-duplicate.

If your site already appears for the query, filter Search Console → Performance to that query and check the Pages tab. Google's Performance tasks guide documents this query-to-page view. Read the page Google is showing: is its answer incomplete, buried, or out of date? If so, brief an update on that URL. The report does not show every possible query or guarantee that the same URL appears for every searcher, so treat it as evidence to inspect, not a verdict.

For similar searches with possibly different outcomes, use our one-page-or-two test before assigning a new slug. The brief should state why the existing page cannot satisfy both tasks without making the answer harder to use.

2. Read the results for the deliverable, not an outline to copy

Search two or three representative phrases and record the date and locale. Note the form of the useful results: a tutorial, template, tool, comparison, checklist, or service page. Ask what someone could actually do after reading them. A result page is a snapshot of what is being offered, not a list of headings you must reproduce.

For example, a check of English-language results for “SEO content brief” and “content brief template” on 21 October 2026 surfaced guides with templates and filled examples. That is a clue that a reader wants something reusable, not another definition-only article. The brief for this page therefore required both a copyable worksheet and a completed example. Search results change; record your observation rather than claiming a permanent ranking pattern.

Write one line about the gap you can responsibly fill. “The top pages are long” is not a useful gap. “Our example shows the update-versus-new-URL decision and a source-checking handoff” is a concrete editorial contribution. Google's people-first content guidance asks whether a page adds original information or analysis and helps its intended audience achieve a goal.

3. Specify the evidence and the writer's boundaries

Separate three things in the brief:

• Observed: what you actually saw in a report, public page, interview, test, or product. Add the date and scope.
• Documented: what an authoritative source says. Link it and note claims that may change.
• Proposed: the angle, example, or hypothesis you want the article to test or explain. Do not write it as a proven result.

This distinction matters when a brief mentions AI search, ranking systems, indexing, or a new product feature. A writer should never have to invent a screenshot, statistic, customer result, or first-person experiment to make the outline work. If the needed evidence is unavailable, narrow the piece or postpone it.

Copy this one-page SEO content brief

Fill these fields in plain language. A short, specific answer beats a long document full of keyword variations.

• Reader and task: Who is stuck, and what should they be able to decide or do afterward?
• Page decision: New URL, update an existing URL, consolidate, or defer? Name the closest existing page and explain why.
• Query group and locale: One main phrasing, a few natural variants, and the country/language you checked. Describe intent rather than prescribing repetition.
• Result observation: Date, representative searches, useful result types, and the reader need those results suggest.
• Distinct contribution: The original example, worksheet, screenshot, interview, or documented test this page can actually provide.
• Answer and structure: The answer near the top, then only the sections needed to complete the task. List what is out of scope.
• Sources and claim checks: Primary documentation, evidence owner, dates, and claims that need verification before publishing.
• Internal path: A useful parent guide, related next steps, and one older page that should link to this page after publication.
• Acceptance check: What must be present and correct before the draft can go live? Include factual, usability, link, and metadata checks.
• Review: Publication date, the query/page filters to revisit, and the useful action you can measure. Do not promise rankings.

There is no mandatory word count or keyword-density field. Give a length only if the format has a real constraint, such as a short FAQ answer or a print handout. Google's SEO Starter Guide recommends content that is useful, well organized, and easy to understand, rather than trying to satisfy a fixed word target.

A filled brief: a page-indexing decision guide

The example below is a public-safe excerpt of a real brief prepared for a planned guide on why a page is not indexed. It records an editorial decision, not a published outcome or a claim about this site's private Search Console numbers.

• Reader and task: A site owner sees “Not indexed” in Search Console and needs to decide whether a particular important URL should be indexed, what evidence to inspect, and which action to take.
• Query group: “page not indexed Search Console,” plus the narrower “discovered – currently not indexed” and “crawled – currently not indexed” questions. The page is a troubleshooting decision guide, not a broad introduction to how search engines work.
• Result observation: On 21 October 2026, public results for the topic included Google's Page indexing report help and reason-specific fix guides. The brief calls for a reason-to-action decision tree, with a copyable record for one URL.
• Existing-page decision: The site's search-engine fundamentals guide explains crawling, indexing, and ranking. The new page has a different finish line: inspect one URL and decide whether to keep, fix, wait, or escalate. If drafting merely repeats the fundamentals guide, update that URL instead.
• Distinct contribution: A decision tree that starts with “Should this exact canonical URL be indexed?” and a worksheet recording URL, intended canonical, report reason, indexed versus live inspection, action, and recheck date.
• Sources and boundaries: Use Google's Page indexing and URL Inspection help. Do not call every excluded URL an error, treat a single status as proof of poor quality, or promise that an indexing request will work.
• Acceptance check: Each branch names the evidence a reader should inspect; expected redirects and duplicates are separated from important canonical pages; links and metadata are checked; no private property data or invented screenshot appears.

Compare that with “Write 1,500 words about indexing and use the keyword five times.” The filled brief tells a writer which question to answer, which existing article to avoid repeating, what artifact to produce, and what would make the draft wrong.

Hand off the brief, then review the actual page

Before drafting, ask someone unfamiliar with the plan to read the brief. Can they name the reader's decision and the evidence they will need? If the answer is vague, fix the brief. When the draft comes back, check the promised answer first, then source claims, examples, links, headings, title, description, and mobile readability. An editor can change the outline when a better answer becomes clear; the brief is a shared decision record, not a contract to keep weak sections.

After publication, record the URL and revisit the relevant non-branded query group and page in Search Console after enough time has passed for discovery. Compare impressions, clicks, CTR alongside position, and country/device mix; an immediate indexing request is not a traffic result. If readers cannot find the new page from related guides, use our internal-linking audit to choose a contextual path.

Optional tool, with disclosure: Opportunity Finder is a separate project connected to The SEO Station. For SaaS sites, it can turn a website into prioritized page ideas and editable briefs. Use its suggestions as starting points; the reader task, evidence, and final editorial decision still need a human check.