Google's NotebookLM Rebrand to Gemini Notebook Puts Websites at Risk of Increased AI Scraping

Google's rebranding of NotebookLM to Gemini Notebook is more than a name change — it creates an urgent deadline for website owners to update their blocking rules or risk uncontrolled AI scraping of their content.

The shift matters because Gemini Notebook's crawlers do not obey robots.txt and can scrape website content without permission or attribution. Site owners who have hardcoded the old user agent string face a shrinking window to act before the legacy Google-NotebookLM user agent stops functioning in August 2026.

What the Rebrand Actually Means for Your Website

NotebookLM is now called Gemini Notebook. According to Google's updated documentation, the product itself has not changed — it works exactly the same way it always has. Gemini Notebook is a multimodal AI research assistant that allows users to upload documents and use them as source material for research, learning, and content generation.

The rebrand carries a practical consequence buried in the technical details. Google has retired the old user agent string — Google-NotebookLM — and replaced it with a new one: Google-GeminiNotebook. Any firewall rule or .htaccess file built around the old string will stop working when Google ends support for the legacy agent in August 2026.

Google's changelog is direct on this point: "If you hardcoded the old value in your code, update the string to avoid potential bugs. We will continue to support the old value to allow for a smooth transition."

The new desktop user agent string reads: Mozilla/5.0 (X1; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36 (compatible; Google-GeminiNotebook). A separate mobile agent string has also been issued. Site owners have a matter of weeks — not months — to update their configurations.

What Has and Hasn't Changed

It is worth being precise about what the rebrand does and does not affect. The underlying functionality of the tool remains identical. Gemini Notebook still operates as a research assistant, still uses the Discover Sources feature, and still processes scraped content to generate summaries, audio, and video outputs. The only change of immediate practical consequence is the user agent string — but that single technical detail carries significant implications for anyone who has built blocking rules around the old identifier.

For site owners who have never implemented any blocking, the rebrand is a timely reminder that this exposure has existed since NotebookLM launched and continues to grow as the tool's user base expands.

Why Gemini Notebook's Scraping Features Concern Publishers

The core issue for publishers and content creators is how Gemini Notebook interacts with their content. The tool's Discover Sources feature automatically finds and scrapes up to ten online sources in response to a user's research query. It then generates an AI summary of that content. No referrals or attribution are sent back to the original source.

This creates a measurable risk for content publishers. A website's original reporting or analysis can be consumed, summarized, and repurposed — all without a single visit being recorded or credited. The practical effect is comparable to someone reproducing your published work in its entirety and distributing it to others without ever directing an audience back to you.

The concern deepens when Gemini Notebook's audio and video features enter the picture. The tool can convert scraped web content into an audio podcast episode or a video explainer. If that output is then published online, it can directly compete with the original source material — using that source's own ideas and research against it.

Roger Montti, writing for Search Engine Journal, described the situation plainly: "It automates the process of scraping and creating something else from unique online content without attribution to the original source."

Critically, Gemini Notebook's crawlers are classified as user-triggered fetchers. Because a human user initiates the fetch rather than an automated crawl, Google does not require these fetchers to obey robots.txt. This distinction strips away one of the most common tools website owners rely on to manage crawler access. Understanding the wider risks and challenges artificial intelligence presents to businesses helps frame why this specific issue deserves serious operational attention rather than being dismissed as a minor technical inconvenience.

The Business Impact on Publishers

The economic stakes here are real. Publishers who depend on organic traffic for advertising revenue or lead generation face a quiet erosion of value when AI tools consume their content without generating visits. Consider the compounding effect: a single well-researched article can be scraped by multiple users across multiple sessions, with each instance producing zero referral traffic and zero revenue attribution.

As generative AI tools become more capable and more widely used, the volume of user-triggered fetching is likely to grow — making this a structural challenge rather than a one-time technical fix. The question for publishers is not simply whether to block Gemini Notebook today, but how to build content access policies that remain effective as the AI scraping landscape continues to evolve.

Data privacy intersects with this issue in ways that are easy to overlook. When proprietary research, commissioned data, or commercially sensitive analysis is scraped and repurposed, the exposure extends beyond lost traffic. Publishers handling sensitive subject matter should review the key big data privacy issues businesses must consider when evaluating the full scope of their risk exposure from user-triggered AI fetching.

How Site Owners Can Block Gemini Notebook Right Now

Robots.txt is not a directive in this context — it is a request that Gemini Notebook has no obligation to follow. The only reliable options for blocking the fetcher are a firewall rule or an .htaccess configuration targeting the new user agent string.

Implementing the .htaccess Block

Roger Montti provided a working example of an .htaccess rule that blocks the Google-GeminiNotebook fetcher:

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} Google-GeminiNotebook [NC]
RewriteRule ^ - [F,L]

This rule intercepts any request carrying the Google-GeminiNotebook user agent string and returns a 403 Forbidden response before the content is served. It is a server-level control, which means it operates independently of any CMS-level settings or robots.txt directives. Site owners who currently block or track the old Google-NotebookLM user agent must replace that string with Google-GeminiNotebook before August 2026. Failure to do so means the blocking rule will no longer function and Gemini Notebook will be able to scrape the site unimpeded.

Firewall-Level Controls

For sites running a web application firewall — whether through Cloudflare, Sucuri, or a hosting provider's built-in solution — a user agent block can be applied at the network edge before the request reaches the origin server. This approach offers a performance advantage over .htaccess rules and provides centralised management if you are protecting multiple domains. Site owners should treat firewall-level controls as the primary defence, with .htaccess rules serving as a secondary fallback.

Broader website security best practices recommend layering server-level and network-level controls precisely for situations like this — where a single rule set may be insufficient or where legacy configurations need to be maintained in parallel during a transition period.

Additional Documentation Changes

Two additional documentation changes accompanied the rebrand. Google removed all mentions of Project Mariner from its user-triggered fetchers page, reflecting that tool's retirement in May 2026. The old Google-NotebookLM documentation block has been fully replaced with new Gemini Notebook-specific entries covering both mobile and desktop agents. Site owners maintaining detailed crawler logs should update any monitoring rules that reference Project Mariner at the same time they update their NotebookLM blocking configurations.

Acting Before the Deadline

Site owners should treat the August 2026 deadline as a hard cutoff and audit their blocking rules immediately. Those who have not yet implemented any blocking should consider whether Gemini Notebook's scraping activity aligns with their content distribution strategy — and act accordingly before the grace period closes.

The steps to prioritise are straightforward:

• Update any existing .htaccess or firewall rules that reference Google-NotebookLM to use the new Google-GeminiNotebook string before August 2026
• Audit your site's current robots.txt strategy, recognise its limitations against user-triggered fetchers, and invest in firewall-level controls instead
• Monitor your site's referral traffic for signs of AI scraping by comparing content consumption patterns against actual visitor data to quantify the business impact
• Review Google's user-triggered fetchers documentation directly to stay current with any further agent string changes as Google's AI product line continues to evolve