Google adds 'things to do' queries to its EEA search units
Summary
Google's aggregator and supplier units, the booking-style result blocks shown to searchers in the European Economic Area, now cover "things to do" queries, so tour and attraction businesses serving the EEA are eligible.
Direct sellers should confirm their activity pages are crawlable and indexable, since the supplier unit asks for no feed, no form and no markup.
Google added “things to do” query support to the aggregator unit and supplier unit documentation on 9 November, both of which are European Economic Area features. Search Engine Roundtable flagged the entry, noting the phrase now appears throughout both help pages.
The two units are what EEA searchers get for queries like “hotels near me”. The aggregator unit carries approved vertical search services, meaning the comparison and booking sites, while the supplier unit carries direct providers: the hotel, the airline, the tour operator itself. Between them they now cover hotels, flights, long-distance trains or buses, products, local businesses, and things to do.
For a tour or attraction operator selling direct, the bar is low. Google’s supplier unit page says a business does not need to provide additional data beyond what is accessible through web crawling to appear in the feature, and that supplier results can be enhanced with data feeds where those exist. No schema.org type is named anywhere on it, which puts this in the group of features where structured data is not the lever.
The aggregator side has real requirements, and they are not markup either. A site has to be approved as a vertical search service, hold relevant content for the query category, comply with Google’s Search content policies, and then apply through the Google Search Aggregator Features form. Things to do data goes through Google’s feed for local business and activity listings, the Local and things to do Point of Interest Feed. The page does not say so directly, but it lists a separate feed per vertical, so an aggregator already approved and feeding the Lodging Point of Interest Feed for hotels would have to supply the other feed to compete on activity queries.
The same two units gained local business queries on 18 September, in near-identical changelog wording. The likelier explanation is that Google is extending two existing containers vertical by vertical rather than building new EEA placements, so the next expansion will arrive as one changelog line and not as a new help page. That makes the changelog feed the thing to watch here.
Placement that Google hands to third parties is scarce enough in travel to be worth the paperwork. In AI Mode, by contrast, flight answers link only to Google Flights.
What to do
- If the business sells tours, tickets or attraction entry and serves EEA users, read the supplier unit page and confirm the activity and ticketing pages are crawlable and indexable. There is no form to submit and no feed to build for that path.
- If the business is a marketplace or comparison site for activities, start with the Google Search Aggregator Features form and vertical search service approval, then the Local and things to do feed. Budget for an approval cycle, not a deploy.
- If the site serves no EEA traffic, there is nothing to do. Neither unit appears outside EEA countries, and the eligibility change does not reach other markets.