Why Your Rankings Look Different Inside the EEA

A drop that appears in one country and nowhere else is usually not an algorithm change, and since 8 September 2026 there is a Google page that explains why. On that date Google added documentation about regional differences in the Search experience, covering search experiences available in certain countries. Ten days later, on 18 September 2026, it updated the aggregator unit and supplier unit documentation to include support for local business queries. Both pages now carry a last-updated date of 18 September 2026.

The page that explains the split

Google’s framing is that it is evolving the search results page for certain types of queries to create opportunities for Vertical Search Services, Comparison Shopping Services, direct suppliers and content providers. The regional differences in Search experience documentation is built as a filter: pick the region your company is based in and the query types relevant to it, and it lists the features that exist there.

The first surprise for most readers is that it is not an EEA page. Three regions appear:

• EEA — aggregator unit and supplier unit for hotels, flights, ground transportation, local businesses and products; an ecosystem carousel for weather, sports, finance and translate queries; dedicated job sites features; and structured data carousels across seven query types.
• Türkiye — places sites features for hotels and local businesses, plus structured data carousels for hotels, local businesses and vacation rentals.
• South Africa — a badge and refinement chip for travel, products, car hire, food delivery and ground transportation, plus structured data carousels.

If you operate in more than one of these, your results page differs in three ways for reasons that have nothing to do with your site.

Aggregator units and supplier units

The aggregator unit documentation describes a multi-provider feature for vertical search services — online travel agencies, comparison shopping services, metasearch engines and directories. Eligible aggregators populate the unit with results relevant to the query, the top-ranked provider’s results are expanded by default, and users can switch to a different provider from a list of alternatives. Only one aggregator unit shows at a time, and clicks inside it go directly to that aggregator’s site. The supplier unit does the same job for direct providers, and Google shows it alongside the aggregator unit.

Eligibility is not something you optimise into. A business must be approved as a vertical search service, must have relevant content for the query type, must supply data through direct feed integrations or real-time APIs, and must comply with Google’s content policies. Participation starts with a form — the Google Search Aggregator Features form for transport, flight, hotel and local business queries, or the comparison shopping services contact form for product queries.

What this does to your reporting

These units occupy space above ordinary results for exactly the query classes that matter most to travel, retail and local sites. A site that has lost no position at all can lose clicks in one region because a unit now sits where the first organic result used to be. Aggregated across all countries, that reads as a gentle sitewide decline with no cause.

The diagnostic is a country-segmented performance report before any other step. Split EEA from non-EEA, and where you trade in Türkiye or South Africa, split those out too. Compare impressions against clicks separately in each segment: a click fall with flat impressions points at the results page, while both falling together points at something else. Only when the pattern survives that segmentation is it worth reaching for a ranking explanation. The same discipline applies on the analytics side, and the reports worth building are in GA4 reports that matter for SEO.

What you can and cannot do about it

Very little of this is optimisable, and saying so is more useful than pretending otherwise. The features exist because of regulation, the eligibility criteria are approval-based rather than quality-based, and no amount of on-page work makes a publisher into a vertical search service. Two things are in scope. Structured data carousels are listed as a regional feature that requires markup, so a site with correct markup in an eligible query type can be eligible where a site without it cannot. And if your business genuinely is an aggregator or a direct supplier, the forms are open.

Everything else is accounting. Build the regional split into reporting permanently rather than constructing it each time something looks wrong, and keep it separate from genuine international problems — the targeting and duplication failures in hreflang mistakes that break rankings produce a similar-looking chart from a completely different cause, as do the wider shifts in SERP feature changes.