Can SEO, AEO, GEO and AIO be measured as one score? No. Search discovery, AI answers, brand mentions, source selection, direct evidence, and traffic and revenue are different events with different denominators. CiteAngle measures each stage with its own denominator and receipts, then connects the result to the next action and to re-measurement. In our own measurement (2026-07-14) every question is asked seven times, and every planned observation in a run is published with its state.
Four market terms, one precise data model
AEO (answer engine optimization) is optimization for answer adoption and source linking on search surfaces that return a complete answer; GEO (generative engine optimization) is the practice of building citable original assets that earn direct citations and mentions in generative AI answers. In paid audits, CiteAngle measures both with seven repeated runs (k7) per query. The categories stay familiar to buyers while the underlying evidence remains stage-specific and decision-ready.
What is answer engine optimization (AEO) and how is it different from SEO?
AEO (answer engine optimization) is optimization for answer adoption and source linking on search surfaces that return a complete answer. SEO is the crawl, indexation, organic-presence and click foundation underneath it; AEO reads a different event on top of that foundation: whether an answer surface appears and how the brand is mentioned in it. That is why the model above gives the two separate denominators instead of one blended score.
What is LLMO (large language model optimization)?
LLMO (large language model optimization) is another label the market uses for the practice the four terms above already cover: earning visibility, mentions and citations for a brand in answers assembled by large language models. It carries no separate metric of its own. In this model, LLMO work is measured through the same states: answer surfaces, brand mentions, target citations and direct source support.
What does AIO mean in AI search measurement?
AIO here refers to Google AI Overview, the generative summary surface in Google Search, measured separately from organic results. Treating it as its own surface matters because an AI Overview appearing, your brand being mentioned inside it, and your page being cited as a source are separate states in the model above, each with its own denominator.
Is FAQ schema still worth adding for AI visibility?
As semantic hygiene, yes; as a visibility boost, no. Google stopped showing the FAQ rich result on May 7, 2026, so this model treats FAQ markup as clean structure for real buyer questions rather than as an AI-visibility lever. Performance is evaluated with the observed evidence rails below, not with markup presence.
Why not blend SEO, AEO, GEO and AIO into one visibility score?
Because the underlying events have different denominators. A failed run, an answer surface that never appeared, a brand mention, a target citation and a verified referral are distinct states; adding them into one number hides which stage actually moved. The model above keeps each rate on its own denominator so the next intervention stays visible.
How does CiteAngle measure AEO and GEO in paid audits?
With repeated controlled observation: paid audits measure both indicators with seven repeated runs (k7) per query, and each result is recorded against the state model above: answer surface, brand mention, target citation and direct support, each with its own denominator and receipt.
Seven states from collection quality to business outcome
Every state has an independent verifier. The chain shows exactly where visibility converts, and where the next intervention belongs.
Measurement failure
Timeout · 403/429 · provider · capture or parse error
Report against all attempts; exclude from visibility denominators.
Answer surface
Target AI surface shown or not shown after a valid search
Keep runs with no AI answer shown separate from brand absence.
Brand absent or mentioned
Approved company, brand and product aliases in answer text
Judge role only within appeared, evaluable surfaces.
Target citation
Customer canonical URL appears as a visible source link
Record citation independently from a brand-name mention.
Direct source support
Verifiable link between an answer claim and a source evidence span
Separate source-panel inclusion from claim-level support.
Verified referral
Referrer · UTM · landing log identifies the session
Preserve displayed citations and referred visits in separate ledgers.
Business outcome
Consented analytics · CRM · payment evidence for leads, signups, purchases and revenue
Connect outcomes through a preregistered evaluation.
Visible denominators make the next move obvious
| Metric | Denominator | Quality rule |
|---|---|---|
| Failure rate | failed runs ÷ all attempts | Keep failure reason as a quality KPI |
| Surface rate | surface shown ÷ applicable valid runs | Exclude failed and not-applicable runs |
| Brand mention rate | brand mentioned ÷ mention-evaluable shown surfaces | Exclude alias-judgment errors |
| Target citation rate | target URL cited ÷ citation-evaluable shown surfaces | Exclude surfaces that were not shown |
| Direct support rate | direct support ÷ span-evaluable shown surfaces | Exclude inaccessible source text |
| Referral conversion | verified conversions ÷ verified referred sessions | Exclude unattributed conversions |
Owned platform aggregates and controlled observations stay side by side
They answer different questions about different populations. Owned aggregates count every impression the platform served; controlled observation counts 7 runs per query on a fixed question set. Preserving both delivers market-level evidence and query-level diagnosis without a blended score.
Search Console generative AI report
Where Google makes the report available, connect AI Overviews and AI Mode link impressions by page, country, date and device. Report unavailability is not zero exposure; keep the breakout distinct from overlapping Web performance.
Bing AI Performance
Read visible citations, cited pages and sampled grouped grounding queries. Join clicks, rank and revenue from their own sources.
OpenAI, Anthropic and Perplexity runs
Freeze question, market, language, time and raw response at run level. Keep these request samples distinct from publisher-wide user exposure.
GA4, CRM and payment records
Connect AI Assistants and Organic Search sessions to enquiries, signups and purchases with attribution and data-quality receipts.
What runs on its own, what waits for your approval, and what a named specialist owns
Diagnosis, evidence-bound recommendations, drafts and remeasurement run on their own. Two points bring a person in. The first is the moment a change reaches your site. You approve the exact URL, the exact section and the exact diff. It then ships small with a rollback ready, and widens once the live checks come back clean. The second is work that carries judgment: third-party editorial, legal, medical, financial and pricing claims. A named specialist owns that from start to finish.
Diagnosis, recommendation and draft
- Public technical audit and delegated read-only evidence
- Repeated collection, error classification and state judgment
- Evidence-bound page diffs and content briefs
- Reporting, remeasurement scheduling and evaluation
Owned-site publishing and rollback
- Only what the customer approves goes live
- Exact URL, section and diff-hash authorization
- Pre-publish snapshot and remote version or ETag
- Independent verifier and limited canary
- Live checks, rollback and restored-hash receipt
External and high-risk work
- Third-party editorial, PR, reviews and partner negotiation
- Legal, medical, financial and pricing fact review
- Global robots, CDN or WAF changes and domain migrations
- Consumer surfaces without an approved collection route
Read the table the other way and it says this: diagnosis, the rewritten page going live, and the remeasurement all sit inside one engagement, and the two human checkpoints exist so every change stays reversible. What you receive is not a leaderboard. It is the repaired page, with the before-and-after measurement beside it.
Use FAQ for clarity; evaluate performance with observed evidence
FAQ remains a useful editorial format for real buyer questions. Google stopped showing the FAQ rich result on May 7, 2026, so CiteAngle treats FAQ schema as semantic hygiene rather than an AI-visibility boost.
Primary sources
Accessed July 14, 2026. Platform documentation and standards are mapped directly to the claims above.
- Google guide to generative AI search optimizationGenerative Search uses SEO foundations; special AI schema and artificial chunking are not prerequisites
- Google Search Console generative AI reportAI Overviews and AI Mode link impressions, dimensions and reporting limits
- Google Search documentation updatesFAQ rich-result retirement from May 7, 2026
- Bing AI PerformanceVisible citations, cited pages, grounding queries and representative-sample scope
- OpenAI crawler overviewSeparate search, training and user-request crawler roles
- Anthropic Web Search ToolRequest-level URLs, titles, cited text and error handling
- Perplexity crawlersSeparate search crawler and user-request fetch roles
- RFC 9309Robots Exclusion Protocol semantics
Want this evidence model applied to your own category? A paid audit runs 7 runs per query and reports every rate on its own denominator. Contact us and we will scope it before you buy.