{"id":63830,"date":"2026-07-18T06:32:13","date_gmt":"2026-07-18T10:32:13","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=63830"},"modified":"2026-07-18T06:32:13","modified_gmt":"2026-07-18T10:32:13","slug":"gemini-notebook-rebrand-ai-scraping","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/gemini-notebook-rebrand-ai-scraping\/","title":{"rendered":"Google Gemini Notebook Rebrand Exposes Sites to More AI Scraping"},"content":{"rendered":"

Google’s rebranding of NotebookLM to Gemini Notebook<\/a> has introduced a critical change for website owners and SEO professionals: a new user agent string that must be proactively blocked to prevent the AI-powered research tool from scraping site content without permission. The transition, effective immediately, leaves site operators a narrow window of only a few weeks to update their firewall rules and server configurations before the legacy user agent is permanently retired in August 2026.<\/p>\n

This is not a cosmetic name change. The shift from Google<\/a>-NotebookLM to Google-GeminiNotebook carries real operational consequences for anyone who has hardcoded the old user agent string into their robots.txt files, .htaccess configurations, or firewall rules. Google has explicitly stated that the old user agent will continue to function only until August 2026, after which it will stop working entirely. For site owners who rely on the former string to identify, monitor, or block traffic from Gemini Notebook, the clock is ticking.<\/p>\n

What Is Gemini Notebook and Why Does It Scrape Content?<\/h2>\n

Gemini Notebook, formerly known as NotebookLM, is a Google-hosted research assistant that allows users to upload documents, paste URLs, or use the Discover Sources<\/a> feature to automatically find and fetch web pages relevant to a query or topic. The tool is multimodal, meaning it can process YouTube videos, audio files, and uploaded documents, and it can generate AI summaries, audio podcasts, and video explainers from the content it ingests.<\/p>\n

The Discover Sources feature is particularly concerning for publishers. It automatically scrapes up to ten online articles for a given user-defined query, generates an AI summary of those sources, and produces no referral traffic back to the original sites. The audio and video overview features go a step further: they repurpose scraped content into entirely new formats that can, if published online, directly compete with the original material. All of these capabilities are intended functions of the product, not bugs or edge cases. Gemini Notebook is designed to automate the process of scraping unique online content and transforming it into something else, all without attribution to the original source.<\/p>\n

The User Agent Change: What Site Owners Need to Know<\/h2>\n

Google has updated its official documentation for user-triggered fetchers to reflect the rebrand. The old entry for Google NotebookLM has been completely removed and replaced with a new entry for Gemini Notebook. The new user agent strings are as follows:<\/p>\n

For mobile agents:
Mozilla\/5.0 (Linux; Android<\/a> 10; K) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/138.0.0.0 Mobile Safari\/537.36 (compatible; Google-GeminiNotebook; +https:\/\/developers.google.com\/crawling\/docs\/crawlers-fetchers\/google-gemininotebook)<\/p>\n

For desktop agents:
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)<\/p>\n

The former user agent, Google-NotebookLM, is listed as a “former agent” and will be supported only until August 2026. Google’s changelog explicitly advises users who have hardcoded the old value to update their code to avoid potential bugs.<\/p>\n

Why Robots.txt Won’t Protect You<\/h2>\n

A critical detail that every site owner must understand is that Gemini Notebook’s crawlers are classified as user-triggered fetchers. These fetchers are initiated by individual user actions, not by Google’s own crawling infrastructure, and as a result, they are not bound by robots.txt directives. Robots.txt is not a directive in the strict sense; it is a request. Most well-behaved crawlers honor it, but user-triggered fetchers operate under a different set of rules. Google’s documentation is clear on this point: user-triggered fetchers do not obey robots.txt.<\/p>\n

This means that even if you have a perfectly configured robots.txt file that disallows Gemini Notebook, it will have no effect. The only reliable methods for blocking these fetchers are server-level controls: firewall rules and .htaccess configurations.<\/p>\n

How to Block Gemini Notebook: A Working Example<\/h2>\n

Site owners who want to block the new Gemini Notebook fetcher can do so by adding a rule to their .htaccess file. The following example demonstrates how to block requests that contain the Google-GeminiNotebook user agent string:<\/p>\n

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} Google-GeminiNotebook [NC]
RewriteRule ^ – [F,L]<\/p>\n

This rule checks the User-Agent header of incoming requests and returns a 403 Forbidden status for any request that matches the Gemini Notebook string. The same logic can be applied in most firewall systems, including web application firewalls (WAFs), by creating a rule that blocks or rate-limits traffic from the specified user agent.<\/p>\n

Site owners who previously used the old Google-NotebookLM string in their firewall or .htaccess rules must update their configurations to include the new Google-GeminiNotebook string. The old string will continue to work for a limited time, but relying on it beyond August 2026 will leave sites exposed.<\/p>\n

The Retirement of Project Mariner<\/h2>\n

In a related development, Google has also retired Project Mariner, an experimental agent that navigated the web and performed actions on behalf of users. Project Mariner was shut down in May 2026, and Google’s documentation for user-triggered fetchers has been updated to remove any mention of it. The section that previously read “Associated products Google-Agent is used by agents hosted on Google infrastructure to navigate the web and perform actions upon user request (for example, Project Mariner)” has been stripped of the Project Mariner example. The rest of the documentation remains structurally identical.<\/p>\n

While Project Mariner’s retirement is a separate event, it underscores a broader trend: Google is consolidating its user-triggered fetching capabilities under fewer, more clearly defined agents. The rebrand of NotebookLM to Gemini Notebook is part of this consolidation, and site owners should expect further changes as Google continues to refine its AI product lineup.<\/p>\n

What the Documentation Change Actually Means<\/h2>\n

The old documentation for NotebookLM read as follows:<\/p>\n

“Google NotebookLM
User-Agent in HTTP requests Google-NotebookLM
Associated products The Google-NotebookLM fetcher requests individual URLs that NotebookLM users have provided as sources for their projects.”<\/p>\n

This entire section has been removed and replaced with the new Gemini Notebook documentation, which includes the new user agent strings and the note about the former agent being supported until August 2026. The changelog accompanying the update states: “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.”<\/p>\n

It is important to note that the rebrand represents no functional change to the product itself. Gemini Notebook is identical to NotebookLM in every respect except for its name and user agent. The same features, the same scraping behavior, and the same lack of robots.txt compliance all carry over. The only difference is the string that site owners must use to identify and block the tool.<\/p>\n

The Broader Implications for Publishers and SEOs<\/h2>\n

The Gemini Notebook rebrand arrives at a time when publishers are increasingly concerned about AI-driven content scraping and the erosion of referral traffic. The Discover Sources feature, which automates the discovery and scraping of up to ten sources per query, represents a direct threat to the traffic and visibility that publishers depend on. When a user triggers a Gemini Notebook research session, the tool fetches content from live web pages, generates an AI summary, and presents it to the user without any link back to the original source. The user never needs to visit the publisher’s site, and the publisher receives no attribution, no referral traffic, and no opportunity to monetize the visit.<\/p>\n

The audio and video overview features compound this problem. By converting scraped text content into podcast episodes or video explainers, Gemini Notebook creates derivative works that can be distributed and consumed independently of the original source. If those derivative works are published on platforms like YouTube or Spotify, they can rank in search results alongside or even above the original content, further displacing the publisher’s own traffic.<\/p>\n

For SEO professionals, the change introduces a practical workflow issue. Any reporting or analytics setup that relies on the Google-NotebookLM user agent string to identify traffic from the tool will break after August 2026 unless the string is updated to Google-GeminiNotebook. The same applies to server logs, bot detection systems, and any automated rules that filter or flag requests based on the user agent.<\/p>\n

How Site Owners Should Respond Before the August 2026 Deadline<\/h2>\n

The grace period provided by Google is generous but finite. Site owners who have not yet updated their configurations should take the following steps:<\/p>\n

First, audit all existing firewall rules, .htaccess files, and server configurations for any reference to the old Google-NotebookLM user agent string. Replace or supplement those references with the new Google-GeminiNotebook string. Second, update any monitoring or analytics scripts that parse user agent strings to identify traffic from the tool. Third, consider adding both the old and new strings to your blocking rules during the transition period to ensure continuous coverage. The old string will remain functional until August 2026, but relying on it exclusively after that date will leave your site unprotected.<\/p>\n

For site owners who are implementing blocking for the first time, the .htaccess example provided earlier is a straightforward starting point. For those using a web application firewall, create a custom rule that matches the Google-GeminiNotebook user agent and either blocks the request or returns a 403 status. It is also worth considering whether to block the older Google-NotebookLM string as a precautionary measure during the transition.<\/p>\n

It is also worth noting that user-triggered fetchers can change their IP ranges. Google publishes a JSON file containing the IP ranges used by user-triggered agents, and site owners who rely on IP-based blocking should monitor that file for updates. The user agent approach is generally more reliable for identifying Gemini Notebook traffic, but IP-based blocking can serve as a supplementary layer of defense.<\/p>\n

Finally, site owners should recognize that blocking user-triggered fetchers is a cat-and-mouse game<\/a>. Google may update the user agent string again in the future, or introduce new fetchers under different names. The Gemini Notebook rebrand is unlikely to be the last change of its kind. Staying informed about updates to Google’s crawling and fetching documentation is essential for maintaining effective controls.<\/p>\n

The rebrand of NotebookLM to Gemini Notebook is not a major product overhaul, but it is a significant operational event for anyone who manages a website. The name change brings a new user agent, a hard deadline for legacy support, and no change to the underlying scraping behavior that has concerned publishers since the tool first launched. Site owners who act before the August 2026 deadline will ensure that their blocking rules remain effective and that their content is not unknowingly fed into Google’s AI research assistant without permission or attribution.<\/p>\n","protected":false},"excerpt":{"rendered":"

Google’s rebranding of NotebookLM to Gemini Notebook has introduced a critical change for website owners and SEO professionals: a new user agent string that must be proactively blocked to prevent the AI-powered research tool from scraping site content without permission. The transition, effective immediately, leaves site operators a narrow window of only a few weeks […]<\/p>\n","protected":false},"author":7,"featured_media":83836,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/63830.png","fifu_image_alt":"Google Gemini Notebook Rebrand Exposes Sites to More AI Scraping","footnotes":""},"categories":[31],"tags":[],"class_list":["post-63830","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/63830.png","fifu_image_alt":"Google Gemini Notebook Rebrand Exposes Sites to More AI Scraping","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/63830","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=63830"}],"version-history":[{"count":0,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/63830\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/83836"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=63830"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=63830"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=63830"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}