The email came in on a Tuesday. A content site owner, runs a personal finance blog based in Texas, had implemented the nosnippet directive across his top fifty pages after reading that major publishers were moving to block Google's AI Overviews. He wanted to know why his organic traffic hadn't recovered. Six weeks in. The crawl report was clean. The rankings hadn't moved. The AI Overview for his main keywords was still there, just pulling from somewhere else now.
Nobody told him that part.
The framing around this publisher blockade story is almost entirely wrong, and I want to be precise about how. The coverage presents it as a standoff: publishers asserting control, Google being forced to comply, traffic flowing back to sources that opt out. That is not what is happening. What is happening is that Google is doing exactly what it was built to do when a source becomes unavailable: it finds another one. The answer still appears. The click still doesn't come. The only thing that changed is who got scraped.
I have been watching this play out across a few client categories now and the pattern is consistent. When a publisher blocks their content from appearing in AI Overviews, Google does not respond by sending the user to that publisher's website. Google responds by sourcing the same information from a publisher who did not block. The user gets their answer. The blocking publisher gets their content protected and loses the visibility they had, however thin that visibility was translating to traffic. The non-blocking publisher gets the citation and, depending on the query type, sometimes gets a click and sometimes doesn't. The user got what they needed without visiting anyone.
Image credit: Screenshot from "How to RANK in Google’s AI Overviews (Complete 2026 SEO Guide)" by Surfer Academy on YouTube (https://www.youtube.com/watch?v=rtrLA42XRog).
Here is what the conventional wisdom gets wrong on this: most SEOs are watching the publisher blockade and thinking about what it means for big media. Forget big media for a minute. Think about what it means for the content that fills the vacuum.
When a large authoritative source opts out of AI Overviews for a given topic category, Google's retrieval model has to go somewhere. That somewhere is usually the next most structured, topically coherent source it can find. For a certain class of queries, that is now mid-tier content sites, niche expertise blogs, and very occasionally, a well-structured small business website that has been doing the patient work of entity optimization and semantic markup while everyone else was arguing about word count.
I ran an experiment with a home services client in the midwest. We had built out structured FAQ schema on their service pages, dense internal linking between related service categories, clean entity associations in the page copy. Nothing gray hat, nothing clever. Just the unglamorous infrastructure work. After a mid-sized HVAC information publisher in the same region implemented a broad nosnippet rollout, that client started appearing in AI Overview citations for two queries they had never appeared in before. The traffic from those citations was not transformative. But the brand impression data in Search Console shifted, and thirty days later, two of those queries started producing clicks they had never produced.
That is not the outcome I would have predicted. The conventional advice was to focus on getting your own featured snippet and treat AI Overviews as a separate problem. What actually moved was the structural work we had done six months earlier becoming relevant because the field changed around it.
What I tell publishers and content site owners now is this: blocking Google AI Overviews is a defensible business decision if you are protecting genuinely proprietary content or if the citation without the click is actively cannibalizing your subscription conversion. Those are real situations. But blocking because you expect traffic to return is a misreading of how the system works. Google is not going to redirect users to you because you opted out. It is going to route around you. The user still gets their answer. The only variable is whose content gets used to generate it.
The third of publishers moving to block are making a copyright argument and a revenue argument, both of which are legitimate. But they are not making a traffic argument, because the traffic argument doesn't hold. The click was already not coming. What the block does is remove any chance that your brand gets associated with the answer, on the slim possibility that the association was worth anything.
For small businesses watching this and wondering where they fit: the vacuum is real, the window is open right now, and the sites filling it are not the ones with the biggest domain authority scores. They are the ones Google can read cleanly.
Waleed Qamar holds a BSc in Computer Science from Purdue University and has spent the years since turning that technical foundation into something the curriculum never covered: figuring out why websites rank, why they fall, and why most businesses never find out until it is too late.
Pakistan-born and based between the United States and South Asia, he has managed search visibility for e-commerce stores, local service businesses, and SaaS startups across two continents. He started in SEO when guest posting still worked, survived the Penguin update, and has rebuilt client sites from scratch after algorithm hits more than once.
He has watched good businesses get sold packages that looked like progress and delivered nothing lasting. He has also seen the right approach quietly double a site’s traffic without a single press release about it.
His writing on SEO By Highsoftware99 covers Google algorithm updates, autocomplete optimization, semantic SEO structure, and the widening gap between what agencies promise and what Google actually rewards in 2026.
He knows what a traffic cliff looks like in Search Console on the morning you discover it.
