What Changed and Why It Matters
Google rebranded NotebookLM to Gemini Notebook and updated its user agent from Google-NotebookLM to Google-GeminiNotebook. The old user agent will stop working in August 2026. If your site uses the old agent to block or track this scraper, you have a few weeks to update your firewall or .htaccess file.
This matters because Gemini Notebook's user-triggered fetchers do not obey robots.txt. They scrape up to ten sources per query, generate AI summaries, and produce no referral traffic. The tool can also turn your content into audio podcasts or video explainers that compete directly with your original material.
Strategic Consequences for Your Business
Loss of Control Over Content Access
User-triggered fetchers ignore robots.txt by design. That means your standard blocking method won't work. The only way to stop Gemini Notebook from scraping your site is through firewall rules or .htaccess directives. If you don't update your user agent string before August 2026, your existing blocks will fail, and the scraper will access your content freely.
Increased Competition from AI-Generated Content
Gemini Notebook's audio and video overview features repurpose your content into new formats. If users share those outputs online, they can rank in search results or appear on social media, drawing attention away from your original site. This is a direct competitive threat, especially for publishers, educators, and content-driven businesses.
Bandwidth and Server Load
Even if you don't mind AI scraping, the fetcher's activity consumes server resources. For small sites on shared hosting, a sudden spike in requests can slow performance or trigger overage charges. Blocking the fetcher can prevent these issues.
What This Means for Your Business
If you run a website that publishes original content, you should update your user agent blocking rules now. The grace period is short—August 2026 is just weeks away. Businesses that rely on referral traffic or exclusive content face the highest risk. Sites that don't mind AI scraping can ignore this change, but they should monitor bandwidth usage.
Your Move: Update your firewall or .htaccess file to block the new user agent Google-GeminiNotebook before August 2026. Use the example rule provided in the source: RewriteCond %{HTTP_USER_AGENT} Google-GeminiNotebook [NC] followed by RewriteRule ^ - [F,L].
FAQ
User-triggered fetchers like Gemini Notebook's scraper do not obey robots.txt. They are initiated by users, not by Google's crawlers, so robots.txt directives don't apply. You must use firewall or .htaccess rules instead.
Your existing block using the old user agent (Google-NotebookLM) will stop working. Gemini Notebook's scraper will then be able to access your site freely, scrape content, and generate AI summaries without attribution.
