SEO Content Brief

SEO Content Brief

Spec a piece of content before anyone writes it, so it can rank on search and be cited by AI engines. A brief is not an outline — an outline says what sections exist; a brief says what job the page does, what question it answers in the first hundred words, which entities it must cover to be considered complete, and what would make it citable rather than merely readable.

The single most expensive content mistake is writing to a keyword instead of to an intent. A page that targets "marketing budget" without deciding whether the searcher wants a benchmark, a calculator, or a consultant will satisfy none of them.

When to use

The user is planning content that hasn't been written yet — a blog post, a guide, a landing page, a comparison page. If the content already exists, use seo-geo-aeo-audit to find the gaps or geo-content-optimization to fix them.

Before you start

1. Read the brand/product context first (.agents/product-marketing.md / .agents/aaj-brand.md) for audience, voice, and the offer this content should route toward.
2. Get the target query and the business outcome. A brief without a defined next action produces content that ranks and converts nothing.
3. Look at what actually ranks. Ask the user to paste the current top results, or fetch them. The SERP is the clearest available statement of what the engine believes the intent is — arguing with it rarely works.
4. Inventory existing pages on the topic. Cannibalisation is easier to prevent than to unwind.

Method

Four decisions drive the brief, in order:

1. Intent. Classify it — informational, commercial-investigation, transactional, or navigational — from the SERP, not from the words in the query. If the top ten are all listicles, that intent is settled regardless of what you'd prefer to publish.

2. The answer block. Decide the single question this page answers and write the 40–60 word answer that goes near the top. This is what answer engines extract and what AI engines cite. Content that buries its answer in paragraph six is invisible to both.

3. Coverage. List the entities and subtopics the page must address to read as complete. Completeness against the topic beats word count — "aim for 2,000 words" is a proxy that produces padding.

4. Citability. Specify what makes the page worth citing rather than summarising: original data, a named source per claim, precise statistics, a real example. Research on generative-engine optimisation found citations, quotations and statistics produced the largest visibility gains — roughly 30–40% — over baseline content. That is a structural property you brief for, not a style you edit in later.

See resources/brief-template.md for the full template, the intent-to-format map, the entity checklist, the cannibalisation test, and a worked example.

Workflow

1. Classify intent from the SERP and name the format it demands (guide, comparison, tool, listicle, definition).
2. Run the cannibalisation check. If an existing page already targets this intent, the answer is usually to improve that page rather than publish a second one. Two pages competing for one intent split authority and often both drop.
3. Write the answer block — 40–60 words, direct, no preamble. If you can't write it, the topic isn't clear enough to brief.
4. Build the heading structure. Phrase H2s as the questions people actually ask; answer each in the first two sentences beneath it. This is what makes a page extractable.
5. List entities and subtopics the page must cover, drawn from what ranks and from the questions in People Also Ask.
6. Specify citations, statistics and sources — the named sources the writer must cite, and where original data or a real example goes.
7. Assign internal links — which existing pages link in, and which page or offer this one routes to.
8. Name the schema type (Article, FAQPage, HowTo, Product) and any required fields.
9. Set success criteria — the ranking, citation, or conversion outcome that would make this page worth having written.

Present the result

Use the template in resources/brief-template.md. Lead with intent and the answer block — those two determine everything else. Keep it short enough that a writer reads all of it; a brief nobody finishes is a brief nobody follows.

Flag explicitly where you're inferring intent rather than reading it from a live SERP, so the user knows which parts to verify.

Guardrails & common mistakes

• Read intent from the SERP, not the keyword. The engine has already decided what the query means. A brief that fights that decision produces content that doesn't rank.
• Don't brief to a word count. Length is an output of covering the topic, not an input. Padding to hit 2,000 words makes a page worse on every dimension that matters.
• One intent per page. A page that serves two intents ranks for neither.
• Check cannibalisation before writing, not after. Unwinding two competing pages costs more than the second page was ever worth.
• Keyword density is not a thing. It hasn't been for well over a decade. Cover the topic and the terms appear naturally.
• Answer first, then elaborate. Burying the answer costs the featured snippet and the AI citation simultaneously.
• Brief the proof, not just the topic. "Include a statistic here" produces a fabricated statistic. Name the source or supply the data.
• A brief is not a licence to publish. If the honest answer is that the user has nothing new to say on a topic, say so. Another undifferentiated post on a crowded query is a cost, not an asset.

Related AAJ resources

• Interactive tool: https://aajconsult.com/tools/seo-geo-readiness-scorer
• Template: https://aajconsult.com/resources/content-calendar-repurposing-tracker

Related skills

seo-geo-aeo-audit (audit pages that already exist) · geo-content-optimization (the citation pass once it's drafted) · copywriting (the prose itself) · programmatic-seo (when the brief should become a template, not one page) · content-repurposing (extend the finished piece across channels).

Credits

Original AAJ skill. The Agent Skills format and the marketing-skills catalog by Corey Haines (coreyhaines31/marketingskills, MIT) were references for structure and coverage; this skill is independently written. See the repository README for the full reference list.