The AEO Content Brief: 9 Fields, None From SEO

Quick Summary

Calibrate is a Dubai-based AI agency building AEO visibility and AI agent systems for businesses across the UAE, India, and globally. Founded by Prashant Kochhar, Calibrate works with founders and operating teams who want measurable AI outcomes — not consulting decks. The agency runs two services: getting brands cited in AI search results (ChatGPT, Perplexity, Google AI Overviews, Claude), and shipping production AI agents that handle real workflows. Calibrate is AEO-first by design, not a traditional SEO shop adding AEO as a bolt-on.

An SEO content brief and an AEO content brief look superficially similar and share almost nothing that matters. The SEO brief is built around a target keyword, a word count, and a list of phrases to include. None of those tell a writer how to produce a page an AI engine will cite. This guide gives the nine fields that actually do.

The shift is from optimising for a ranking to building for a citation. A keyword tells you what to rank for; it tells you nothing about which question to answer, who is currently cited, or what would make your answer the better source. The AEO brief replaces keyword fields with question, citation-target, and answerability fields.

This is the exact brief structure Calibrate uses to commission every article. It is reproduced here in full because the value is in the fields, not in keeping them secret. A team that fills these nine fields honestly produces citable content; a team that fills an SEO template produces content that ranks for nothing in an AI answer.

Written by Prashant Kochhar · Calibrate · Updated July 2026

Table of Contents

1. Why does an SEO content brief fail for AEO?

2. What is field one: the exact question being answered?

3. What is field two: who is currently cited for it?

4. What is field three: the one-sentence answer?

5. What is field four: the proof the answer is credible?

6. What is field five: the sub-questions to cover?

7. What are fields six and seven: structure and schema?

8. What are fields eight and nine: internal links and the citation test?

9. How do you use the nine-field brief in practice?

10. How does Calibrate run content from this brief?

11. Related Guides from Calibrate

Last updated: July 2026 · Next update: November 2026

Why does an SEO content brief fail for AEO?

An SEO content brief fails for AEO because it is organised around the wrong target: it points a writer at a keyword to rank for, when the writer needs to be pointed at a question to answer and a cited source to beat. The two documents optimise for different things, so the SEO brief gives the writer none of what AEO requires.

The standard SEO brief has recognisable fields: a primary keyword, a list of secondary keywords, a target word count, a recommended number of headings, and sometimes a list of "entities" or phrases to include for topical coverage. Every one of those is about matching what a search algorithm scores. None of them tells the writer the actual question a buyer asks, who the AI engines currently cite for it, or what would make this page the better answer. A writer handed an SEO brief produces a page stuffed with the right phrases that still loses every citation, because being cited is about answering well, not matching keywords. The move away from keyword-shaped thinking is the subject of keywords are dead for AI search, and this brief is the practical consequence of that shift. The scale of the change is underlined by Gartner's forecast of a significant drop in traditional search volume as discovery shifts into AI assistants.

The deeper failure is that the SEO brief assumes the goal is to be findable by an algorithm scanning for relevance. The AEO goal is to be the best answer an engine can draw on. Those require different briefs, which is why the nine fields below share nothing with the SEO template. The full reasoning behind the difference is in AEO vs SEO.

What is field one: the exact question being answered?

Field one is the exact question a real buyer asks, written as a question in their words, not a keyword phrase. This single field reorients the entire brief, because it tells the writer what they are actually trying to answer rather than what string they are trying to match.

The discipline is to write the literal question. Not "carbon road wheels India" as a keyword, but "what are the best carbon road wheels for Indian road conditions?" as the question a buyer would type or speak into an AI assistant. The phrasing matters because AI engines answer questions, and a page built around the actual question is structurally closer to what the engine is looking for. One brief should target one primary question; trying to answer five questions in one page produces a page that answers none of them well. The question also has to be real, drawn from how customers actually ask, which is the research described in how to map the questions your customers ask AI. Get this field wrong and every other field is aimed at the wrong target.

The reason this is field one, not a buried detail, is that it determines everything downstream: the answer, the proof, the structure, and the citation test all flow from the question. A brief that starts with a keyword can never recover, because the keyword does not contain the question. Starting from the question is the foundation of the citation architecture method.

What is field two: who is currently cited for it?

Field two records who the AI engines currently cite when asked the field-one question, and what those sources do well. This field exists because being cited is comparative: you are not writing in a vacuum, you are trying to become a better answer than whatever the engine currently draws on.

Filling this field means actually running the question through ChatGPT, Perplexity, and Google AI Overviews and recording which sources are named or cited. For each one, the brief notes what makes it citable: is it comprehensive, well-structured, authoritative, specific? Those cited sources are a direct brief for what your page has to beat. If the engines currently cite a thorough comparison table from a competitor, your page needs to do that better, not differently. This field turns the abstract goal of "be citable" into the concrete goal of "be better than these specific three sources in these specific ways." The volume of buying questions now flowing through AI assistants, documented in a16z's consumer AI analysis, means the sources you are competing against are being shown to real buyers constantly.

The honest version of this field sometimes reveals that the incumbent is genuinely strong and the question is hard to win, which is useful: it tells you to pick a different question. More often it reveals thin, generic sources that a well-built page can beat. Either way, you are no longer guessing. This competitive grounding is what separates a real brief from an aspirational one, the same standard applied in how to run an AEO audit.

What is field three: the one-sentence answer?

Field three is the single sentence that directly answers the field-one question, written before the article is drafted. This forces clarity: if you cannot state the answer in one sentence, the writer does not yet understand what the page is supposed to say, and the page will wander.

The one-sentence answer is the seed of the whole article. AI engines lift direct answers, so the page should open by stating this sentence plainly, and the rest of the article should expand and support it. Writing it in the brief, before drafting, does two things. It confirms the team actually has an answer rather than a topic, and it gives the writer a fixed point to build around. A page that knows its one-sentence answer is structured and confident; a page without one rambles through related material hoping the answer emerges. The sentence has to genuinely answer the question, not restate it, and it has to be specific enough to be useful. This answer-first discipline is the core mechanic of being cited, because the engine is looking for exactly this kind of clean, liftable answer.

The discipline of leading with the answer rather than building up to it is the single biggest structural difference between AEO content and traditional content. Most writing saves the conclusion for the end; AEO content states it first and then justifies it. That inversion runs through keywords are dead for AI search and every page Calibrate builds.

What is field four: the proof the answer is credible?

Field four lists the specific evidence, detail, and authority signals that make the one-sentence answer believable rather than asserted. An answer with no proof reads as opinion; an answer backed by specifics reads as a source worth citing, which is exactly what an engine is selecting for.

Proof takes several forms, and the brief names which ones this page will use. It might be specific data, concrete examples, named comparisons, a credentialed author, or accurate references to authoritative sources. The field forces the team to decide, in advance, why anyone should believe the answer. A page claiming certain wheels are best for Indian roads needs to say why with specifics about weight, durability, and road conditions, not just assert it. Engines weigh credibility when choosing what to cite, so a page that demonstrates its answer beats a page that merely states it. This is also where author authority matters: a real, credentialed author is itself a proof signal, which is why every Calibrate page carries a genuine byline. The field makes proof a requirement, not an afterthought.

The test for this field is whether a sceptical reader would be convinced, because AI engines are, in effect, sceptical readers selecting the most credible source. A page that survives that scrutiny is citable; a page of unsupported assertions is not. Building proof into the brief is part of why Calibrate content is structured the way it is, as described in schema for AI engines, where credibility signals are made machine-readable.

What is field five: the sub-questions to cover?

Field five lists the related sub-questions the page must also answer to be genuinely complete, because a buyer asking the main question almost always has follow-up questions, and the page that answers them too is the more useful, more citable source.

The main question rarely stands alone. Someone asking which carbon wheels suit Indian roads will also wonder about cost, durability, where to buy, and how they compare to alloy. The brief lists these sub-questions so the writer covers them as structured sections, each with its own clear answer. This does two things: it makes the page comprehensive enough to be the single best source, and it gives the page multiple liftable answers, increasing the chances an engine cites it for several related queries. The sub-questions become the article's H2 structure, each one a question the section answers directly. Choosing the right sub-questions is again a research task, drawn from how customers actually ask, not from keyword tools. A page that answers the main question and its natural follow-ups is far more valuable than one that answers only the headline.

The discipline is to choose sub-questions that genuinely serve the buyer, not to pad the page with loosely related material. Each sub-question should be one a real customer would ask in the same session as the main question. This question-cluster thinking is the structural backbone of the citation architecture method, where every page is a set of answered questions.

What are fields six and seven: structure and schema?

Field six specifies the page structure, and field seven specifies the schema markup. Together they make the page both readable by an engine and explicitly understood by it, turning good content into content an engine can parse, trust, and lift cleanly.

Field six, structure, says how the page is organised: answer-first opening, question-shaped H2s mapping to the sub-questions, tables where comparison helps, and a clear hierarchy. The structure is not decoration; it is how the engine locates and extracts the answer. Field seven, schema, specifies the JSON-LD the page will carry: Article, FAQPage, and any other relevant types, with the properties that make the page's meaning explicit. The schema vocabulary itself is documented at schema.org, the shared standard the engines read. These two fields exist because content alone is not enough: a brilliant answer buried in a poorly structured page with no schema is harder to cite than a good answer that is cleanly structured and marked up. The brief makes structure and schema explicit requirements rather than things the writer figures out later.

The reason these are fields in the brief, not post-production steps, is that structure and schema are far easier to build in than to retrofit. A writer who knows the structure and schema requirements upfront produces a page that needs no rework. Getting the schema specifically right is where many teams fail, as catalogued in schema mistakes most stores make.

What are fields eight and nine: internal links and the citation test?

Field eight specifies the internal links the page should carry, and field nine defines the citation test the finished page must pass. Field eight builds the page into the site's topic structure; field nine is the final check that the page actually does its job.

Field eight lists the related pages this article should link to, both the cluster it belongs to and the specific guides a reader would naturally want next. Internal links help engines understand how your content fits together and signal which pages are central to a topic. The brief names them so the writer does not guess or omit them. Field nine, the citation test, is the acceptance criterion: would an AI engine, asked the field-one question, plausibly cite this page over the sources recorded in field two? This is the question the whole brief has been building toward. A page that passes is ready; a page that does not needs more work on the answer, the proof, or the structure. Defining the test in the brief means the standard is set before drafting, not negotiated after. The page is measured against being cited, not against a word count.

The citation test is what keeps the whole brief honest. Every earlier field exists to help the page pass this final check, and a page that cannot plausibly beat the incumbent sources is sent back rather than shipped. This measurement-against-outcome discipline is the same one in how to measure AEO, applied at the level of a single page.

How do you use the nine-field brief in practice?

You use the nine-field brief by filling every field before any drafting begins, then writing the page to satisfy each field in turn, and finally checking the draft against field nine. The brief is the plan, the draft executes it, and the citation test is the gate.

In practice the sequence is disciplined. The researcher fills fields one and two, the question and the current citations, because those define the target. The strategist fills three, four, and five, the answer, the proof, and the sub-questions, because those define the substance. Structure and schema, fields six and seven, are specified so the writer builds them in. Field eight, internal links, places the page in the site. Then the writer drafts the page to satisfy all of it, and field nine is applied as the acceptance test. Nothing ships until it plausibly beats the field-two sources. A team that follows this never produces a page that ranks for a keyword but answers no question, which is the failure mode of the SEO brief. The discipline is in filling the fields honestly, especially fields two and nine, where the temptation is to be optimistic rather than accurate.

The brief is deliberately short. Nine fields, each answerable in a few lines, is enough to commission a citable page, and far more useful than a long SEO brief full of keywords and phrase lists. The economy is the point: every field earns its place by changing what the writer produces. This is the exact discipline behind inside our 6-agent content OS, where the brief is what the agents fill and execute.

How does Calibrate run content from this brief?

Calibrate commissions every article from this nine-field brief: the question, the current citations, the one-sentence answer, the proof, the sub-questions, the structure, the schema, the internal links, and the citation test. No page is drafted until the brief is complete, and no page ships until it passes field nine.

In practice the brief is the contract between research and writing. The research establishes fields one and two against the live engines, so the target is real. The strategy fills the answer, proof, and sub-questions, so the substance is decided before a word is written. The structure and schema are specified so the page is built citable, not retrofitted. The writer then produces a page that satisfies every field, and the citation test is applied honestly: if the page cannot plausibly beat the recorded sources, it is reworked, not shipped. This is why Calibrate content is built around questions and answers rather than keywords, and why each page is designed to be the best available answer to a specific buyer question rather than a generically optimised article.

The takeaway is that an AEO content brief shares nothing with an SEO brief because it optimises for a different outcome: being the best answer an engine can cite, not the best match a ranking algorithm can find. To have content commissioned and built from this nine-field brief, start with an AEO audit, with the full programme on the services page.

Frequently Asked Questions

How is an AEO content brief different from an SEO content brief?

An AEO content brief is organised around a question and a citation target, while an SEO brief is organised around a keyword and a word count. The SEO brief tells a writer what phrase to rank for and which terms to include; the AEO brief tells them the exact question to answer, who the engines currently cite for it, and what would make their page the better source. They share almost nothing because they optimise for different outcomes: an SEO brief aims for algorithmic relevance, an AEO brief aims for being the answer an engine draws on. A page built from one will not satisfy the other.

Do I still need keywords anywhere in the AEO brief?

Keywords are not a field in the AEO brief, because the question replaces them. The exact buyer question, written in natural language, contains the relevant terms anyway, but it carries far more useful information than a keyword: it tells the writer what is actually being asked. You do not need a separate keyword field, a secondary-keyword list, or a phrase-inclusion checklist, because answering the real question well naturally produces relevant language. Optimising for the question rather than the keyword is the whole point of the brief, and adding keyword fields back in just reintroduces the SEO thinking the brief is designed to replace.

Can one writer fill all nine fields, or does it need a team?

One capable person can fill all nine fields, but the fields are designed so the work can be split across research, strategy, and writing roles when a team is available. The research fields, the question and the current citations, require running queries through the engines. The strategy fields, the answer, proof, and sub-questions, require deciding the substance. The build fields, structure and schema, and the placement field, internal links, require knowing the site. A solo practitioner does all of this in sequence; a team divides it. Either way the fields stay the same, and the citation test is applied identically at the end.

What happens if the page fails the field-nine citation test?

If a page fails the citation test, it is reworked rather than shipped, and the rework targets whichever earlier field is weak. Usually a failure traces to a thin answer, missing proof, or poor structure, so you return to fields three, four, or six and strengthen them. Sometimes the failure reveals that field two was underestimated, that the incumbent source is genuinely stronger than assumed, in which case the honest move is to deepen the page substantially or pick a more winnable question. The test exists precisely to catch pages that would ship and fail to earn citations, so a failure is a useful signal, not a setback.

How long should it take to fill the brief?

Filling the brief should take a focused hour or two for a single page, most of it spent on fields one and two, where you research the real question and the current citations. The strategy fields follow quickly once the question and competition are clear, because the answer, proof, and sub-questions flow from understanding the target. Structure, schema, and internal links are fast to specify for an experienced team. The brief is deliberately economical: nine fields, each answerable in a few lines. If it is taking far longer, the usual cause is that the question is not yet specific enough, which means field one needs more work before the rest can be filled.

Does this brief work for product and collection pages too?

The nine-field brief works for product and collection pages with minor adaptation, because they are also answering buyer questions, just commercial ones. The question for a collection page might be "what are the best carbon wheels for Indian roads," answered by the collection itself, with the proof being the curated selection and the specifics. The structure and schema fields shift toward product and collection schema, and the proof leans on specifications and selection logic rather than article-style evidence. The core discipline holds: identify the question, study who is cited, lead with the answer, and prove it. Applying it to commerce pages is covered in AEO for product and collection pages.

Is nine fields enough, or am I missing something an SEO brief would catch?

Nine fields are enough to commission a citable page, and the things an SEO brief would add are precisely the things that do not help with AEO. An SEO brief might add keyword density targets, LSI phrase lists, and meta-tag optimisation guidance, none of which determine whether an engine cites the page. The nine fields cover what actually matters: the question, the competition, the answer, the proof, the scope, the structure, the schema, the placement, and the test. Adding SEO fields back in does not make the page more citable; it just reintroduces effort spent on algorithmic matching rather than on being the best answer. The economy of the brief is a feature.

How does this brief connect to schema and structure work?

The brief connects to schema and structure through fields six and seven, which specify both before drafting rather than leaving them as post-production fixes. Field six defines the page structure, answer-first, question-shaped H2s, tables where useful, so the page is built for clean extraction. Field seven defines the schema, the JSON-LD types and properties that make the page's meaning explicit to engines. Specifying these in the brief means the writer builds them in from the start, which is far more reliable than adding them afterward. The detailed reasoning behind the schema choices lives in schema for AI engines, and the brief is where those choices become a per-page requirement.

Related Guides from Calibrate

• Keywords Are Dead for AI Search — why the brief drops keyword fields entirely.

• How to Map the Questions Your Customers Ask AI — sourcing fields one and five.

• The Citation Architecture Method — the method the brief operationalises.

• Schema for AI Engines vs Schema for Google — the detail behind field seven.

• AEO for Product and Collection Pages — adapting the brief for commerce.

• Inside Our 6-Agent Content OS — how the brief is filled and executed at scale.