Why isn't my site showing up in AI search?
There are 5 common reasons a site never shows up in AI search, and almost all of them are mechanical, not mysterious. You block the crawlers, your content only renders in JavaScript, you aren't in Google's index, the page is too thin to quote, or there's no self-contained answer near the top. Google's own position, in Google's AI optimization guide, is that the same fundamentals apply. The rule underneath all of it: “you can't be quoted by a machine that can't read you.”
1. You block the crawlers in robots.txt, often by accident
This is the single most common cause, and most owners do it to themselves. To be cited in ChatGPT, Perplexity, or Claude, you have to let their retrieval bots fetch the page. Those are separate user-agents: OAI-SearchBot for ChatGPT search, PerplexityBot for Perplexity, and Claude-SearchBot for Claude. To appear in Google AI Overviews, you have to let plain Googlebot in, because Overviews are built on Google's normal index.
What goes wrong: an owner reads a scare headline about AI training, decides to "keep the AI out," and adds a blanket Disallow: / for every bot they can name. That removes the site from the answers entirely. Training and retrieval are different jobs done by different bots. You can refuse the training crawler and still welcome the one that cites you.
How to check: open yoursite.com/robots.txt in a browser and read it line by line. Look for any Disallow: / under the search bots above, or a wildcard User-agent: * block that catches them. If the retrieval bots are blocked, that alone explains the silence.
2. Your content only renders with JavaScript
Retrieval crawlers take the raw HTML your server returns. They generally do not run your JavaScript, wait for a framework to boot, and hydrate the page the way a browser does. So if your headline, your answer, and your body copy only appear after JavaScript runs, the crawler sees an empty shell and quotes a competitor whose answer is sitting in the HTML.
A page can look flawless to you and be nearly blank to a bot. This is one of the failures we catch most often on otherwise well-built sites, because modern frameworks default to client-side rendering and nobody told the owner what that costs.
How to check: load your page with JavaScript disabled in your browser settings, or right-click and view the raw page source. Search that source for a sentence you can see on the rendered page. If your real content is not there as plain text, the crawler can't see it either.
3. You aren't indexed by Google
Google AI Overviews are drawn from Google's existing index. There is no separate AI index. If your page can't surface in ordinary Google Search, it can't surface in an Overview either. So an indexing problem is also an AI-search problem, and it has to be fixed first.
Pages drop out of the index for ordinary reasons: a stray noindex tag, a canonical pointing at another URL, a site that's too new to be crawled yet, or a thin page Google chose not to keep. None of it is AI-specific, but all of it ends the same way.
How to check: search Google for site:yoursite.com and see whether your pages come back. For the real answer, open Google Search Console, use the URL Inspection tool on the exact page, and confirm it says the URL is on Google. If it isn't indexed, that is the first thing to fix.
4. The page is thin or commodity
Even a perfectly crawlable, indexed page gets skipped if there is nothing specific worth quoting. AI engines pull passages that say something. A page that restates the obvious in generic language, the same paragraph a hundred other sites already published, gives the engine no reason to choose you over any of them.
The fix is not length for its own sake. It is substance: unique, first-hand, specific content. A real number, a named tool, a step someone actually performed, a result with a date attached. Specifics are what make a passage quotable, because they carry information the generic version doesn't.
How to check: read your page and ask what a person could not get from any other page on the topic. If the honest answer is "nothing," that's the gap. Add the detail only you have.
5. There's no self-contained answer near the top
Engines quote passages that answer the question directly, on their own, without the reader needing the rest of the page. If your answer is buried below three paragraphs of preamble, or split across the page, the engine has nothing clean to lift. The most quotable shape is a short, complete answer placed right under a heading that matches the question.
So lead with the answer in the first paragraph, in plain language, before any windup. Put a specific number or a named entity in it. Use a clear, question-style heading so the engine can match it to what the person typed. This page is built that way on purpose: the answer block sits first, with a number and a source.
How to check: read only your first paragraph. If it does not answer the page's main question by itself, rewrite it until it does.
What you do not need to chase
There is a lot of folklore in this space, so be careful where you spend effort. Google's official AI guide is blunt about it: there is no separate framework for AI search, the same SEO fundamentals apply, and the page has to be crawlable and indexable before anything else matters. Google has also said on the record that it does not use llms.txt, so do not treat that file as a requirement or a shortcut. The work that pays off is the work that always paid off. Be reachable, be readable without JavaScript, be indexed, and be the most specific answer on the page.
Check all five in one scan
You can walk through every reason above by hand, or you can paste your link into Brimm and let us check them at once. We read your site the way the engines do, then tell you whether the retrieval bots can reach you, whether your answer survives without JavaScript, whether you look indexable, and how quotable your top passage is. We print the failures in fix order, in plain language, so you know exactly what to change first.