Why is my site in Google but not in AI answers?
The four differences between ranking in search and being cited by an assistant — and why the first does not lead to the second.
Because they are different systems with different inputs. Google renders JavaScript and most AI crawlers do not. Google ranks pages; assistants extract passages. Google has your whole history; an answer engine is choosing a source for one specific question, right now.
Difference one: rendering
The largest and most common cause. Googlebot executes JavaScript on a second pass — slowly and selectively, but it does. Most AI crawlers do not render at all.
A site built with client-side rendering therefore presents two entirely different faces: a complete page to Google, and an empty container to almost every AI crawler. It can rank respectably while being invisible to every assistant, and nothing in your search analytics would ever hint at it.
curl -sL https://yoursite.com | grep -i "a distinctive sentence from your page"If that returns nothing, this is your answer, and it is one change rather than a strategy.
Difference two: pages versus passages
Google ranks documents. A person clicks and finds the relevant part themselves.
An assistant extracts a passage and presents it as the answer. That requires a self-contained span of text that makes sense removed from its surroundings. A page that builds an argument over eight paragraphs is excellent for a reader and offers nothing liftable.
Difference three: different crawlers, different permissions
Allowing Googlebot says nothing about the others. Each operator uses its own tokens, and a robots.txt permitting Google can block every AI crawler — often unintentionally, via a blanket rule or a copied snippet.
The specific trap: a catch-all Disallow: / with a named Allow group for Googlebot. Google is fine. Every crawler without its own group is blocked, which is most of them.
Difference four: no accumulated history
Your Google position reflects years of signals — links, engagement, domain history. An answer engine choosing a source for one question weighs the page in front of it far more heavily. That cuts both ways: established sites lose some of their structural advantage, and a well-structured page from a smaller site can be chosen over a famous one.
Working through it
curl -sLyour page and confirm your content is in the delivered HTML. This is the single highest-yield check.- Read your
robots.txtand confirm the AI search crawlers have permission, by name. - Check your logs for their requests — and specifically the status codes they receive, since a WAF can block what robots.txt permits.
- Restructure your key pages so each answers a specific question directly beneath a heading that asks it.
- Add clear attribution: a named author, an organisation, a date.
The first three are mechanical and take under half an hour between them. They account for most cases where a site ranks in Google and appears nowhere else.
When the mechanics are already right
If you are crawled, indexed and readable and still not cited, you are competing on merit — and the competitive question is narrower than in search. Look at who is cited for your topic and what their pages do: usually a direct answer near the top, original detail rather than a summary of others, and visible authorship. That is a content project rather than a technical one, and it is a much better position to be in.
What our audit reports about this
Every item below is measured directly, not inferred. Run it against your own site and the result names the exact rule or header responsible.
- How much of your content is in the delivered HTML versus added by JavaScript — the difference Google papers over and AI crawlers do not.
- Per-crawler access resolution, so a rule permitting Googlebot while stranding others is visible.
- Whether pages carry question-shaped headings with direct, extractable answers beneath them.
- Whether authorship, organisation and dates are present and machine-readable.
For agents and scripts, the same measurement is at
/api/v1/ai?url=yoursite.com —
see the API documentation.
Related questions
Does Google AI Overviews work the same way as ChatGPT?
No. AI Overviews draw on Google's own Search index, so if you rank you are already eligible. ChatGPT search, Perplexity and Claude use their own crawlers and indexes, which is exactly why you can be present in one and absent from the others.
My site is server-rendered and still not cited. What now?
Then the mechanics are likely fine and it is a structure and substance question. Look at what is cited for your topic — it is usually a page that answers one specific question directly rather than covering the area comprehensively.
Should I make a separate version for AI crawlers?
No. Serving different content to crawlers than to people is cloaking, it is against the guidelines of every major operator, and it risks removal from search. Server-render the same content for everyone.
How long until AI assistants pick up my changes?
Search-index inclusion is typically days to weeks. User-triggered fetches are immediate, which is why a URL pasted into a conversation works for a page published minutes ago. Training data is months at minimum and tied to model releases.
Read next
What is the difference between crawling, indexing and citing?
Three separate stages, each with its own failure mode — and why fixing the wrong one wastes months.
ReadDoes JavaScript hurt AI crawlers?
Yes, more than it hurts search engines. If your content only exists after JavaScript runs, most AI crawlers see an empty page.
ReadHow do I make a page quotable by AI?
The structural changes that make a passage extractable — most of them a rearrangement of what you have already written.
ReadHow does Google AI Overviews pick sources?
What is known about how AI Overviews selects what it quotes, what follows from it, and what nobody outside Google actually knows.
Read