Google-GeminiNotebook fetches URLs that Gemini Notebook users add as project sources. Google lists it with user-triggered fetchers. Aiola Analytics can store those hits when your server or edge reports them.
The NotebookLM token was renamed
Google's July 16, 2026 changelog changed the NotebookLM user agent to Google-GeminiNotebook. The same note says NotebookLM became Gemini Notebook.
The July note said Google would keep supporting the old value during the transition. The fetcher listing calls Google-NotebookLM a former agent, supported until August 2026.
If you hardcoded Google-NotebookLM, Google says to update that string. Match Google-GeminiNotebook, not the search spelling google-geminibotnotebook. That extra word is not in Google's token.
Published headers fetch one source URL
Google documents a mobile header and a desktop header. Both contain Google-GeminiNotebook. The fetcher requests individual URLs supplied as project sources.
The desktop example on that page is:
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)
The mobile example uses Chrome/138 and the same token. Match that token inside the full header. The current examples are browser-like user agents. The former token is the short string Google-NotebookLM.
These four Google names do different work
Common crawler documentation defines Googlebot, GoogleOther, and Google-Extended. The fetcher page defines Google-GeminiNotebook. Those pages say their lists are not exhaustive.
| Identity | Documented role | Keep this separate |
|---|---|---|
| Google-GeminiNotebook | Fetches URLs a Gemini Notebook user supplied as sources | User-requested source fetch |
| Googlebot | Crawls pages for Google Search indexing | Search indexing |
| Google-Extended | robots.txt control for Gemini training and grounding | No separate HTTP user agent |
| GoogleOther | Generic crawler product teams may use, including internal research | Not tied to one product |
Crawling preferences for Googlebot affect Google Search, including Discover, Images, Video, and News.
Google-Extended has no HTTP user agent of its own. Google crawls with existing user agents. Publishers use the token to manage future Gemini training and grounding. It does not change Search inclusion or ranking.
GoogleOther may fetch public pages for product teams. One example Google gives is a one-off crawl for internal research. Preferences for GoogleOther do not target a named product.
See the token and source-fetch note on Aiola's Google-GeminiNotebook reference.
Robots.txt generally does not stop this fetch
User-triggered fetchers generally ignore robots.txt, because a person requested the fetch. That is the fetcher page's rule. Common crawlers always obey robots.txt when crawling automatically.
A disallow for Google-GeminiNotebook does not guarantee that these source requests stop. Compare the rule you published with the requests your logs still show.
Google-Extended is a different control. It manages training and grounding for content Google already crawls. It is not a request user agent for this fetcher. A Google-Extended line does not replace the user-triggered rule above.
Confirm the address before you trust the name
Google warns that a user-agent string can be spoofed. Its verification guide gives a manual check and a range check.
Use the source IP from your server or edge log.
- Run a reverse DNS lookup on that IP.
- Confirm the domain is
googlebot.com,google.com, orgoogleusercontent.com. - Run a forward lookup on the hostname from step 1.
- Require that lookup to return the original IP.
User-triggered fetchers share published ranges. Google names user-triggered-fetchers.json, user-triggered-fetchers-google.json, and user-triggered-agents.json. Reverse DNS masks on that page use gae.googleusercontent.com or a google-proxy name on google.com.
The Gemini Notebook section does not name a range file of its own. A match on a shared list shows a published user-triggered address. It does not name this fetcher by itself.
Aiola's crawler record for Google-GeminiNotebook has no dedicated IP range. Do the address check in your logs.
Aiola lists both tokens in Answers
The AI crawler reference lists Google-GeminiNotebook, formerly Google-NotebookLM, in Answers. Analytics shows these user-requested fetches.
The AI view shows crawl totals, bots, pages, and activity over time. It groups hits into Answers, Indexing, Training, and Other. AI-answer referrals, crawler 404s, and discovery-file health also appear there.
Crawlers do not run JavaScript, so the browser tag cannot see them. One server or edge snippet from the setup guide posts each matching hit. Only known crawler user agents are stored.
A recorded crawl is not proof that the vendor cited the page. An empty period is not proof that the vendor cannot reach the site.
Try it in Aiola
Download Aiola free for macOS 12 or later and Windows 10 or later. Hosted Analytics needs Pro or the 7-day trial, and the pricing page lists both. Open the AI view and review Google-GeminiNotebook in Answers.
