Google Just Moved Links Higher in AI Answers — What It Changes for AEO

On 15 October 2026, Google announced that it will show inline links higher in the response, and more often, in AI Mode and AI Overviews. It was one of five link-related changes announced together, and it is the one that matters most for anyone tracking AEO visibility.

Google also said that usage of Preferred Sources — the feature that lets people nominate sites they want to see more of in AI answers — has grown, in its words, more than sevenfold since the start of the year. Two things it did not say are as important as what it did: Google gave no country list and no exact rollout dates. So treat this as rolling out, unevenly, rather than a global switch flipped on 15 October. If your AI answers look unchanged today, that does not mean the change has skipped you — it may simply not have reached your market yet. Coverage of the announcement is available via trade press.

Here is the part almost nobody is writing, and the part most likely to cost a marketing team a bad decision: this change moves your AEO numbers whether or not anything you did changed.

AEO visibility is measured by tracking how often, and how prominently, AI answers cite or link your site for the prompts your buyers actually use. If Google starts placing inline links higher and showing them more often, then across a fixed set of prompts your citation rate, your link visibility and your share of voice can all move — upward for some sites, downward for others — purely because the interface changed, not because your content, your authority or your work changed.

Anyone comparing month-over-month AEO visibility across 15 October will see a step in the line. The risk is attribution: a marketer who reads a mid-October jump as proof their AEO work is paying off, or a mid-October dip as a failure, is reading a reporting artefact as a performance signal. Both readings can be wrong, and both lead to the wrong next move — doubling down on something that did nothing, or killing something that was working.

This is the same failure mode we flagged in our guide to AEO tracking: the metric moved, but the cause was not you. The fix is not to stop tracking. It is to re-baseline cleanly so that real performance change is visible again.

Treat 15 October 2026 the way you would treat a Google core update: a dated line in your tracking that every later comparison has to respect. Concretely:

• Annotate the date. Mark 15 October in your AEO tracking sheet or tool so every future comparison knows a platform change sits there. A month-over-month delta that straddles that date is not clean.
• Re-baseline after the change, not across it. Take a fresh baseline of citation rate, link visibility and share of voice on your fixed prompt set in the days after the change reaches your market, and compare forward from there.
• Separate interface movement from performance movement. If your visibility moved but your content, your coverage and your competitors did not, suspect the interface first. If a competitor genuinely started getting cited where you are not, that is a real signal worth chasing.
• Hold the prompt set fixed. Changing prompts at the same time as a platform change makes it impossible to tell which caused the movement. Keep the set stable through the re-baseline.
• Track position, not just presence. Because the change is about links moving higher, record where you appear in the answer, not only whether you appear. A link that moved from buried to prominent is a real gain the old "cited: yes/no" metric would miss entirely.

Everything above is about protecting a clean baseline across one platform change — not a full how-to on AEO measurement. For the metrics, the tools and the monitoring cadence themselves, our AEO tracking guide is the canonical treatment; this piece assumes it and covers only what 15 October changes.

For completeness, here are all five link changes Google announced on 15 October 2026. Most teams only need to act on the first; the rest are context.

Two of the five are tests, which Google may change or drop. That is another reason to date your baseline rather than assume today's layout is permanent.

Separately, and covered in the same window, Google is testing paying publishers when their content contributes significantly to an AI answer, through a new AI Contribution report in Search Console covering AI Overviews, AI Mode and Gemini.

Keep expectations low and precise. It is an early-stage pilot, offered to a limited set of publishers rather than to everyone. Reporting notes that the panel's visibility is inconsistent — participants cannot clearly see which article earned what, or why — and that payouts so far are small. Do not budget for it, do not promise a client revenue from it, and do not restructure anything around it. It is worth knowing about for two reasons only: you may see it referenced in a client's Search Console, and reporting suggests that opting out of the payment does not remove your content from Google's AI features. It is not a revenue line today.

In priority order:

• 1. Annotate 15 October 2026 in your AEO tracking as a platform-change line.
• 2. Re-baseline citation rate, link visibility and share of voice on your fixed prompt set, forward from the change.
• 3. Add link position to what you track, not just whether you were cited.
• 4. Hold off on big conclusions about any mid-October swing until you have a clean post-change baseline — it is very likely part artefact.
• 5. Note the publisher-payment pilot for awareness only; do not plan around it.

The teams that win from a change like this are not the ones who react fastest to the headline. They are the ones whose measurement is clean enough to tell, a month from now, whether their AEO visibility actually moved — or whether the interface just rearranged itself around them.