Google-GeminiNotebook
Google · User fetch · robots.txt: No
Fetches the individual URLs that Gemini Notebook users add as sources for their projects.
Block Google-GeminiNotebook
User-agent: Google-GeminiNotebook
Disallow: /
Unconfirmed by the operator Google's documentation we checked does not say what blocking Google-GeminiNotebook changes beyond the crawler itself.
Allow Google-GeminiNotebook
User-agent: Google-GeminiNotebook
Allow: /
An allow group only changes anything if a broader rule would block Google-GeminiNotebook. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.
Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.
Already have a robots.txt? Paste it into the robots.txt checker to see whether it blocks Google-GeminiNotebook on a given path, and which line decides.
Facts
- Operator
- Purpose
- User-requested fetch
- Obeys robots.txt
- No. Google says its user-triggered fetchers generally ignore robots.txt, because a user requested the fetch. It replaces Google-NotebookLM, which Google lists as a former agent supported until August 2026.
- In your server logs
- The user-agent string contains "compatible; Google-GeminiNotebook;", in mobile and desktop variants.
- How to verify it
- Google publishes three IP lists for its user-triggered fetchers (user-triggered-fetchers.json, user-triggered-fetchers-google.json and user-triggered-agents.json) and a reverse DNS pattern, but does not say which list this fetcher uses; run the reverse and forward DNS check Google describes.
What Google says
Quoted word for word from the operator's documentation.
“The Gemini Notebook fetcher requests individual URLs that Gemini Notebook users have provided as sources for their projects.”
“Because the fetch was requested by a user, these fetchers generally ignore robots.txt rules.”
“Former agent (supported until August 2026) Google-NotebookLM”
“(compatible; Google-GeminiNotebook;”
“The IP ranges the user-triggered fetchers use are published in the user-triggered-fetchers.json, user-triggered-fetchers-google.json, and user-triggered-agents.json objects.”
“Verify that it's the same as the original accessing IP address from your logs.”
Sources
- Google: List of Google's user-triggered fetchers — fetched and checked 2026-09-24
- Google: Verify requests from Google — fetched and checked 2026-09-24