AI search visibility
How assistants retrieve, ground, and select sources, and the work that makes your pages eligible to be named in the answer.
Explore ai search visibility
Pillar two
A growing share of buying research never reaches a results page. Someone asks an assistant, gets a synthesized answer, and clicks one or two citations. AEO is the work of being in that answer.
What this is
Classic search retrieves pages. Answer engines retrieve passages, then decide which ones to attribute. Optimizing for the first does not automatically win the second.
An assistant assembling a response is choosing between passages, not between domains. It rewards a paragraph that answers the question completely in isolation, and it discards prose that only makes sense after four scrolls of setup. That single difference reshapes how a page should be written.
Trust resolution is the second difference. The model needs to know who is speaking. Consistent entity data, real named authors with credentials, corroborating references across the web, and structured data that agrees with the visible page all feed that judgment. Anonymous, unattributed content is cheap to generate and gets treated accordingly.
Access is the third. If your content only exists after JavaScript runs, or your robots file quietly blocks the assistant crawlers, none of the writing matters. We fix access first, then structure, then authority.
The last difference is measurement. There is no rank tracker for a conversation. We track prompt-level visibility, citation share against named competitors, and the referral traffic that arrives from assistant surfaces, then feed that back into which questions get answered next.
What is inside
Access and structure come first. Citation tracking only means something once there is something to cite.
How assistants retrieve, ground, and select sources, and the work that makes your pages eligible to be named in the answer.
Explore ai search visibilityA maintained machine front door describing what your organisation does and where the canonical pages live. This site runs one at /llms.txt.
Explore llms.txt implementationDisambiguation, knowledge graph presence, sameAs and NAP consistency, and the corroboration that resolves two mentions into one entity.
Explore entity optimizationStructured data as machine-readable truth, generated from a shared component library rather than hand-written blobs, then validated.
Explore schema markupPrompt tracking, citation share, sentiment, and competitor comparison, with honest limits on what this young discipline can measure.
Explore ai citation trackingThe audit deliverable. What we test, which engines we test against, what the report contains, and the remediation plan that follows.
Explore answer engine auditHow we run it
Five phases, starting with the questions your buyers already ask an assistant instead of the keywords a tool suggested.
We build the real prompt set, run it across the major assistants, and record who gets cited today and in what tone.
Crawler policy, rendering, schema coverage, and entity consistency reviewed against what the assistants can actually reach.
Each priority question is assigned to a page and rewritten answer-first, with schema generated from the same content.
Author credentials, third-party references, and consistent entity signals so the answer has a verifiable source behind it.
Monthly re-run of the prompt set. Gained citations get reinforced, lost ones get diagnosed, new prompts enter the set.
Answer engine optimization is the practice of structuring content, entity data, and site access so AI assistants such as ChatGPT, Perplexity, Gemini, and Google AI Overviews retrieve your page, use it in a synthesized answer, and cite you as the source.
The difference
Both matter. Confusing one for the other is why most brands are invisible on the newer surface.
Classic SEO
AEO
| Dimension | Classic SEO | AEO |
|---|---|---|
| Unit retrieved | A page in a ranked list | A passage inside a synthesized answer |
| Winning shape | Comprehensive page covering a topic | Self-contained answer that survives extraction |
| Trust signal | Links and domain authority | Entity consistency, authorship, corroboration |
| Structured data role | Eligibility for rich results | Direct machine-readable answer mapping |
| Access requirement | Googlebot, renders JavaScript eventually | Assistant crawlers, often no rendering at all |
| Measurement | Positions, impressions, clicks | Citation share, sentiment, prompt coverage |
Extraction mechanics
Five properties. A page missing any one of them tends to get read and then passed over.
The answer sits in the first paragraph under the heading, phrased as a complete sentence that survives being lifted out of the page.
Headings match how people ask, not how marketers write. An assistant matching a prompt to a passage finds the question already written.
FAQPage, QAPage, Article, and Organization markup rendered server side and consistent with the visible text. Disagreement gets the markup ignored.
Consistent name, address, phone, sameAs references, and author credentials so the model can resolve who is speaking and why it should trust them.
GPTBot, ClaudeBot, PerplexityBot, and Googlebot allowed explicitly, content delivered server rendered, and llms.txt published as a machine-readable front door.
Straight answers
ChatGPT, Google AI Overviews, Perplexity, and Gemini account for the large majority of assistant-driven research in the United States today. Claude matters for technical and professional categories. We baseline all of them and prioritize by where your buyers actually ask.
Yes, and often more than national brands. Assistants answering local questions lean on consistent entity data, reviews, and genuinely local pages. Those are the same signals a local SEO program builds, which makes local businesses unusually well positioned.
It is a plain text file at the root of a site that summarizes what the organization does and points to the pages worth reading. It is a low-cost front door for assistant crawlers. We publish and maintain one on every site we build.
Partially. Content restructuring and schema can be added to most platforms. What cannot be worked around is a site that only renders in the browser, because many assistant crawlers never execute JavaScript and see an empty page.
Answer library
Every one of these is a live page on this site, written answer first so an assistant can lift it whole. That is the format we build for clients.
Cross-pillar
Citations are downstream of structure, speed, and proof. These four connections carry most of the weight.
Assistants lean heavily on pages that already rank, so the topical and authority work in SEO is the substrate AEO builds on rather than a separate track.
Passages only exist for a crawler when the HTML arrives complete, which is exactly what application frontends guarantee with server rendering on the first request.
Running a prompt set every month by hand does not scale, so monitoring is automated under AI and automation and the results land in a dashboard instead of a spreadsheet.
Assistant referrals are small in volume and high in intent, so they need the attribution built in analytics or they get miscounted as direct traffic and dismissed.
Models corroborate entities across the open web, which makes the presence and consistency delivered by social part of how a brand resolves as trustworthy.
Questions
We run your prompt set and show you the answer before anything is signed.