Google Is Changing Local Search in Europe: What Aggregator and Supplier Units Mean for Brands

Google local search in Europe is becoming more layered. On September 18, 2026, Google Search Central confirmed that aggregator units and supplier units now support local business queries in the European Economic Area (EEA).

This matters because a local-intent query can now expose several discovery layers at once: classic organic listings, Maps and local experiences, an aggregator unit, and a direct supplier unit. The shift is not a global ranking update. It does, however, change what visibility can mean for brands serving European users.

What exactly changed?

Google updated its documentation on September 18, 2026, to state that aggregator units and supplier units now support local business queries in the EEA. Local businesses join hotels, flights, ground transportation, and products among the query areas where aggregator units can appear for eligible users in that region.

The regional boundary matters. Google describes this experience as available to users in the EEA. Brands should not treat the documentation update as evidence of a worldwide rollout. They should also avoid interpreting it as a new ranking-system announcement. It is a change in the search surfaces available for certain queries and users.

What is an aggregator unit?

An aggregator unit is a multi-provider search feature for approved Vertical Search Services (VSSs). These services can include directories, metasearch engines, online travel agencies, and comparison platforms that help users evaluate multiple providers.

Within the unit, one aggregator's results can be expanded by default. Users can then switch between participating providers. When a user selects a result, the click leads to the aggregator rather than directly to the underlying local business.

For local business queries, eligible aggregators populate the experience through direct feed integrations, including Local Point of Interest feed data. Participation is not automatic. An aggregator must be approved as a VSS and meet the relevant integration requirements.

What is a supplier unit?

A supplier unit is designed for direct providers. That can include restaurants, salons, clinics, local retailers, attractions, local service companies, individual hotels, and other brick-and-mortar or service businesses that fulfil the user's need directly.

The supplier unit appears alongside the aggregator unit. It only appears when the aggregator unit appears, so it is not an independent feature that should be expected on every local query.

For direct suppliers, Google says no additional data submission is required beyond the information it can access through normal web crawling. Supplier results may still be enhanced with feeds, but a direct business does not need the same VSS approval and feed integration required of an aggregator.

Eligibility should not be confused with guaranteed inclusion. Crawlable information gives Google the material it may use to understand and represent a business. It does not promise that the business will appear for a particular query.

The key difference between aggregators and direct businesses

The distinction is operationally important:

Aggregators therefore have an explicit participation path. They need VSS approval and, for local business queries, suitable Local Point of Interest feed readiness.

Direct suppliers have a different path. Their crawlable website information can make them eligible, while feeds can improve the result. This makes accurate, accessible business information important, but it does not turn structured data into a shortcut.

LocalBusiness structured data can help machines understand a page, when it accurately reflects visible content. It should not be framed as a guarantee of supplier-unit inclusion. Schema is one part of technical clarity, not an admission ticket.

Why this matters for local SEO

Local SEO reporting often compresses performance into a small set of rankings. That model can understate the real search landscape when one query presents several ways for a user to discover a business.

For the same local-intent query, a brand can be:

• present or absent in classic organic results
• visible in Maps or a local pack
• surfaced directly in a supplier unit
• represented indirectly through one or more aggregators

A brand can now be visible in traditional organic results, Maps, a direct supplier unit, and indirectly through multiple aggregators for the same local-intent query. Measuring only rank position increasingly misses the real search landscape.

Local search share should therefore be measured by surface, not just position. Teams need to record what appeared, who occupied it, how the brand was represented, and where the resulting click would take the user.

Why this matters for directories and marketplaces

For VSSs, aggregator-unit visibility is becoming a distinct competitive layer. Approved aggregators can compete within the same module, with one provider expanded by default and alternatives available for users to select.

Directories should treat this as a product and data-quality challenge as much as an SEO task. Search, engineering, partnerships, and catalogue teams may all need to contribute.

Why this matters for direct brands

For restaurants, salons, attractions, local retail, clinics, service providers, hotels, and similar businesses serving EEA users, the update reinforces the value of basic crawlability and accurate business information.

Google can use information available through normal web crawling when considering direct suppliers. A business website should therefore make core facts easy to access and interpret: what the business is, where it operates, when it is open, what it offers, and how a user can take the next step.

None of this guarantees supplier-unit visibility. It creates a stronger information foundation from which Google and participating aggregators can understand the business accurately.

A local visibility audit brands should run now

Brands and platforms can turn the update into a focused audit:

• Identify important local-intent query groups by market and city.
• Check whether aggregator and supplier units appear for those queries when tested from relevant EEA markets.
• Record which aggregators are present and which one is expanded by default.
• Check whether the brand appears as a direct supplier when the supplier unit is shown.
• Compare the brand's website information with its listings across the key aggregators in that market.
• Confirm that name, category, location, opening hours, and pricing or availability where relevant are accurate and crawlable.
• For aggregators, assess VSS eligibility and Local Point of Interest feed readiness.
• Track changes by geography because this is an EEA-specific experience.

What brands should not conclude

The documentation update is meaningful, but several conclusions would go beyond what Google has said:

• This is not a global local-search rollout.
• This is not a new ranking-system announcement.
• LocalBusiness schema does not guarantee supplier-unit inclusion.
• Appearing inside an aggregator does not mean the brand itself has direct supplier visibility.
• The feature should be tested in the actual EEA markets and query sets that matter to the business.

The right response is to measure the surfaces that appear, improve the accuracy of business data, and monitor changes without promising inclusion.

The DareAISearch POV

At DareAISearch, we think this is another example of why search visibility has to be measured as a multi-surface system, not a single rank. For a local query, brands can compete across traditional organic results, Maps, direct supplier units, aggregator units, and AI-generated discovery surfaces.

We call the required capability Regional Search Surface Intelligence. It gives teams a market-specific view of how discovery is assembled rather than reducing visibility to one universal search results page.

DareAISearch should help brands understand:

• which surfaces appear for each query
• which competitors occupy each surface
• which aggregators influence discovery
• whether the client appears directly or indirectly
• how visibility changes by geography
• which technical or data gaps may be suppressing discoverability

The bigger shift

Google Search is becoming more modular and more region-specific. Search visibility is no longer one universal results page reproduced consistently across markets. Different geographies can expose different surfaces, eligibility rules, providers, and competitive sets.

For international brands, this makes geography-specific search intelligence essential. A strategy based on screenshots from one market or a single rank-tracking location can miss important discovery paths elsewhere. Teams need local query sets, local observations, and a clear model of the surfaces that matter in each region.

As search platforms combine organic results, maps, comparison modules, direct providers, and AI-generated answers, discovery becomes a system of connected surfaces. Brands need to know where they are represented directly, where an intermediary represents them, and where competitors control the path to the customer.

From rank tracking to discoverability

The September 18 update does not rewrite local SEO overnight. It adds another layer that brands, directories, and marketplaces serving EEA users should understand and monitor carefully.

The practical response is straightforward: validate what appears in the markets that matter, make business information accurate and crawlable, assess aggregator readiness where relevant, and measure visibility across every meaningful surface.

Brands should stop asking only, “Where do we rank?” and start asking, “Across which search surfaces are we actually discoverable in each market?”

DareAISearch helps brands measure, understand and improve visibility across traditional search, AI Search and emerging discovery surfaces. As Google adds more regional and modular search experiences, DareAISearch gives teams a unified view of where they appear, where competitors are winning, and what actions can improve discoverability.