What Still Gets a Click When AI Answers the Question First

A Flaw Nobody Could See

Did you catch the recent disclosure about a UEFI firmware flaw sitting in the boot process of a huge share of the world's servers? Security researchers found it buried in code that runs before the operating system even loads, the kind of layer most of us never think about because it just works until it doesn't. Nobody votes on firmware. Nobody reads the changelog. It sits underneath everything, quietly deciding whether the machine boots clean or gets hijacked, and the only time anyone pays attention is when a researcher proves it was broken all along.

Search works the same way right now, and most business owners haven't noticed.

There's an invisible layer between your business and the customer who's looking for it, and that layer is increasingly a large language model deciding whether to answer the question itself or send someone to your website at all. You don't see this happening. There's no changelog, no disclosure, no moment where someone tells you your visibility just changed. It just quietly starts happening, the same way a flawed boot process sits there for years before anyone notices the lights are on but nobody's actually checking who's in control.

Zero-click search is that layer. It decides, on every query, whether you get a visitor or just get summarized.

The Shrinking Click

Google calls this a feature, not a side effect. The company has said directly that AI Overviews exist to let people ask questions in ways a traditional search box never allowed, and that the format is meant to do more of the thinking for the searcher before they ever scroll to a blue link. That's not a conspiracy theory extracted from a leaked memo. It's the stated goal, published in Google's own blog posts about the feature.

What that goal does to your website is straightforward even if nobody at Google phrases it this way: the question gets answered on the results page, and the click that used to land on your site never happens. Pew Research Center looked at this pattern directly, tracking how often people click through to a website when a search results page includes an AI-generated summary versus when it doesn't, and found that users engage with outside links far less often when the summary is sitting right there answering the question.

None of this means search traffic disappears entirely. It means the query itself gets intercepted earlier, and the businesses that used to collect that visitor almost automatically now have to earn it on different terms.

What Earns a Visit Anyway

An AI Overview can tell someone what a thing is. It struggles to tell someone what it costs them specifically, what two options look like side by side, or what happens when they actually try to buy, book, or configure something. Those gaps are where the click still survives.

Pricing detail is the clearest example. A summary can say "prices vary" or quote a range it scraped from somewhere, but it can't run a quote based on someone's square footage, their zip code, or the three add-ons they actually want. Anything that requires an input only the visitor has stays a click.

Comparison content works the same way. "X vs Y" articles that walk through tradeoffs in plain language tend to survive because the AI can summarize the general shape of the comparison but can't make the decision for someone with a specific constraint the model doesn't know about.

Interactive tools are the sturdiest category of all. A calculator, an estimator, a configurator — anything where the output depends on what the user types in — simply can't be replicated inside a chat answer. Same with anything transactional: booking a slot, checking live inventory, submitting an application. The model can describe the process. It can't do it for you.

Making Your Site Worth Clicking Into

Here's where the firmware comparison actually becomes useful instead of just unsettling. You can't patch Google's crawler the way you'd patch a BIOS, but you can control what you're running on your own side of the connection, and that's not nothing.

Start with schema. FAQ schema, product schema, review schema — these tell AI systems what's on the page instead of making them guess, and a page that's easy to parse is more likely to get cited, which still puts your name in front of someone even when the click doesn't happen immediately.

Then build the pages an Overview literally can't write. A pricing estimator that takes someone's actual inputs. A comparison page that walks through your product against the obvious alternative with specifics instead of vague praise. An FAQ page answering the exact questions your customers ask in your own words, not generic category language.

Audit your own site for "prices vary" and "contact us for a quote" — language like that routes people to a dead end. Something fillable or bookable on that same page keeps the visitor from bouncing to whoever built the calculator you didn't.

This week's actual task: pick one page, add schema, add one interactive element. That's the whole assignment.