What is Google-NotebookLM? AI crawler guide
Google-NotebookLM by Google: Superseded name for the Google fetcher that reads a URL when someone adds it as a source in Gemini or NotebookLM. Check its reported user-agent, robots.txt behavior, source, and verification guidance.
Superseded name for the Google fetcher that reads a URL when someone adds it as a source in Gemini or NotebookLM.
What is Google-NotebookLM?
Google-NotebookLM is a superseded name for a Google fetcher that reads a URL when someone adds it as a source in Gemini or NotebookLM. The fetcher is now documented as Google-GeminiNotebook. The old token was supported only until August 2026, and new rules should target Google-GeminiNotebook instead. A robots.txt rule that names only the old token may no longer match, so site owners relying on the old name may find their directives ineffective.
What it's for
If your site receives traffic from Gemini or NotebookLM when users add your URLs as sources, this fetcher may be responsible. Because the token has been renamed, continuing to block only the old name could allow the new fetcher to access content you intended to restrict, potentially affecting how your pages appear in those tools.
Google-NotebookLM access decides whether Google can fetch your pages. Whether those pages get used in generated answers is a separate question, so track your presence in Google's AI results rather than treating crawl volume as visibility.
How to handle Google-NotebookLM
Update your robots.txt to target the current token Google-GeminiNotebook. A rule that only mentions Google-NotebookLM may no longer be honored.
robots.txt rule
User-agent: Google-NotebookLM Disallow: /
Blocking cost
Blocking the current fetcher may prevent your content from being used as a source in Gemini or NotebookLM, which could reduce visibility in those AI-assisted tools.
Examples
- A user adds a URL from your site as a source in NotebookLM, and the fetcher retrieves the page content for processing.
- Someone includes your page as a reference in Gemini, triggering a fetch to incorporate the information.
- A robots.txt rule that only disallows Google-NotebookLM fails to block the renamed fetcher, allowing access you meant to prevent.
Related bots
- Google-GeminiNotebook: Another Google live fetcher to compare.
- Gemini-Deep-Research: Another Google live fetcher to compare.
- Google-Gemini-CLI: Another Google live fetcher to compare.
- Google-Agent: Another Google live fetcher to compare.
- MistralAI-User: Also tracked as a live fetcher.
- GoogleAgent-Mariner: Another Google live fetcher to compare.
- Claude-Code: Also tracked as a live fetcher.
- Claude-Web: Also tracked as a live fetcher.
- Amzn-User: Also tracked as a live fetcher.
- Gemini 2.0: Google-NotebookLM gives crawler context for Gemini 2.0.
- Google DeepMind: Google-NotebookLM connects this operator term to its crawler behavior.
Frequently Asked Questions
Is Google-NotebookLM still active?
No, it has been renamed to Google-GeminiNotebook. The old token was supported only until August 2026 and should no longer be used for new rules.
What happens if I only block Google-NotebookLM in robots.txt?
The rule may not match the current fetcher, so Google-GeminiNotebook could still access your content. You should update your robots.txt to target the new token.
Does blocking this fetcher affect my site's search ranking?
There is no direct impact on search ranking, but it may prevent your content from being used as a source in Gemini or NotebookLM, which could influence visibility in those tools.
How can I confirm the fetcher is accessing my site?
Check your server logs for requests with the user-agent token Google-GeminiNotebook. The old token Google-NotebookLM may still appear in older logs but is no longer in active use.
Data & Sources
- Google-NotebookLM source reference - Source used to verify Google-NotebookLM.