Google's EEA Local-Business Units Need a Role Check, Not an AEO Rewrite

On 18 September 2026, Google updated the documentation for two European Economic Area search-result features to include local-business queries: the aggregator unit and the supplier unit.

That sounds like a local AEO announcement. It is not.

It is a narrowly scoped Google Search feature with two different participation paths. An approved directory, comparison service or online travel agency may be an aggregator. A hotel, plumber or other direct provider may be a supplier. The distinction matters more than a new checklist of markup or generic “AI visibility” advice.

For a local business, the practical question is: what role do we actually play in this feature, for which users, and what evidence can we collect? Start there before changing a feed, publishing more pages or reporting an AEO gain.

What changed, and what did not

Google's September documentation update says that both units now support local-business queries. The feature documentation puts both units in the EEA for queries concerning hotels, flights, long-distance trains or buses, products and local businesses.

That scope is important. It is not a statement that every local business globally has a new result type, and it is not an announcement of a new answer-engine ranking signal.

Google's regional feature guide separates several country-specific search experiences. The aggregator and supplier units are EEA features. The same guide lists different features for places sites in Türkiye and structured-data carousels in several regions. Treat a feature's region, query type and business role as part of its eligibility criteria, not as incidental footnotes.

Google's generative-AI guidance has a related but separate message: local-business information can be included in generative responses where appropriate, and Google Business Profile and Merchant Center can help make business and product information visible in Search. It also says there is no special structured-data requirement for generative AI search. Do not turn the September unit update into a claim that a new local schema type, feed or directory listing earns a place in AI Overviews or AI Mode.

Know which unit fits the business

The aggregator unit is for Vertical Search Services: online travel agencies, comparison shopping services, metasearch engines and directories. It lets eligible aggregators populate a result unit for a relevant query, and clicks go to that aggregator's site. Google says only one aggregator unit shows at a time, with the top-ranked provider expanded by default.

An aggregator is not simply a business that aggregates its own locations. The published eligibility path includes approval as a Vertical Search Service, an expression-of-interest form, relevant query content, required data and compliance with Google's content policies. For local-business queries, Google points participating aggregators to its Local Point of Interest Feed documentation.

The supplier unit is the direct-provider path. Google's examples include individual hotels and airlines, brick-and-mortar business owners and service providers such as plumbers. It appears alongside an aggregator unit, and Google says it appears only if the aggregator unit appears.

The supplier requirements are narrower but not automatic: serve users in the EEA and be a direct provider relevant to the listed query categories. Google says a supplier does not need to provide extra data beyond what web crawling can access, although available supplier feeds can enhance results.

That gives a small team an unglamorous but useful decision tree:

1. Are we a direct provider, or do we operate a genuine comparison, directory or metasearch service?
2. Do we serve users in the EEA for a supported query category?
3. If we are an aggregator, do we have the relevant content and reliable data-feed capability?
4. If we are a supplier, can Google crawl pages that accurately state the entity, service, availability and destination details?
5. Can we distinguish this regional Search exposure from independent AI-answer visibility in reporting?

If the answer to the first two questions is no, this update should not trigger an implementation sprint.

Build source data before chasing the surface

For an eligible aggregator, Google's documentation is unusually concrete about the operational burden. Local-business units are populated through direct data-feed integrations. Google recommends rich entity details, factual and descriptive titles, original high-quality imagery, and up-to-date pricing and availability. These are data-quality requirements for a Search unit, not evidence that a model has cited a page.

For a direct provider, the immediate work is simpler: check the crawlable site that Google can already see. Make sure entity names, locations, categories, operating hours, service details and landing-page claims agree with the business's maintained source of truth. If a supplier feed is available, treat it as an enhancement path that needs its own reconciliation process. A feed containing stale availability or inconsistent names can create a customer problem even if it changes no organic rankings.

This is also where overfocusing on markup becomes expensive. Google explicitly says the supplier path needs no additional data beyond crawlable web content, and its generative-AI guide says there is no special schema markup required for generative AI Search. Continue to use supported structured data where it matches a real search feature, but do not invent a “supplier-unit schema” project from a documentation update that does not require one.

Keep four observations separate

A local business can see several kinds of exposure around the same query. They should not be collapsed into one dashboard score.

First, record whether the EEA feature is even eligible for the business role and country. Second, record any observable aggregator or supplier-unit presence with the date, location and query context. Third, keep Google Search and Search Console performance in their own report. Fourth, maintain a fixed set of independent answer-engine prompts to observe non-paid mentions, citations and accuracy outside Google's regional unit.

For that fourth record, a small team can sample manually. For repeatable checks across supported answer engines, CiteCue can rerun a stable prompt set, inspect non-paid brand mentions and citations, and create follow-up work from supported findings. Disclosure: AEO Landscape and CiteCue are commonly owned; read our full disclosures. CiteCue is not a Google feed validator, a supplier-unit status source or first-party evidence about how Google's systems selected a result. Its useful role here is to prevent independently observed answer visibility from being mixed with a regional Search feature.

This boundary produces better questions. If a supplier unit becomes visible while the independent prompt sample stays flat, that is not a failed AEO test; it is evidence about two different surfaces. If a prompt sample changes while no unit appears, investigate content, crawlability, reputation signals or normal answer variation before assigning the cause to this feature.

Google's Generative AI performance report is another separate observation. It reports URLs that appeared in Google Search and Discover generative-AI features, along with dimensions such as pages, countries, devices and dates. It does not replace checks of the EEA aggregator or supplier units, and it does not measure other answer engines.

Use a small, dated rollout record

For an eligible business, record the region, business role, relevant query group, data source, crawlability checks and any feed owner before making a change. Then document the observed result surface with date and location. This matters because the supplier unit appears only when the aggregator unit does, and Google does not promise every qualified business will appear.

For aggregators, add the expression-of-interest step and data-feed validation to the same record. For suppliers, record any feed enhancement separately from the crawlable-site baseline. In both cases, preserve a before-and-after snapshot of titles, images, availability and landing-page claims so a customer-facing discrepancy is traceable.

The right conclusion is deliberately modest: Google has opened an EEA local-business route with distinct paths for aggregators and direct providers. It may matter a great deal to an eligible business. It does not justify a universal AEO rewrite, a promised visibility outcome or a new category of unsupported optimization claims.

Sources and verification

• Google Search Central: Latest documentation updates
• Google Search Central: Aggregator unit in Google Search
• Google Search Central: Supplier unit in Google Search
• Google Search Central: Regional differences in Search experience
• Google Search Central: Optimizing your website for generative AI features on Google Search
• Google Search Central: Introducing Search Generative AI performance reports in Search Console

Sources checked 20 September 2026. The feature scope, eligibility conditions and reporting capabilities above are attributed to the Google sources. The role check, data workflow and measurement boundaries are AEO Landscape editorial analysis.