If AI Overviews are eating the click and your “vs” page traffic is shrinking, the fix isn’t more content—it’s making the visitors you still get convert with less friction and cleaner answers.

If your comparison page traffic is down and qualified pipeline is getting harder to explain, here’s the constraint: AI search is reducing clicks, so the few visits that still land on your “vs/alternatives/best-for” pages have to do more work.

One analysis associated Google AI Overview–style results with a 34.5% CTR drop for the top result. And separate reporting puts zero-click searches in the U.S. at 58.5%. That’s not a rounding error. That’s the channel changing shape.

So the goal for 2026 isn’t “rank and hope.” It’s: turn comparison pages into answer pages that convert—for humans and for the models that pre-sell the click.

If you only change one thing, change this: redesign the top of every comparison page into an answer-first decision block, then test it with an AI-source segment. That’s the primary tactic in this piece.

Why this matters now: the funnel is getting compressed

AI search doesn’t just change where people discover you. It changes what the click means. McKinsey’s framing (as summarized in the research brief) is that AI shifts clicks toward people further along the purchase funnel because the decision work happens inside the AI layer before they ever hit your site.

Orbit Media has said something similar in plainer language: AI behaves like a decision-support tool, so visitors arriving from AI are often more informed and more likely to become a lead (again, per the research brief).

But the data tells a different story in one important way: it’s not guaranteed. Some syntheses show AI-referred traffic converting worse and generating less revenue per session. Translation: treat this like a measurement problem first, a design problem second.

Still, there’s enough signal that it’s worth operationalizing. One industry analysis cited in the brief found 7.05% conversion from AI-driven sessions vs 5.81% for organic search on high-traffic sites. Microsoft has also reported that Copilot-assisted journeys are 33% shorter on average and high-intent conversion rates are 76% higher in those AI-powered experiences.

Fewer clicks. Higher intent (sometimes). That combination makes comparison pages the highest-leverage CRO surface in the new search mix.

The tactic: build an “answer-first” decision block above the fold

Comparison pages used to be “ranking pages.” Long intros. A table somewhere. A CTA buried under politeness. In AI-influenced search, that shape underperforms because the visitor shows up with a shortlist and low patience for throat-clearing.

The better approach is to treat the first screen like a decision meeting. Not a blog post.

Answer-first decision block (what it includes):

Here’s why this works in an AI-shaped funnel: models and humans both reward extractability. The research brief calls out a shift toward “answer-first formatting”—direct answers near the top, summary blocks, comparison tables, concise FAQs—because that structure is easier for AI systems to pull into generated comparisons.

Seen from the other side, this is also plain old CRO. Visitors who arrive pre-educated skim harder. They want confirmation, not education.

The experiment (make it falsifiable): measure lift without lying to yourself

Hypothesis (falsifiable): If we add an answer-first decision block above the fold on our top comparison pages, then demo/trial starts from AI-referred sessions will increase versus baseline because those visitors are already mid-funnel and need faster confirmation and a clearer next step.

Setup (segments): create an “AI referrals” segment in analytics based on known AI referrers (when available) and campaign tagging where possible. The research brief explicitly recommends custom UTMs and event tracking to understand AI-influenced behavior—do that before declaring victory.

Primary metric: conversion rate to your intended next step on the comparison page (demo submit, trial start, or “contact sales” submit), split by AI vs non-AI source.

Secondary metrics (directional): lead-to-SQL rate (or whatever your qualified pipeline gate is) and time-to-conversion (AI-assisted journeys are reported as shorter; see if that shows up in your data).

Guardrails: bounce rate and form completion rate. If CVR rises but form completion collapses, you likely created a high-click, low-finish UI trap.

Stop-loss threshold: if total conversions (not just rate) drop more than 10% for two straight weeks on the page set you changed, roll back and isolate what broke. (Directional, not definitive—adjust to your traffic volume.)

Trade-off to name upfront: this will often reduce “engaged time” and scroll depth. That’s fine. Those are vanity metrics on evaluation pages if qualified pipeline doesn’t move.

When this is wrong: if your comparison page is attracting mostly early-stage traffic (top-of-funnel “what is X” intent disguised as a “best tools” query), answer-first can feel too sharp and hurt trust. In that case, keep the block but soften the verdict and add a short “how we compared” line for credibility.

Run it this week: a tight build-and-readout plan

Here’s the 5-minute version you can run this week:

What to measure (and what not to over-interpret): don’t treat last-click attribution as incrementality proof. Use it as a leading indicator. If you can, pair this with a simple holdout (some pages unchanged) to sanity-check lift directionally.

One more operational detail that matters more in 2026 than it used to: the research brief flags consistency across the web (pricing, product names, feature terminology) because AI systems cross-check facts. If the new decision block introduces different naming than your pricing page or docs, expect confusion—and fewer mentions in AI answers.

That’s the circle to close: AI search may send fewer clicks, and those clicks may be more qualified. But you don’t get credit for either unless the comparison page makes the decision easy, measurable, and consistent enough to trust—by a buyer and by the model that advised them to click in the first place.