{"id":8321,"date":"2026-02-24T18:23:44","date_gmt":"2026-02-24T18:23:44","guid":{"rendered":"https:\/\/theseospot.com\/blog\/?p=8321"},"modified":"2026-02-24T18:28:52","modified_gmt":"2026-02-24T18:28:52","slug":"google-ai-overviews-are-stealing-website-traffic-and-i-have-the-late-proof","status":"publish","type":"post","link":"https:\/\/theseospot.com\/blog\/google-ai-overviews-are-stealing-website-traffic-and-i-have-the-late-proof\/","title":{"rendered":"Google AI Overviews Are Stealing Website Traffic \u2014 And I Have The Late Proof"},"content":{"rendered":"\n

My colleague published an article on TheSEOSpot back in May 2023 answering a simple question: are Twitter handles case sensitive<\/a>? Straightforward stuff. He wrote it, published it, and Google indexed it. The meta description reads: “No, Twitter handles are not case-sensitive. ‘@JohnDoe’ and ‘@johndoe’ are considered the same handle by Twitter.”<\/p>\n\n\n\n

What Google’s AI Overview Actually Did to Our Content<\/h2>\n\n\n\n

Fast forward to 2026. Google’s AI Overview now sits at the top of that exact search result, answering the question almost word for word. Our original content \u2014 the thing Google clearly trained on and pulled from \u2014 is sitting somewhere around position 9 or 10 on the page. Below the fold. Below the AI Overview. Below everything that matters.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Look at the AI Overview response. It says Twitter handles are not case sensitive, that @Username and @username are treated identically, that capitalization is just cosmetic. Key details about uniqueness and display behavior. All of it structured with bullet points and delivered with confidence at the top of the page.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Now look at our original meta description from 2023 that Google crawled and learned from. The overlap isn’t subtle. Google didn’t just happen to know this information floating around in its training data \u2014 it indexed our page, read our content, used our explanation to inform its AI-generated answer, and then pushed our actual page so far down the results that almost nobody will ever see it.<\/p>\n\n\n\n

Nobody scrolls that far down. And that’s exactly the problem.<\/p>\n\n\n\n

And this isn’t a one-off. Every publisher, every blogger, every small website owner creating informational content is watching this happen to their traffic in real time.<\/p>\n\n\n\n

The Data Confirms What We’re All Experiencing<\/h2>\n\n\n\n

When Google first rolled out AI Overviews to US users in May 2024, people hoped it would be limited. A test. Something that might affect a small slice of searches. That hope didn’t age well.<\/p>\n\n\n\n

Semrush tracked over 10 million keywords throughout 2025 and found AI Overviews went from appearing in roughly 6.5% of searches in January to peaking around 25% by July. They pulled back to about 16% by November, but the damage was already baked in. Some estimates from late 2025 put the number closer to 50-60% of US searches showing some form of AI summary, depending on who you ask and how they measure it.<\/p>\n\n\n\n

The traffic impact is not theoretical<\/a>. Pew Research Center \u2014 not some SEO blog with an agenda \u2014 tracked 68,000 real search queries and found that when AI summaries appeared, users clicked on results just 8% of the time. Without the summaries, that number was 15%. That’s a 47% drop in the likelihood of anyone clicking through to an actual website.<\/p>\n\n\n\n

Chartbeat data tracking over 2,500 news sites globally showed Google search referrals declining by 33% from November 2024 to November 2025. In the US specifically, the drop was 38%. Seer Interactive’s study across 42 organizations found organic CTR dropped 61% on queries where AI Overviews appeared. Some publishers reported numbers even worse. DMG Media, which runs MailOnline and Metro, saw click-through rates fall by close to 90% for certain searches. Chegg, the learning platform, reported a 49% decline in non-subscriber traffic and ended up filing an antitrust lawsuit.<\/p>\n\n\n\n

Business Insider lost 55% of its organic search traffic between April 2022 and April 2025. HuffPost’s search referrals got cut in half over the same period. These aren’t small niche sites. These are major publications with massive editorial teams, and they’re still getting crushed.<\/p>\n\n\n\n

It’s Not Just Google \u2014 GPT and Grok Are Doing the Same Thing<\/h2>\n\n\n\n

Here’s where it gets worse. At least Google’s AI Overview has the decency to show a few source links somewhere in the response \u2014 even if basically nobody clicks them (only 1% of searches with AI summaries result in someone clicking a link within the overview, according to Pew).<\/p>\n\n\n\n

ChatGPT doesn’t even bother with that courtesy for most queries.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

I asked ChatGPT the exact same question. Got a clean, confident answer: handles aren’t case sensitive, @username and @UserName and @USERNAME all point to the same account. Correct information. Our information, arguably \u2014 or at least information that sites like ours spent time writing, structuring, and publishing so it could be discovered through search. ChatGPT offers nothing in return. No link. No citation. No “this comes from…” nothing. Just the answer, served up like it was born knowing it.<\/p>\n\n\n\n

Grok’s fake attempts to cite sources, but the user experience makes actually visiting those sources almost impossible.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Grok’s approach is fascinating in how it technically gives credit while practically ensuring nobody follows through on it. You get the answer upfront. Sources are tucked behind a “Sources” button on the side. Click that, and you see a panel with search queries Grok ran \u2014 not even direct links to the cited pages. You’d need to click through at least two or three more times before you’d land on any publisher’s website. That’s not a citation. That’s a fig leaf.<\/p>\n\n\n\n

Also? Grok pulls from X posts, web content, whatever it can scrape \u2014 and the sourcing is even less transparent. Reports from 2025 confirmed xAI was ignoring robots.txt directives entirely<\/a>, crawling sites that explicitly told bots to stay out.<\/p>\n\n\n\n

The Core Problem Nobody Wants to Say Out Loud<\/h2>\n\n\n\n

Google trained on our content. Our meta description. Our article body. Our structured explanation. By our I am not representing my own website or a one blog post but over all publishers from the internet. theGoogle built a product feature that answers the question so completely at the top of the page that there’s zero reason for anyone to scroll down and visit the source.<\/p>\n\n\n\n

That’s the transaction publishers didn’t agree to. You write it. Google indexes it. Google learns from it. Google serves its own version of it. You get pushed to page irrelevance.<\/p>\n\n\n\n

\n