Search Console Uses Block Flattening for AIOs, Forget Position & Focus on Outcomes

Declining clicks from organic search have been a shift in the industry for the past couple of years, and we've faced increasing pressure from clients and stakeholders to provide explanations for this, or to show that "traffic" has basically shifted to AI. This has led to a panic in the industry, as we try to find a new normal to educate stakeholders on what matters and what doesn't.

Alongside this, AI tool vendors have been quick to jump into the space, forcing a narrative that their tool is the answer to AI visibility when, in reality, it just suits their product and not what is really needed. On top of this, Google has now openly admitted that its Search Console reporting cannot keep up with how AI search actually works. This connects with Working Framework when the same signal needs a clearer operating decision. The same pattern also shows up in Working Framework, where the practical question is how the signal becomes visible.

Why 'Average' Position Gives The Wrong Impression

Even before AI arrived, Search Console's ranking numbers could be misleading because they rely on a simple mathematical average. I've always had a problem with this metric in the form it is presented. An average works well when numbers. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path.

The reporting question is whether this signal changes a decision. If it only creates another number in a dashboard, it adds noise. If it helps separate profile activity, website visits, calls, bookings, and direction requests, it can make local performance easier to understand.

What 'Block Flattening' Means In Practice

This problem gets worse because of how Search Console records AI Overviews, using an approach known as block flattening. Instead of checking where an individual link sits inside an AI summary, Google just looks at the overview box as a. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path. A useful companion note is Cloudflare’s AI Crawler Rules Can Block Googlebot, because it looks at a nearby part of the same system.

How Impression Rules Skew The Numbers

This flattening issue runs straight into Google's standard rules for counting impressions, which were written long before search results became interactive. Under the normal rules, an impression is logged the moment a search result is. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path.

What This Means For Real Traffic

When you put these reporting quirks together, they make standard traffic metrics much harder to trust. Articles across Search Engine Journal show just how much AI answers are changing user behavior. Looking at data where AI Overview CTR. The measurement question is whether this signal changes a decision, not whether it adds another number to a dashboard. Useful reporting connects visibility, engagement, and business outcomes without pretending every AI influenced journey will produce a clean click path.

Moving Beyond The 1-To 10 Ranking Scale

During his comments on Reddit, John Mueller mentioned that Google has tried to explain these rules in its help documents, while asking the SEO community for practical ideas on how position could be measured when search pages no longer look. For search teams, the important part is not the headline movement by itself. It is whether the shift changes which communities, forums, video surfaces, or publisher pages now satisfy the query better than the old ranking pattern.

The useful check is whether this improves the system behind search performance, not only the words on the page. Internal links, crawlable content, clear entities, current evidence, and a sensible page structure all help the recommendation become easier to trust.

How To Measure What Matters Now

The reality is that the old ways of measuring performance cannot simply be patched up to solve this, and the tsunami of AI visibility tools can't provide any deeper or further insights into this problem. If you want a clearer picture of. The practical read is that brand signals need to be consistent enough for both people and AI systems to form a stable view of the company, its expertise, and its trust signals.

Why 'Average' Position Gives The Wrong Impression in practice

Introduction Declining clicks from organic search have been a shift in the industry for the past couple of years, and we've faced increasing pressure from clients and stakeholders to provide explanations for this, or to show that "traffic". For search teams, the important part is not the headline movement by itself. It is whether the shift changes which communities, forums, video surfaces, or publisher pages now satisfy the query better than the old ranking pattern.

What the visibility signal actually changes

What the visibility signal actually changes: search Console Uses Block Flattening for AIOs, Forget Position & Focus on Outcomes: the Practical Angle should be treated as a visibility signal, not a standalone headline. Introduction Declining clicks from organic search have been a shift in the industry for the past couple of years, and we've faced increasing pressure from clients and stakeholders to provide explanations for this, or to show that "traffic" has basically.

What the visibility signal actually changes: the practical question is whether the page, brand evidence, and surrounding content make the answer easier to trust. If that support is weak, search systems can still understand the topic but fail to connect it confidently to the brand.

What the visibility signal actually changes: that is why the response should begin with an audit of the evidence already on the site before creating a new asset. The fastest improvement is often a clearer page, a better internal link, or a stronger explanation of why the brand belongs in the answer.

Where the evidence needs to be tested

Where the evidence needs to be tested: a single study or ranking observation should not become a strategy by itself. It should become a diagnostic prompt: which source is being trusted, which query pattern is affected, and which part of the site would make that trust easier to earn?

Where the evidence needs to be tested: that keeps the response grounded. The goal is to improve the evidence chain around the topic rather than publish another summary that repeats what every other page already says.

Where the evidence needs to be tested: the important distinction is between a useful signal and a fashionable talking point. A useful signal changes the brief, the page structure, the linking plan, or the measurement view.

How to avoid overreacting to one data point

How to avoid overreacting to one data point: for content teams, the strongest move is to map the claim to existing assets before creating anything new. The right page may already exist, but it may need clearer headings, stronger internal links, fresher proof, or a better explanation of why the brand belongs in the answer.

How to avoid overreacting to one data point: this is also where title rewriting matters. A title should not copy the source headline; it should frame the practical implication so readers immediately know why the topic deserves attention.

How to avoid overreacting to one data point: the same standard should apply to every section. Each heading needs to earn its place by moving the reader through the evidence, not by repeating the outline in a more polished voice.