Key Takeaway
Google's September 2026 documentation added local business queries to Aggregator and Supplier Units in the EEA. Direct providers should prioritize crawlable local pages and consistent business facts for Supplier Unit eligibility. Eligible directories and booking platforms follow the Aggregator path, including approval, direct merchant relationships and a daily full Local POI Feed. These roles are not interchangeable, and markup alone guarantees neither eligibility, rankings nor AI citations.
Facts and background
Google's September 18, 2026 documentation update added local business query support to Aggregator and Supplier Units, following the September 8 regional-search documentation. This concerns EEA result features, not a new worldwide ranking signal or AI citation tag.
Local queries may concern restaurants, beauty services, attractions and other offline activities. First identify the business role: direct store operators or service providers are suppliers; services comparing or booking multiple merchants through their own landing pages are aggregators. That distinction determines eligibility, data and acceptance requirements.
Keep the two participation paths distinct
| Role | Primary route | Eligibility | Data route | Click destination |
|---|---|---|---|---|
| Brand-owned locations, local businesses and direct service providers | Supplier Unit | Serves EEA users and directly provides the relevant goods or services | Crawlable web pages; optional feeds may enhance results | The direct provider's website |
| Directories, booking platforms, vertical search and comparison services | Aggregator Unit | An approved Vertical Search Service with direct merchant contracts and required quality standards | Participation application and structured entity data through a Local POI Feed | The aggregator's own landing page |
Google describes the Supplier Unit as a feature for direct providers, including store owners, hotels, airlines and service businesses such as plumbers. It appears only when an Aggregator Unit also appears. Crawlable web content can supply the required data; optional feeds may enhance presentation but do not replace accurate, accessible pages.
Aggregator Units serve vertical search services such as directories, metasearch, booking and comparison platforms. The cited documentation describes one unit at a time, with the highest-ranked provider expanded by default and clicks leading to that provider. Participation requires relevant content, necessary data and quality compliance; local-business integration also requires an application and Local POI Feed.
Make each direct-provider page a verifiable business record
An optional feed does not remove the need for data governance. Give each location or service area a stable URL with its name, category, address or service area, phone, hours, services, pricing conditions, booking or purchase path, market and language. Connect headquarters, country and location pages through a clear hierarchy and internal links.
Use accurate entity names rather than unverifiable 'best nearby' or 'number one' templates. Images should represent the actual business. Keep prices, stock, operating status and booking availability current. Correct data in one system does not establish consistency across the page, schema, maps and product or booking feeds.
Aggregator participation requires ongoing data operations
The cited local VSS process covers account setup, sandbox feeds and review, production feeds and review, then launch. Applicants must be qualifying aggregators, not simply a single chain, with direct relationships to listed merchants. Google's documentation states that POI data populates the partner's own unit, not other Google services or competitors' units.
The cited POI workflow requires a complete daily refresh through SFTP using one consolidated JSON feed, preferably gzip-compressed. Do not create separate files per entity or unrelated country feeds. Core fields include a stable poi_id, name and location; phone, URL, address, images, ratings, categories, description, hours, price range and landing pages improve entity completeness.
Localization means more than copying an English name. POI records can include a default language and localized names, descriptions, display addresses and landing URLs. Keep each version tied to the same entity and its intended language and market; inconsistent names, addresses or URLs impede reconciliation.
Reconcile pages, entity master data and feeds
Use a stable location or service-point ID to connect CMS pages, master data, structured data, booking or product systems and POI feeds. Reconcile names, addresses, coordinates, phone numbers, categories, hours, prices and URLs field by field. Aggregators should also track contract status and remove merchants whose participation has ended.
| Check layer | Pass evidence | Common failures |
|---|---|---|
| Role and eligibility | Documented direct-provider or aggregator relationship and clear EEA service scope | A single brand presented as an aggregator, or an undocumented merchant relationship |
| Page discovery | Location pages return HTTP 200, allow crawling and are linked from country or directory pages | Discovery requires client-side interaction, a map popup or a search form |
| Entity consistency | Names, addresses, coordinates and URLs agree across pages, schema, master data and feeds | Duplicate IDs, old addresses, incorrect coordinates or mismatched language links |
| Feed operations | Daily full feed delivered on time, with valid formatting, images and landing pages | Partial updates presented as full feeds, fragmented country feeds, broken images or obsolete merchants |
| Results validation | Search Console and query samples can be matched to page and feed versions | One appearance used to claim comprehensive coverage, ranking gains or growth |
Separate eligibility from observed display
Keep Search Console monitoring, prices and availability current. The public guidance promises no fixed display frequency, position or launch deadline. Because Supplier Units depend on Aggregator Unit appearance, an absent feature does not by itself establish a technical failure on an otherwise eligible page.
Retain country, language, device, query, date, screenshot, landing URL, page version and feed batch. Record eligibility documentation, feed receipt, production approval, actual display, clicks and conversions as separate stages. Only comparable repeated samples can support incremental-effect analysis; one screenshot proves neither coverage nor ranking or AI-citation gains.
Impact on enterprises
The expansion adds a distinct discovery surface for brands with EEA locations, distribution networks or local services. Direct providers can begin with crawlable landing pages; qualifying multi-merchant platforms can evaluate Aggregator participation for their comparison or booking pages. Responsibilities must be explicit across owned locations, dealers, franchisees and third parties: who directly supplies the service, who may submit data, who maintains hours and prices, and who owns localized pages. Conflicting roles, contracts and IDs can undermine both page and feed work.
Zhihe Growth's Assessment
This is a role-specific regional-search integration, not a reason to add more local schema indiscriminately. Direct providers need verifiable local pages; aggregators need eligibility, contracts, daily POI operations and quality landing pages. Both need shared entity facts, but their deliverables differ. Separate the business paths first. Use one identity system across dealer directories, brand location pages and feeds, with change records linking pages, markup, feeds and query evidence. This article interprets the EEA support and requirements documented as of September 24, 2026. It guarantees no approval or display, and result-unit impressions are not AI citations, general ranking gains or revenue growth.
Recommended action
- Inventory owned stores, franchisees, dealers, service providers and aggregators by country and business line; identify each entity's role.
- Use stable location IDs across CMS pages, merchant master data, schema, booking or product systems and feeds.
- Provide internally linked, crawlable HTTP 200 local pages with name, category, address or service area, phone, hours and a conversion path.
- Reconcile names, addresses, coordinates, operating status, language and URLs across pages, markup, maps and pricing or booking feeds.
- Provide appropriate localized titles, descriptions, display addresses and landing pages for EEA markets, preserving entity identity across versions.
- Direct providers should prioritize crawlable pages and monitor country, query, page and date samples in Search Console.
- Aggregators should verify merchant contracts and quality responsibilities before applying for participation.
- Generate the required complete daily Local POI Feed and retain delivery times, validation results, versions and rollback evidence.
- Automate checks of direct image URLs, formats, sizes, landing responses and localized URLs; remove closed or departed merchants promptly.
- Accept eligibility, feed receipt, production approval, display, clicks and conversions separately. A screenshot is not evidence of full coverage or growth.
Limitations
This article reflects official material accessible on September 24, 2026. These result features serve EEA users; display depends on queries, markets, devices, supply quality and Google's selection. Supplier Units appear only with Aggregator Units, and eligibility promises no fixed position, frequency or launch time. Supplier results can rely on crawlable pages, with optional feed enhancements. Local-business Aggregator participation requires approval and the specified integration and POI process. Google determines individual partner approval, account requirements, data validation and production launch. The update expands supported query scope. It does not create a universal ranking signal, schema guarantee, AI-citation mechanism or revenue-attribution model. Interpret Search Console, query samples, feed receipts and conversions separately; do not extrapolate the rules to other regions, products or AI platforms.