Google’s redesigned EEA search results went live on September 8, 2026, splitting commercial queries for hotels, flights, long-distance trains, and products into two new placements across the European Economic Area. The rollout responds to a July 23 European Commission ruling that fined Google €460 million for promoting its own services over rival comparison tools, part of a broader €890 million enforcement package. Brands and platforms serving EEA users now operate in a materially different search landscape.
What changed in Google’s EEA search results?
The redesign replaces the familiar integrated results format with two distinct placements for commercial queries in the EEA. According to Google Search Central documentation published September 8, 2026, an aggregator unit (a dedicated slot for comparison platforms and travel booking intermediaries) and a supplier unit (a slot for direct providers such as individual hotels or airlines) now appear alongside each other. Both units apply only to users in EEA countries and cover hotel, flight, long-distance train or bus, and product queries.
The European Commission had given Google 60 days from July 23 to comply with the Digital Markets Act (DMA, the EU law requiring large tech platforms to give rivals equal access to their surfaces), or face periodic penalty payments of up to 5% of its total worldwide turnover. The Commission described Google’s earlier tests of these changes as “substantial progress towards compliance” but has not confirmed as of publication whether this rollout fully satisfies the ruling.
How the aggregator unit works
The aggregator unit is designed for what Google calls Vertical Search Services (VSSs, meaning online comparison platforms and intermediaries): online travel agencies, comparison shopping services, metasearch engines, and directories. Eligible aggregators supply their listings through direct data feeds or real-time APIs (direct data connections), depending on the query type. The top-ranked provider’s results expand by default, showing photos, prices, or ratings where available. Users can switch to a different participating aggregator from within the unit; only one aggregator unit shows at a time.
To appear in the unit, per Google Search Central, businesses must be approved as a VSS, have relevant content for the query type, and supply data through the appropriate channel. For hotel queries, that means a Lodging Point of Interest Feed; for flights, a Live API integration; for products, Google’s standard product feed. Aggregators not yet integrated must submit interest through a dedicated Google Search Aggregator Features form, or through a separate contact form for product queries.
How the supplier unit works
The supplier unit is reserved for direct providers: individual hotels, airlines, and brick-and-mortar businesses. According to Google Search Central, suppliers do not need to submit additional data beyond what Google can gather through standard crawling (the automated process by which Google’s systems index web content), though structured feeds can improve results quality. Critically, the supplier unit only appears when an aggregator unit is also present for the same query. A direct supplier’s visibility is therefore tied to whether a qualifying aggregator is active in that category.
Reuters, which reported the rollout the same day, described a slightly different visual layout: one specialized search service at the top of the page, two others with fewer details below, and a carousel of hotels, airlines, and restaurants with real-time prices removed. Reuters’ description includes restaurants, which Google Search Central does not list as a supported query type for either unit as of publication.
What Google says about the quality trade-off
Google has been unusually direct in its objections. Nick Fox, Google’s senior vice president of knowledge and information, told Reuters: “These changes degrade the user experience for Europeans, boosting online intermediaries at the expense of local businesses, and removing helpful features people rely on every day. Users outside the EU will not be impacted by these changes.”
Google described the rollout to Reuters as the largest reduction in quality of service in Search’s 29-year history, citing internal testing with millions of European users who showed high dissatisfaction because they had to retype queries. Reuters did not report details of how the test was conducted.
Google also told Reuters that earlier DMA compliance changes, separate from this rollout, cut free direct booking traffic to European businesses by 30%. The company expects the current changes to have a similar effect on direct suppliers.
What this means for AI-search visibility
Think of the aggregator unit as Google handing comparison platforms a permanent front-row seat for EEA commercial queries. If your brand is not listed inside one of those platforms, you may not appear at all for the most commercially valuable searches, even if you rank well in standard organic results.
That matters beyond traditional SEO. AI-powered search tools such as Perplexity and Google’s own AI Overviews (generative summaries shown above search results) often pull structured data from rich search features, not just standard blue-link results. When the dominant result unit for “hotels in Paris” or “flights to Berlin” becomes an aggregator-populated block rather than an organic list, the signal the AI layer reads changes too. Brands that appear only in the supplier unit, or only in organic results, may see their share of AI-driven referrals in EEA markets shrink, even if their underlying content quality hasn’t changed.
In Hingewise’s assessment, the aggregator/supplier split creates a structural choice that did not previously exist: whether your EEA strategy optimises for aggregator feed inclusion, direct supplier presence, or both. These are now separate tracks with separate data requirements and separate ranking systems. Treating them as interchangeable will likely produce underperformance in one or both. The brands most exposed are direct suppliers in travel and retail that have historically relied on Google’s own carousels for commercial traffic, because that carousels experience is precisely what has been replaced.
A subtler risk: rank tracking and Search Console data from EEA countries will now reflect a different search experience than equivalent queries in the US or UK. Teams comparing EEA and non-EEA performance need to account for the unit structure before drawing conclusions about what is or isn’t working. Baseline data from the first few weeks post-rollout will be noisy by nature.
What to check before the September compliance window closes
- Determine whether your EEA-facing properties qualify as aggregators (VSSs) or direct suppliers under Google’s definitions, since the two tracks have different data requirements and different eligibility paths.
- If you operate as an aggregator, confirm whether you have the required data feed or API integration for each query type you want to appear in.
- If you operate as a direct supplier, identify whether qualifying aggregators are active in your category, since the supplier unit only appears when an aggregator unit does.
- Filter Search Console performance data by EEA countries and affected query types to establish a clean post-rollout baseline, separate from global figures.
- Update rank tracking configurations to treat EEA and non-EEA queries as distinct environments, not a single global view.
- Monitor AI Overview appearances for affected query types in EEA markets as a separate data stream from non-EEA AI feature data.
- Watch for a potential extension to local queries (dining, services, things-to-do), which Google has indicated is forthcoming through its Actions Center page, with no confirmed launch date.
The European Commission has not closed the compliance question. Its 60-day window from July 23 runs into late September, and the Commission has said it will monitor implementation. The first reliable traffic signal will likely come from country-filtered Search Console data once several weeks of post-rollout numbers accumulate.
Sources: Search Engine Journal, September 8, 2026; Google Search Central, September 8, 2026; Reuters (via Search Engine Journal), September 8, 2026.
Lam Nguyen · Hingewise
This article was drafted with AI assistance from the sources cited above and checked against them before publishing. The "What this means for AI-search visibility" section is Hingewise's editorial analysis, built on the frameworks and positions we use in our GEO work. How we work: Editorial policy.