AEO mistakes: 11 reasons AI search skips your site

TL;DR: Most AEO failures are not content-quality problems. They are configuration mistakes: bot rules that block ChatGPT and Perplexity from fetching your pages, an llms.txt file you added thinking it moves Google, structured data added in the wrong place, and pages that never state the answer in one sentence. Each one below comes with a test you can run this week.

---

Table of contents

1. Why AEO mistakes are different from SEO mistakes
2. Mistake 1: blocking AI crawlers without knowing it
3. Mistake 2: treating llms.txt as a ranking lever
4. Mistake 3: assuming schema markup guarantees citations
5. Mistake 4: measuring rankings instead of citations
6. Mistake 5: ignoring Reddit and other UGC platforms
7. Mistake 6: no unlinked brand-mention strategy
8. Mistake 7: never tracking AI referral traffic
9. Mistake 8: pages that cannot be lifted as an answer
10. Mistake 9: blaming AEO for a core-update problem
11. Mistake 10: no direct-answer FAQ format
12. Mistake 11: auditing once instead of continuously
13. Old habit vs AEO-ready practice
14. Frequently asked questions
15. Key takeaways

Why AEO mistakes are different from SEO mistakes

You can rank on page one and still never show up in a ChatGPT or Perplexity answer. That gap is what an r/seogrowth thread from July 2026 asked directly: sites that rank well on Google but are invisible in AI answers, and what actually fixed it (r/seogrowth). The replies split roughly into two camps: technical blockers the site owner did not know existed, and content that ranks but never states a clean, extractable answer.

Answer engines do not return ten blue links. They synthesize one response and cite a handful of sources inside it. A YouTube breakdown from July 2026 put organic click-through rate down 61% on queries where Google’s AI Overviews appear, and Ahrefs’ own measurement (via seo-kreativ) found a 58% CTR reduction on the top-ranking page for AI Overview keywords as of July 2026, with roughly 60% of searches now ending without a click at all, 77% on mobile (seo-kreativ, citing Ahrefs). If your site is not one of the sources the model pulls from, that traffic is gone, not delayed.

The mistakes below are not about writing worse or better content. Most of them are structural: something is blocking the model, something is misconfigured, or something is measured wrong. Each one gets a fix and a test you can run without a new tool. If you have not run a baseline audit yet, do the 40-check AI visibility audit first so you know which of these mistakes actually apply to you before you start fixing all eleven at once.

Mistake 1: blocking AI crawlers without knowing it

The mistake: a CDN rule, a bot-management vendor, or a robots.txt line added years ago for a different reason blocks OpenAI’s GPTBot, Anthropic’s ClaudeBot, or Perplexity’s PerplexityBot from fetching your pages. Nobody notices because the site still ranks fine on Google, which uses a separate crawler.

Why it happens: many bot-blocking defaults (Cloudflare’s “AI Scrapers and Crawlers” managed rule, generic “block bad bots” plugins) treat every non-Googlebot AI agent as scraper traffic, because from a pure crawl-cost standpoint, that is exactly what it is. The rule was correct for the problem it was solving. It is wrong for AEO.

The fix: pull your robots.txt and check it line by line for Disallow rules scoped to GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Amazonbot, and OAI-SearchBot. Then check your CDN or WAF dashboard separately, because robots.txt is instructional (compliant bots honor it, nothing enforces it), while a CDN rule is enforcement. A clean robots.txt with an active WAF block still shows zero AI crawler hits in your logs.

The test: search your server logs or CDN analytics for GPTBot and PerplexityBot user agents over the last 30 days. Zero hits on a site with real traffic is the signal, not the absence of Disallow lines. Whether to block them at all is its own decision with real trade-offs on training-data exposure vs citation potential; if you are undecided, work through the crawler-blocking decision framework before you change anything.

Mistake 2: treating llms.txt as a ranking lever

The mistake: publishing an llms.txt file at your domain root and assuming it moves you up in Google’s AI Overviews, the way an XML sitemap moves crawl priority.

It does not, for Google specifically. Gary Illyes said as much in July 2025, and John Mueller has compared llms.txt to the old keywords meta tag: something a lot of sites publish, that Google Search does not use for ranking or inclusion (ALM Corp; Baseline Labs; Wix Studio AI Search Lab). The confusion is understandable: the file format looks authoritative, and it is genuinely useful for something, just not the thing most people assume.

The fix: stop treating llms.txt as an SEO or AEO growth lever. Perplexity and Claude do consume it as a content map when they crawl, and as of the 2026 update, Chrome’s Lighthouse 13.3 moved llms.txt auditing into its default Agentic Browsing category, which is a real signal that agentic browsers are starting to read it. Publish it if you want a clean machine-readable index of your key pages for the engines that do use it. Do not publish it expecting a Google AI Overviews lift.

The test: if your llms.txt strategy consists of “we added the file, now we wait,” you have confused a nice-to-have with a growth lever. Go check whether you show up in Perplexity and Claude answers for your target queries at all; that is the metric llms.txt can plausibly move. For the full breakdown of what each engine actually does with the file, read the engine-by-engine llms.txt truth table.

Mistake 3: assuming schema markup guarantees citations

The mistake: spending a sprint adding FAQPage, HowTo, and Article schema across the site because “AI needs structured data to understand your content,” then being confused when citations do not move.

Google has stated structured data is not a requirement for inclusion in AI-generated search features; a July 2026 breakdown flagged this explicitly (GEO vs SEO in 2026, YouTube). Structured data helps machines parse a page faster and more reliably, but the model still has to decide the content is worth citing. Schema without an extractable, well-organized answer does nothing; a clear answer with zero schema still gets cited if the model can parse it from the HTML.

The fix: use schema for what it is actually good for: disambiguating entities, exposing prices and availability, and giving rich results a shot at a SERP feature. Do not treat it as an AEO checkbox that substitutes for writing a direct, quotable answer. Prioritize the content structure work first, schema second.

The test: pull three pages that already have full schema and check whether they show up in any AI answer for their target query. If they do not, the bottleneck is the content, not the markup. This exact tension between Google’s own guidance and what actually moves citations is worth reading in full at is structured data required for AI search.

Mistake 4: measuring rankings instead of citations

The mistake: reporting the same keyword-position dashboard to leadership every month, with no visibility into whether AI answers ever mention your brand.

Rankings and citations are different distributions. A page can sit at position 3 on Google and never appear in a single ChatGPT or Perplexity answer for a semantically identical query, because the model is not paginating results, it is picking a handful of sources based on different signals: entity clarity, extractable structure, and how often the brand is mentioned elsewhere, not just backlink count. One X post from a marketer put it plainly: traditional SEO metrics cannot capture AI search, because answer engines reward brand authority signals, not keyword optimization in the classic sense (@KDHungerford).

The fix: add a citation-tracking line to your reporting, even a manual one. Run your top 20 target queries through ChatGPT, Perplexity, and Google AI Overviews monthly and log whether you appear, and where in the response. It is tedious the first time and takes fifteen minutes after that.

The test: ask yourself whether you could answer “which of our pages got cited by an AI engine last month” right now, without opening a new tool. If the honest answer is no, your reporting is measuring the wrong funnel stage. Share of answer is the metric built to replace share of voice for exactly this gap, and it belongs in the same dashboard as the KPIs that still matter when clicks are disappearing.

Mistake 5: ignoring Reddit and other UGC platforms

The mistake: running an SEO and content program that never touches Reddit, forums, or Q&A sites, because they historically had a low return relative to owned content.

That calculation flipped. Reddit was the single most-cited domain by both Google AI Overviews and Perplexity between August 2024 and June 2025, ChatGPT cites Reddit in roughly 12% of US answers, and Reddit shows up in about 37% of Google SERPs overall (Sitebulb; CMSWire). Answer engines treat community discussion as a trust signal separate from your own site’s authority, because it reads as unprompted, third-party corroboration.

The fix: participate on Reddit where your actual customers ask questions, with disclosed, non-promotional answers that would stand on their own without your brand attached. Answers that read as an ad get downvoted and removed before an AI engine ever indexes them.

The test: search your product category plus “reddit” and see whether any thread mentioning you ranks or gets pulled into an AI answer. If every relevant thread is about a competitor, that is a specific, fixable gap, not a vague brand-awareness problem. The full compliant playbook, including what gets threads banned versus cited, is in how to use Reddit to get cited by AI search.

Mistake 6: no unlinked brand-mention strategy

The mistake: running link-building outreach that only counts as a win when it produces a hyperlink, and ignoring every mention of your brand name that does not link back.

Answer engines do not need a hyperlink to register a brand. They parse text. A named mention on a review site, a comparison post, or a forum answer, with zero anchor text, still tells the model your brand is associated with the topic. Backlink-only measurement misses all of that signal entirely.

The fix: track branded mentions the same way you track backlinks: volume, source quality, and sentiment, whether or not they link. Outreach scripts built purely around “will you link to us” leave real citation opportunities on the table when the answer is “we’ll mention you but we don’t do outbound links.”

The test: search your brand name in quotes across the web and count how many results are not your own domain and do not link to you. If that number is small relative to your linked mentions, unlinked mentions are an underbuilt channel, not a dead one. The full case for treating mentions as a ranking signal in their own right is at brand mentions are the new backlinks for AI search.

Mistake 7: never tracking AI referral traffic

The mistake: GA4 is configured to bucket ChatGPT, Perplexity, and Copilot referrals under “unassigned” or generic “referral” traffic, so the channel is invisible in every report, and nobody notices it growing or shrinking.

This is a setup problem, not a data problem. The July 2026 GEO breakdown named it directly: set up GA4 to track AI referral traffic from ChatGPT and Perplexity as explicit referrers, rather than letting default channel grouping swallow them (GEO vs SEO in 2026). Without that, you cannot tell whether last month’s AEO work did anything.

The fix: build a custom channel group or exploration in GA4 that isolates referrer domains for chat.openai.com, chatgpt.com, perplexity.ai, copilot.microsoft.com, and gemini.google.com. This is a one-time setup, not a recurring task.

The test: open GA4 right now and try to answer “how much traffic did ChatGPT send us last month.” If the answer requires guessing from an “Other” bucket, the tracking is not done yet. The full referrer regex and exploration setup is in how to track ChatGPT and Perplexity traffic in GA4.

Mistake 8: pages that cannot be lifted as an answer

The mistake: writing a 2,000-word article with a five-paragraph introduction before the actual answer appears, structured the way a magazine feature is structured rather than the way a reference page is structured.

Answer engines extract passages, not whole pages. A page that buries its direct answer under throat-clearing forces the model to either skip the page or extract a worse, out-of-context passage. Roughly a third of AI citations come from comparative, list-style content with clear, scannable structure, which is exactly the format that is easiest to lift a clean passage from.

The fix: answer the title question in the first sentence or two, before any context, history, or caveats. Follow with the supporting detail. This is the inverse of the classic magazine-lede structure, and it feels unnatural to write the first few times.

The test: cover the rest of the page and read only the first 60 words. If a reader could not state your answer from that alone, an AI model extracting that same passage cannot either. This same front-loading discipline is what makes good SEO overlap with good GEO in some places and diverge from it in others.

Mistake 9: blaming AEO for a core-update problem

The mistake: a traffic drop happens, and the team spends weeks chasing AEO fixes when the actual cause was a Google core update or continuous relevance re-evaluation that has nothing to do with AI answer engines.

As of July 8, 2026, Google had confirmed two 2026 core updates, one running March 27 to April 8, and one running May 21 to June 2, with no announced core update in June or July, even though third-party volatility trackers recorded elevated ranking movement through that window (DualMedia; ALM Corp). A drop that lands outside an announced window is more likely continuous re-evaluation drift than a named update, and neither one is an AEO problem.

The fix: before touching AEO tactics, check the date of the traffic drop against Google’s confirmed update calendar and a third-party volatility tracker. If the drop lines up with an announced window, that is a core-update recovery problem. If it does not, check for technical issues or content decay before assuming AI search stole the traffic.

The test: pull your analytics for the exact week of the drop and cross-reference it against the confirmed update dates above. A mismatch is your signal to look elsewhere first. If it is a core-update pattern, the core update recovery playbook separates update damage from ongoing drift; if the dates do not line up at all, start with why traffic dropped with no announced update.

Mistake 10: no direct-answer FAQ format

The mistake: skipping a dedicated FAQ section because “the content already answers those questions somewhere in the body,” which is true for a human reader skimming the whole page and false for a model extracting one passage at a time.

An FAQ section with a clear question as the heading and a self-contained 40 to 80 word answer underneath is close to the exact shape an answer engine needs: a bounded unit of text that answers one specific query without requiring the rest of the page for context. Burying the same answer inside paragraph four of a narrative section makes the model do extraction work it would rather skip in favor of a page that already did it.

The fix: add a real FAQ section, formatted as headings plus short paragraphs, not a collapsed accordion rendered client-side with JavaScript the crawler may not execute. Answer real questions your audience actually asks, pulled from the same forums and Reddit threads you are already reading for mistake 5, not invented questions that pad a template.

The test: check whether an AI crawler can see your FAQ text in raw HTML (view source, not the rendered DOM). If the questions only appear after JavaScript executes, some crawlers will miss them entirely.

Mistake 11: auditing once instead of continuously

The mistake: running one AEO audit, fixing the crawler-blocking and llms.txt issues, and considering the project closed.

Answer engines change their citation behavior as models update, and each engine behaves differently. Perplexity, ChatGPT, and Gemini select and weight sources in different ways, so a fix that improves your citation rate in one engine may do nothing in another. Model updates, index refreshes, and shifting community sentiment all move the target without any change on your side.

The fix: put the citation check from mistake 4 on a recurring monthly calendar, alongside a quarterly recheck of the crawler-blocking, schema, and llms.txt items from mistakes 1 through 3. Treat it the way you treat a Core Web Vitals check: infrequent enough not to burn time, frequent enough to catch drift before it compounds.

The test: ask when you last re-ran your full AEO checklist. If the honest answer is longer than three months, you are due. Understanding how Perplexity, ChatGPT, and Gemini differ in what they cite makes the recurring check faster, because you already know which engine to test first for which query type.

flowchart TD
    A[AI answers never mention you] --> B{Can GPTBot, PerplexityBot,\nand ClaudeBot fetch your pages?}
    B -- No --> C[Fix robots.txt and CDN bot rules]
    B -- Yes --> D{Does the page state the answer\nin the first 60 words?}
    D -- No --> E[Rewrite the lead as a direct answer]
    D -- Yes --> F{Are you mentioned, linked or not,\non Reddit and review sites?}
    F -- No --> G[Start a brand-mention program]
    F -- Yes --> H{Is AI referral traffic\ntracked in GA4?}
    H -- No --> I[Set up AI referrer tracking]
    H -- Yes --> J[Recheck citations monthly]
    C --> D
    E --> F
    G --> H

Old habit vs AEO-ready practice

Area	Old SEO habit	AEO-ready practice
Bot management	✗ Block all non-Google bots by default	✓ Allow named AI crawlers, decide per engine
llms.txt	✗ Publish it and expect a Google ranking lift	✓ Publish it for Perplexity and Claude, not Google
Structured data	✗ Treat schema as the AEO checklist item	✓ Use schema for entities and rich results, write the answer first
Reporting	✗ Track keyword position only	✓ Track citations and share of answer alongside rankings
Community content	✗ Skip Reddit as low-ROI	✓ Participate where the AI engines already cite the community
Off-site mentions	✗ Count links only	✓ Track unlinked brand mentions as their own signal
Analytics	✗ Let AI referrers fall into “unassigned”	✓ Isolate ChatGPT, Perplexity, and Copilot as named referrers
Page structure	✗ Lead with a narrative introduction	✓ Answer the title question in the first two sentences
Drop diagnosis	✗ Assume every drop is an AI-search problem	✓ Cross-check the date against confirmed core updates first
FAQ sections	✗ Skip them, “the answer is in the body”	✓ Bounded, self-contained 40-80 word answers per question
Audit cadence	✗ One-time AEO audit	✓ Monthly citation check, quarterly technical recheck

If you are running this checklist across a content program rather than one page, doing it manually every month gets expensive fast, which is where a workflow that pairs keyword and citation-target research with word-count-controlled drafting and direct publishing to WordPress, Ghost, Shopify, or a webhook starts to matter; Vrid.ai builds that pipeline for teams who need the audit-fix-republish loop above to run on a schedule instead of whenever someone remembers.

Frequently asked questions

What is answer engine optimization (AEO)?

AEO is the practice of structuring content so ChatGPT, Perplexity, and Google AI Overviews can extract and cite it directly in a synthesized answer, rather than just ranking it in a list of links. It overlaps with SEO but adds crawler access, direct-answer formatting, and citation-worthy structure as distinct requirements.

Is AEO different from GEO?

Practitioners use AEO and GEO (generative engine optimization) close to interchangeably, though GEO leans slightly broader, covering any generative AI surface, while AEO focuses on answer-style responses specifically. Neither term has a single standardized definition yet; treat the tactics as the same discipline under two names.

Why does my site rank on Google but never get cited by ChatGPT?

The most common causes are a bot rule blocking GPTBot from fetching your pages, content that never states a direct answer near the top, or a lack of corroborating mentions elsewhere on the web. Google’s crawler and OpenAI’s crawler are separate systems with separate access rules, so ranking with one says nothing about access for the other.

Does blocking AI crawlers hurt my SEO rankings?

No. Blocking GPTBot, ClaudeBot, or PerplexityBot has no effect on Googlebot or your Google rankings, because these are entirely separate crawlers with separate purposes. It only affects whether that specific AI engine can access and potentially cite your content.

Does llms.txt help me rank on Google?

No. Google’s Gary Illyes and John Mueller have both indicated Google Search does not use llms.txt for ranking or inclusion, comparing it to the old keywords meta tag. It may help Perplexity and Claude, which do consume it during crawling, and Chrome’s Lighthouse 13.3 now audits for it under Agentic Browsing.

Is structured data required to get cited by AI search?

No, and Google has said so directly. Structured data can help machines parse your content faster and supports rich results, but a page with clean, extractable prose and no schema can still get cited if the direct answer is present and well-organized.

How do I check if AI crawlers can access my site?

Check your robots.txt for Disallow rules scoped to GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, and OAI-SearchBot, then separately check your CDN or WAF dashboard for bot-management rules, since those enforce blocks that robots.txt only requests. Cross-reference with server logs to confirm actual crawl attempts.

How do I track ChatGPT and Perplexity traffic in Google Analytics?

Build a custom channel group or exploration in GA4 that isolates referrer domains for chatgpt.com, chat.openai.com, perplexity.ai, copilot.microsoft.com, and gemini.google.com. Without this setup, AI referral traffic defaults into a generic “unassigned” or “referral” bucket and is effectively invisible in standard reports.

Why is Reddit so often cited by AI search engines?

Reddit was the single most-cited domain by both Google AI Overviews and Perplexity between August 2024 and June 2025, and ChatGPT cites it in roughly 12% of US answers. Answer engines treat community discussion as independent, unprompted corroboration, which carries different weight than content published by the brand itself.

What counts as a brand mention for AI search if there is no link?

Any instance of your brand name appearing in text that an AI model’s training or retrieval process can parse, including reviews, comparison articles, and forum answers, whether or not the mention includes a hyperlink. Models read text, not just link graphs, so unlinked mentions still register as association signals.

How often should I re-audit my site for AEO?

Run a lightweight citation check monthly, testing your top target queries across ChatGPT, Perplexity, and Google AI Overviews. Run a fuller technical recheck of crawler access, llms.txt, and schema quarterly, since model updates and engine behavior shift the target continuously.

Can a traffic drop be caused by AI Overviews instead of a core update?

Yes, and the two causes need different fixes. Cross-check the date of your traffic drop against Google’s confirmed core update windows; if it does not match an announced update, check whether the drop concentrates on queries where AI Overviews now appear, since CTR on those queries can drop 34-58% even without any ranking change.

Do I need to write differently for AI search than for Google?

Mostly the same fundamentals apply: clear structure, direct answers, credible sourcing. The addition for AI search is stating the direct answer in the first sentence or two rather than building up to it, since answer engines extract short passages rather than reading the whole page in context.

What is share of answer and how is it different from rankings?

Share of answer measures how often your brand appears inside AI-generated responses for a defined set of queries, compared against competitors appearing in the same responses. Unlike keyword rank, which measures position in a list, share of answer measures whether you show up in the synthesized response at all.

Should I add an FAQ section to every page for AEO?

Add one where real user questions exist for the topic, formatted as a heading plus a self-contained 40-80 word answer in raw HTML rather than a JavaScript-rendered accordion. Skip it on pages where there is no natural question to answer; padding a template with invented questions does not help.

Does AI content get penalized in AI-generated answers?

There is no evidence that AI-assisted content is penalized specifically for being AI-generated, in either Google Search or AI answer engines. What gets filtered out is thin, unoriginal, or unverified content, regardless of how it was produced.

How many AI citations come from list and comparison content?

Comparative and list-format content accounts for roughly a third of AI citations, because that structure is already close to the extractable passage format answer engines prefer: bounded, scannable, and easy to lift without losing meaning.

Is E-E-A-T still relevant for AI search?

Yes, arguably more so, since answer engines weigh corroborating signals like brand mentions and community discussion alongside on-page expertise signals. A small site with no press coverage can still build these signals through consistent, honest participation in the communities where its audience already asks questions.

What is the single fastest AEO fix to check first?

Confirm AI crawlers can actually reach your site. It takes ten minutes to check robots.txt and CDN bot rules, and if GPTBot or PerplexityBot is blocked, every other AEO improvement on the page is irrelevant until that is fixed.

Where should I start if I have never done an AEO audit?

Start with a full baseline audit covering crawler access, content structure, schema, and off-site mentions before fixing anything individually, so you know which of these eleven mistakes actually apply to your site rather than guessing.

Key takeaways

• Blocked AI crawlers is the single most common and most fixable AEO mistake; check robots.txt and your CDN’s bot-management rules separately, because either one alone can block access.
• llms.txt does not move Google rankings; Gary Illyes and John Mueller have both said so. It may help Perplexity and Claude, which do consume it.
• Structured data helps machines parse content faster but does not substitute for a direct, extractable answer near the top of the page.
• Track citations and share of answer alongside keyword rankings, or you will not notice AEO progress or regression until it shows up in traffic.
• Reddit was the most-cited domain by Google AI Overviews and Perplexity from August 2024 through June 2025; participating there compliantly is a real citation lever, not a vanity channel.
• Unlinked brand mentions carry citation weight. Track them the way you track backlinks.
• Set up GA4 to isolate ChatGPT, Perplexity, and Copilot as named referrers before you draw any conclusion about how much AI traffic you are or are not getting.
• Front-load the direct answer in the first two sentences of every page; that is the passage most likely to get extracted.
• Cross-check any traffic drop against Google’s confirmed core-update calendar before assuming AI search caused it.
• Re-run your citation checks monthly. Each engine’s behavior shifts independently as models update.

Run the eleven checks above against your five highest-traffic pages this week. If crawler access and answer-format issues turn up on more than two or three of them, fix those first before touching anything else on this list; they block everything downstream.