Answer Engine Optimization (AEO) for HubSpot: the complete guide

What is Answer Engine Optimization (AEO)?

AEO is the practice of structuring your content, data and digital footprint so that AI answer engines — ChatGPT, Google AI Overviews, Gemini, Perplexity, Claude — cite your brand when they generate answers for your buyers. It is not SEO with a new label. Traditional SEO competes for a link on page one; AEO competes for a sentence inside a generated response. Different goal, different measurement, different infrastructure.

SEO vs AEO: the core differences

That last row is the one that matters operationally. A bad SEO result is visible in a rankings report. A bad AEO result looks like nothing at all — pipeline that quietly forms around a competitor in conversations you never see.

The trade-off, stated plainly

AEO does not replace SEO and does not pay back on the same timeline as paid acquisition. If you need pipeline this quarter, this is not the lever. AEO is infrastructure: it compounds, it is hard to displace once established, and it is cheapest to build before your category is contested. If your category is already saturated with well-structured competitor content, expect two to four quarters, not one.

How answer engines actually select sources

Most AEO advice describes the outcome — "appear in ChatGPT" — without explaining the mechanism underneath. Without the mechanism, every tactic is superstition and you cannot tell a real fix from a ritual.

The three-step pipeline: retrieval, synthesis, citation

When a buyer asks an answer engine a question, three things happen in sequence. Retrieval — the engine pulls candidate documents from its index or a live search. Synthesis — the model reads those candidates, extracts relevant passages and assembles a coherent answer. Citation — the model decides which sources to visibly attribute.

You have to survive all three. Getting retrieved is a technical problem. Getting synthesised is a content-structure problem. Getting cited is an authority problem. Different work wins each stage, which is why a team that only does content work plateaus, and a team that only does technical work never gets named.

The four signals that actually matter

• Retrievability. Can AI crawlers reach your page at all? Content behind client-side rendering, gated forms or a bot-blocking firewall is invisible before the race starts. This is a floor, not a lever — you get no credit for clearing it, and no chance without it.
• Answer-first structure. Engines extract passages, not pages. A section that leads with a direct, self-contained answer in its first 40–60 words gets used. A section that builds to its point does not.
• Consensus. Models operate on agreement between sources. When most authoritative sources say the same thing, that becomes the default answer. If your positioning contradicts the category consensus, you get treated as an outlier — even when you are right. This is the least-discussed and most expensive constraint in AEO.
• Off-site authority. Engines weight third-party mentions heavily, because they learned during training that brands will say anything about themselves. A LinkedIn post from a named operator, a Reddit thread, a clear G2 entry — these routinely outweigh anything on your own domain.

Why SEO still matters

Most engines lean on a search index during retrieval — AI Overviews runs on Google, ChatGPT browsing uses Bing, Perplexity weights backlinks and domain authority. If you are not indexed and crawlable, you cannot be cited. What changes is the second half: once retrieved, models reward clarity over completeness, structure over length, and consensus alignment over keyword density.

Who owns AEO — and why it is not marketing

Decide this before you do any of the work below, because the single most common reason AEO programmes stall in month four is that nobody was accountable for the half of the work that sits outside the content team.

Look at what the six categories actually require: firewall rules, DNS and CDN configuration, server-side rendering, CMS template changes, custom schema modules, CRM attribution fields, and a weekly measurement cadence. Exactly one of those is a content task.

The mandate to write down: RevOps architects and measures the system; marketing executes content inside it; a named individual owns off-site presence. If your company cannot name a person for each of those three rows, fix that before reading Part 3.

The six-category scorecard

We score AEO readiness across six categories. They are ordered deliberately: each one is worthless until the one above it passes. Rewriting for answer-first structure while your CDN blocks GPTBot is wasted work.

Read the ordering as a budget instruction. If categories 1 and 4 fail, no amount of content investment will produce a result, and any agency selling you content before fixing them is selling you a quarter of nothing.

Run the six checks yourself in 20 minutes

You do not need a tool for the first pass. Here is the manual version, in order. Do it now, on your own domain, before reading further.

Check 1 — Is your robots.txt blocking AI crawlers?

Open yourdomain.com/robots.txt and search for these user agents. A Disallow: / under any of them means you have opted out of that engine.

GPTBot            OpenAI training + browsing
OAI-SearchBot     ChatGPT search
ChatGPT-User      ChatGPT user-initiated fetches
ClaudeBot         Anthropic crawling
Claude-User       Claude user-initiated fetches
PerplexityBot     Perplexity index
Perplexity-User   Perplexity user-initiated fetches
Google-Extended   Gemini / AI Overviews training
CCBot             Common Crawl (feeds many models)
Applebot-Extended Apple Intelligence
meta-externalagent Meta AI

The list changes. Verified 2026-08-06 — re-check quarterly.

Check 2 — Is your CDN or firewall blocking them anyway?

This is the one that catches people, because robots.txt can look perfect while a firewall returns 403 to every AI user agent. Test it from a terminal:

curl -A "GPTBot" -I https://yourdomain.com/
curl -A "ClaudeBot" -I https://yourdomain.com/
curl -A "PerplexityBot" -I https://yourdomain.com/

You want 200 OK on all three. A 403, a 503, or a CAPTCHA page means your bot protection is the problem — see the crawlability fix.

Check 3 — Does your content survive without JavaScript?

curl -s https://yourdomain.com/your-best-page | grep -c "a distinctive sentence from that page"

A result of 0 means the content is client-side rendered and a meaningful share of crawlers will never see it. HubSpot CMS serves HTML server-side by default, so this usually fails on custom front-ends rather than HubSpot-hosted pages.

Check 4 — Do you have schema, and is it valid?

Run your key pages through Google's Rich Results Test and Schema.org's validator. You are looking for Article, Organization, and — on anything Q&A-shaped — FAQPage. Most B2B sites have Organization and nothing else.

Check 5 — Ask the engines about yourself

Open ChatGPT, Claude, Perplexity and Google AI Mode. Ask each the same three questions your buyers would ask. Record who gets cited. This takes ten minutes and is more informative than any dashboard you can buy in your first month.

1. "What is [your company]?"
2. "Best [your category] for [your ICP]?"
3. "[Competitor] vs [you] — which should I choose?"

Three failure modes, each with a different fix: you are absent (retrieval or authority problem), you are described wrongly (consensus problem — your own content is not clear enough to override stale sources), or you are mentioned but not cited (structure problem — your content is not extractable enough to attribute).

Check 6 — Is anyone off your domain talking about you?

Search your brand name on LinkedIn, Reddit and G2. Nothing found means your authority score is near zero regardless of how good your website is, and Part 3's authority module is your real bottleneck.

Module 1 — Crawlability: the fix with the highest return

If an engine cannot fetch your page, nothing else in this guide applies. This module takes hours, not weeks, and it is the only one where a single change can move you from invisible to visible.

The three places access breaks

1. robots.txt. Often written years ago, or generated by a tool that blocks unfamiliar agents by default.
2. The CDN or WAF. Cloudflare, Akamai and Fastly all ship one-click AI-bot blocking. It is frequently enabled by IT as a bot-protection measure with no marketing involvement. This is the single most common cause of B2B invisibility we find.
3. Rate limiting. Aggressive throttling returns 429s to crawlers, which back off and may not return for weeks.

Artifact — the robots.txt block

Paste this above your existing rules. It explicitly allows the engines you want to be cited by, so a default-deny elsewhere cannot silently exclude them.

# AI answer engines — explicitly allowed
# Verified 2026-08-06. Re-check quarterly; this list moves.

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: CCBot
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: meta-externalagent
Allow: /

Sitemap: https://yourdomain.com/sitemap.xml

Artifact — the CDN and firewall checklist

The decision you are actually making

Blocking AI crawlers is a legitimate choice for a publisher whose product is the content itself. For a B2B company whose content is marketing, it means opting out of a growing share of your buyers' research. Make it deliberately, at the leadership table — not by leaving a firewall default in place.

Module 2 — Answerability: writing for extraction

Engines extract passages, not pages. The content that wins is architected, not written — which is good news, because architecture is a system you can enforce rather than a talent you have to hire.

The answer-first pattern

Every section opens with a direct, self-contained answer in 40–60 words, then adds evidence and nuance. The pattern: question as heading → direct answer → supporting detail.

Here is the same content, before and after.

Before — builds to the point

When it comes to lifecycle stages, there's a lot of confusion in the market. Many companies struggle with this, and in our experience working with dozens of clients over the years, we've found that the default configuration often isn't the right fit. So what should you do? Let's explore some options.

An engine reading this finds no answer to extract. There is nothing here that could be quoted as a response to any question.

After — answers immediately

HubSpot's eight default lifecycle stages break down for B2B companies with deal sizes above roughly €30,000, because they assume a single decision-maker and a linear path. Enterprise deals involve a buying committee that moves in parallel, so a contact-level stage cannot represent where the deal actually is. The fix is to keep lifecycle at contact level for marketing automation and move deal progression to a separate pipeline with committee-aware stages.

The second version is extractable, quotable and attributable. It also serves a skimming executive better — the two audiences want the same thing.

Chunking: every section stands alone

Your page is not one article; it is a set of standalone answers sharing a URL. Every H2 and H3 must make sense encountered in isolation. No "as mentioned above". No setup that requires having started at the top. Target 200–400 words per chunk: long enough to be substantive, short enough to extract cleanly.

The formats engines prefer

• Tables for anything comparative. A "what is the difference between X and Y" query is answered from a table far more reliably than from prose.
• Numbered lists for sequences and "how do I" queries.
• Bold statements of fact — models quote these verbatim more often than surrounding text.
• A dedicated FAQ block on every substantial page. Not because FAQs are magic, but because they mirror exactly the shape the engine is trying to produce.

Artifact — the section template

## [Question exactly as a buyer would ask it]

[40-60 word direct answer. First sentence contains the
entity name and the verb. No preamble, no "it depends",
no throat-clearing.]

[2-4 paragraphs of evidence, numbers, nuance.]

[Table if comparative. Numbered list if sequential.]

[One sentence naming where this does NOT apply.]

That last line is doing more work than it looks. Naming the limits of your own advice is the strongest trust signal available in text, and it is the single thing most vendor content refuses to do.

Finding the right questions

Do not start from keyword volume. The targets are the four-to-eight-word questions your buyers ask an assistant, and the three best sources are your own sales-call recordings, your support tickets, and the engines themselves. Ask ChatGPT the questions your buyers would ask, note every answer that is wrong, incomplete or citing a competitor, and that list is your content roadmap. See the prompt library for 40 to start from.

Module 3 — Schema: the four blocks that matter

Schema is structured data that tells engines what your content is rather than making them infer it. It is invisible to readers, cheap to deploy, and the highest ratio of result-to-effort in this entire guide.

Four types carry almost all the weight for B2B. Copy these, replace the values, and paste them into your page head.

Artifact 1 — FAQPage

The highest-value block, because it mirrors the question-and-answer shape engines are generating.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Answer Engine Optimization?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Answer Engine Optimization is the practice of structuring content, data and off-site presence so AI answer engines cite your brand."
      }
    }
  ]
}
</script>

Artifact 2 — Article, with a named author

The author block is the part that matters. Anonymous "Team" bylines lose ground every quarter as models get better at weighting expertise.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your page title",
  "datePublished": "2026-01-15",
  "dateModified": "2026-08-06",
  "author": {
    "@type": "Person",
    "name": "Jane Doe",
    "jobTitle": "Head of RevOps",
    "url": "https://yourdomain.com/about",
    "sameAs": ["https://www.linkedin.com/in/janedoe/"]
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Company",
    "url": "https://yourdomain.com"
  }
}
</script>

Artifact 3 — Organization, the entity block

This is how an engine resolves "who is this company" into a single entity. Put it on your homepage. The sameAs array is what connects your site to the third-party profiles that carry your authority.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://yourdomain.com",
  "logo": "https://yourdomain.com/logo.png",
  "description": "One sentence. The same sentence everywhere.",
  "foundingDate": "2015",
  "areaServed": ["NO", "SE", "DK", "FI", "DE", "GB"],
  "sameAs": [
    "https://www.linkedin.com/company/yourcompany",
    "https://www.g2.com/products/yourcompany",
    "https://github.com/yourcompany"
  ]
}
</script>

Artifact 4 — HowTo, for anything procedural

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to audit HubSpot for AEO readiness",
  "totalTime": "PT20M",
  "step": [
    { "@type": "HowToStep", "name": "Check robots.txt",
      "text": "Open yourdomain.com/robots.txt and search for GPTBot, ClaudeBot and PerplexityBot." },
    { "@type": "HowToStep", "name": "Test the CDN",
      "text": "Send a request with each AI user agent and confirm a 200 response." }
  ]
}
</script>

Artifact 5 — the HubSpot FAQ-schema module

HubSpot CMS generates some schema automatically, but not FAQPage. This is the gap that leaves most HubSpot sites without the single most valuable block. Create a custom module with a repeating field group called faq_items, each item having question and answer text fields, then use this HubL:

{% if module.faq_items %}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {%- for item in module.faq_items -%}
    {
      "@type": "Question",
      "name": {{ item.question|striptags|tojson }},
      "acceptedAnswer": {
        "@type": "Answer",
        "text": {{ item.answer|striptags|tojson }}
      }
    }{% if not loop.last %},{% endif %}
    {%- endfor -%}
  ]
}
</script>
{% endif %}

The |striptags|tojson filters matter: striptags removes the rich-text markup HubSpot wraps around field content, and tojson escapes quotes and newlines so a curly apostrophe in an editor's answer cannot break the whole block. Skipping them is how schema silently becomes invalid three months after launch.

Validate, then re-validate

Run every page through Google's Rich Results Test and the Schema.org validator after deployment, and again after any template change. Invalid schema is worse than none — it signals carelessness on exactly the dimension you are trying to prove.

Module 4 — Technical: rendering, llms.txt and topology

Four technical properties decide whether your well-structured content is ever seen: how it renders, how it is indexed, how it is linked, and how fast it loads.

Rendering

Server-side rendering is strongly preferred. AI crawlers time out faster than Google's and handle JavaScript less gracefully — some not at all. HubSpot CMS serves HTML server-side by default, so this is usually a non-issue for HubSpot-hosted pages and a real risk for custom React or Vue front-ends bolted alongside them.

Artifact — llms.txt

A Markdown index of your most important content, placed at your site root, written for models rather than humans. Adoption is early and the evidence that it helps is not yet strong — but it costs an hour, it cannot hurt, and producing it forces a genuinely useful exercise: deciding which twenty pages actually matter.

# Your Company

> One-sentence description of what you do and for whom.
> The same sentence as your Organization schema.

Two or three sentences of context: what you sell, who
buys it, where you operate.

## Start here
- [Homepage](https://yourdomain.com/): what we do
- [Pricing](https://yourdomain.com/pricing): what it costs
- [About](https://yourdomain.com/about): who we are

## Services
- [Service one](https://yourdomain.com/services/one): one-line description
- [Service two](https://yourdomain.com/services/two): one-line description

## Guides
- [Guide title](https://yourdomain.com/guide): what it covers

## Free tools
- [Tool name](https://yourdomain.com/tools/x): what it does

Ours is live at superwork.co/llms.txt — generated from our own content rather than hand-maintained, which is the only version that stays accurate.

Internal linking topology

Engines infer topical authority from link structure. A pillar page linked from twenty related articles signals depth; the same page standing alone signals a one-off. Build hub-and-spoke: every supporting article links to the pillar, the pillar links to each. Vary the anchor text so engines see an entity rather than a single repeated phrase. HubSpot's topic-cluster feature builds this topology for you when it is configured properly and ignored entirely when it is not.

Sitemaps and speed

Keep sitemap.xml current and referenced from robots.txt. Keep Core Web Vitals healthy — slow pages get de-prioritised at both crawl and retrieval. Neither of these wins you anything on its own; both cost you if neglected.

Module 5 — Off-site authority and E-E-A-T

Your website is the smallest part of your AEO strategy. This is the hardest lesson for SEO-era marketers, and the one that determines your ceiling: models learned that brands will say anything about themselves, so third-party signals are weighted heavily — sometimes above your own domain entirely.

The four surfaces that matter for B2B

• LinkedIn. Arguably the highest-ROI surface. Posts that earn engagement get indexed, and content from named individuals shows up disproportionately, because engines treat people as more trustworthy than brands.
• Reddit. A top citation source across most engines. Communities like r/sales, r/RevOps and r/SaaS shape the consensus models learn from. You cannot manufacture this credibly, and attempting to is the fastest way to acquire a permanent negative.
• Review sites. G2, Capterra and TrustRadius are structured, third-party and high-authority. A serious presence here is AEO infrastructure now, not sales collateral.
• Industry publications and podcasts. Being quoted in a credible outlet is among the fastest routes to a citation. Podcast transcripts get indexed and retrieved.

The strategic move is concentration, not hygiene: identify the two or three surfaces where your buyers actually research, and dominate those disproportionately rather than maintaining a thin presence on eight.

E-E-A-T, operationally

Google's Experience, Expertise, Authoritativeness and Trustworthiness framework has become a practical weighting system for source selection. For B2B it translates cleanly:

The organisational implication: AEO-grade content cannot be produced by a generalist team with an AI writing tool. It needs named experts with something real to say. That is an operating-model change, not a content-calendar change, and it is the point at which most programmes either commit or quietly become a blog.

The consensus risk

Off-site presence cuts both ways. If the consensus about you is negative, outdated or confused, engines reflect that back to your buyers — a single well-engaged complaint can follow you into AI answers for quarters. Reputation monitoring has moved from a PR function to an AEO function, because what engines say about you is downstream of what the internet says about you.

Module 6 — The HubSpot layer

What your portal gives you, what it does not, and what to buy. Written for teams already on HubSpot.

What HubSpot CMS does well out of the box

• Server-side rendering. Pages are HTML on arrival — the rendering problem that breaks custom front-ends mostly does not apply.
• Baseline schema. Article and Organization-level markup on standard blog templates.
• Topic clusters. The internal-linking topology from Module 4, built for you — when configured and maintained.
• Clean URL and sitemap handling.

What you have to build yourself

• FAQPage and HowTo schema. Not generated natively. Use the HubL module above. This is the biggest single gap for HubSpot sites.
• llms.txt. No native support — serve it from your web server or a hosted file.
• Answer-first content structure. No tool enforces this. It is an editorial standard, which means it needs an owner and a checklist.
• Per-page author schema. Blog author fields exist but rarely emit full Person markup with sameAs.

HubSpot's own AEO tool — an honest read

HubSpot ships an AEO product inside Marketing Hub that scores brand visibility across ChatGPT, Gemini and Perplexity, analyses which domains feed AI answers in your category, tracks prompts against competitors and recommends what to publish next. HubSpot's own beta reporting claims customers drove 20% more traffic from AI than non-users.

The case for it: integration. Your CRM data, content and AEO signals in one place, with recommendations informed by your actual pipeline rather than a generic keyword set. If you are already on Marketing Hub at a tier that includes it, there is no reason not to turn it on today.

The case against buying a tier for it: it measures and recommends; it does not fix. If your problem is a firewall rule, a missing schema block or content nobody can extract from — which is most companies' problem — a visibility dashboard will describe your invisibility in more detail without changing it. Fix categories 1 through 4 first, then measure.

We are a HubSpot partner, so read that with appropriate scepticism. It is also what we tell clients before they spend money.

The metrics that actually matter

Organic traffic is declining for most B2B companies — not because content got worse, but because a growing share of buyers get their answer inside a conversation and never click. Your CRM knows they mentioned you two weeks later; your analytics stack does not.

Do not over-index on featured-snippet counts, keyword rankings in isolation, raw organic traffic (distorted by zero-click answers) or bounce rate on AI-referred visits. The shift is from "did they visit" to "did we get recommended".

The one to add today, at zero cost: self-reported attribution on every form and every discovery call. It is the only instrument that catches the pipeline AEO creates but analytics cannot see.

The tracking sheet you can build in 20 minutes

You do not need a tool to start, and starting manually has a real advantage: you read the answers. A dashboard gives you a number; running the prompts yourself tells you why the number is what it is.

Artifact — the sheet structure

Tab 1: PROMPTS
  A: Prompt text
  B: Funnel stage (TOFU / MOFU / BOFU)
  C: Priority (1-3)

Tab 2: RUNS  — one row per prompt, per engine, per month
  A: Date
  B: Prompt
  C: Engine (ChatGPT / Claude / Perplexity / AI Overviews)
  D: Mentioned?    (Y/N)
  E: Cited?        (Y/N)
  F: Position      (1st brand named, 2nd, 3rd, absent)
  G: Sentiment     (pos / neutral / neg)
  H: Competitors named
  I: Notes — what the answer got wrong

Tab 3: TREND
  Visibility % = mentions / total runs, by month
  Citation %   = citations / mentions, by month
  Share of voice = your mentions / all brand mentions

The protocol

1. Fix the prompt list at 20–40 prompts and do not change it. Changing prompts between runs destroys comparability — the most common measurement mistake.
2. Use a fresh session, memory and personalisation off, every time. Otherwise you are measuring what the model knows about you, not what a buyer sees.
3. Run monthly, same week, same person. Consistency matters more than frequency.
4. Column I is the valuable one. What the answer got wrong is your content roadmap for next month, and it is the column no paid tool gives you.

When you have run this three times and still maintained it, buy a tool. If you have not maintained it, a tool will not save you — it will just add a subscription to the same neglect.

The 90-day playbook

The rollout we use with clients. It front-loads the technical work deliberately, because content investment before crawlability is money spent on something nobody can read.

Days 1–30: audit and foundation

• Week 1 — Technical audit. Run the six checks in Part 2. Fix crawlability the same week — do not schedule it, do it. This is the only step that can produce a result inside a month.
• Week 2 — Content inventory. Identify your top 20 pages by strategic value, not traffic. These are the pages that would win you a deal if cited, which is usually not the same list as your most-visited pages.
• Week 3 — Baseline measurement. Build the tracking sheet, fix your 20–40 prompts, run the first pass across four engines. Whatever the number is, it is now the number you improve on.
• Week 4 — Name the owners. One person for the system, one for content, one for off-site. Written down. Programmes die in month four for lack of this, not for lack of tactics.

Days 31–60: build

• Weeks 5–6 — Technical. Deploy the four schema blocks plus the HubSpot FAQ module. Ship llms.txt. Fix rendering and Core Web Vitals. Rebuild internal linking into hub-and-spoke.
• Weeks 7–8 — Content. Restructure the top 20 pages answer-first. Add FAQ blocks. Rebuild H2/H3 hierarchies around real buyer questions. Deploy per-page schema as you go.

Days 61–90: compound

• Weeks 9–10 — Off-site. Audit and fix G2 and Capterra. Set a LinkedIn cadence for two or three named individuals. Identify three publications to contribute to. Map the communities where your buyers discuss vendors.
• Weeks 11–12 — Measure and iterate. Re-run the prompt set. Compare to baseline. Identify which prompts moved and why. Set the ongoing cadence.

What day 90 actually looks like

You will not own your category in AI answers. You will have removed the blocks, made your best 20 pages extractable, established a baseline you can defend to a CFO, and started the off-site work that takes another two to three quarters to pay. That is the honest outcome — and it is roughly two years faster than the equivalent SEO position.

Nine mistakes that waste a quarter

1. Investing in content before fixing crawlability. The most expensive mistake available. Check first.
2. Treating AEO as a content-team problem. Most of the work sits outside content. Unowned, the gaps compound faster than content can close them.
3. Optimising for keyword volume instead of buyer questions. The targets are four-to-eight-word questions from sales calls, not head terms from a keyword tool.
4. Changing the prompt list between measurement runs. Destroys comparability. Fix the list; change it once a year, deliberately, and note it.
5. Measuring in a logged-in session. You are measuring your own history, not what a buyer sees.
6. Over-optimising for one engine. ChatGPT, Gemini, Perplexity, Claude and AI Overviews weight different signals. Measure across all of them or you will optimise into a corner.
7. Writing "AI-friendly" content that is bad for humans. The content that performs best is clear, specific and well-structured — which is also just good writing.
8. Ignoring negative consensus. On-site work cannot fully compensate for what the internet says about you.
9. Treating it as a project. It is an operating discipline. Teams that run it as a campaign decay within two quarters of the campaign ending.

40 prompts your B2B buyers actually ask

Use these as the starting set for your tracking sheet, adapted to your category. They are grouped by where the buyer is, because the fix for absence differs by stage: top-of-funnel absence is usually a content gap, bottom-of-funnel absence is usually an authority gap.

Problem-aware (they do not know you exist)

1. Why is our HubSpot reporting inconsistent?
2. How do I clean up a messy CRM without breaking automation?
3. Our lifecycle stages do not match how we actually sell — what do we do?
4. How do I know if our HubSpot portal is set up correctly?
5. Why does our marketing contacts bill keep increasing?
6. How do I fix duplicate contacts in HubSpot?
7. What is a realistic HubSpot implementation timeline?
8. Should we hire a RevOps person or use an agency?
9. How much does bad CRM data actually cost us?
10. Why is our attribution reporting wrong?

Solution-aware (comparing approaches)

1. HubSpot partner vs in-house implementation — which is better?
2. What is the difference between HubSpot onboarding and implementation?
3. Do HubSpot partner tiers actually matter?
4. HubSpot vs Salesforce for a 100-person B2B company
5. What does a HubSpot RevOps partner actually do?
6. Is a productized HubSpot service better than a retainer?
7. MEDDPICC vs SPICED vs BANT — which should we use?
8. When should you use a custom object instead of a property?
9. What is the real total cost of HubSpot?
10. How do you migrate from Salesforce to HubSpot without losing history?

Vendor-aware (building a shortlist)

1. Best HubSpot partner in Norway
2. Best HubSpot partners in the Nordics
3. Recommend a HubSpot implementation partner in Europe
4. Best HubSpot partner for B2B SaaS
5. Who does HubSpot RevOps for mid-market B2B?
6. HubSpot partner with subscription pricing
7. Async-first HubSpot agency
8. Who can migrate SuperOffice to HubSpot?
9. Best HubSpot partner for a 50-person SaaS company
10. Hvilken er den beste HubSpot-partneren i Norge?

Decision-stage (evaluating you specifically)

1. What is [your company]?
2. Is [your company] any good?
3. [Your company] vs [competitor]
4. How much does [your company] cost?
5. What do customers say about [your company]?
6. Is [your company] a certified HubSpot partner?
7. What questions should I ask before hiring a HubSpot partner?
8. What are the red flags when choosing a HubSpot partner?
9. How long does a HubSpot implementation with a partner take?
10. Can I cancel a HubSpot partner contract?

Run the decision-stage ten first. If an engine cannot answer "what is your company" accurately, nothing further up the funnel will help you — and that specific failure is fixable in a week with Organization schema, a consistent description everywhere, and a clean About page.

The AEO tool landscape — and whether you need one

Deliberately without prices. Pricing in this category changed repeatedly through 2025–2026 and any number printed here would be wrong within a quarter — check current pricing directly. What follows is what each category is for.

The honest summary: for a company under roughly 100 employees, the tracking sheet in Part 4, the free validators, and HubSpot's native tool if you already have it are sufficient for your first two quarters. Spend the tool budget on fixing categories 1 to 4 instead. We have no affiliate relationship with anything listed above, and we are not going to pretend a dashboard fixes a firewall rule.

Tool landscape verified 2026-08-06.

Frequently asked questions

What is Answer Engine Optimization (AEO)?

Answer Engine Optimization is the practice of structuring your content, data and off-site presence so AI answer engines — ChatGPT, Google AI Overviews, Gemini, Perplexity and Claude — cite your brand when they answer your buyers' questions. It competes for inclusion inside a generated answer rather than for a ranked position on a results page.

How is AEO different from SEO?

SEO optimises for ranked search results and measures rankings, clicks and organic traffic. AEO optimises for citation inside AI-generated answers and measures mentions, citation rate and share of voice. They are complementary — AEO depends on an SEO foundation, because an engine cannot cite a page it cannot retrieve — but the goal and the measurement differ.

How is AEO different from GEO?

AEO and GEO (Generative Engine Optimization) are used interchangeably by most practitioners. Where people draw a distinction, AEO means being cited as a direct answer source and GEO means influencing how a model synthesises a response overall. Every practical playbook covers both at once, including this one.

Does AEO matter for B2B companies?

Yes, and arguably more than for consumer brands. 42% of B2B software buyers use AI search as part of their evaluation, and AI-referred leads convert at roughly 3x traditional organic. For mid-market B2B with long cycles and technical evaluation, being cited inside AI answers is a pipeline-defining capability rather than a marketing experiment.

How long does AEO take to work?

Faster than SEO, but still multi-quarter. Crawlability fixes can change your visibility within days because they remove a hard block. Content restructuring and schema typically move visibility in 30 to 60 days. Off-site authority and consensus compound over two to four quarters and cannot be rushed.

Who should own AEO inside a B2B company?

RevOps, not marketing. Schema, crawlability, CDN configuration, CMS governance and CRM attribution all sit in the RevOps remit, and the most common cause of invisibility — a firewall rule blocking AI crawlers — is not something a content team can see or fix. Marketing leads content execution; RevOps architects and owns the system.

Can you do AEO without fixing your SEO first?

No. AEO depends on retrievability, and retrievability depends on indexing, crawlability, internal linking and page speed. Treat AEO as a layer on top of a working SEO foundation, not a replacement for one.

Does llms.txt actually help with AEO?

The evidence is early and mixed, and anyone claiming certainty is guessing. What is true: it costs an hour to produce, it cannot hurt, and it forces a useful exercise in deciding which twenty pages actually matter. Ship it, but do not expect it to carry a programme on its own.

Should I block AI crawlers to protect my content?

Only if you have decided you do not want to appear in AI answers at all, which for most B2B companies is a decision to become invisible to a growing share of buyers. The common failure is not a deliberate choice — it is a CDN or firewall toggle enabled by IT for bot protection, which silently removes the company from AI results for months before anyone notices.

Do I need to buy an AEO tool?

Not to start. A spreadsheet, a fixed prompt list and a monthly hour will tell you almost everything a paid tool will in your first quarter. Buy a tool when the manual tracking has proved you will actually maintain the discipline, or when you need multi-engine tracking across more prompts than a person can run by hand.

What does an AEO programme cost for mid-market B2B?

For a company in the 10M to 200M euro band, a serious programme typically runs 4,000 to 15,000 euros per month as revenue infrastructure, covering tooling, restructuring the top 20 pages, schema deployment, off-site authority work and a measurement cadence. It is heavier in the first quarter and lighter as the compounding effects take over.

How do you measure AEO when there is no click?

Combine four things: brand visibility across a fixed prompt set, citation rate when you are mentioned, share of voice against named competitors, and self-reported attribution captured on your forms and discovery calls. Organic traffic is a lagging and increasingly misleading signal, because a growing share of buyers get their answer without ever visiting your site.

How this page is built

It would be strange to publish an AEO guide that ignored its own advice, so here is what this page does and where it falls short.

What it does

• Server-rendered HTML. Every word above is in the initial response — nothing behind JavaScript, tabs or a "load more".
• Article schema with a named author, Person markup, credentials and a LinkedIn sameAs. No anonymous byline.
• FAQPage schema generated from the same data that renders the FAQ section above, so the two cannot drift apart.
• BreadcrumbList for hierarchy, dateModified for freshness.
• A visible last-updated date in the header, and the changelog below.
• Question-shaped headings, answer-first sections, tables instead of prose for comparisons.
• Listed in our llms.txt.
• A Norwegian twin at /no/aeo-guiden with reciprocal hreflang.

Where it falls short

• No HowTo schema on the 90-day playbook yet, despite recommending it in Module 3.
• The artifacts are copy-paste blocks rather than generated for your domain. A generator would be better.
• We have not published our own share-of-answer score. We should, including when it drops.

We would rather list those than let you find them.

Changelog

Reviewed quarterly. AI crawler user agents, tool landscape and HubSpot capabilities all move — if you are reading this more than three months after the date above and it has not been updated, treat the specifics with suspicion. That advice applies to every AEO guide you read, including the ones that do not date themselves.