I have spent a lot of time over the last week going through Google’s documentation around the new EEA Search changes.
Not the headlines. Not the LinkedIn posts saying “Google has changed search again”.
The actual documentation.
And I think there is something much bigger happening here than a SERP layout change.
Google has effectively introduced a new layer between businesses and organic visibility for certain commercial searches.
For businesses operating in hotels, flights, rail, coach travel and products across the European Economic Area, getting visibility in some of the most valuable parts of the SERP is no longer purely about ranking.
It is also about eligibility, data, feeds, APIs and whether Google accepts you into the system.
That is a pretty significant change to how I think about SEO.
1. What actually happened with Aggregator Unit in Google Search?
On 8 September 2026, Google rolled out a redesigned search results experience for commercial queries across the European Economic Area.
At the same time, Google published new documentation covering the aggregator unit, the supplier unit, and a wider regional Search experience hub.
The aggregator unit is designed for what Google calls Vertical Search Services.
That includes organisations such as:
- Online travel agencies
- Comparison shopping services
- Metasearch engines
- Directories
The unit can appear for searches covering hotels, flights, long-distance trains and buses, and products.
Google then allows approved providers to populate that space with relevant results.
The interesting part is what happens inside the unit.
The top provider can have its result expanded with things such as prices, images and ratings, while users can also switch between different providers.
And the click goes directly to the provider’s website.
That is important.
This is not simply another Google-owned feature sending traffic somewhere else inside Google.
Google is creating a piece of SERP real estate that external platforms can compete for.
But there is a catch.
You don’t simply rank into it.
You need to qualify.
2. This is where I think SEO people need to pay attention
The biggest change here isn’t the visual design.
It is how visibility is earned.
For most of my SEO career, the basic assumption has been quite simple:
You optimise the website.
You create the right content.
You build authority.
You fix technical issues.
You build relevance.
Google crawls it, evaluates it and decides where you rank.
You cannot apply for position one.
The aggregator unit changes that model.
Google’s eligibility requirements include being approved as a Vertical Search Service, having relevant content, supplying data through a direct feed or real-time API, and complying with Search policies.
So before we even get to “Who ranks highest?”, there are multiple gates to pass.
That creates a few consequences that I think businesses should take seriously.
Visibility becomes an operations problem
This is not just an SEO problem anymore.
Take a hotel aggregator.
Its visibility could depend on whether its Point of Interest feed validates correctly, whether its images can be crawled, whether prices match the landing page and whether the data has been packaged correctly.
That involves SEO.
But it also involves engineering, product, data and commercial operations.
The SEO team needs to own the strategy, but it cannot execute this in isolation.
Traditional organic listings can be pushed further down
Whatever your view is on the European regulation, an additional aggregator block and supplier unit changes the economics of the SERP.
If those features appear above the traditional results, your previous number-one organic ranking may no longer have the same commercial value.
This is something enterprise brands need to start modelling.
Being absent becomes much more uncomfortable
This is probably the point I would pay the most attention to.
Historically, if your competitor ranked and you did not, you could say:
“They have better content.”
“They have more authority.”
“They have a stronger domain.”
With these units, there can be another explanation.
Your competitor is inside the system.
You are not.
And the difference may not be a ranking algorithm at all.
It could be an application, a feed, an API or an implementation problem.
That is a very different SEO conversation.
3. The UK creates an interesting complication
I have already seen some confusion around this.
The UK is not part of the EEA.
So if someone in Manchester searches Google.co.uk, these EEA changes do not automatically apply just because the company is British.
But that does not mean UK businesses can ignore them…..
So keep reading, and speak with your trusted UK-based SEO consultant.
A UK-headquartered business serving customers in Germany, France, Ireland, or the Netherlands can absolutely be affected.
That matters for enterprise businesses running a central SEO programme across multiple European markets.
You cannot simply look at “Europe” as one search environment.
The SERP can be materially different depending on the market and user location.
And that means your reporting should probably change too.
4. Who should actually care?
Online travel agencies and metasearch
This is probably the most obvious group.
For a query such as “hotels in Paris”, being inside the aggregator unit is a completely different proposition from being the fourth organic result.
The route into the feature runs through Google’s Search Aggregator Features process and, for accommodation, the relevant lodging feed.
Hotels and hotel groups
There are effectively two different routes.
A large hotel organisation with its own bookable inventory infrastructure may have an argument for Vertical Search Service status.
An individual hotel is more likely to operate as a supplier and rely on Google’s crawled information and structured data.
There is also an important dependency here:
No aggregator unit means no supplier unit.
Airlines, rail and coach operators
This becomes much more technical.
Flight data is handled through Google’s Partner standard Live API.
Ground transport uses Google’s Transport features API, with different integration options depending on the existing data infrastructure.
And if you want pricing displayed, there is another implementation requirement.
At this point, this is as much technical infrastructure as it is traditional SEO.
Ecommerce and comparison shopping
Product queries are handled separately through the comparison shopping services route.
That means another process, another integration and another set of requirements.
There is also an interesting feature around prioritising ranking signals such as price, rating and review count among your own products.
Again, this starts to look less like “SEO optimisation” and more like search visibility infrastructure.
Directories, marketplaces and review platforms
This is the group I think could be caught sleeping.
Google explicitly includes these businesses within its Vertical Search Service definition.
Many of them are looking at the current change and thinking:
“This is a travel thing.”
I don’t think they should.
Enterprise businesses with multiple European markets
This is where I see the biggest strategic issue.
If you are running one SEO programme across the UK, EEA and the rest of the world, you no longer have one consistent SERP environment.
Your reporting needs to distinguish those markets.
Your competitor tracking needs to distinguish those markets.
And your forecasting needs to distinguish those markets.
5. What would I do?
If I were responsible for an enterprise SEO programme affected by this, I would start with five things.
1. Work out whether you are an aggregator or supplier
This is the first question.
It determines the implementation path, the application process and whether you need to build a feed.
If you potentially qualify for both, decide which route makes the most commercial sense rather than treating the process casually.
2. Submit the expression of interest
For hotels, flights and ground transport, that means going through Google’s Search Aggregator Features process.
For products, the process is different and runs through comparison shopping services.
Google is very clear that submitting an expression of interest is not a guarantee.
I would still submit it.
There is very little reason to sit back and wait.
3. Build the feed properly
This is where I think a lot of companies will get caught.
“Technically valid” is not necessarily the same as “well implemented”.
For hotel data, for example, you need reliable identifiers, property names, locations and images, alongside supporting information such as ratings and star classification.
And some of the implementation details matter more than people might initially realise.
I have seen plenty of integrations fail because something relatively boring, like an image directory being blocked from Googlebot, was overlooked.
This is exactly the kind of thing that happens when SEO, engineering and data teams are working separately.
4. Start measuring the EEA separately
Before worrying about traffic gains, make sure you can actually measure what is happening.
Can you tell me what happened to your German non-brand organic clicks after 8 September?
Can you see the difference between UK and EEA performance?
Can you identify whether an organic decline is caused by rankings, SERP layout or something else?
If not, that is the first problem I would solve.
Search Console remains central to this because Google itself points to it as the monitoring source for the feature.
5. Don’t ignore supplier-side SEO
This is the less exciting part, but probably the easier win.
Suppliers may not need to submit a feed themselves.
That does not mean there is nothing to do.
If Google is relying on crawled information, then your entity data, structured data, images, content and overall information quality become even more important.
The control surface is smaller.
But it still matters.
6. What I am watching next
There are a few things I am particularly interested in here.
The end of September
The European Commission’s 60-day compliance period following its July decision reaches its next major milestone.
Whether the Commission considers Google’s changes sufficient could have a major impact on what happens next.
Expansion into other verticals
Google has already referenced broader categories beyond the features currently available.
If this expands into local services, dining and other areas, the implications become much larger than travel and ecommerce.
Google’s legal position
Google has been very vocal about the potential quality implications of the European changes.
If Google’s legal challenge succeeds, some of this could change again.
So I would work with what exists today, but I would not build a five-year strategy around assuming this exact implementation stays forever.
The AI overlap
This is actually the part I am watching most closely.
The European Commission has already raised questions around how the principles of the Search decision could apply to AI-generated search experiences.
Now think about what happens if this same data infrastructure starts feeding AI Overviews or AI Mode.
Suddenly the feed is not just helping Google decide what appears in a SERP feature.
It potentially becomes part of the information Google uses to construct an AI answer.
That is a very different level of importance.
The UK divergence
The UK is also regulating Google, but through a different framework.
So we now have another situation where the UK and EEA search environments could continue moving in different directions.
For enterprise brands, that means “European SEO” increasingly needs to be treated as a collection of different search ecosystems rather than one market.
My main takeaway
I think the mistake would be to look at this and say:
“Google has redesigned the SERP.”
That is technically true.
But strategically, I think something more important is happening.
Google is moving parts of search towards an eligibility + data + infrastructure model.
The companies that win will not necessarily be the ones with the best SEO content alone.
They will be the ones that can connect SEO, structured data, engineering, product, feeds and commercial operations together.
That is where enterprise SEO is heading.
And, honestly, this is one of the reasons I enjoy working on enterprise AI SEO.
The interesting problems are no longer just:
“How do we rank this page?”
They are increasingly:
“How does Google understand this business?”
“How does Google retrieve its data?”
“How does it decide whether to include it?”
“How does that visibility change across markets?”
“And increasingly, how does that information make its way into AI-generated search?”
That is a much bigger SEO problem.
And I think we are only at the beginning.
About Szymaniak Digital
At Szymaniak Digital, we work with enterprise marketing teams on search strategy where the rules are changing quickly.
The EEA redesign is a good example of why I approach SEO the way I do.
The most important information wasn’t in a ranking update.
It was buried in the feed specification, implementation requirements and European competition decision.
That is where the real strategic opportunities usually are.
If you operate across EEA markets and are not sure whether you qualify for the new search features, whether your data is ready, or what these changes could mean for your organic visibility, that is exactly the kind of problem we help enterprise teams solve.
