Google Local Business Aggregator & Supplier Units: What Changed in September 2026
Google documented local-business query support for aggregator and supplier units on September 18, 2026. In the EEA, approved Vertical Search Service aggregators can participate by meeting eligibility, quality and Local Point of Interest feed requirements. Direct suppliers such as individual local businesses follow a different path: Google says supplier-unit eligibility can rely on information accessible through web crawling, with supplier feeds optional where available. This is not a generic ranking boost, and adding LocalBusiness schema by itself does not guarantee appearance in either unit.
You operate a local-business marketplace, directory or booking platform serving EEA users
You saw Google's September 2026 local-business aggregator-unit documentation and are unsure whether it applies to your site
You are considering adding LocalBusiness schema because you think it automatically enables the new unit
Your platform already maintains a structured catalog of local points of interest and needs to understand Google's feed requirements
Possible causes
Google expanded its aggregator and supplier unit documentation to include local-business queries
The experience is available in the EEA and separates multi-provider aggregators from direct suppliers
Aggregator participation depends on VSS approval, quality standards and Local POI data, while supplier-unit eligibility can use crawlable website information
Search documentation, structured data and commercial feed integrations are easy to confuse even though they serve different systems
HOW TO FIX IT
Work from the safest step to the harder repair.
Step 1. First identify which role you actually have. A marketplace, directory, OTA or metasearch product may be an aggregator; an individual brick-and-mortar business or service provider may be a direct supplier. The requirements are not identical.
Step 2. If you are pursuing the aggregator unit, read Google's VSS eligibility, content-policy and data requirements before changing production code. Local-business aggregator participation requires approved VSS status plus the applicable Local Point of Interest feed; it is not enabled by a meta tag, sitemap flag or schema property.
Step 3. If you are a direct supplier, keep the business website accurate and crawlable. Google's supplier-unit documentation says no additional data beyond crawlable website information is required to be eligible, although supplier feeds can enhance results where available.
Step 4. For an aggregator feed, inventory only businesses you can represent truthfully and consistently. Use persistent identifiers and keep names, locations, categories, URLs and other supplied attributes synchronized with the source of truth.
Step 5. Review Google's Local POI feed specification and Actions Center onboarding requirements for the exact aggregator use case. Do not invent availability, pricing, ratings, booking actions or other commercial attributes merely to make records look complete.
Step 6. Keep ordinary organic-search SEO separate from these units. Continue serving useful pages with accurate metadata, canonicals, internal links and page-appropriate structured data whether or not the site participates in an aggregator or supplier unit.
Step 7. Validate deduplication and entity matching. An aggregator should avoid producing multiple feed records that represent the same physical business unless Google's specification explicitly calls for distinct entities.
Step 8. Create a monitoring plan for policy changes and data freshness. Aggregator feed records can become stale as businesses close, move, change names or alter availability; direct suppliers should likewise keep crawlable business facts current.
Need the actual code? Go to GenesisCodeDoctor.com to search the Code Store or request code for the exact platform, error, and repair you are working on.
Keep feed generation separate from visible-page structured data so one integration cannot silently overwrite the other.
Validate required fields and identifier stability before pushing records to a production feed.
Log source timestamps for changing facts such as availability and pricing so stale records can be detected and removed.
STOP AND GET HELP WHEN
Do not turn a repair into a larger outage.
Do not build a Local POI feed merely because a direct supplier wants to appear in the supplier unit; Google says crawlable website information can be sufficient for supplier eligibility.
Do not treat LocalBusiness JSON-LD as a substitute for Google's aggregator VSS approval and Local POI feed requirements.
Do not publish fabricated prices, availability, reviews, ratings, locations or booking relationships to satisfy a feed field or search feature.
HOW GENESIS HANDLES IT
Diagnose the exact failure before choosing a repair.
Genesis separates the visible symptom from the underlying technical cause. Run the supported diagnostic first, review the evidence, and then use a matching repair only when the failure is actually verified.
Platform scope
EEA local-business aggregators, marketplaces, booking platforms and eligible direct suppliers
Category
Google Search · Current changes
Last updated
2026-09-22
REPAIR PROFILE
Know the complexity before you edit.
Difficulty
Intermediate
Change risk
Low
These labels describe implementation complexity and blast radius, not a guaranteed repair time.
AUTHORITATIVE SOURCES
Verify time-sensitive platform details at the source.
Does every local business need to change its website because of Google's September 2026 update?
No. The units are documented for users in the EEA. A direct supplier should keep its business information crawlable and accurate; an aggregator has a separate VSS approval and feed path.
Will LocalBusiness schema make my site appear in an aggregator or supplier unit?
No guarantee. Structured data can help search systems understand a page, but Google documents separate participation rules for the units. Aggregators need the applicable VSS approval and data feed, while direct suppliers can be eligible from crawlable website information.
Is this a worldwide Google Search feature?
Google documents aggregator and supplier units as an EEA search experience. Do not describe it as a universal worldwide feature unless Google expands the program and updates its documentation.
Once you know the platform and the verified problem, search the Genesis Code Doctor Code Store for a matching package. If the exact integration or repair is not there, use Request a Code and describe the platform, official documentation, desired behavior, and sanitized error—never send your secret key.
Start with a free diagnostic. If Genesis verifies a problem and a compatible treatment exists, continue to the matching Code Store product or repair path. If you cannot find the exact code you need, request it at GenesisCodeDoctor.com rather than forcing a generic snippet into the wrong platform.
GENESISCODE DOCTOR AI