What Google-GeminiNotebook does
Google-GeminiNotebook is the user agent for the Gemini Notebook fetcher, which requests individual URLs that Gemini Notebook users have provided as sources for their projects. Google renamed NotebookLM to Gemini Notebook and moved the fetcher from the Google-NotebookLM token to Google-GeminiNotebook; Google listed the old token as supported until August 2026, so anything still matching only on Google-NotebookLM will now miss this traffic. Because each fetch is requested by a user, Google states these fetchers generally ignore robots.txt rules.
How to control Google-GeminiNotebook
Target Google-GeminiNotebook in your robots.txt with the Google-GeminiNotebook token. Rules apply per bot, so you can allow this one while blocking others, or the reverse.
Allow Google-GeminiNotebook
User-agent: Google-GeminiNotebook
Allow: /Block Google-GeminiNotebook
User-agent: Google-GeminiNotebook
Disallow: /Because fetches are user-requested the fetcher generally ignores robots.txt, and requests can be verified against the IP ranges Google publishes in its user-triggered-fetchers.json and user-triggered-fetchers-google.json files or via reverse DNS matching the gae.googleusercontent.com or google-proxy-*.google.com patterns.
User-agent string
As published by Google. Remember that user-agent strings can be spoofed, so verify suspicious traffic against the operator's published IP ranges.
Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36 (compatible; Google-GeminiNotebook; +https://developers.google.com/crawling/docs/crawlers-fetchers/google-gemininotebook)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)Google-GeminiNotebook FAQ
What is Google-GeminiNotebook?
Google-GeminiNotebook is the user agent for the Gemini Notebook fetcher, which retrieves individual URLs that users have added as sources to their Gemini Notebook projects. Because the fetch is requested by a user rather than scheduled by a crawler, Google states these fetchers generally ignore robots.txt.
What happened to Google-NotebookLM?
Google renamed NotebookLM to Gemini Notebook and changed the fetcher's user agent token from Google-NotebookLM to Google-GeminiNotebook. Google's documentation lists Google-NotebookLM as the former agent, supported until August 2026. If your robots.txt, log filters, or bot analytics still match only on Google-NotebookLM, they will no longer see this traffic.
How do I block Google-GeminiNotebook?
You can add a robots.txt group with User-agent: Google-GeminiNotebook followed by Disallow: /, but Google's documentation states that because each fetch is requested by a user, these fetchers generally ignore robots.txt rules. Server-side blocking would need to rely on the IP ranges Google publishes in its user-triggered-fetchers.json files or on reverse DNS verification.
About AI Assistant Fetchers
Agents that fetch a page in real time because a user asked an AI assistant about it. They don't build an index; each visit maps to a live conversation.
Blocking these removes your pages from live AI answers at the exact moment a user is asking about you or your category.