Does Google's AI Overviews Actually Hurt a Small Newsroom's Traffic?
Less than the panic suggests, for most of
Ahrefs analyzed 146 million search results to see where AI Overviews actually show up. Local-intent searches, the "near me" and business-lookup kind of query, trigger an AI Overview only 7.9% of the time. That's well below the 20.5% average across all search categories. If most of your traffic comes from that kind of query, AI Overviews show up on it less often than on the average search.
Which of
your stories actually get answered
directly
Ahrefs also found that AI Overviews trigger far more often on broad informational questions than on narrow local lookups. Weather. School closings. Election results. Sports scores. Road closures. These are single-fact queries , and Google now answers most of them directly at the top of the page.
If a reader searches "is school closed today in [your town]" and Google gives them the answer in three lines, they have no reason to click through to your site for the same three lines.
This is a different kind of query than a general local-intent search, and it's usually a large share of what a small newsroom's readers actually search for. A story recapping last night's high school football score exists mainly to answer one question: who won. Once Google answers that inside the search result, the story's search traffic can disappear even though the reporting behind it was solid.
What happens to the click when an Overview does appear
Separate from how often AI Overviews show up, there's what happens when one does. Pew Research's data, reported by NPR, found that people are about half as likely to click through to a source once they see an AI Overview. This isn't a local-news-specific effect. It applies to the same kinds of direct-answer queries everywhere.
So: general local-intent content triggers an AI Overview less often. Single-fact content triggers one more often, and gets fewer clicks when it does.
What this changes for a small newsroom
Reporting that requires an interview , a document, or a decision made in a closed meeting has no three-line AI answer. "What did the city council decide and why" isn't something an Overview can synthesize. That kind of story isn't at risk here.
The single-fact stories are: the score, the closing, the number, the yes-or-no. Those were never what made your outlet worth reading. They were traffic, and now some of that traffic goes to Google instead of you.
A reader who only wants the school-closing update leaves the moment they have it, subscriber or not. Building a subscription base on that kind of traffic was already unreliable before AI Overviews existed. The reader worth building around is the one who comes back for the reporting, not the fact .
Questions we get asked directly
Should we stop covering weather, closings, and results if AI Overviews are going to answer them anyway?
No. Readers still expect a
Does this mean AI Overviews aren't really a threat to local news?
No. It means the threat is
Is there anything we can do about AI Overviews directly?
Not in
A
subscription
Started with video subscription and
After years, we