Google AI Overview Links: What AEO Teams Should Do Now

25 September 2026 · The Cresia team

Yes, more links in AI Overviews should mean more chances to be cited, but a link in the panel is not the same as a visit to your site. According to Search Engine Journal, some of those links lead to websites while others lead into AI Mode, and Search Console measures the two interactions differently. Treat every citation as exposure first and a click second, and set up your reporting so the two never get mixed into one number.

Key takeaways

An AI Overview link is not always a route to your site: some lead into AI Mode, and Search Console measures the two differently, as Search Engine Journal reports.
Treat a citation as exposure first and a visit second, and keep those two numbers in separate columns.
Answer engines pick passages, not pages, so write sections that stand alone and answer one question completely.
Build a fixed panel of queries and check citations on a schedule; a weekly Search Console total will not tell you this.
Ignore single-day swings and vendor scores you cannot audit. Fix the pages, tagging and reporting you control.

What changed in how AI Overview links work

Search Engine Journal, in a piece by Matt Southern, reported that the links inside Google's AI Overviews do not all behave alike. Some take the reader to a website. Others take them into AI Mode, Google's conversational search experience, where the reader stays inside Google and asks a follow-up. Search Console, the same report says, measures those two kinds of interaction differently.

That is a small sentence with large consequences for anyone who reports on AI search. Until now a lot of teams have been working with a simple mental model: the Overview cites us, the reader clicks, we see a session. This says the middle step has a fork in it. A citation can end at your page or it can end at another Google answer.

There is a lot we should not pretend to know from a headline. Exactly which interactions land in which Search Console bucket, and how that shows up in the Performance report, is something to confirm in Google's own Search Console documentation and in your own property. Look at how your data is labelled there before you build a dashboard on an assumption.

The direction is clear enough to act on, though. Google is putting more links into its answers, and it is also building more ways to continue the conversation without leaving. Bing is testing something similar, with Search Engine Roundtable reporting that Bing is trying AI Mode in place of Copilot in its search tabs. Google has also been testing AI Overviews in a hotel side panel, again per Search Engine Roundtable. The answer is showing up in more places, and each place has its own link behaviour.

Why an AI Overview link that doesn't reach your site still matters

It is tempting to read the AI Mode fork as bad news and move on. A click that never arrives is a click you cannot bill to anyone. But there are two separate questions here, and they have different answers.

The first is whether being cited has value when nobody clicks. Sometimes it does. A buyer who sees your brand named as a source on three different questions about analytics governance is building an impression of you, even if they never open a tab. That effect is real but soft, and it is hard to prove from a dashboard. Anyone who tells you it is worth a precise dollar amount is guessing.

The second question is whether a link that leads into AI Mode still points back to you. That depends on what AI Mode cites in the follow-up answer, which is a fresh selection with its own logic. Your page can be in the first Overview and absent from the conversation that follows. Or the reverse.

Picture a B2B software company with a strong comparison page. The Overview cites it for a question about tool categories. A reader taps the link, lands in AI Mode, asks which option suits a mid-size team, and gets an answer built from other sources. The company was cited, got a visit-shaped event in one report and no session in another, and has no idea what happened next. That gap is the thing to plan for.

So the position worth taking is this: citations are a legitimate goal, visits are a legitimate goal, and they are now different goals with different evidence. Pick which one each page is supposed to earn.

How answer engines choose and cite sources

Nobody outside the vendors knows the exact selection logic, and it changes. What is well established from how these systems are built and described publicly is a rough shape.

An answer engine takes a question, often breaks it into several related sub-questions, retrieves candidate documents or passages for each, and then writes an answer that draws on some of them. Google has described AI Mode as running multiple related searches to build a response. The citation is attached to the passage or page that supported a claim in the final text.

Three practical things follow from that shape.

Passages compete, not pages. A long page with one relevant paragraph can be cited for that paragraph. A page that never states its answer plainly gives the system nothing clean to lift.
Being retrievable comes first. If a page is not indexable, is blocked from the relevant crawler, or renders its main content only after heavy client-side script, it cannot be a candidate at all. This is the dull step that quietly decides most cases.
Consensus and specificity both help. Systems tend to favour statements that are clear, attributable and consistent with other trusted sources. A page that says something distinctive but well supported, such as your own process, data or definitions, gives the model a reason to cite you rather than a generic summary.

None of this is a trick. It is a description of why clear writing on crawlable pages tends to get cited more often than vague writing on fragile pages. If you are wondering whether you need a separate GEO playbook, the answer is mostly no: you need the fundamentals of search content done properly, plus some new measurement.

What to change on your pages this quarter

Don't rewrite the site. Pick the twenty or thirty pages that matter most to pipeline and work through them in order.

Lead each section with the answer. Put the direct answer in the first two sentences under a heading that matches how a person would ask the question. Follow with the reasoning, the caveats and the example.
Make sections quotable on their own. A passage that says 'this approach' or 'as above' cannot be lifted. Name the subject in the sentence.
Give a reason to click through. If a citation might end inside AI Mode, the page needs something the summary cannot carry: a worked template, a calculator, a dataset, a screenshot of the real configuration. Summaries can describe those. They cannot replace them.
Check crawl access. Review your robots rules and server responses for the crawlers you want, and confirm key content is in the served HTML. Use each vendor's documentation to see which user agents they publish and what each one controls.
Tag landing pages properly. If AI-driven traffic arrives, you want to be able to tell it apart from ordinary organic sessions. That takes consistent campaign and content-group naming, and it takes a written spec so different teams do not invent different labels. A tracking specification is the plain way to hold that agreement.
Keep facts current. Prices, feature lists and dates that are wrong on your page will be wrong in someone's answer. Assign an owner and a review date to each high-value page.

The order matters. Steps one, two and four are cheap and apply to every page. Step three is where your effort should go on the pages that already get cited.

How to measure AI Overview visibility without fooling yourself

The Search Engine Journal report is, at bottom, a measurement story. If one interaction type is counted one way and another interaction type is counted a different way, then adding them together gives you a number that describes nothing.

So separate the layers. There are at least four things you may want to know, and each comes from a different place.

Question	Where the evidence comes from	Owner	Cadence
Are we cited for the queries we care about?	A fixed panel of queries, checked in the live results or with a citation-tracking tool	SEO lead	Weekly
Do those citations produce site visits?	Search Console and your web analytics, compared for the same landing pages	Analytics lead	Monthly
Is AI-referred traffic tagged consistently?	Your tracking specification and a periodic audit of landing-page parameters	Analytics lead	Quarterly
Does that traffic convert or assist?	Conversion and assisted-conversion reports by landing page group	Growth lead	Monthly

A few habits make this workable.

Fix the query panel. Choose 40 to 100 queries that map to your real buying questions and keep them stable for at least a quarter. Changing them mid-stream destroys any trend.
Record the date and the place. An Overview, an AI Mode answer and a Bing answer are different surfaces. Log which one you looked at.
Expect noise. Generated answers vary from one run to the next. One check means little. A pattern across weeks means something.
Read the vendor's own reporting notes. Confirm in Search Console's documentation how AI features are counted before you make a chart that compares clicks and impressions across them.

Teams that run this across several channels tend to need a shared place to hold the panel, the tagging rules and the reporting. That is a marketing operations problem before it is an SEO problem, and it is why media, analytics and content people should agree the definitions together. MediaPilot is Cresia's product for media and AI-search visibility, and it is worth a look if you want that in one place.

What to ignore and what not to do

Most of the wasted effort in AI search comes from reacting to things that are either unproven or outside your control.

Ignore single-week swings. Google is testing AI Overviews in new places, as the hotel side panel shows, and Bing is trying AI Mode in tabs. Layouts will keep shifting. A drop in citations the week a layout test starts is not evidence about your content.

Ignore any single 'AI visibility score' you cannot inspect. If a tool cannot show you which queries, which surface and which date sit behind the number, you cannot act on it.

Don't chase citation share by stuffing pages with definitions. Padding a page with dozens of short answer blocks reads as padding to people and adds nothing a system can use. One clear answer per section is the aim.

Don't treat AI Mode clicks as lost traffic to be recovered at all costs. Some of that behaviour is simply how a reader is choosing to research. Your job is to be the source they trust, and to have a reason to visit when they are ready.

Don't mix metrics. Never sum Search Console interactions and web-analytics sessions into a single 'AI traffic' line. They come from different systems and measure different events.

Don't wait for perfect data. The measurement is imperfect and will stay imperfect for a while. A rough weekly panel is far better than nothing.

Who owns what across the team

AI search work fails most often at the handoffs. The SEO lead sees the citation, the analytics lead sees the session, and the content lead sees neither. A short division of labour helps, and teams that work in a growth-focused or analytics-focused setup can adapt it.

SEO and content: own the page structure, answer-first sections and the query panel.
Analytics: owns the tagging rules, the Search Console comparison and the caveats attached to each number.
Engineering: owns crawl access, rendering and server responses.
Growth or marketing leadership: decides which pages are meant to earn citations and which are meant to earn visits, and holds the team to that.

Once the split exists, the question of what a good week looks like has an answer. It is a stable panel, a clean tagging spec, one or two pages improved and a short note of what the reports can and cannot say.

Frequently asked questions

Do AI Overview links still send traffic to websites?

Some do. Search Engine Journal reports that AI Overview links can lead to websites or to AI Mode, so the same panel can produce both outcomes. How much of each you see depends on the queries and pages involved, so check your own Search Console data rather than relying on a general figure.

How does Search Console report AI Overview and AI Mode interactions?

Per Search Engine Journal, it measures the two kinds of interaction differently. The exact labelling and where each shows up should be confirmed in Google's Search Console documentation and in your own property before you build reports on top of it.

Is answer-engine optimisation different from SEO?

Mostly it is SEO done with more care at the passage level, plus new measurement. Crawlable pages, clear answers, accurate facts and real expertise remain the foundation. The new part is tracking citations across several answer surfaces and separating exposure from visits.

Should we change our reporting because of this?

Yes, in one specific way: stop treating citations, impressions and sessions as one number. Keep a separate view for each, name the source system on every chart, and record when a surface or a definition changes. That protects you when Google adjusts the reporting again.

Where do we start if we have limited time?

Pick your top twenty pages by revenue influence, rewrite the opening of each section to answer directly, and confirm those pages are crawlable. Then set up a small query panel and check it weekly. If you want help organising the wider operating model, the overview of marketing operations is a sensible next read.

Sources

https://www.searchenginejournal.com/google-ai-overviews-have-more-links-but-not-all-reach-the-web/590762/
https://www.seroundtable.com/bing-ai-mode-search-tabs-42165.html
https://www.seroundtable.com/google-hotel-ai-overviews-42146.html
https://developers.google.com/search/blog