The 30-second answer
AEO in one paragraph.
AEO (Answer Engine Optimization) makes public content easier for retrieval systems to access and understand, then measures whether that content appears as a cited source. SEO measures rankings and organic traffic. AEO adds retrieval readiness and source monitoring. A sound baseline has crawlable content, accurate structured data where appropriate, accountable authorship, retrieval access, and useful source material. llms.txt is optional, and FAQPage belongs only where matching Q&A is visible. Neither guarantees citations.
If your buyers use ChatGPT, Perplexity, or Google AI Overviews, AEO gives you a way to improve observable source readiness and measure whether your brand appears. The product still decides which sources to select.
Search behavior now spans more products than classic results alone.
For two decades, the way to be found online was simple: rank on Google, get clicks, convert traffic. Search engines returned a list of ten blue links, the user picked one, the site they picked got the visit. The whole industry of SEO was built around moving up that list.
Search now includes classic results, AI summaries, assistants, and research products. Usage and source presentation vary by category, query, location, product, and date. There is no single adoption percentage that describes every commercial search or buyer journey.
No universal percentage supports a claim that commercial searches now end inside AI answers. Measure your own queries and buyer behavior. Citation is not a binary visibility score.
When a source citation appears, it creates another discovery path. When it does not, that result is one observation, not proof that a brand is invisible. AEO adds retrieval access, explicit source material, and repeat source monitoring to an SEO foundation. Products may combine indexes, retrieval systems, and language models in different ways, so measure rankings, traffic, citations, and referrals separately.
Three layers to audit before citation monitoring.
A useful way to plan AEO is in three practical layers. They organize observable work, but they are not universal source-selection filters and none guarantees a citation.
Machine readability
Can retrieval agents access crawlable page content and can machines identify the page accurately? Blocking access can prevent direct retrieval, but structured data alone is not a selection guarantee.
- Valid JSON-LD schema
- Optional llms.txt discovery file
- Clean sitemap
- Retrieval access checked separately from training policy
- Semantic HTML
Content accountability
Once a page is crawlable, make its ownership, claims, dates, and evidence explicit. These qualities help readers and retrieval systems interpret the source without guaranteeing selection.
- Named author
- FAQPage schema
- Quotable claims
- Publication dates
- Entity coverage
Authority
Third-party evidence can support factual claims and entity consistency. Its effect varies by query and product, so measure outcomes rather than assuming a compounding citation advantage.
- Quality backlinks
- Brand mentions
- Domain age
- Third-party reviews
- Industry coverage
Technical factors you can verify before monitoring citations.
Source-selection systems are proprietary and change over time. The factors below are observable content and technical checks, not universal filters or weights.
Answer the actual buyer question.
Some systems expand or decompose a query during retrieval. Pages should answer the buyer question with clear, factual sections, but no specific content shape guarantees source selection.
Make content crawlable and explicit.
Crawlable HTML and accurate structured data help machines interpret a page. They do not establish a universal order between parseability and authority, and they do not guarantee that a cleaner page will be cited.
Keep dates, claims, and evidence accurate.
Use factual publication and modification dates. Time-sensitive queries may need current evidence, but adding a recent date or Article schema does not guarantee ranking or citation.
FAQ schema must match visible answers.
FAQPage schema describes visible question and answer content in a machine-readable format. It is not a ranking factor, and the Meridian15 audit treats exact visible-to-schema parity as an optional 2-point check out of 66.
Use accountable claims and consistent entity information.
Keep organization details, author identity, and third-party claims factual and consistent. Avoid keyword stuffing. No universal rule says entity coverage outweighs every other factor in every product.
The two are not in conflict, but they are not the same.
The most common mistake we see is treating AEO and SEO as alternatives. They are not. They share infrastructure but optimize for different outcomes. We cover the full breakdown in a separate post; here is the short version.
SEO
Optimizes for being clicked.
AEO
Optimizes for being cited.
The infrastructure overlap (clean technical health, substantive content, structured data, authority) means investing in one usually improves the other. The divergence is where the leverage is. AEO and SEO share the same core foundation: crawlable content, accurate metadata, structured data, authorship, and authority. AEO does not require deep keyword targeting at the URL level, but SEO does.
If buyer research shows that classic search drives discovery, keep SEO central. If repeated query sampling shows that AI answers affect the category, add source monitoring and answer-focused content. Do not assume AEO weight increases every quarter for every brand.
Source presentation differs by product and mode. The interface examples below are illustrative, not live Meridian15 results.
ChatGPT, Perplexity, Google AI Overviews, and Claude expose different retrieval agents, training controls, and source interfaces. Treat public access controls separately and measure source selection instead of inventing a universal refresh order or weighting model.
| Engine | Retrieval access | Citation style | Training control | What access means |
|---|---|---|---|---|
Perplexity |
PerplexityBot | Source presentation varies by product and mode | No paired training-control claim in this audit | Retrieval access does not guarantee selection |
Google AI Overviews |
Googlebot for Search indexing | Source presentation varies by query and product | Google-Extended is a separate training control | Google does not use llms.txt |
ChatGPT |
OAI-SearchBot and ChatGPT-User | Source presentation varies by product and mode | GPTBot is a separate training control | Retrieval access does not guarantee selection |
Claude |
Claude-SearchBot and Claude-User | Source presentation varies by product and mode | ClaudeBot is a separate training control | Retrieval access does not guarantee selection |
The practical takeaway: keep content crawlable, structured data accurate, and retrieval access explicit. llms.txt is optional, Google does not use it, and training crawler policy is separate. Measure each product without claiming a fixed weighting or refresh order.
What this looks like in practice.
Do not use a generic citation curve as a client outcome. Establish a dated baseline, keep the query set stable, record the product and mode, and report what changes. The framework below is illustrative and contains no client performance data.
Illustrative reporting framework · no client outcome claim
Citation monitoring by product
measurement statusSet the baseline first.
Record the exact query, product, mode, date, cited sources, and answer before implementation. A baseline makes later changes measurable.
Keep the query set stable.
Compare like with like. A changing prompt set cannot prove citation growth, and a recurring citation does not establish a permanent source preference.
Report uncertainty.
Answers vary across products and over time. Report observed citations without claiming a fixed engine order, training cycle, or guaranteed catch-up.
Six baseline checks worth reviewing.
Review these six baseline items against the page and business. They are practical checks, not universal citation levers, and implementation time depends on the site.
Publish an optional llms.txt file
A curated Markdown discovery file for compatible tools. Support is incomplete, Google does not use it, and it does not guarantee citations. See the full guide.
Check retrieval access in robots.txt
Check that robots.txt does not block OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, or PerplexityBot. Decide training crawler access separately.
Add accurate Organization JSON-LD sitewide
Accurate structured data makes the brand name, URL, logo, and factual sameAs links explicit. Keep those values consistent with the visible site.
Add FAQPage schema where you have Q and A content
The visible questions and schema must match exactly. Schema must match visible Q and A on the page. Highest-impact single move on most sites.
Name the author on every editorial page
Even a single meta name="author" tag flips the E-E-A-T signal. Person schema with bio and credentials is the stronger version when the author is real.
Audit and iterate
Once the baseline is shipped, measure a stable query set and record what changes. Iteration does not guarantee reliable citation.
Try it now
See where your site stands.
Type a URL. We will fetch the page, run the same 13 technical checks our audit tool runs, and show you a real score in about ten seconds. No email required.
What not to do, because doing it makes things worse.
Bad implementation can make content inaccurate, inconsistent, or inaccessible. These are common technical and editorial mistakes, not a universal engine penalty list.
Faking FAQ schema with no visible Q&A.
FAQPage JSON-LD must represent matching visible questions and answers. The Meridian15 audit penalizes schema-only FAQ markup. FAQPage is not a ranking factor or citation guarantee.
Blocking AI crawlers in robots.txt.
Separate retrieval access from training policy. Check OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, and PerplexityBot for retrieval. GPTBot, ClaudeBot, and Google-Extended are separate training controls.
Walls of marketing prose with no quotable claims.
"We are a leading provider of innovative solutions" gives readers little evidence. Specific, verifiable details give people and retrieval systems clearer source material.
Hiding answers inside accordions only.
Accordions are fine for design, but keep answer text crawlable in the delivered HTML. JavaScript support varies, so do not make essential content depend on an interaction.
Stuffing keyword density.
Repeating a keyword does not create useful evidence. Write factual coverage for people, keep language natural, and evaluate search performance separately.
Skipping author attribution because "we are a brand."
Use a factual named author or accountable organization where appropriate. Authorship is worth 8 of 66 audit points, but a meta author tag alone is not the single biggest E-E-A-T signal and does not guarantee citation.
Frequently asked.
Measure source visibility
Audit your site, then build the plan.
Two minutes to see where you stand. Then either ship the baseline yourself, or talk to us about doing it for you. If budget is the open question, here is what AEO costs.