The AEO Methodology
A versioned framework for building pages that answer engines can reliably read, trust, and cite — five pillars, each with an explicit, testable verification method, developed from direct citation testing rather than general SEO folklore. Looking for the plain-language version instead? Read the beginner's guide.
Scope & intent
This document defines five pillars a page must satisfy to be considered AEO-compliant under this methodology, plus the specific method used to verify each one. It is not a list of tips — each pillar is written to be auditable: a third party should be able to check a given page against each criterion and reach the same pass/fail conclusion independently. Where a claim in this document is empirical rather than definitional, it links to the underlying test data in the same sentence, per Pillar 3 below applied to itself.
Pillar definitions & verification criteria
Machine-Readable Delivery
The content an answer engine needs must exist in the raw HTML response, not only after client-side JavaScript executes. Several major AI crawlers execute JavaScript inconsistently or not at all, so content gated behind a JS render is content that may simply not exist as far as the engine is concerned.
Pass criteria
- Primary content is present in a plain HTTP fetch of the page, with no JavaScript execution
- No critical text, price, or claim is injected only after page load
- Core Web Vitals do not depend on deferred content to reach a complete state
Verification method
View the page's raw HTML source directly (not the rendered DOM). If the claim under test isn't present in that raw source, the page fails this pillar regardless of how it looks in a browser.Direct-Answer Architecture
The first substantive sentence on a page should state its core claim declaratively — not build up to it, not open with a question, not lead with a fragment. This is the sentence most likely to be lifted and quoted directly by an answer engine, so it needs to be able to stand alone.
Pass criteria
- The lede answers the page's core question in one complete, quotable sentence
- Genuinely recurring questions are marked up with FAQPage schema, phrased the way people actually ask them
- Headings map cleanly onto the sub-questions a reader (or model) would have
Verification method
Extract only the first sentence of the page and ask: does this sentence, alone, answer the query the page targets? If it requires the next two sentences of context, the page fails this pillar.Evidence Density
Every claim that could plausibly be challenged needs a same-sentence link to something that verifies it — a live tool, a dataset, a report, a source. Confident phrasing alone is not evidence, and answer engines are measurably worse at trusting content that only asserts rather than demonstrates.
Pass criteria
- No standalone factual claim exists without an adjacent link to its evidence
- Evidence links resolve to something a reader can independently re-verify, not a citation of the same site's own unverified claim
- Numbers are stated exactly, not rounded for effect
Verification method
List every factual claim on the page. For each one, confirm a link exists in the same sentence, and that following the link actually substantiates the claim rather than restating it.Entity Clarity
A page should state, plainly and near the top, who is behind the content, where they're based, and what specific expertise qualifies them to make the claims on the page. Vague brand language does less for an answer engine's confidence than a named, locatable, specific entity.
Pass criteria
- A real name, location, and specific area of expertise appear within the first few hundred words
- Identity claims are consistent across every page on the site, not restated differently each time
- Organization and Person schema, where applicable, match the visible on-page text exactly
Verification method
From the page alone, could a model state in one sentence who wrote this, where they're based, and why they're qualified? If it requires guessing or inference, the page fails this pillar.Cross-Engine Verification Loop
AEO compliance isn't a one-time build state — it has to be periodically re-tested against real prompts across multiple answer engines, and the results published regardless of outcome. A methodology that's never checked against reality is just a set of assumptions.
Pass criteria
- A defined panel of real, representative queries is tested against at least three independent answer engines
- Results are published in full, including queries where the page was not cited
- Re-testing happens on a fixed, disclosed cadence, not only when results are expected to look favorable
Verification method
Run the query panel live against ChatGPT, Gemini, Claude, and Perplexity. Record citation, mention, or absence for each engine and each query, and publish the raw result set.Why these five pillars, specifically
This methodology wasn't assembled from general SEO advice relabeled for AI — it was built directly from a citation test run on this site on July 21, 2026, using a fixed panel of five real questions targeting specific claims, tested cold across ChatGPT, Gemini, and Perplexity.
The gap between those two numbers is the entire empirical case for Pillar 3 specifically, and the fix applied afterward — adding same-sentence evidence links to every promise-only claim on the tested pages — is the direct origin of this methodology's evidence-density requirement. A re-test against the same panel is scheduled for July 28, 2026, and the results will be published on the incident log whichever way they land.
Checked by systems outside our control
Grok was asked to grade this site's actual SEO and AEO implementation directly, unedited, published in full. Read Grok's grades.
ChatGPT independently landed on A- (8.8/10) for SEO and A (9.3/10) for AEO from the site's public content alone. Read ChatGPT's grades.
Neither model was told this methodology existed before grading — both were pointed only at the live site and asked to assess it on its own terms.
Common questions
What is the AEO Methodology?
It's ZenMasterWorks's formal, versioned framework for building pages that AI answer engines can reliably read, trust, and cite — five defined pillars, each with explicit verification criteria, developed from direct citation testing rather than general SEO folklore.
How is this different from a typical AEO guide?
Most AEO advice is a list of tips. This is a versioned methodology: five named pillars, each with a specific pass/fail verification method, backed by a real citation test run across ChatGPT, Gemini, and Perplexity rather than general best-practice claims. It's meant to be audited, not just read.
What evidence supports this methodology?
A five-question citation test run July 21, 2026 across ChatGPT, Gemini, and Perplexity found that promise-only claims scored 0 out of 5 citations, while the same site's verifiable, evidence-linked claims scored 3 out of 6. A re-test is scheduled for July 28, 2026, and results will be published either way.
Is this methodology open to use by other sites?
Yes. The five pillars and their verification criteria are published in full on this page, free to apply to any site. ZenMasterWorks also offers this as a service for businesses that want it implemented and verified directly.
Want this applied and verified on your own site?
We build the page first, run the same evidence-density and cross-engine verification checks defined above, and you pay only if you're satisfied with the result.
Start a Project →