What Google-NotebookLM does
Google-NotebookLM is the legacy user agent token for the Gemini Notebook fetcher, which requests individual URLs that Gemini Notebook (formerly NotebookLM) users have provided as sources for their projects. Current requests identify as Google-GeminiNotebook in the user agent string, with the legacy Google-NotebookLM token supported until August 2026. Because each fetch is requested by a user, Google states these fetchers generally ignore robots.txt rules.
How to control Google-NotebookLM
Target Google-NotebookLM in your robots.txt with the Google-NotebookLM token. Rules apply per bot, so you can allow this one while blocking others, or the reverse.
Allow Google-NotebookLM
User-agent: Google-NotebookLM
Allow: /Block Google-NotebookLM
User-agent: Google-NotebookLM
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.
How to identify Google-NotebookLM
Temso identifies Google-NotebookLMtraffic by matching the request's User-Agent header against this pattern. User-agent strings can be spoofed, so treat a match as an indication, not proof.
Google-NotebookLMGoogle-NotebookLM FAQ
What is Google-NotebookLM?
Google-NotebookLM is the legacy user agent token for the Gemini Notebook fetcher, which retrieves individual URLs that users have added as sources to their Gemini Notebook (formerly NotebookLM) projects. Current requests identify as Google-GeminiNotebook, with the legacy token supported until August 2026.
How do I block Google-NotebookLM?
You can add a robots.txt group with User-agent: Google-NotebookLM (or the current Google-GeminiNotebook token) 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.
