Live answer fetcher from Google
Google-GeminiNotebook (was Google-NotebookLM)
In short
Google-GeminiNotebook (was Google-NotebookLM) is Google's live answer fetcher. Google-GeminiNotebook has no robots.txt token, so robots.txt cannot address it and the crawl cannot measure a block rate. Check a visitor against the operator's published IP list. The former Google-NotebookLM agent string was supported until August 2026, per Google (page last updated 2026-08-19). Google-GeminiNotebook generally ignores robots.txt, per Google.
- Operator
- Purpose
- Live answer fetch All live answer fetch rows. Fetches a page because a person asked an assistant about it, one request at a time.
- User-agent string
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 token
- None. No robots.txt line can address this agent.
- Respects robots.txt
May not apply (user-triggered)
User-triggered fetcher: generally ignores robots.txt, per Google. Source, read 2026-11-04.
- Verification
Published IP list (JSON)
Match the source address of a request against the operator's published list. Documentation, read 2026-11-04.
- IP ranges
- developers.google.com/static/search/apis/ipranges/user-triggered-fetchers-google.json
- Rate behaviour
- Fetches individual URLs a user adds as sources.
- Block rate
-
None: the agent has no token, so a robots.txt block rate does not exist.
- Documentation
- developers.google.com, read 2026-11-04.
Note. The former Google-NotebookLM agent string was supported until August 2026, per Google (page last updated 2026-08-19).
Allow and refuse lines
This agent has no robots.txt token, so there are no lines to copy. Use the verification method above to decide at the WAF.
Refusing or allowing in robots.txt states a preference. For this row the operator or its documentation says robots.txt may not govern the fetch, so enforcement belongs in your WAF.
Google in the Verification Ledger
Five IP lists, reverse DNS for every class, and an experimental key directory for Google-Agent. Nothing for auto browse in the user's Chrome. All operators.
- IP lists
- developers.google.com/static/search/apis/ipranges/googlebot.json
- developers.google.com/static/search/apis/ipranges/special-crawlers.json
- developers.google.com/static/search/apis/ipranges/user-triggered-fetchers.json
- developers.google.com/static/search/apis/ipranges/user-triggered-fetchers-google.json
- developers.google.com/static/search/apis/ipranges/user-triggered-agents.json
- Reverse DNS
- crawl-*.googlebot.com, geo-crawl-*.geo.googlebot.com, rate-limited-proxy-*.google.com, *.gae.googleusercontent.com, google-proxy-*.google.com
- Key directory
- https://agent.bot.goog/.well-known/http-message-signatures-directory (Google-Agent, subset of requests, experimental)
- Cloudflare
- not checked
- Visa TAP registry
- no public operator-level registration found (checked 2026-11-04)
- Mastercard Agent Pay
- no public operator-level registration found (checked 2026-11-04)
In the news
Other Google rows
- Googlebot Search index
- Google-Extended (control token) Training
- Google-CloudVertexBot Other
- GoogleOther Other
- Storebot-Google Search index
- Google-Agent Task agent
- Gemini in Chrome (auto browse) Task agent
Sources
Last reviewed 2026-11-04