Google Adds “Things to Do” Support to Two EEA Search Units
Google updated two help documents to state that both the aggregator unit and supplier unit now support “things to do” queries, adding EEA-focused guidance for searches such as “hotels near me.”

- Google updated two EEA help documents: the aggregator unit and supplier unit pages.
- Both units now support “things to do” queries, according to Google.
- Google names one example query, “hotels near me,” for EEA users who may notice changed experiences.
- Businesses can express interest in the aggregator unit or participate in the supplier unit.
- The source provides no rollout date, traffic figure, ranking shift or coverage percentage.
Google updated two help documents to state that the aggregator unit and supplier unit now support “things to do” queries, extending an existing Google Search query class into guidance for two European Economic Area (EEA) features.
The search company’s notice is explicit: “Updated the aggregator unit and supplier unit documentation to include support for ‘things to do’ queries.” That confirms a documentation revision. It does not mark the arrival of a new query category, because Google Search already supported “things to do” queries before this update.
Google also wrote: “The aggregator unit and supplier unit now support ‘things to do’ queries.” The phrase appears throughout both help pages rather than in one appended note. For businesses serving EEA users, the practical change is that each unit’s guidance now addresses the query type.
What changed in Google’s documentation?
Google changed two documents: the aggregator unit page and the supplier unit page. The phrase now appears throughout both pages. The source provides no publication date or schedule showing when the newly documented support began operating for users.
The wording establishes support, not a guaranteed result. It does not say that every eligible page will appear, that a particular query will always trigger either unit, or that support will be identical across all EEA countries and languages. Those limits matter when interpreting a documentation update as a visible rollout.
“Things to do” itself is not new. What Google calls new here is the units’ inclusion of that query support in their documentation. That chronology leaves the precise start of user-facing behavior unresolved in the source.
How do the aggregator and supplier units differ?
Google describes the aggregator unit as the unit in which a business serving EEA users can express interest. Its help page explains how the unit works and how businesses can signal that interest. The same page says EEA users searching for things such as “hotels near me” may notice a changed experience.
The supplier unit offers a participation path. Google says its page explains how the unit works and how businesses serving users in the EEA can participate. It gives the same “hotels near me” example for people searching in EEA countries and again says those users may notice a change.
For site operators, those descriptions point to different actions. An aggregator-side business can review the documentation to determine whether expressing interest fits its operation. A supplier-side business can use its page to review the participation route. Google does not say that one route replaces the other.
Which vertical and users does this affect?
The travel and hotel sector supplies the only concrete search example in the source: “hotels near me.” Google ties that example to EEA users and says they may encounter changed experiences involving the two units. The announcement does not identify any other vertical with a concrete example.
EEA availability is the clearest geographic limit. Google repeatedly frames both units as features for the European Economic Area, and its business guidance addresses companies serving users there. The source does not say how many EEA countries or languages have the same experience at the same time.
The source describes the change through both query intent and site role. Support for “things to do” gives both units documented coverage for that query class, while the hotel example places the update in a local-search setting where EEA users may notice a change. It supplies no live result layout, so it cannot show how the two units appear together.
Is this a ranking update?
Google does not describe the change as a ranking update. Its wording covers query support and documentation. The source offers no dated before-and-after result, ranking-factor explanation or quantitative performance change, so it does not establish a measured algorithmic shift.
What does Google confirm?
Google confirms four connected points:
- It updated two help documents: the aggregator unit page and the supplier unit page.
- Both pages mention “things to do” support repeatedly.
- Google says both units support those queries.
- The units are EEA features with separate paths for businesses to express interest or participate.
The source does not establish:
- A dated ranking shift, traffic increase, revenue effect or new ranking factor.
- A rollout percentage, country-by-country schedule or live result layout.
- A listing guarantee or query-specific visibility for every participating business.
The source also links to a forum discussion on X, but supplies no quoted practitioner finding, screenshot or independent data from that thread. The update therefore stands as Google’s own confirmation, without measurable impact evidence.
A support statement also falls short of a visibility promise. Google has not said, in the quoted material, that a business will receive a listing, feature placement or query-specific benefit merely by expressing interest or participating. The documentation gives businesses a framework; it does not guarantee an outcome.
What should site operators monitor next?
Site operators serving EEA users should watch the two unit pages and live results for “things to do” and “hotels near me” queries. The next concrete signal will be visible aggregator and supplier output, consistent behavior across EEA markets and languages, and any measurable response from businesses using the two pathways.
Google has established documented query support. The timing, scale and commercial effect of that support remain open for measurement.
via developers.google.com (Original)
More from James Calloway
Show full bio
Market editor covering money, funding and market shifts around Search rankings and algorithm updates, generative engine optimization at SERP Journal.
220 articles