Google's aggregator unit: what it means for retailers

Google has changed how organic Shopping results look in the European Economic Area. Instead of a single grid of products, shoppers now see an expandable list where each row belongs to a different comparison shopping service, and Google is one option among them.

It is the most visible change to Shopping results in years, and the questions it raises for retailers are simpler than the coverage suggests. This is what has actually changed, what it means for where your products appear, and what you need to do about it. Which, for most retailers, is less than you would expect.

What Google has actually changed

Google calls it the aggregator unit. It is a search feature that lets several providers show their own results inside one block on the search results page.

In practice, for product searches:

• Organic Shopping results are presented as rows, one per comparison shopping service.
• Only one row is open at a time, showing that provider’s product tiles, prices and links.
• The top-ranked provider’s row is the one expanded by default.
• The unit is labelled in the local language of the market.

Two things it does not change. Paid Shopping ads are unaffected and continue to appear as they always have. And the unit is not limited to products at all: Google uses the same format for hotels, flights and long-distance trains and buses, with comparison shopping services being the product-specific case.

Why it happened

In July 2026 the European Commission ruled against Google’s self-preferencing under Article 6(5) of the Digital Markets Act, the provision that stops a gatekeeper favouring its own services in its own rankings. Google was given 60 days to comply, and the rollout of the new unit began across the EEA in early September 2026.

It is being introduced market by market rather than everywhere at once, so what a shopper sees still depends on where they are and what they searched for. Google has also said the unit’s final shape depends on the Commission’s assessment of whether the change is compliant, so this is not necessarily its settled form.

Your CSS now decides which row you are in

Here is the part that matters commercially.

Before, organic Shopping listings sat in one grid. Now they sit in rows, each belonging to a comparison shopping service, with one row open by default and the rest collapsed behind a click. Which row your products appear in is determined by which CSS your Merchant Center is associated with.

That makes the choice of CSS a more consequential decision than it was a month ago. It is no longer only about the cost of a click. It is about which row your products are sitting in, and whether that row is the one a shopper sees without having to open anything.

Google says placement within the unit is decided by what is most helpful to users for their query, and points to its search quality rater guidelines rather than to a checklist. There is no published formula, and anyone telling you they have one is guessing.

It is a channel you cannot reach on your own

This is the part that gets lost in the coverage. The rows are not simply a new place your existing listings turn up. They are provider rows, and the only route into one is a comparison shopping service.

Google’s documentation is explicit about it. A business has to be approved as a vertical search service to supply results into the unit at all, and for product searches that route runs through comparison shopping services. There is no self-serve path for an individual retailer, no form of your own to fill in, and nothing you can buy.

So the aggregator unit is a distribution channel that exists for retailers working with a CSS and does not exist for anyone else. No amount of work on your own site opens it, which makes your CSS relationship the whole of your access to it.

There is nothing for you to build

Retailers keep asking us what they need to implement. The answer is nothing.

Google’s documentation sets out no structured data requirement, no schema markup and no new feed specification for retailers who want to appear in the aggregator unit. There is no code to add to your product pages and no attribute to add to your feed. Eligibility for the product unit runs through comparison shopping services, not through anything you do on your own site.

If someone is selling you an aggregator unit implementation project, it is worth asking exactly what they intend to implement.

What nobody knows yet

Being straight about the limits of what is known here matters more than sounding certain.

The rollout is partial, so market-level observations are snapshots rather than trends. The Commission has not yet confirmed whether the redesign satisfies its ruling, which means the format could change again. And any performance figures circulating at this stage come from individual providers reporting on their own traffic, over days rather than quarters. Treat them as what they are.

What is not in doubt is the structural change: comparison shopping services have moved from being invisible plumbing behind a grid to being the named rows that organic Shopping results are organised into.