NotebookLM Fetcher (Google): User Agent & robots.txt Rules

Q: What is the official user-agent string for NotebookLM Fetcher?

The official user-agent string for NotebookLM Fetcher is: NotebookLM. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from NotebookLM Fetcher by performing a reverse-DNS lookup on the source IP.

Q: How do I block NotebookLM Fetcher in robots.txt?

Add the following lines to your /robots.txt file: User-agent: NotebookLM Disallow: / This instructs NotebookLM Fetcher not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).

Q: How do I verify if NotebookLM Fetcher is crawling my site?

Search your web server access logs for the string NotebookLM (case-insensitive: grep -i "NotebookLM" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Quick Facts

User-Agent:: NotebookLM
Category:: AI & LLM Bots
Operator:: Google
Safety:: Safe
Blocking Impact:: Low - No SEO ranking impact
SEO Impact Score:: 2/10
Official docs:: developers.google.com

What is NotebookLM Fetcher?

NotebookLM Fetcher is an on-demand AI fetcher operated by Google. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into Google's assistant.

NotebookLM Fetcher is an on-demand AI fetcher operated by Google. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into Google's assistant. NotebookLM Fetcher uses the user-agent token NotebookLM. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block NotebookLM Fetcher?

✅ **No SEO Impact** - Blocking NotebookLM Fetcher does not affect your rankings in Google, Bing, or any other search engine. NotebookLM Fetcher is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.

Generally safe to allow; provides legitimate crawling value.

How to block NotebookLM Fetcher with robots.txt

<code>User-agent: NotebookLM</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)

User-agent: NotebookLM
Disallow: /

Allow all (robots.txt)

User-agent: NotebookLM
Allow: /

Block private only (robots.txt)

User-agent: NotebookLM
Disallow: /private/
Disallow: /api/
Disallow: /admin/
Allow: /

Nginx server block

# Nginx: Hard-block NotebookLM Fetcher
if ($http_user_agent ~* "NotebookLM") {
    return 403 "Bot blocked";
}

Apache .htaccess

# Apache: Hard-block NotebookLM Fetcher
SetEnvIfNoCase User-Agent "NotebookLM" bad_bot
Order Allow,Deny
Allow from all
Deny from env=bad_bot

Meta robots tag

X-Robots-Tag header

X-Robots-Tag: noindex, nofollow

Is NotebookLM Fetcher safe to allow?

Yes, NotebookLM Fetcher is a **safe and legitimate** crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.

Verify by reverse-DNS lookup: legitimate NotebookLM Fetcher requests resolve to Google's domain.

What does NotebookLM Fetcher do?

Understanding NotebookLM Fetcher's purpose helps you decide whether to allow or block it.

Fetches a page only when a user asks an AI assistant to read it
Summarizes or extracts the URL the user provided
Triggered by real user intent, not bulk crawling
Low traffic volume compared with training crawlers
Blocking it prevents users from pulling your content into the assistant

Frequently Asked Questions

What is the official user-agent string for NotebookLM Fetcher?

The official user-agent string for NotebookLM Fetcher is: NotebookLM. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from NotebookLM Fetcher by performing a reverse-DNS lookup on the source IP.

Is NotebookLM Fetcher safe?

Yes, NotebookLM Fetcher is a **safe and legitimate** crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.

Will blocking NotebookLM Fetcher hurt my SEO?

✅ **No SEO Impact** - Blocking NotebookLM Fetcher does not affect your rankings in Google, Bing, or any other search engine. NotebookLM Fetcher is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.

How do I block NotebookLM Fetcher in robots.txt?

Add the following lines to your /robots.txt file:

User-agent: NotebookLM
Disallow: /

This instructs NotebookLM Fetcher not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).

Does NotebookLM Fetcher respect robots.txt?

NotebookLM Fetcher is operated by Google and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.

How do I verify if NotebookLM Fetcher is crawling my site?

Search your web server access logs for the string NotebookLM (case-insensitive: grep -i "NotebookLM" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).