The only door Google gives aggregators returns 404
Google redesigned its European results for hotels, flights and long-distance transport and documented the change in two pages. We read both on 9 September 2026 from an address inside the EEA. One of them is three times longer than the other, and the link it tells you to click does not exist.
By Cittago, a digital studio in Cluj-Napoca since 2011

Google has redesigned search results in the European Economic Area for queries about hotels, flights, long-distance trains and buses, and products. Where a single panel used to sit there are now two blocks: the aggregator unit, reserved for approved comparison services, metasearch engines and online travel agencies, and the supplier unit, for businesses that sell directly. The official documentation is two pages, published on 8 September 2026.
It does not land on everyone the same way. If you sell through a portal and the direct channel is not your business, little changes. If your own website is where you want people to book, one sentence in the documentation matters more than the rest: the supplier unit appears only when the aggregator unit appears.
Below: what the two pages actually say, how much each one asks of its reader, what neither of them says at all, and the three things worth checking today, without waiting for somebody to publish a guide.
- You know the order Google now puts European travel results in, and why.
- You know what you must do to appear — and that, if you sell directly, the official answer is close to nothing.
- You know which questions to put to whoever runs your website, in the right words.
- You know what these numbers do not prove, before somebody points it out to you.
The form Google tells aggregators to fill in returns 404
The aggregator unit page opens its eligibility section with a single instruction: express interest by filling out the Google Search Aggregator Features form. The link is there. It is the only entry point named anywhere in either page. On 9 September 2026 it goes nowhere.
We asked for it in three forms of the address — bare, with hl=it, with hl=en — and all three answered 404. Then we opened it in a real browser from Cluj-Napoca, Romania, inside the EEA, in case an automation filter was the explanation. It was not.
«Sorry, this page can't be found. This page doesn't exist in Google Search Help. It may be deleted because the feature doesn't exist anymore, or the URL may be incorrect.» — Google's own error page, read with a real browser on 9 September 2026 from an address inside the EEA.
We do not know why, and we are not going to guess in public. An address may have changed the day before publication; a form may not be open yet; it may be an oversight. What we can say is that on 9 September 2026 the single door offered to European aggregators was shut, and that anyone reading this can check it in ten seconds.
What the aggregator unit and the supplier unit are
The aggregator unit is a multi-provider block reserved for what Google calls Vertical Search Services: online travel agencies, comparison shopping services, metasearch engines, directories. Inside the block, the top-ranked provider's results are expanded by default with photos, prices or star ratings; the others sit behind a list. Google states that only one aggregator unit shows at a time, and that clicks inside it lead straight to that aggregator's website.
The supplier unit is the block for businesses that sell directly. And here is the sentence the rest of this article hangs on. The supplier unit is the block that shows direct providers, and Google's documentation states that it appears only when the aggregator unit appears as well. That is not our inference; it is written twice, on the same page, in two different sections.
| Aggregator unit | Supplier unit | |
|---|---|---|
| Who it is for | comparison services, metasearch engines, online travel agencies, directories | direct providers: hotels, airlines, brick-and-mortar shops, tradespeople |
| How you get in | approval as a Vertical Search Service, relevant content, data by feed or API | two conditions: serve users in the EEA and be a direct provider |
| When it shows | for hotel, flight, long-distance train or bus, and product queries | only when the aggregator unit shows |
| How much Google writes | 799 words, 20 bullet points, 11 links | 240 words, 2 bullet points, 3 links |
The rule that defined the set
A count without a rule is an anecdote. The rule here: the two Google Search Central pages describing the new EEA units, downloaded on 9 September 2026 from an IP address inside the European Economic Area — Cluj-Napoca, Romania — each requested twice, once in English and once with hl=it, plus the pages they send you to and that a business would have to open, plus the February 2024 Search Central post on the same subject as a control.
The vantage point matters: these blocks exist only for people searching from inside the EEA, so reading them from elsewhere would not be the same measurement. The count is on the article body — no sidebar, no menu, no footer. Anyone who wants to repeat it needs two addresses and ten minutes.
Google gives the aggregator's page 799 words and the supplier's 240
On 8 September 2026 Google published two documentation pages describing the two new blocks that appear in search results across the European Economic Area. One is addressed to comparison sites and online travel agencies, the other to businesses that sell directly: the hotel, the airline, the plumber. We downloaded both on 9 September and counted the words in the article body, with no navigation and no footer.
Source: Cittago count on the body of the two Google Search Central pages about the EEA units and on the official February 2024 post, downloaded on 9 September 2026 from an IP address in the EEA · cittago.com
| words in the page body | |
|---|---|
| Aggregator unit page | 799 |
| Official post, February 2024 | 596 |
| Supplier unit page | 240 |
What Google asks of an aggregator
The aggregator page is an operational page. It says you are eligible when you are approved as a Vertical Search Service, you have relevant content and you provide data; then it lists the formats one by one. Lodging Point of Interest Feed for hotels. Transport features API for ground transport. Partner standard Live API for flights. For products, the guide on showing product pages across Google.
There is a best-practices section with six items — rich entity details, accurate titles, high-quality imagery, current pricing and availability, specific categories, performance monitoring in Search Console — and one recommendation worth quoting in full, because it describes a craft: «avoiding all caps, excessive punctuation, emoji, or promotional text (such as «BEST DEALS» or «Free shipping») in entity names».
All four action words are missing from the supplier's page
In technical documentation the words that matter are the ones telling you to do something: fill out a form, send a feed, connect an API, express interest. We counted them in the body of both pages. The aggregator's page has all four, with links to the data formats. The supplier's page has none: two conditions to satisfy and no step to take.
Source: Cittago count of the action words in the body of the two pages, read in English on 9 September 2026; the Italian page does not exist · cittago.com
| occurrences in the page body | |
|---|---|
| Aggregator · «form» | 7 |
| Aggregator · «feed» | 6 |
| Aggregator · «API» | 4 |
| Aggregator · «express interest» | 3 |
| Supplier · all four | 0 |

What it asks of you, if you sell directly
The supplier page has a section headed «How to participate in the supplier unit». Under that heading sit two conditions: your website must serve users in the EEA, and your business must be a direct provider. No form. No feed. No API. No box to tick.
In one sense that is good news: the documentation says plainly that the supplier unit needs no data feeds beyond standard crawling. If Google can read your site, you are already inside the perimeter. In another sense it is the thing that should raise an eyebrow: your only way in is organic ranking, and that ranking only counts inside a block that shows up when a different block shows up.
- What you actually need, per the documentation: a crawlable website, content relevant to the query, and the right kind of business. End of list.
- What you do not need: a feed, a contract, a technical integration, enrolment in a programme.
- What you cannot control: whether the block that hosts you shows at all, because that depends on the aggregator unit being there.
- Where the one operational link goes: to Hotel Center, the infrastructure Google uses for hotel prices and bookings, where free placements and paid ones live in the same card.
That last point deserves precision, because it is where a documentation page turns into a budget decision. The supplier page carries three links. Two are definitions. The third — the only one that asks you to do anything — is «Learn more about supplier feeds» and lands on the Hotel Center starter guide. The block about you asks for nothing; the door next to it does.
The page about you does not exist in your language
Both pages are in English. Nothing odd about that on its own. The right question is not whether a translation exists but whether the translation machinery sees these pages at all. We requested both with hl=it: the final address drops the parameter, the page attribute stays lang=«en», and the body is identical character for character to the English version — 5,300 characters in both requests.
For the comparison to be honest it needs a control. We requested three older pages of the same documentation the same way: structured data for articles, local business, site names. All three keep hl=it, are in Italian, and carry a language selector listing 18 locales. The two new pages carry zero. The translation is not late; these pages are outside the system that translates.

The word that appears in neither page
These blocks exist for a specific reason, and the reason has a name. On 23 July 2026 the European Commission adopted two non-compliance decisions against Google under the Digital Markets Act, with a fine of €460 million for self-preferencing in Google Search and one of €430 million over Google Play restrictions — €890 million in total. The Commission writes that Google «gives preferential treatment to its own services, including shopping, hotels, transport and sports results, over those of third parties».
In the body of the two documentation pages, «DMA» appears zero times. «Digital Markets Act» zero. «Regulation» zero, «law» zero, «compliance» zero. We searched in five different forms and checked the opposite as well, to make sure the method worked: «EEA» appears four times in each, «aggregator» twenty-five times in the first, «supplier» twelve in the second. In the raw HTML the string «dma» survives in exactly two places: the class name of the Google wordmark, and the address of the form that returns 404.
The control makes it more interesting, not less. The post in which Google announced the first version of these blocks, in February 2024, does name the DMA — once as an acronym, once in full — inside 596 words. Two and a half years later, on the pages describing the new version, it is gone. That is a change of register rather than a mistake, and there is no conclusion to draw from it: we record it because somebody reading documentation cold has no way of knowing why the page exists.
What these numbers do not say
This is the part we care about most, because an honest count is the easiest thing to misuse. None of the figures here measure traffic, bookings or money. They measure how much Google writes, and to whom.
- They do not say what you lose. The figures published on 8 September 2026 — a 30% drop in free direct booking traffic to European businesses, «the largest reduction in quality of service in Search's 29-year history» — are statements by a Google official reported by Reuters on 8 September 2026. They are not something we can verify, and we do not treat them as if they were.
- They do not say a short page is a bad page. If there is nothing to do, saying so in 240 words is correct. The measurable fact is different: the section is called «how to participate» and contains no verb aimed at you.
- They do not say when you will see this. Neither page carries a date, names the countries where the rollout is complete, or mentions a percentage of users.
- They are not a compliance assessment. Whether this arrangement satisfies the Digital Markets Act is for the Commission and the courts, not for a word count. We do not give legal opinions.
- They do not cover restaurants yet. The documented verticals are hotels, flights, long-distance trains and buses, and products. Local queries are announced as coming later, with no date.
Three thresholds, to work out whether this is about you
Not a conclusion — three diagnoses. Take the one you recognise.
First threshold — under 20% of bookings come through your own site. Then little changes for you: you were already inside the intermediary channel, and the aggregator block is, in practice, where you already were. The useful move is dull and everybody postpones it: open Search Console and check whether queries carrying your own name still land on you.
Second threshold — the direct channel is worth between a fifth and a half. Here «the supplier unit appears only if the aggregator unit appears» stops being trivia and becomes a planning problem. This is the moment to know how much of your demand is branded (people searching your name) and how much is generic (people searching «hotels in Florence»), because the two behave differently and only the second passes through these blocks.
Third threshold — direct is the majority and you want to defend it. Then the only lever left under your control on that same results page is the paid one — and that is the part of the work where we run Google Ads campaigns for businesses that sell direct. It is not a universal rule: if branded demand is already strong and the bookings arrive, buying that name back is an elegant way of paying twice for the same guest. Who does not need this: a single property, a name people search for, and a calendar full since March.
We will talk about this again in 3–6 months 😉
Questions with answers we think are useful
These are the questions we asked ourselves while reading the two pages, answered as the documentation answers them — or with a note that it does not.
What is Google's aggregator unit?
What is the supplier unit?
What do I have to do to appear in the supplier unit?
Does the aggregator application form work?
Do these pages exist in other languages?
Do the pages say why these blocks exist?
Are restaurants affected?
Do I need to buy ads to fix this?
Where do the numbers in this article come from?
Last updated: 9 September 2026. Every count and quotation in this article comes from the two Google Search Central pages on the aggregator unit and the supplier unit, downloaded on 9 September 2026 from an IP address inside the European Economic Area, each requested in English and with hl=it, plus the February 2024 official post on the same subject and three older pages of the same documentation as a language control. Neither new page carries a last-updated date, so the only certain date here is the date we read them. No figure comes from an advertising account.
Sources: Google · Aggregator unit in Google Search · Google · Supplier unit in Google Search · Google · New Search experiences in the EEA (February 2024) · Google · Hotels starter guide (Hotel Center) · Google · the aggregator form · European Commission · €890 million fine on Google, 23 July 2026 · Search Engine Journal · the EEA rollout, 8 September 2026
Free analysis
How much of your booking demand <em>goes through somebody else</em>?
Half an hour with a senior strategist, Search Console open: we look together at how much of your demand is branded and how much is generic, and what the new blocks change for you. No change of supplier required.
Book the analysis

