# Google Gemini SEO: How Gemini Picks Sources

> Source: https://rankxai.com/blog/gemini-seo · Last updated: 2026-09-08

Google Gemini SEO is the work of getting your pages cited by Gemini, the Google AI assistant. Gemini grounds its answers in Google Search results rather than in a crawler of its own, and a separate robots.txt token, Google-Extended, decides whether your content is eligible. That token does not control AI Overviews, which Googlebot governs.

## What is Gemini SEO?

Google Gemini SEO is the practice of getting your pages retrieved and cited by Gemini, Google's AI assistant. The unit of visibility is a mention or a citation inside a written answer, not a position in a list of search results, so a page is either in the answer or it is absent from it.

The first job is deciding which Google surface you actually mean. Google runs at least three things people call Google AI: [Google AI Overviews](/glossary/ai-overview) at the top of a search results page, [AI Mode](/glossary/google-ai-mode) as a conversational tab inside the search engine itself, and the Gemini assistant as a separate app and API. They are not interchangeable, and the first two are further apart than they look: [AI Mode and AI Overviews compared](/blog/google-ai-mode-vs-ai-overviews).

Getting that wrong is expensive rather than academic. The two families answer to different controls, they are measured in different places, and one of them reports into Search Console while the other reports nowhere at all. Most AI search advice on this subject treats them as one system.

## Gemini and AI Overviews are different surfaces with different controls

Gemini and AI Overviews answer to different controls. Three of them exist. Most published guides describe two, and Google documents each one in a separate place, which is most of why the field keeps merging them.

Google's [AI features documentation](https://developers.google.com/search/docs/appearance/ai-features) states the Search half: AI is built into Search and integral to how Search functions, which is why robots.txt directives for Googlebot are the control site owners use to manage access. The preview controls that apply are `nosnippet`, `data-nosnippet`, `max-snippet` and `noindex`.

Google's crawler documentation states the Gemini half just as directly. [Google-Extended](/glossary/google-extended) governs Gemini Apps, the Vertex AI API for Gemini, and grounding in both. It then adds the sentence that settles the question: Google-Extended does not impact a site's inclusion in Google Search, nor is it used as a ranking signal in Google Search.

**A third control arrived on 31 August 2026 and most published advice predates it.** Search Console now carries a Search generative AI setting, under Settings, offering Include, Exclude or Inherit, and it covers AI Overviews, AI Mode and generative AI in Discover. Google states that it affects only those features and is not used as a ranking or inclusion signal elsewhere in Search.

| Surface | What governs access | What excluding yourself costs |
| --- | --- | --- |
| AI Overviews and AI Mode | The Search generative AI setting in Search Console | Those features only. Google states it is not a ranking or inclusion signal for the rest of Search |
| AI Overviews and AI Mode | Googlebot, via robots.txt and the preview controls | Your place in Google Search as a whole, since the same token serves both |
| Gemini assistant and Vertex AI | Google-Extended in robots.txt | Grounding and training eligibility for Gemini, with Search untouched |

That setting is now an eligibility condition as well as an opt-out. Google's [generative AI optimisation guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), updated 10 July 2026, says a site must be included in Search generative AI features in Search Console to be eligible for display in them, on top of the ordinary requirement to be indexed and snippet-eligible.

## The mistakes this distinction prevents

Blocking Google-Extended to stay out of Google's AI answers does not work, because it leaves AI Overviews running exactly as before. Google-Extended reaches the assistant and the Vertex API, and Google says in terms that it carries no weight in Search. AI Overviews are part of Search.

The reverse error costs more. Blocking Googlebot does remove you from AI Overviews and AI Mode, and it removes you from ordinary Google results in the same stroke, because that token serves both at once. For most of the period this subject has been written about, that was the whole choice available.

**The third error is now the commonest, and it is quoting the old answer.** Guides published before 31 August 2026 say no setting keeps the blue links and drops the AI summary. That was true and is not: the Search Console control does precisely that, for AI Overviews and AI Mode, on Google's own statement that it carries no weight elsewhere in Search. It still does nothing about Gemini.

So three controls reach three different things, and only one of them is a general opt-out from Google's AI answers in Search. None of them opts you out of everything Google labels AI. Our [AI Crawler Access Checker](/tools/ai-crawler-access-checker) reads a live robots.txt against both tokens and more than twenty other AI agents.

## Does Google Gemini have its own crawler or index?

Google Gemini has neither a crawler of its own nor a search index of its own. This is the most commonly misstated fact about the platform. Google's crawler documentation says Google-Extended has no separate HTTP request user agent string, that crawling is done with existing Google user agent strings, and that the token is used in a control capacity.

One practical consequence follows immediately. Google-Extended will never appear in a server log, because nothing by that name ever requests a page. A log-based crawler audit cannot confirm or deny that your Google-Extended rule is working, and the only way to check it is to read the robots.txt you are actually serving.

For reaching the live web, Gemini uses [grounding](/glossary/grounding). Google's [Gemini API documentation](https://ai.google.dev/gemini-api/docs/google-search) describes Grounding with Google Search as connecting the model to real-time web content, returning grounding metadata and inline citation annotations alongside the answer.

The detail worth carrying away is that Gemini decides whether to search at all. Google's wording is that the AI model analyses the prompt and determines if a Google Search can improve the answer. A question it answers without searching is answered from [training data](/glossary/training-data), which was fixed at the model's [knowledge cutoff](/glossary/knowledge-cutoff) and which nothing you publish this month can change. **No amount of SEO reaches an answer the model never searched for.**

## Does ranking in Google get you cited by Gemini?

Ranking in Google predicts Gemini citations weakly, which is a strange result for an assistant grounded in Google Search. [Ahrefs searched 15,000 long-tail queries](https://ahrefs.com/blog/ai-search-overlap/) in early July 2025 and compared what four assistants cited against what ranked. Gemini's overlap was 8.6 per cent of cited URLs also ranking in Google's top 10. Perplexity was the outlier at 28.6.

The unquoted column in that study is the more useful one. **For 84.9 per cent of the URLs Gemini cited, the page did not rank in Google's top 100 at all** for the query that produced the answer. Not outside the top ten: absent from the first hundred results. A further 6.5 per cent ranked somewhere beyond position ten.

[Query fan-out](/glossary/query-fan-out) is the likeliest explanation, and Google names the technique in its own documentation. The answer is assembled from several related searches instead of the one you typed, so the pages Gemini reaches are often top results for questions the user never saw. Your ranking for the visible query is only loosely connected to whether you appear.

Two things follow for how you spend effort. Chasing position one on a head term optimises for a query Gemini may never issue, while covering the adjacent questions competently puts you in the searches it does. Note the age of the evidence as well: the measurement is fourteen months old and nobody has published a 2026 replication that separates the assistants this way.

## Google has published requirements for AI Overviews and none for Gemini

Google publishes eligibility rules for AI Overviews and AI Mode, and publishes nothing equivalent for the Gemini assistant. The asymmetry has widened rather than closed: Google shipped a dedicated optimisation guide for its Search AI features in July 2026 and a Search Console report for them in August, and produced neither for its own assistant. Our [AI Overviews article](/blog/rank-in-google-ai-overviews) sets out what those Search requirements say.

Check the scope of the sentence being quoted. Google's statement that you need no new machine readable files, no AI text files and no special schema.org data is made about AI Overviews and AI Mode, the two features inside Search. The Gemini assistant is a different product and appears nowhere in that guidance.

For Gemini itself Google documents exactly one lever, and it is a permission, not a technique. Google-Extended decides whether your content may be used for grounding and training in Gemini Apps. There is no published list of things a page should do to be selected once it is eligible.

Two conclusions follow, and the second is the uncomfortable one. Advice that cites Google's no-special-optimisation line as settled guidance for Gemini is quoting a Search document about a different surface. And **anyone claiming to know what Gemini rewards is working from inference, because Google has not said.**

## Which parts of traditional SEO carry over to Gemini?

More of traditional SEO carries over to Gemini AI than to most assistants. The reason is structural, and it is not especially encouraging. Gemini reaches the web through Google Search, so the work that makes a page eligible for Google is the same work that makes it reachable for Gemini. Technical SEO is not a separate discipline here, and there is no Gemini-specific checklist that sits beside it.

The floor is the ordinary one. A page has to be crawlable by Googlebot, indexed, eligible for a snippet, and readable as text without JavaScript. A page that fails any of those is invisible to Google Search, to AI Overviews and to Gemini grounding at the same time, which makes technical SEO the cheapest AI-visibility work available.

[Schema markup](/glossary/schema-markup) deserves a straight answer, because most SEO strategies aimed at Gemini lead with it. Google says no special structured data is required for its AI features, and it publishes nothing at all about schema and the Gemini assistant. Structured data still earns its place for rich results and for making entities unambiguous. No public evidence ties it to being cited by Gemini.

What changes is the unit of optimisation. Traditional SEO tunes a page to compete for a query, while Gemini lifts a passage out of a page and drops the rest. **A section that only makes sense after three paragraphs of preamble is a section the assistant cannot use**, which is why answer-first writing does more for Gemini than any markup does.

Two Google surfaces outside your own site count as well, and Google names them itself. Its generative AI guidance says Merchant Center feeds and Google Business Profile can help products and services appear in AI responses. Read the scope again before acting on it: that guidance covers the Search AI features, so it is AI Overviews work that happens to share a programme with Gemini.

The discipline that covers this across every assistant is [Generative Engine Optimization](/blog/generative-engine-optimization), and Gemini is the platform where it overlaps most with the SEO a team already does. Treat the Gemini-specific work as a thin layer on top of that, rather than as a separate programme with its own budget.

## What Gemini visibility looks like on our own site

RankX AI runs a tracked prompt panel against its own domain. Gemini names the brand there less often than three of the four other assistants. The panel holds 45 prompts covering research, comparison and purchase-stage questions about AI-visibility tooling, scheduled daily across five platforms. The window to 7 September 2026 returned 595 answers with an analysed verdict, well short of what a full daily run of every prompt would produce, because the panel was widened on 30 August and its recorded history is still filling.

| Platform | Answers naming RankX AI | Mention rate | 95% confidence interval |
| --- | --- | --- | --- |
| ChatGPT | 17 of 123 | 13.8 per cent | 8.8 to 21.0 per cent |
| Grok | 15 of 119 | 12.6 per cent | 7.8 to 19.8 per cent |
| Claude | 14 of 124 | 11.3 per cent | 6.8 to 18.1 per cent |
| Gemini | 10 of 118 | 8.5 per cent | 4.7 to 14.9 per cent |
| Perplexity | 9 of 111 | 8.1 per cent | 4.3 to 14.7 per cent |

The ordering is what the panel shows and the gaps are not separable at this sample size, which is the part most platform comparisons leave out. Gemini's interval runs from 4.7 to 14.9 per cent and ChatGPT's from 8.8 to 21.0, and they overlap across most of their range. A two-proportion test on that pair returns p = 0.19, so the difference does not clear conventional significance.

Reported honestly, then: Gemini sits in the lower half of this panel, and a sample this small on a single brand cannot tell you it sits below Claude or Grok specifically. Anyone publishing a confident league table of platforms from a panel this size is reporting noise as a finding. **The useful reading is the width of those intervals, not their order.**

One pairing is worth stating because it cuts against the obvious explanation. Across an overlapping 28-day window the same site recorded 9,819 Search Console impressions at an average position of 63.8, which is to say it ranks nowhere in particular. It is still named in about one Gemini answer in twelve. That illustrates a loose coupling between assistant mentions and Google position without testing it, because a single site with no ranking variation cannot test anything.

**Now the uncomfortable part, because our own published numbers demonstrate the trap.** On 30 August this panel read 61 mentions in 328 answers, 18.6 per cent. On 4 September it read 61 in 401, 15.2 per cent. Today it reads 65 in 595, 10.9 per cent. Four mentions arrived across those eight days and the headline rate fell by nearly eight points, because the denominator grew by 82 per cent.

Gemini shows it in the sharpest form. Our [Perplexity SEO article](/blog/perplexity-seo), published on 4 September, gives Gemini 10 of 78 answers, 12.8 per cent. This article gives 10 of 118, 8.5 per cent, three days later. **The numerator did not move once.** Both figures are correct, both are honestly labelled, and read side by side without the denominators they look like a collapse in visibility that never happened.

## How to work on Gemini visibility, in order

Gemini SEO work divides into the settled and the speculative. The settled comes first. The order below runs cheapest and most certain to most speculative, and most of it is ordinary SEO pointed at an AI search surface rather than a new discipline.

1. **Check the Search generative AI setting in Search Console, under Settings.** It is newer than most published advice, it is now an eligibility condition for AI Overviews and AI Mode as well as an opt-out, and it takes about ten seconds to read. Include is the default. This step does nothing for Gemini and is here because people arrive looking for it.
2. **Decide the Google-Extended question deliberately.** Read your live robots.txt and confirm whether you allow it. Blocking it removes Gemini grounding eligibility and, on Google's own statement, costs you nothing in Search. Allowing it is the default and is what most sites want.
3. **Confirm Googlebot is not restricted**, by robots.txt or by a CDN or bot-management rule. This is the control that governs AI Overviews and AI Mode, and it is the one that also governs whether you are in Google at all.
4. **Serve the content in the HTML, while knowing Gemini is the one assistant that may cope without it.** Because Gemini reaches the web through Google Search, it inherits Googlebot's rendering, so client-side content can survive here where it dies on the others. Google's rendering is deferred rather than guaranteed, and the other four assistants read raw HTML, so [server-side rendering](/glossary/server-side-rendering) is still the right default. Treat Gemini as the exception that does not change the rule.
5. **Answer the question in the opening sentence of each section.** Retrieval lifts passages without their surrounding context, so a section that builds to its conclusion gets extracted before the conclusion arrives.
6. **Name the entity instead of using pronouns across section boundaries.** A chunk beginning "It supports" is unusable once separated from the heading above it.
7. **Earn coverage on pages that already rank for the fan-out questions**, not only for your head term. Because Gemini assembles answers from several related searches, the pages it reaches are often ranking for questions adjacent to the one asked.
8. **Skip the AI-specific file work if Google's AI surfaces are the only goal.** Google says no AI text file or extra schema is required. Publish llms.txt if you want it for other assistants, with clear eyes about what it is for.

## How to measure Gemini visibility in AI search

Gemini assistant visibility does not appear in Search Console. That surprises SEO teams who assume every Google surface reports together. Search Console gained a dedicated generative AI performance report on 31 August 2026, breaking impressions down by page, country, date and device. It covers AI Overviews and AI Mode, the two features inside Search.

The Gemini assistant is absent from that report, and its absence is the point. Google shipped reporting for its Search AI features and nothing for its assistant, so the surface most people mean by Gemini is the one surface Google gives you no numbers for. Anyone quoting a Search Console figure as their Gemini visibility is reading AI Overviews.

So the two surfaces need two instruments. Google AI Overviews and AI Mode are measured in that report, against the pages you already track. The assistant has to be measured by asking the AI platform questions repeatedly and recording whether your brand appears, which is what a tracked prompt panel does.

Two cautions apply to any such panel, and both come from running one. Answers vary between identical runs, so a single check is close to meaningless and a rate over many checks is the only readable number. And the denominator moves whenever you add prompts, so a rate that falls after a panel expansion may record nothing except a larger denominator.

## How RankX AI tracks Gemini

RankX AI is our own product. This is the part of the article where we describe it instead of the field. It runs a fixed set of prompts against Gemini, ChatGPT, Claude, Perplexity and Grok on a daily schedule and records whether each answer names your brand. It reports the rate per platform with the check counts visible, which is where the table earlier in this article comes from.

It tracks Gemini and AI Overviews as separate things on purpose, for the reason this article opens with. Gemini is measured through the assistant run; [AI Overviews tracking](/features/ai-overviews) runs through the rank-tracking pipeline on tracked keywords, because that is the surface they belong to. Reporting them as one number would hide the fact that a site can do well in one and be absent from the other.

If you want the crawler-access half without signing up for anything, the [AI Crawler Access Checker](/tools/ai-crawler-access-checker) reads a live robots.txt against Google-Extended, Googlebot and the other AI agents and tells you what each one is currently allowed to do. The [AI Visibility](/features/ai-visibility) page covers the tracking side in full.

## Is Gemini SEO different from optimising for AI Overviews?

Yes, and three separate controls are involved rather than two. AI Overviews and AI Mode are part of Search: they answer to Googlebot via robots.txt and the preview controls, and since 31 August 2026 also to a Search generative AI setting in Search Console that includes or excludes a site from those features alone. The Gemini assistant answers to Google-Extended, which governs training and grounding for Gemini Apps and the Vertex AI API. Google states that Google-Extended does not affect inclusion or ranking in Google Search, so blocking it removes you from Gemini grounding while leaving AI Overviews untouched.

## Does Google-Extended show up in server logs?

No, and that surprises people running log-based crawler audits. Google's crawler documentation states that Google-Extended has no separate HTTP request user agent string, that crawling is done with existing Google user agent strings, and that the robots.txt token is used in a control capacity only. Nothing called Google-Extended ever fetches a page, so it cannot appear in a log file. You verify it by reading your robots.txt, not your access log.

## Does Gemini have its own web crawler or index?

No separate crawler, and it reaches the web through Google Search. Google's own documentation describes Grounding with Google Search as connecting the model to real-time web content, with the model deciding whether a search would improve the answer before running one. Google-Extended has no user agent of its own and relies on existing Google crawlers. A question that does not trigger a search is answered from training data instead, where nothing you change on your site can reach it.

## Do you need llms.txt or extra schema to appear in Google's AI answers?

Not according to Google. Its AI features documentation, last updated 10 December 2025, says you do not need to create new machine readable files, AI text files, or markup to appear in these features, and that there is no special schema.org structured data you need to add. Read the scope carefully: that statement covers AI Overviews and AI Mode inside Google Search. It is not a claim about ChatGPT, Perplexity or Claude, which publish their own guidance and behave differently.

## Does ranking in Google get you cited by Gemini?

It helps and it is a weak predictor. Ahrefs searched 15,000 long-tail queries in early July 2025 and compared what four assistants cited against what ranked. Gemini's overlap was 8.6 per cent of cited URLs also ranking in Google's top 10, against 28.6 per cent for Perplexity, the outlier. The more striking figure from the same study is that 84.9 per cent of the pages Gemini cited did not rank in Google's top 100 at all for the query that produced the answer, which is what query fan-out would predict.

## How long does it take to show up in Gemini?

Google publishes no figure for this, and anyone quoting a specific number is guessing. The binding constraint is Google's crawl and index cycle, because Gemini grounds through Google Search rather than a crawler of its own. Google's own documentation says recrawling can take anywhere from several days to several months, depending on how often its systems decide a page needs refreshing. A page nobody has recrawled reaches Gemini at the speed of that recrawl, whatever you changed on it.

## Can you measure Gemini visibility in Search Console?

Only for AI Overviews and AI Mode, not for the Gemini assistant. Search Console gained a dedicated generative AI performance report on 31 August 2026, with impressions broken down by page, country, date and device, and it covers those two Search features. The Gemini app is a separate product and reports nothing there, so the only way to measure it is to ask it questions repeatedly and record whether your brand appears, which is what a tracked prompt panel does. A Search Console number quoted as Gemini visibility is really AI Overviews.