Google-NotebookLM
Run by Google
How to detect Google-NotebookLM
Google-NotebookLM names itself in its user agent, but anyone can copy a user agent, so it is detected by confirming the user agent against other signals: source IP confirmed as the operator's own network; and how the session clicks, types, moves and navigates matches an automated agent.
- Detection method
- Self-declaredThe agent names itself in its user agent, and Verisoul confirms it with network, device or behavioral data. A user agent alone is never enough.
- Signals that identify it
- NetworkSource IP confirmed as the operator's own network
- DeviceDevice profile of Google's page-rendering browser
- BehavioralHow the session clicks, types, moves and navigates matches an automated agent
Every signal Verisoul checks for Google-NotebookLM
Google-NotebookLM names itself in its user agent. Anyone can copy that, so we only label a session Google-NotebookLM when the other signals check out too.
- Not used
Cryptographic
Not needed to identify it
- Used
Network
Source IP confirmed as the operator's own network
- Used
Device
Device profile of Google's page-rendering browser
- Used
Behavioral
How the session clicks, types, moves and navigates matches an automated agent
How often you'll see it
Uncommon
Seen on some sites, in small volumes
More from Google
- GooglebotGoogle's main crawler for Google Search.Self-declaredHow common: Very common
- AdsBot-GoogleChecks the quality of ad landing pages for Google Ads.Self-declaredHow common: Common
- AdsBot-Google-MobileChecks the quality of mobile ad landing pages for Google Ads.Self-declaredHow common: Common
- Googlebot-ImageCrawls images for Google Images and Google Search.Self-declaredHow common: Common
- GoogleOtherGoogle's general-purpose crawler for product teams' one-off crawls.Self-declaredHow common: Common
- Mediapartners-GoogleReads pages on AdSense sites so Google can show relevant ads.Self-declaredHow common: Common
Questions about Google-NotebookLM
How do you detect Google-NotebookLM?
Google-NotebookLM names itself in its user agent, but anyone can copy a user agent, so it is detected by confirming the user agent against other signals: source IP confirmed as the operator's own network; and how the session clicks, types, moves and navigates matches an automated agent.
What is Google-NotebookLM?
Google-NotebookLM is Fetches the pages a person adds as sources in NotebookLM.
Does Google-NotebookLM identify itself?
Partly. Google-NotebookLM names itself in its user agent, but user agents are easy to copy, so the name alone is not proof.
Can a bot pretend to be Google-NotebookLM?
A bot can copy Google-NotebookLM's user agent or markers, but the network, device and behavior signals will not match, so it is not labeled Google-NotebookLM.
How common is Google-NotebookLM?
Uncommon. Seen on some sites, in small volumes.
What does the Verisoul API return for Google-NotebookLM?
Every session Verisoul identifies as Google-NotebookLM carries an agent block with id "google_notebooklm", name, provider, type "ai_assistant", detection_method "self_declared" and the detection_signals used (network, behavioral). Build rules on the id, type and detection method.