Google's AI Mode read our page before Google had indexed it.

18 October 2026 · About a 6 minute read

What happened

On the evening of 17 October we added kimidori.ai to Google Search Console and submitted the sitemap. URL Inspection, the tool that tells you what Google knows about a page, reported the homepage as URL is unknown to Google: never crawled, not in the index.

Later that evening, Google's AI Mode gave a summary of the same page. We could find nothing else on the web that describes the site, so the summary most likely came from the page itself. Google's AI had read a page that Google Search said it had never seen.

What Google says about AI Mode and the index

Google's guidance for site owners is clear about what it takes to appear in its AI features:

To be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed.Google Search Central, AI features and your website

Note the wording: that rule is about being shown as a supporting link. It does not say AI Mode can never read a page some other way. Google documents three other ways its systems read pages that are not in the index:

• User-triggered fetchers. Google publishes a list of tools that fetch a single page when a person asks them to, such as Google-Agent, Gemini Notebook and Read Aloud. Google says these fetchers generally ignore robots.txt rules, because a person asked for the page.
• URL context in the Gemini API. When a developer gives Gemini a link, it checks Google's cache first and, if the page is not there, automatically falls back to do a live fetch.
• Agentic browsing in AI Mode. Google says AI Mode uses the live web browsing capabilities of Project Mariner for tasks like booking a table. That is described for taking actions, not for ordinary answers.

What our logs showed

We went through our traffic records for kimidori.ai over the previous three days and listed every visit from a Google user agent. The records are sampled, so treat the counts as close rather than exact. Times are Sydney time on 17 October.

None of the fetchers on Google's published list appeared at all: no Google-Agent, no Gemini Notebook, no Read Aloud, no GoogleOther. The visitor that stands out is Google-Lens, three times in six minutes, before Googlebot had crawled the page properly.

The best-supported explanation

The question was typed straight into Google. Nobody was looking at the page in a browser and asking about it, which rules out the obvious route: Chrome's Ask Google about this page feature, which sends the page you are viewing to Google.

That leaves the Google-Lens visits. Three details stand out:

• They came from a server, not a browser. The visitor identified itself only as Google-Lens, with none of the browser details a person's Chrome sends.
• Each one asked for the bare address. Every visit first requested http://kimidori.ai/ and followed our redirect to the secure page, which is what happens when a system is handed a domain name rather than a link.
• They came first. Googlebot also fetched the homepage at 10:09 pm, two minutes after the first Google-Lens visit, but Search Console still reported the page as unknown and only called it indexed at 11:15 pm, after a full crawl.

So the likeliest sequence is this: AI Mode was asked about a site it had no record of, Google fetched the page on the spot using a fetcher that calls itself Google-Lens, and AI Mode answered from what it fetched. Google has not documented that behaviour anywhere we could find.

In one line: URL is unknown to Google describes the search index. It does not describe everything Google can read, or how fast it can read it.

What we could not confirm

• Google-Lens is not on Google's published list of fetchers, which Google says is not exhaustive, and nothing says when it runs. The link between those visits and the AI Mode answer rests on timing and pattern, not on Google's word.
• We do not know the exact minute AI Mode answered, so we cannot rule out that it drew on Googlebot's 10:09 pm visit instead.
• We could not verify that the requests came from Google's network. Anyone can send a user agent that says Google-Lens, although nothing else on the web pointed at this page yet.
• Our traffic data is sampled, so a single request from a rare visitor could be missing. Every Google visitor that came more than once is in the table.
• One published experiment from May 2025 found the opposite: AI Mode could not fetch a brand new page. Either Google has changed how AI Mode works since then, or something else was going on. We cannot tell which from one evening of logs.

What it means if you run a website

1. Being described by AI Mode is not proof you are indexed or ranking. Check URL Inspection in Search Console before you read anything into an AI answer.
2. A brand new page can be read the moment someone asks about it. Say only what is true on every page you publish, including the ones you have not promoted yet.
3. Robots.txt is not a privacy control. Google says its user-triggered fetchers generally ignore it. A page that must stay private needs a login, not a robots rule.
4. The index catches up quickly once Google has the sitemap. Ours went from unknown to indexed in about an hour.

How to test it yourself

1. Put up a new page on a fresh domain or subdomain, with no links pointing to it and no sitemap.
2. Confirm in Search Console that URL Inspection says it is unknown to Google.
3. In Google, switch to AI Mode and ask what the site is, typing the address.
4. Check your server or hosting logs for a Google-Lens visit in the minutes that follow, and note whether AI Mode describes the page.

If the visit appears and AI Mode describes the page, you have reproduced what we saw. We will run this test ourselves and update this note with the result.

Sources

• Google Search Central: AI features and your website
• Google Search Central: Google's user-triggered fetchers
• Gemini API: URL context
• Google: AI Mode gets more agentic
• Google Chrome Help: Search with Google Lens in Chrome (the route we ruled out)
• DEJAN: AI Mode is not live web (May 2025)

All sources read on 17 October 2026. Our own figures come from Google Search Console and our hosting logs for kimidori.ai.