Overview
Google-NotebookLM is the former user-triggered source-fetcher identity used before Google-GeminiNotebook.
The historical token is Google-NotebookLM. Google documented transition support through August 2026; as of September 2026 this record is retained as a legacy identity for historical log matching.
Use Google-GeminiNotebook for the current fetcher identity.
As with any user-agent string, treat the token as an identity claim and corroborate it with stronger operator-controlled evidence when authentication matters.
Identity
- User-Agent Pattern
-
Google-NotebookLM - Aliases
- NotebookLM; NotebookLM source fetcher
- HTTP Agent Examples
-
Google-NotebookLM - Robots Token
- Google-NotebookLM
- Identity Type
- Officially documented
- Evidence Method
- Verify Google-NotebookLM by matching `Google-NotebookLM` to Google evidence, then corroborating the request with source-network ownership, reverse DNS, signed request data, or current operator documentation.
Classification
- Type
- AI
- Kind
- Fetcher
- Family
- Purpose
- AI assistant
Behavior and handling
- Common Use
- fetching source URLs supplied by NotebookLM users during the transition to Gemini Notebook
- Detection Notes
- Google-NotebookLM traffic is primarily detected by `Google-NotebookLM`; related patterns include `NotebookLM; NotebookLM source fetcher`; a representative HTTP user-agent is `Google-NotebookLM`. Treat these values as identification claims and corroborate them with source-network ownership, reverse DNS, signed request data, or current operator documentation.
- Respects robots.txt
- No
- Spoofing Risk
- Google-NotebookLM can be spoofed if identification relies only on a user-agent string; corroborate the request with stronger operator-controlled evidence when available.
- Risk
- Neutral
- Recommended Handling
- Monitor
Rules and controls
- Robots.txt Snippet
-
# Legacy or noncanonical identity. Confirm the current canonical token before relying on robots.txt.
Relationships
- Operator
- Google Checked 2026-09-02
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.