Planning playbook
AEO Buyer-Question Mapping Playbook: What Should Your Company Answer First?
Buyers rarely begin with your product page. They begin by asking questions that help them decide whether your company belongs on a shortlist. Start with eight questions: what your company does, who it is for, how it compares, what it costs, whether it works with the buyer's existing systems, what evidence supports it, whether it is credible and safe, and what results buyers can reasonably expect.
Start here
Give each important buyer question one clear canonical answer location, support it with appropriate evidence, and prioritise the gaps that affect real buying decisions.
- Goal
- Identify the buyer questions that must be answered clearly before a prospect can evaluate, compare, trust or shortlist your company.
- Inputs
- Known buyer concerns, sales questions, category context, comparison needs, technical requirements, pricing information, available proof and observed gaps in AI answers.
- Output
- A prioritised buyer-question map connecting each question to a canonical answer location, supporting evidence, responsible owner, publishing action and validation measure.
Define
Define the buyer decision before choosing pages
Start with the decision the buyer is trying to make, not a predetermined page type.
Do not start by deciding that you need a category page, comparison page, FAQ or case study. Start by defining the decision the buyer is trying to make.
A buyer may be trying to determine:
Category, fit and alternatives
Whether your company belongs in the category.
Whether the product is suitable for their organisation.
Whether it is better than a known alternative.
Whether it meets a technical requirement.
Viability, trust and value
Whether the commercial model is viable.
Whether the claims are credible.
Whether adopting it presents unacceptable risk.
Whether the expected outcome justifies the investment.
Record three inputs
1. Category and company context
The category your company belongs to and the problem it solves.
The primary entity name you want used consistently.
The audience for whom it is most relevant.
Adjacent categories with which it is commonly confused.
2. Fit and comparison questions
Strongest use cases and weak-fit or excluded use cases.
Company-size and industry requirements.
Alternatives buyers frequently consider and important trade-offs.
Technical or operational constraints.
3. Available evidence
Product and integration documentation.
Security and compliance information.
Customer evidence, case studies and outcome data.
Pricing information and founder or expert statements.
Third-party reviews, reports, partner records or certification records.
How to use this playbook
This framework is a practical starting point rather than a universal buyer-journey model. Validate it against your own:
Buyer and market signals
Sales and discovery calls.
Customer interviews.
Search and site data.
Support questions.
Win-loss analysis.
Answer and evidence inputs
AI-answer observations.
Product and technical documentation.
Available first-party and third-party evidence.
For Google Search, generative AI features still depend on core Search systems, and pages must satisfy conventional Search access and eligibility requirements. Google warns against creating separate content for every possible query or fan-out variation when the primary purpose is to manipulate rankings or generative AI responses. The better approach is useful, reliable, non-commodity content that covers meaningful questions coherently. See Google's official guidance for generative AI features in Search.
Record this: the buyer decision, audience, commercial objective and question scope for the first answer cluster.
Map
Map the eight shortlist questions
Adapt this starting framework to your category, buyer, geography, product maturity and sales process.
A canonical answer location is the clearest place where a buyer or answer system should find the authoritative answer. It may be a dedicated page, a substantial section of another page, product documentation, a trust centre, a comparison page or a case study. It does not always need to be a separate URL.
Scroll horizontally if needed
| Buyer question | Buyer needs to decide | The answer must explain | Likely canonical answer location | Evidence required |
|---|---|---|---|---|
| What is this? | Whether the company belongs in the relevant category | Category definition, problem solved, core capabilities and important exclusions | Homepage, category page or product overview | Product facts, category definitions and documentation |
| Is it for companies like ours? | Whether the product fits the buyer's situation | Ideal customer profile, company size, industry, use cases, requirements and poor-fit conditions | Fit page, use-case page or industry page | Customer examples, requirements and implementation evidence |
| Why choose it over alternatives? | Which option best fits the decision criteria | Comparison dimensions, differentiation, trade-offs, strengths, weaknesses and situations in which another option may fit better | Comparison, alternatives or “why us” page | Current product facts, competitor documentation and evaluation criteria |
| What does it cost? | Whether the commercial model is viable | Pricing logic, packages, ranges, inclusions, exclusions and cost drivers | Pricing or packaging page | Current pricing, commercial terms and implementation costs |
| Can it work with our stack? | Whether the product is technically and operationally compatible | Integrations, data flows, prerequisites, setup requirements, limitations and implementation path | Integration page or technical documentation | API documentation, partner records and implementation guidance |
| What proof supports it? | Whether the claims are credible | Customer evidence, case results, methodology, baseline, intervention, result and limitations | Case study, customer story, research page or proof library | Customer-approved evidence, measurements and methodology |
| Is it safe and credible? | Whether the operational, legal and security risks are acceptable | Security controls, data handling, compliance status, governance, company identity and relevant limitations | Trust centre, security page, legal documentation or company page | Policies, certifications, audit records and legal documents |
| What results can we reasonably expect? | Whether the likely value justifies the investment | Expected outcomes, conditions, timeframe, assumptions, variables and what is not guaranteed | ROI page, business-case guide, case study or value methodology | Outcome data, calculation methodology, assumptions and customer evidence |
Record this: the buyer question, buyer decision, canonical answer location and evidence required.
Evidence
Map the evidence before expanding the answer
A confident statement is not the same as a supportable answer.
For every shortlist question, create a small evidence ledger.
Scroll horizontally if needed
| Buyer question | Proposed answer | Canonical answer location | Internal evidence | External corroboration | Missing evidence | Evidence owner | Last verified | Status |
|---|---|---|---|---|---|---|---|---|
| The exact decision question | The concise answer the company can defend | The page, section, document or asset that should own the answer | Product facts, documentation, research, policies or customer data | Partner records, certification registries, third-party reviews or customer-hosted evidence | Information required before the claim can be published responsibly | The person responsible for confirming accuracy | The date on which the evidence was checked | Ready, incomplete, outdated, disputed or blocked |
Weak answer
Our platform is ideal for every growing business and delivers faster results.
Stronger answer
Template example — replace bracketed fields with verified company evidence.
The platform is designed primarily for [defined audience] that need [specific capability]. It is less suitable for [excluded audience or condition]. In [named customer or clearly labelled example], the implementation produced [specific outcome] over [timeframe], measured using [method]. Results will vary with [material conditions].
The stronger answer is easier to evaluate because its audience, scope, evidence, measurement and limitations are explicit.
Prioritise
Prioritise questions by decision importance, observed gap, and evidence readiness
Do not assume that every company should publish the same pages in the same order.
Decision importance
How strongly does the question affect evaluation, trust or purchase?
1: Useful but not central.
2: Important during consideration.
3: Frequently blocks or advances the decision.
Observed gap
How weak is the current answer across your site and the AI systems you monitor?
1: Clear and consistently represented.
2: Incomplete, inconsistent or difficult to find.
3: Missing, inaccurate or dominated by competitors.
Evidence readiness
Can the company support the answer now?
1: Evidence is missing or disputed.
2: Partial evidence exists but requires work.
3: Evidence is current, approved and publishable.
Use these scores as a planning heuristic, not as a universal ranking formula. High decision importance plus a serious observed gap usually deserves attention first. Evidence readiness determines whether the immediate action is publishing, research, documentation, customer proof collection or internal fact verification.
Scroll horizontally if needed
| Observed problem | Start with |
|---|---|
| Buyers or AI answers misunderstand the category | Category definition and product overview |
| The company is described as suitable for the wrong audience | Fit, use-case and exclusion content |
| Competitors dominate alternative and comparison prompts | Comparison and decision-criteria content |
| Pricing uncertainty blocks evaluation | Pricing, packaging and commercial-expectation content |
| Technical compatibility is unclear | Integration and implementation documentation |
| Claims are repeated without credible support | Case evidence, methodology and third-party corroboration |
| Enterprise risk prevents progress | Security, compliance, governance and trust content |
| Buyers cannot build a defensible business case | ROI methodology, outcome ranges and assumptions |
| The answer is clear on the site but absent from AI answers | Investigate crawlability, indexing, retrieval, competing sources and answer behaviour before rewriting |
| The company is cited as a source but not named | Investigate entity clarity, attribution and how the source connects the evidence to the company |
Record this: the first three questions to address, why they matter, the evidence required and the responsible owner.
Build
Build an answer cluster, not a collection of prompt-variation pages
Give each important buyer question one clear answer owner and connect it to the evidence buyers need next.
Use one canonical answer location
Each important question should have a clearly identifiable answer owner. It may be:
A dedicated page or a substantial section on a broader page.
Product documentation or a trust centre.
A case study, pricing page or integration record.
A research or methodology page.
Do not create separate pages solely because buyers phrase the same underlying question differently.
Separate materially different decisions
Two questions should normally have different canonical answer locations when they involve different:
Buyer roles or evidence.
Commercial risks or implementation requirements.
Recommended actions.
For example, security and ROI may both contribute to trust, but they are usually evaluated by different stakeholders using different evidence. They should not automatically be combined into one generic proof page.
Scroll horizontally if needed
| Asset | Primary purpose | Keep separate when |
|---|---|---|
| Category or product overview | Define what the company is and where it fits | The category is new, disputed or easily confused |
| Fit and use-case page | Explain who benefits and who does not | Fit varies materially by industry, company size or use case |
| Comparison or alternatives page | Support a specific choice between options | Buyers regularly compare named alternatives |
| Pricing and packaging page | Explain commercial expectations | Cost is a major qualification or procurement question |
| Integration and implementation content | Establish technical and operational fit | Compatibility, migration or setup materially affects adoption |
| Case study or proof library | Demonstrate observed outcomes | Different customer segments require different proof |
| Trust centre or security page | Support risk, governance and compliance review | Enterprise, regulated or sensitive-data buyers are involved |
| ROI or business-case guide | Explain value assumptions and calculation method | Expected value depends on multiple variables or stakeholder approval |
| Contextual FAQs | Answer genuine follow-up questions | The questions belong naturally on an existing owner page |
A standalone FAQ page should not be the default. Put pricing questions on the pricing page, security questions in the trust centre and integration questions in the relevant documentation. Create a separate FAQ only when it serves a genuine support or navigation purpose.
Link the cluster intentionally
Each canonical answer location should link to the evidence a buyer needs next. For example:
Category page → fit and use-case content.
Fit page → comparison and customer evidence.
Comparison page → pricing, integrations and proof.
Pricing page → implementation and ROI methodology.
Integration page → technical documentation.
Case study → methodology and relevant product capability.
Trust centre → policies, certifications and data-handling documents.
ROI page → case evidence, assumptions and calculation method.
Use descriptive anchor text that explains why the next page is relevant.
Worked example
Hypothetical example: assume a B2B analytics company is frequently included in broad analytics answers but is rarely shortlisted for professional-services firms.
Scroll horizontally if needed
| Buyer prompt | Canonical answer location | Required answer | Evidence available | Current gap | Priority |
|---|---|---|---|---|---|
| What is ExampleCo? | Category page | A cross-functional analytics platform for professional-services firms | Product documentation | Category language is too broad | High |
| Is ExampleCo suitable for a 50-person consultancy? | Fit page | Strong fit for firms with multiple client teams; poor fit for single-user reporting | Three consultancy customers | No explicit company-size or exclusion guidance | High |
| ExampleCo vs Competitor A | Comparison page | Differentiate on data unification, implementation and reporting workflow | Product documentation for both companies | No current comparison page | High |
| Does ExampleCo integrate with HubSpot? | Integration page | Explain supported objects, sync direction, prerequisites and setup | API documentation | Implementation timeframe missing | Medium |
| Is ExampleCo secure? | Trust centre | Explain data handling, controls, hosting and current compliance status | Security documentation | Documents are difficult to find | High |
| What ROI should a consultancy expect? | ROI methodology page | Show a calculation method, assumptions and variables rather than a universal promise | Two customer examples | No approved methodology | Blocked pending evidence |
Resulting first sequence
Clarify the category page.
Publish the consultancy fit and exclusion page.
Build the comparison page.
Improve the trust centre and link it from commercial pages.
Expand the integration record with implementation requirements.
Develop an ROI methodology only after the evidence and assumptions are approved.
The sequence follows the observed decision gaps. It is not based on a universal requirement to publish seven or eight pages.
Validate
Validate the answer cluster after publication
Publishing is the beginning of the test, not proof that the problem is solved.
Record a baseline
Capture exact buyer prompts, prompt families, platforms or answer engines, geography and language, date and time, brands mentioned, mention order, cited sources, the company's observed status, factual and entity errors, and relevant search and site performance.
Publish or update the evidence
Record the precise change: a new page, revised definition, added comparison, added product documentation, updated pricing, new customer evidence, improved internal links, corrected security information or added third-party corroboration.
Confirm technical eligibility
Check that the page returns a successful response, is crawlable, is indexable where appropriate, has a stable canonical URL, can appear with a snippet, contains its core answer in accessible HTML, is linked from relevant pages, is included in the appropriate sitemap and does not depend on inaccessible interaction for essential facts.
For Google's generative features, technical eligibility still depends on conventional Search access and indexing. See Google's generative AI search optimisation guidance.
Retest the same prompt set
Keep the baseline conditions as stable as practical. Compare mention rate, direct citation rate, recommendation rate, cited pages, source overlap, entity accuracy, attribute accuracy, competitor co-mentions, referral sessions, qualified engagement, and leads or assisted conversions where measurable.
Interpret the result carefully
A changed answer after publication is an observation, not automatic proof of causation. Search indexes, model versions, retrieval systems, competitor content, third-party sources, query demand, geography or personalisation, and product information may also have changed. Report association unless the evaluation design supports a stronger conclusion.
Record
Record the final planning output
Finish with a usable operating plan.
Copyable buyer-question workbook
Scroll horizontally if needed
| Priority | Buyer question | Buyer decision | Exact prompts | Canonical answer location | Proposed answer | Internal evidence | External corroboration | Missing evidence | Owner | Status | Validation measure |
|---|---|---|---|---|---|---|---|---|---|---|---|
Workbook output
A complete workbook should produce
A defined buyer decision and audience.
A prioritised shortlist-question map.
One canonical answer location for each material question.
An evidence ledger for every important answer.
A list of missing or outdated evidence.
A first publishing or improvement sequence.
Named owners and review dates.
A fixed prompt set for baseline and retesting.
A measurement plan separating access, visibility, citations, engagement and business outcomes.
Sources and further reading
Google: Optimizing your website for generative AI features on Google Search — official guidance on content quality, query fan-out, technical eligibility, unsupported AI-specific tactics and measurement.
Google: Creating helpful, reliable, people-first content — guidance on original value, sourcing, expertise, authorship and reader usefulness.
Kojable Competitive Gap Audit Guide — the next diagnostic step for investigating prompts where competitors appear or are cited first.
Frequently asked questions
Do we need a separate page for every buyer question?
No. Each material question needs a clear canonical answer location, but that location may be a page, a substantial section, documentation, a case study or a trust-centre record. Separate pages are justified when the question serves a different buyer, evidence set, risk or action.
Which buyer question should we answer first?
Start with a question that materially affects the buying decision, is currently missing or misrepresented, and can be supported with credible evidence. A high-priority question without sufficient evidence may require research or documentation before publishing.
Can one page answer several buyer questions?
Yes, when the questions share the same buyer intent, evidence and recommended action. Do not combine materially different decisions merely to reduce page count. Security, technical implementation, customer proof and ROI often require distinct evidence and owners.
Should we create a standalone FAQ page?
Usually not. Put each FAQ answer on the page that owns the underlying topic. A standalone FAQ is useful only when it serves a genuine support, navigation or consolidated-reference need.
What should we do when the evidence is missing?
Narrow or postpone the claim. Assign an owner to collect product documentation, customer evidence, methodology, certification records or other proof. Do not compensate for missing evidence with stronger promotional language.
Does completing the map improve AI citations automatically?
No. The map improves the clarity and governance of the company's answer assets. Retrieval, ranking, citation, recommendation and commercial outcomes depend on additional technical, evidentiary, competitive and platform-specific factors.
How often should the map be updated?
Review it after meaningful product, pricing, integration, security, positioning or market changes. Also update it when sales questions, customer objections, competitor behaviour or observed AI answers reveal a new decision gap.
What should we do after completing this playbook?
Run the Competitive Gap Audit to identify the high-intent prompts where competitors appear ahead of your company, the sources associated with those answers and the evidence gaps that deserve investigation.