Google · Answers
Google-GeminiNotebook
The request is downstream of a click. Somebody opened a notebook, chose to add a source, and handed over your URL; Google then fetches that one address so the notebook has the document to work from. The vendor wording is that the fetcher requests individual URLs that Gemini Notebook users have provided as sources for their projects, *individual* being the load-bearing word, since there is no discovery step, no link-following and no return visit unless another person adds the same page. That is the line between this and a crawl: Googlebot and GoogleOther decide for themselves what to visit and when, whereas this token has no schedule and no queue of its own, and every hit in your log corresponds to one identifiable human act. It is also the string that replaced `Google-NotebookLM` in July 2026, so it is the one worth writing rules against now.
- Operated by
- Purpose
- Answers
- robots.txt token
- Google-GeminiNotebook
- Verification
- IP verified
Fetches a page in real time to answer a question someone just asked.
How to verify Google-GeminiNotebook
Google publishes the IP ranges Google-GeminiNotebook crawls from, and we fetch that list on a schedule. A request claiming to be Google-GeminiNotebook can therefore be checked against 2,163 published ranges: one that does not match is not this crawler.
Published ranges last confirmed by us on .
Google documents reverse-DNS verification: a genuine request resolves to a hostname under .gae.googleusercontent.com or .google.com that forward-resolves back to the same address.
User agent
Google publishes this user agent for Google-GeminiNotebook. Match on the Google-GeminiNotebook product token rather than the whole string: vendors revise the surrounding version and URL fragments without notice.
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36 (compatible; Google-GeminiNotebook; +https://developers.google.com/crawling/docs/crawlers-fetchers/google-gemininotebook)robots.txt for Google-GeminiNotebook
No. It inherits Google's class rule for user-triggered fetchers, which are documented as generally ignoring robots.txt on the grounds that a user asked for the fetch, so a disallow group under this token records an intention Google does not undertake to honour. A mobile variant of the string is published alongside the desktop one, so match on the `Google-GeminiNotebook` substring rather than the full agent.
Block
User-agent: Google-GeminiNotebook
Disallow: /Allow
User-agent: Google-GeminiNotebook
Allow: /robots.txt is a request, not an enforcement mechanism. It is honoured by convention, and a crawler that ignores it is stopped at your edge, not in a text file.
What blocking Google-GeminiNotebook costs you
Since the fetcher is documented as not bound by robots.txt, denying it in practice means a WAF or network-level rule, and the result is invisible to you and obvious to them: an import that fails inside a stranger's workspace. The person on the other end had already read enough to decide your page was worth keeping, and whatever they go on to produce from that notebook is assembled out of everyone's sources but yours: a compounding absence for reference material, standards, documentation and research write-ups, which are exactly the pages people file rather than skim. No ranking, Discover or AI Overviews exposure is involved, and there is no crawl load to recover: one added source is one fetch.