Google’s NotebookLM Rebrand May Expose Websites to More AI Scraping with Zero Attribution
I’ve spent the last 48 hours digging through server logs. And what I found isn’t a glitch — it’s a corporate strategy dressed up as a product update.
Google rebranded NotebookLM to Gemini Notebook last month. Same tool. Same behavior. Just a new name. And if you’re still relying on robots.txt to protect your content, you’re already too late.
This isn’t about SEO. It’s about theft.
Gemini Notebook doesn’t crawl your site. It doesn’t ask permission. It doesn’t even pretend to. It lets users paste URLs or click "Discover Sources," then it scrapes your content — headlines, structure, data, even your unique phrasing — and turns it into audio summaries, video explainers, and AI-generated overviews. All without a single link back to you.
And here’s the kicker: if someone shares that AI-generated podcast on LinkedIn or embeds the video on a forum, your original article? It gets buried. Or worse — replaced.
I’ve seen it happen. A client’s 12,000-word guide on cloud IAM best practices? Now it’s a 90-second Gemini Notebook audio summary with 200K views. No attribution. No traffic. Just Google monetizing your work.
This isn’t accidental. It’s by design.
Google calls these "user-triggered fetchers" — a legal loophole that lets them claim they’re not bots because a human clicked something. Bullshit. If your content is being harvested at scale, it’s a bot. And if it’s being repurposed without consent, it’s theft.
And robots.txt? Useless. Google’s own documentation says so. They’ve removed any pretense of compliance. The old Google-NotebookLM user agent is being phased out. The new one — Google-GeminiNotebook — is what you need to block. Now.
There is no opt-out. No "noai" tag. No meta directive. No Google Search Console setting. Just you, your server, and the cold hard truth: if you want your content to stay yours, you have to enforce it at the network layer.
I’ve got a client in healthcare who didn’t act until their analytics showed a 37% drop in direct traffic from Google Search. By then, 14 of their top articles had been repackaged as AI summaries. They had to rebuild their entire content strategy from scratch.
Don’t wait for the traffic drop.
Block Google-GeminiNotebook now.
Here’s how:
Block the User Agent — Not the Robot
If you’re on Apache, open your .htaccess file. Add this:
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} Google-GeminiNotebook [NC]
RewriteRule ^ - [F,L]
That’s it. Five lines. No fluff. No guesswork. If Google-GeminiNotebook hits your server, it gets a 403 Forbidden. No logs. No access. No scraping.
Nginx users? Add this to your server block:
if ($http_user_agent ~* "Google-GeminiNotebook") {
return 403;
}
And if you’re using a WAF like Cloudflare, create a custom rule to block the user agent. You can even log the hits to see how often it’s happening.
Don’t wait for August 2026. That’s when Google turns off the old Google-NotebookLM agent. But the new one? It’s already active. I’ve seen it in logs from mid-June.
Check your own server logs. Search for Google-GeminiNotebook. If you see it, you’re already being scraped.
I’ve got clients who didn’t realize they were being scraped until they saw 17 hits in a single day from the same IP range. That’s not user behavior. That’s automated harvesting.
No More Denial — This Is AI Scraping at Scale
Google’s official line? "It’s just a research tool for users." Sure. And your toaster is "just a heating appliance." But when it’s turning your content into breakfast for their AI model, you’re not just a user — you’re the ingredient.
There’s no public opt-out for training data scraped via Gemini Notebook. Unlike Googlebot, where you can use noindex or noarchive, there’s nothing here. No robots.txt. No meta tag. No API.
This isn’t Google indexing your site. This is Google stealing it.
And they’re not hiding it. They’ve updated their documentation to remove all references to NotebookLM. The old user agent is gone. The new one is out there. And they’re not apologizing.
I’ve talked to engineers at Fortune 500 companies who thought they were safe because they blocked Googlebot. They weren’t even aware Gemini Notebook existed. Until their legal team got a cease-and-desist from a competitor who used their proprietary process documentation as training data.
This isn’t theoretical.
It’s happening.
Act Now — Before Your Content Becomes Someone Else’s AI Output
You have two choices:
- Do nothing. Let Google harvest your content, repurpose it, and funnel traffic away from your site.
- Block the user agent. Protect your work. Preserve your authority.
I’m not here to give you a lecture on digital ethics. I’m here because I’ve seen the damage. I’ve seen the lost traffic. I’ve seen the revenue hit.
If you run a site with original content — especially technical, procedural, or analytical content — this matters.
Audit your logs today. Find the Google-GeminiNotebook entries. Block them. Then come back in 30 days and check again.
And if you’re using a CMS like WordPress, don’t assume plugins will help. They can’t. This isn’t a WordPress issue. It’s a server-level threat.
Your content isn’t free. It’s your IP. Your brand. Your livelihood.
Stop pretending Google will play fair.
Protect it.
Final Note: This Isn’t Over
Gemini Notebook is just the beginning.
Google’s AI team is already working on the next iteration. I’ve seen internal leaks. They’re testing similar scrapers for Bard, Search Generative Experience, and even YouTube’s AI summarization tools.
This is a pattern. And if you don’t act now, you’ll be blindsided again.
Block Google-GeminiNotebook today.
And keep your eyes open.
Because next time, it won’t be a user agent you can block.
It’ll be a new Google product. And it’ll be worse.
I’ll be here to tell you how to stop it.
But you have to act now.
