ChatGPT vs Gemini: how each one finds your content, and what that means for your business

TL;DR

Difficulty: Intermediate

ChatGPT search and Google's AI features want the same thing from a page: that it can be fetched, may be quoted, and answers the question plainly. What differs is the gate.

  • ChatGPT: your robots.txt must allow OpenAI's search crawler. Blocking its training crawler, GPTBot, only refuses training.
  • Google AI Overviews and AI Mode: the page must be indexed and allowed to show a snippet. No special markup is needed.
  • Gemini app: blocking Google's Extended control keeps you out of its grounded answers, but not out of Google Search.
  • Measure it: ask the same 30 questions in both tools every month and count citations. With 30 questions, a move under about 20 points is noise.

The old advice was to pick a side, ChatGPT or Gemini, and split your content strategy accordingly. In this article I trace how each tool actually finds and cites a page, from OpenAI's and Google's own documentation, set out what the UK usage figures say, and follow an invented Leeds law firm as it opens both gates and measures the result month by month.

The question is not which tool, it is how each one finds a page

When this article first went up, the advice of the day was to pick a side. ChatGPT for the technical crowd, Gemini for the Google crowd, and a content strategy split down the middle. It sounded tidy. Most of it was guesswork about who uses what, and I have cut that guesswork from this version because I could not find a source for any of it.

What can be sourced is more useful anyway. OpenAI and Google both publish how their tools go and fetch pages from the web, which crawler does the fetching, what a page needs to be eligible, and how the sources show up in the answer. Once you know the two paths, the question "where should I optimise" mostly answers itself. You make one good page, you make sure both paths are allowed to reach it, and you check, on a fixed schedule, whether it is being cited.

This article does three things. It traces how ChatGPT search and Google's AI features (AI Overviews, AI Mode and the Gemini app) find and cite a page, with a diagram of each path. It sets out what the usage figures for the UK actually say, from Ofcom and the Reuters Institute rather than from a vendor's blog. And it shows a simple, honest way to measure your own visibility in both, with an invented Leeds law firm and a month by month count.

Two things it does not do, because sister articles already do them well. The vocabulary of SEO, AEO, GEO and AIO is in the complete guide to AI search optimisation. How to write a passage that an engine can lift is in winning visibility in the age of AEO and GEO. If ChatGPT is your only concern, how to rank in ChatGPT is the shorter read.

Worked example: the firm in this article

Kirkgate Family Law is an invented firm of six solicitors in Leeds. It handles divorce, child arrangements and financial settlements, and it sells a fixed fee first consultation at £195. The managing partner is Hannah. Nobody real, every number made up.

Hannah's problem arrived in a sentence from a new client: "I asked ChatGPT how long a divorce takes and it sent me to a firm in Manchester." She did not know whether that was bad luck or a pattern. She also did not know whether Gemini would have done the same, or whether the answer was even the same twice. By the end of this article she will have a way to find out, for £0 and about two hours a month.

How ChatGPT search finds and cites a page

ChatGPT can answer in two ways. It can answer from what the model learnt in training, which carries no live sources. Or it can search the web first and answer from what it finds, with links. OpenAI launched the second mode for everyone as ChatGPT search on 31 October 2024. In its announcement it says that ChatGPT can choose to respond with information from the web, that answers include links to sources such as news articles and blog posts, and that a Sources button under the reply opens a sidebar with the references.1

Where do the results come from? OpenAI's own wording is that ChatGPT search draws on third party search providers, as well as content provided directly by its partners.1 The announcement does not name the providers. The old version of this article said flatly that "ChatGPT uses Bing". I would not write that today on the strength of OpenAI's own page, which does not say it, so I have corrected it to what OpenAI does say.

Then there is OpenAI's own crawler. OpenAI runs three different bots, and the difference between them matters more than anything else in this section.2

  • OAI-SearchBot is for search. OpenAI states that sites opted out of it will not be shown in ChatGPT search answers, though they can still appear as plain navigational links.
  • GPTBot gathers content that may be used to train OpenAI's foundation models. Disallowing it says your content should not be used for training. It does not, on OpenAI's description, remove you from search.
  • ChatGPT-User visits a page when a person in ChatGPT asks for it, for example by pasting a link. Because a person started it, OpenAI says robots.txt rules may not apply, and it is not used to decide what appears in search.

So there are two separate switches. One says "you may show me in answers". The other says "you may train on me". Plenty of sites have flipped both off by accident, usually with a robots.txt line written in a hurry in 2023 that blocked anything with "GPT" in its name.

Worked example: Hannah's robots.txt

Hannah asks her web developer to send over the firm's robots.txt. It contains this:

User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

Step one: read the first block. It refuses the training crawler. That is a perfectly reasonable business choice. A law firm may not want its guides used to train a model, and nothing in OpenAI's documentation says this costs it a place in search answers.2

Step two: read the second block. It refuses the search crawler. On OpenAI's own description, that means Kirkgate's pages will not be shown in ChatGPT search answers.2 This is very likely why the client was sent to Manchester. The Manchester firm was not better. It was simply allowed in.

Step three: decide on purpose. Hannah keeps the training refusal and removes the search refusal. The file becomes:

User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Allow: /

Step four: write the decision down, with the date. Next year, when someone asks why GPTBot is blocked, the answer is a sentence, not an archaeology project.

How Google's AI features and Gemini find and cite a page

Google has three products here that people lump together as "Gemini". It helps to pull them apart.

AI Overviews are the AI written summary at the top of an ordinary Google results page. AI Mode is a separate tab for longer, conversational questions. It launched in the UK on 28 July 2025.3 Google says both run on a custom version of Gemini 2.5.4 The third product is the Gemini app itself, the chatbot, which is a different place again.

For AI Overviews and AI Mode, Google's documentation is unusually direct. Both may use a "query fan out" technique, issuing multiple related searches across subtopics and data sources before writing the answer.5 To be shown as a supporting link, a page must be indexed and eligible to be shown in Google Search with a snippet. Google adds that there are no additional requirements, no special optimisations, and no special schema.org structured data you need to add.5 The controls are the ordinary search ones: nosnippet, data-nosnippet, max-snippet and noindex. And visits from these features are counted inside your normal search traffic in Search Console, under the Web search type, not in a separate line.5

The Gemini app and the Gemini models that developers use work in a similar way, which Google documents for its developer interface as grounding with Google Search. The steps it lists are: the prompt arrives, the model decides whether a Google Search would improve the answer, if so it writes one or more queries and runs them, it reads and synthesises the results, and it returns an answer with inline citations that link parts of the answer to their sources.6

One switch here behaves differently from what most people expect. Google's crawler documentation describes a control token called Google-Extended. It covers whether your content may be used to train future Gemini models, and whether it may be used for grounding in the Gemini app and in grounding with Google Search on Vertex AI. Google is explicit that it does not affect a site's inclusion in Google Search and is not a ranking signal there.7 So blocking Google-Extended can keep you out of the Gemini app's grounded answers while leaving you in AI Overviews and AI Mode, which are part of Search. That is the opposite of the intuition "block the AI bot, vanish from the AI".

Worked example: Hannah's fees page

Hannah's developer checks the Google side. The firm's pages are indexed, so the first condition is met. Then he finds this on the fees page, wrapped around the paragraph that gives the £195 consultation price and the typical cost of an uncontested divorce:

<div data-nosnippet>

Step one: what does it do? It tells Google not to use that text in a snippet.5 Step two: what does that mean now? The only passage on the site that answers "how much does a divorce solicitor cost in Leeds" cannot be quoted in a snippet, and a page needs to be eligible for a snippet to be a supporting link in AI Overviews and AI Mode.5 Step three: the fix. Remove the attribute from that paragraph, and keep it only on the one block that genuinely should never be quoted, a disclaimer about individual circumstances.

Step four: check Google-Extended. The robots.txt does not mention it. Hannah decides that the firm is happy to be used for grounding in the Gemini app, so it stays unmentioned. That is a decision now, not an accident.

The two paths, top to bottom

Here are both paths, each from the question to the cited answer. They are drawn separately because the switches are separate.

Tap or click to open full screen and move around
Tap or click to open full screen and move around

Read each flow from the top. Both start with a question and both end with an answer carrying links. In between, each has one gate that you control: for ChatGPT it is whether OAI-SearchBot may visit, for Google it is whether the page is indexed and may show a snippet, with Google-Extended as an extra switch that only touches the Gemini app. The takeaway is that the two paths look alike from the outside and are opened by different keys. Neither path asks for special markup or a special kind of page.

Worked example: one question through both paths

A prospective client in Headingley types "how long does a divorce take in England" into both tools.

In ChatGPT, step one, the tool decides the question benefits from a search, because it is about current law and timescales. Step two, it searches through its providers. Step three, it reaches the gate. Before the robots.txt fix, Kirkgate's guide fails here and cannot be shown. After the fix, it passes. Step four, the model writes the answer from the pages it read and lists them under Sources. Whether Kirkgate is one of them now depends on the page itself, which is the subject of the sister article on passages.

In Google, step one, the question is split into searches such as "minimum time from application to conditional order" and "how long between conditional order and final order". Step two, those run against the index. Step three, the gate: Kirkgate's guide is indexed and, since the fees page fix, nothing on it blocks a snippet. It passes. Step four, the answer is written and supporting links are attached.

Two different gates. Two different fixes. One page.

What the UK usage figures say, and what they do not

The old version of this article had a section called "who uses what". It said ChatGPT dominates developers and B2B SaaS buyers and Gemini dominates local businesses and enterprise teams on Google Workspace. I could not find a primary source for any of those splits, so the section is gone. Here is what the published figures do say for the UK.

Ofcom's Online Nation report for 2025, using Ipsos audience measurement, found that Google Search reached 82% of UK online adults in May 2025, and ChatGPT, the most used generative AI service, reached 13%.8 The same report, citing Similarweb, puts ChatGPT at 252 million UK web visits in August 2025, up 156% on a year earlier, with Gemini growing 146% from a much smaller base.8 It also reports that around 30% of keyword searches deliver an AI supported overview, and cites YouGov research that 53% of UK people say they often see AI summaries.8 Ofcom's own reading is that much of this is passive adoption: people using ordinary search and getting an AI Overview included.8

The Reuters Institute's Generative AI and News Report 2026, a survey in nine countries, found that weekly use of standalone generative AI tools was lowest in the UK, at 42%.9 Across the six countries it has tracked since 2024, weekly use of ChatGPT rose from 22% to 34% and of Gemini from 11% to 24%, and 57% of people across all nine said they had seen or engaged with AI generated answers in a search engine in the last week.9 For news specifically, the Digital News Report 2026 found that 10% of people across its markets use AI chatbots for news each week, and that the UK was the lowest of any market at 4%.10

Notice that these numbers do not agree, and they are not meant to. Ofcom's 13% is the share of online adults measured visiting ChatGPT in a month, by a panel that records behaviour. The Reuters Institute's 42% is the share who say, in a survey, that they used any standalone AI tool in the last week, a year and a half later. One is measured, one is reported. One is one product, the other is all of them. A careful reader keeps the measure next to the number.

Worked example: what the figures mean for Hannah

Let me turn the Ofcom shares into people, so the sizes are easy to hold. This is arithmetic for scale, not a forecast for Leeds.

Take 1,000 UK online adults. In May 2025, 1,000×0.82=8201{,}000 \times 0.82 = 820 of them used Google Search in the month and 1,000×0.13=1301{,}000 \times 0.13 = 130 used ChatGPT.8

Now the AI Overviews figure. If roughly 30% of keyword searches carry an AI Overview,8 then a Google user who runs ten searches will on average meet about three of them. Most of the 820 will see AI written answers in Google without ever opening a chatbot. That is Ofcom's passive adoption, in numbers.

What Hannah takes from this is not "ignore ChatGPT". It is that the largest AI audience she has is the one already searching on Google, and that the ChatGPT audience is smaller but growing fast and actively choosing to ask. Both are worth being open to. Neither is worth a separate content strategy.

What actually differs for your content, by kind of business

Here is the honest core of it. On the published documentation, both paths want the same thing from a page: that it can be fetched, that it is allowed to be quoted, and that it answers the question plainly. Google says no special optimisation is needed for its AI features.5 OpenAI's only stated requirement for search answers is not blocking its search crawler.2 Everything past that is judgement, and below it is mine, labelled as mine.

Local services, such as a solicitor, a dentist or a plumber. In my view this is where the Google path matters most, simply because Ofcom's figures put far more people in Google Search than in any chatbot,8 and local questions are typed into Google out of habit. What I check first: the pages are indexed, nothing blocks snippets, and every service page states the town, the price range and the timescale in plain sentences. I do not see a separate Gemini tactic here.

eCommerce shops. In my experience the product questions people take to a chatbot are comparisons ("which is better for a small kitchen") rather than "buy this". The pages that get cited in the shops I have worked on are buying guides and comparison pages written by a person, not the product pages. That is true on both paths, and it is my observation, not a documented rule.

SaaS and technical products. The old article claimed ChatGPT "dominates" technical queries. I have no source for that, so I will not repeat it. What I see in my own work is that technical buyers ask longer, more specific questions in both tools, and the pages that get cited answer one specific question each: a setup guide, a pricing explanation, an honest comparison with a named alternative.

Professional services, such as accountants, consultants and law firms. In my experience the thing that most often keeps them out of AI answers is not the writing. It is a robots.txt or a snippet setting nobody remembers adding, exactly like Hannah's. Fix the gates first, then the pages.

The old article also suggested posting on Medium, Quora and Reddit so the models would "train" on you, and putting content in Google Drive to surface in Gemini. I have cut both. Training is not the same as being cited in a live answer, and neither OpenAI nor Google documents Drive content as a route into public answers.

Worked example: Hannah's priority list

Hannah has limited time, so she ranks the work by which gate it opens.

Step one: the ChatGPT search gate. Allow OAI-SearchBot. Ten minutes for her developer.

Step two: the Google snippet gate. Remove data-nosnippet from the fees paragraph. Ten minutes.

Step three: the pages themselves. Kirkgate has 14 guides. Hannah picks the three that answer the questions clients ask most often (how long, how much, what happens to the house) and asks one solicitor to rewrite each so that the question is the heading and the first sentence gives the answer, with the detail after it. The method is in the sister article on being the answer in AI search. Three guides at about two hours each is six hours of a solicitor's time.

Step four: measure, which is the next section. Without it, she will never know whether steps one to three did anything.

Measuring it: the same 30 questions, both tools, every month

Neither OpenAI nor Google gives you a report of how often your site is cited in AI answers. Google counts clicks from its AI features inside your ordinary Search Console figures, without separating them.5 In the analytics I look after, visits from ChatGPT show up as referrals from chatgpt.com, but a referral only tells you about the people who clicked, not about the answers where you were cited and nobody clicked.

So the honest way to measure is the plain one. Write a fixed list of questions your clients actually ask. Ask every one of them in each tool, once a month, in a clean session. Record whether your site is cited in the answer. Then count.

The number you track is a rate:

r=cqr = \frac{c}{q}

Here rr is the citation rate for one tool in one month, cc is the number of questions where the answer cited your site at least once, and qq is the number of questions asked, which stays fixed. Foundations: ratios and rates.

Keeping qq fixed is the whole trick. If you change the questions every month, you are measuring your choice of questions, not your visibility.

And because 30 questions is a small sample, the rate will wobble from month to month even if nothing has changed. The standard error tells you how much wobble to expect:

SE=r(1−r)qSE = \sqrt{\frac{r(1 - r)}{q}}

Here SESE is the standard error of the citation rate, rr is the rate you measured, and qq is the number of questions asked. A change smaller than about two standard errors is the kind of change chance alone produces often. Foundations: sampling.

Worked example: Kirkgate's first three months

Hannah writes 30 questions from the firm's own enquiry emails, such as "how long does a divorce take in England", "do I need a solicitor for a child arrangements order" and "fixed fee divorce solicitor Leeds". In the first week of each month, a trainee asks all 30 in ChatGPT with search on and in the Gemini app, each in a fresh chat, and ticks a spreadsheet column when Kirkgate's site appears among the sources. It takes about an hour per tool.

These are the invented counts. August is before any changes. The robots.txt and snippet fixes went live in the second week of August, and the three rewritten guides in September.

Out of 30 fixed questions asked each month, ChatGPT cited the firm in 6 in August, 8 in September and 11 in October. The Gemini app cited it in 9 in August, 10 in September and 15 in October. Invented figures. Tap or click to open full screen and move around

Along the bottom are the two tools and the three months. Up the side is the number of the 30 questions whose answer cited Kirkgate's site at least once. The takeaway: both tools cite the firm more often in October than in August, and the rise is steady rather than a single jump. Whether that is a real change or a lucky month is what the arithmetic below settles.

Step one: turn the counts into rates with r=c/qr = c / q. ChatGPT in August is 6/30=0.2006 / 30 = 0.200 and in October 11/30=0.36711 / 30 = 0.367. The Gemini app in August is 9/30=0.3009 / 30 = 0.300 and in October 15/30=0.50015 / 30 = 0.500.

So ChatGPT went from 20.0% to 36.7%, a rise of 16.7 percentage points. The Gemini app went from 30.0% to 50.0%, a rise of 20.0 points.

Step two: the standard error of the October ChatGPT rate is 0.367×0.633/30=0.00774=0.088\sqrt{0.367 \times 0.633 / 30} = \sqrt{0.00774} = 0.088, which is 8.8 percentage points. For the Gemini October rate it is 0.5×0.5/30=0.00833=0.091\sqrt{0.5 \times 0.5 / 30} = \sqrt{0.00833} = 0.091, which is 9.1 points.

Step three: compare the rise with the wobble. The standard error of a difference between two months combines both months' errors. For ChatGPT, August to October, it is 0.200×0.800/30+0.00774=0.00533+0.00774=0.01307=0.114\sqrt{0.200 \times 0.800 / 30 + 0.00774} = \sqrt{0.00533 + 0.00774} = \sqrt{0.01307} = 0.114.

A rise of 16.7 points against a standard error of 11.4 points is about 1.5 standard errors. On its own, that is not enough to call it a real change. One more question cited moves the rate by 3.3 points, and asking the same question twice can bring back different sources. With 30 questions, the rule I use is that one month's move of under about 20 points proves nothing by itself.

Step four: read the pattern, not one pair of months. Both tools rose in both months after the fixes, the Gemini rise is 20.0 points against a difference error of about 12 points, and the timing matches the work. That is a reasonable basis for Hannah to keep going. It is not proof, and I would tell her so. Three more months on the same 30 questions will settle it either way.

Step five: decide what to do with the gap between the tools. In October the Gemini app cites Kirkgate in 15 answers and ChatGPT in 11. Four questions apart, out of 30, is well inside the wobble, so Hannah does not start a separate ChatGPT project. She keeps one set of pages and one list of questions, and lets the monthly count tell her if a real gap opens up.

What I would do on Monday

If I sat down with your site tomorrow, this is the order.

  1. Read the robots.txt. Decide, on purpose, for OAI-SearchBot (search answers), GPTBot (training) and Google-Extended (Gemini training and grounding). Write the decisions down.
  2. Check that the important pages are indexed and that nothing stops them showing a snippet. Look for nosnippet, data-nosnippet and max-snippet that nobody remembers adding.
  3. Pick the three questions your clients ask most, and make sure one page answers each, plainly, near the top.
  4. Write 30 fixed questions and count citations in both tools once a month. Treat any one month's move of under about 20 points as noise.
  5. Do not build a separate strategy per tool until the counts show a gap that survives three months.

Less exciting than two strategies side by side. Also what the documentation supports, and it costs less to run than to argue about.

If you would like to know whether your robots.txt is quietly keeping you out of ChatGPT, or a forgotten snippet setting out of Google's AI answers, I run a free workshop and the first two weeks of work are on me. I will bring the 30 questions.

Sources

  1. 1.

    OpenAI, Introducing ChatGPT search, OpenAI, 31 October 2024, https://openai.com/index/introducing-chatgpt-search/

  2. 2.

    OpenAI, Overview of OpenAI crawlers, OpenAI developer documentation, https://developers.openai.com/api/docs/bots

  3. 3.

    Hema Budaraju, Google Search: Introducing AI Mode in the UK, Google, 28 July 2025, https://blog.google/around-the-globe/google-europe/united-kingdom/ai-mode-search-uk/

  4. 4.

    Elizabeth Reid, AI in Search: going beyond information to intelligence, Google, 20 May 2025, https://blog.google/products/search/google-search-ai-mode-update/

  5. 5.

    Google, AI features and your website, Google Search Central documentation, https://developers.google.com/search/docs/appearance/ai-features

  6. 6.

    Google, Grounding with Google Search, Gemini API documentation, https://aistudio.google.com/docs/google-search

  7. 7.

    Google, Google's common crawlers, Google Search Central documentation, https://developers.google.com/search/docs/crawling-indexing/google-common-crawlers

  8. 8.

    Ofcom, Online Nation 2025 report, Ofcom, 10 December 2025 (audience reach from Ipsos iris, May 2025; web visits from Similarweb, August 2025; AI summaries from YouGov, February 2025), https://www.ofcom.org.uk/siteassets/resources/documents/research-and-data/online-research/online-nation/2025/online-nations-report-2025.pdf?v=409837

  9. 9.

    Felix Simon, Rasmus Kleis Nielsen and Richard Fletcher, Generative AI and News Report 2026: from standalone tools to information infrastructure, Reuters Institute for the Study of Journalism, 29 October 2026, https://reutersinstitute.politics.ox.ac.uk/generative-ai-and-news-report-2026-standalone-tools-information-infrastructure

  10. 10.

    Jim Egan, Overview and key findings of the 2026 Digital News Report, Reuters Institute for the Study of Journalism, 16 June 2026, https://reutersinstitute.politics.ox.ac.uk/digital-news-report/2026/dnr-executive-summary