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.
Block or allow it at the server
robots.txt asks; a server rule refuses. Every rule here matches Google-GeminiNotebook, spelled as in the User-Agent Google documents (“compatible; Google-GeminiNotebook;”), and matches it case-sensitively. The server answers 403.
What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user.
(Apache HTTP Server 2.4 documentation). A fake Google-GeminiNotebook is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Google's published addresses.
No “only the real one” rule: Google publishes no IP list file this site holds for Google-GeminiNotebook. Google does not say which of its three user-triggered fetcher lists this fetcher uses.
The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.
Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.
Who blocks it
Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 0 block Google-GeminiNotebook from the whole site by name, 38 block it through their User-agent: * group, and 1 name it with partial rules (some paths closed, the home page open). 0 more name it only to let it in.
0
block it by name 0.0%
38
block it through * 7.5%
1
name it, partial rules 0.2%
Percentages are of the 508 files we could read, not of all 1,000 sites.
None of the 508 files names Google-GeminiNotebook in a group that blocks the whole site.
robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.
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