Google’s EEA Local Search Shake-Up: What The New Aggregator & Supplier Units Mean For Local SEO (And How To Win)
Google expanded its EEA “aggregator” and “supplier” search result units to include local business queries—changing how directories and local providers can appear for services, dining, and things to do. Here’s what changed, why it matters, and a practical playbook for SMEs and agencies using approved execution with AYSA.ai.
Google is continuing to rework how search results appear in the European Economic Area (EEA), and one of the most important ripple effects is now hitting local business queries. In September 2026, Google updated its Search documentation to state that its EEA “aggregator unit” and “supplier unit” now support local business queries—not just hotels, flights, trains/buses, and products.
If you run a local business, manage Local SEO for clients, or operate a directory/marketplace, this isn’t a minor footnote. It’s a structural change to how local search real estate can be allocated in EEA countries, and it may force you to rethink: (1) where you show up, (2) how you measure performance across regions, and (3) how you execute changes safely and quickly.
My perspective: the winners won’t be the teams that “watch rankings.” The winners will be the teams that monitor SERP structure shifts, ship site improvements consistently, and build defensible demand (brand + reputation) even when Google experiments with new layouts. That’s the gap AYSA.ai is built to close: monitor, prepare, request approval, and execute the changes that actually improve outcomes.
Concise summary
- What changed: Google’s EEA aggregator and supplier result units now explicitly support local business queries (services, dining, attractions), per updated documentation.
- How it works: Approved “vertical search services” (directories, comparison services, metasearch) can appear via the aggregator unit after providing a feed; local businesses can appear in a supplier unit alongside it, typically based on what Google can crawl (feeds optional for enhancement).
- Why it matters: This can change which sites get the click, how much traffic goes to directories vs providers, and why your EEA performance may not match the same queries elsewhere.
- What to do: Segment measurement by region, improve provider pages to be “crawl-friendly and conversion-ready,” build listings/mentions strategically, and adopt an execution system (like AYSA) that ships updates with human approval.
Table of contents
- 1) The context: why Google is redesigning EEA search
- 2) What Google changed in the EEA (in plain English)
- 3) The two units: aggregator vs supplier—what they are and how they behave
- 4) Who can appear (and what “approval” really implies)
- 5) What this does to local SEO: clicks, visibility, and competitive dynamics
- 6) Measurement pitfalls: Search Console, rank tracking, and reporting across locations
- 7) Strategy for directories & vertical search services in the EEA
- 8) Strategy for local providers (SMEs): how to win when the SERP adds layers
- 9) A concrete SME scenario: a clinic, a directory, and a shifting SERP
- 10) A practical action plan (30/60/90 days)
- 11) Where AYSA.ai fits: monitoring + approved execution for local search volatility
- 12) What to do next (checklist)
- Sources and further reading
1) The context: why Google is redesigning EEA search
When Google changes search layouts, it’s easy to assume “algorithm update” and move on. But the EEA redesign is tied to something more fundamental: compliance and market structure.
According to Search Engine Journal’s coverage, Google is rolling out redesigned result units in the EEA and updating documentation as it goes. The same SEJ report notes this redesign is associated with compliance pressure under the EU’s Digital Markets Act (DMA) and references an approaching compliance deadline discussed by the European Commission (as cited by SEJ).
Even without restating legal arguments, the business implication is clear: Google is formalizing a way for approved third-party services to appear inside dedicated SERP units for certain query classes—and local is now officially one of those classes.
That matters because local search historically concentrates attention in a few highly visible placements. When the layout changes, the “default winners” can change too—sometimes overnight.
2) What Google changed in the EEA (in plain English)
Here’s the plain-English update: Google’s documentation now says that two redesigned search result units in the EEA—the aggregator unit (for approved vertical search services like directories and comparison engines) and the supplier unit (for direct providers/businesses)—now support local business queries.
In SEJ’s write-up, the change is logged as a one-line documentation update: “The aggregator unit and supplier unit now support local business queries.” The mechanics of the units didn’t change; the scope expanded to local.
What does “local business query” mean in practice? SEJ reports that Google’s documentation points to local searches involving categories like dining, services (example: beauty salons), and things to do (example: attractions). In other words, it’s not just “plumber near me.” It’s a wide slice of commercial intent queries that local businesses depend on.
The key takeaway: EEA local results can now include a directory/aggregator layer and a companion layer for the businesses themselves. That is a meaningful structural shift for how local demand is routed.
3) The two units: aggregator vs supplier—what they are and how they behave
To understand the impact, you need to understand the units at a functional level (without getting lost in jargon).
3.1 The aggregator unit: a “container” for approved vertical search services
Per SEJ’s summary of Google’s documentation, the aggregator unit is where approved vertical search services can show listings. Google describes this group as including directories, comparison shopping services, and metasearch engines.
A few behaviors matter operationally:
- Only one aggregator unit shows at a time (so aggregators compete for that slot).
- The top-ranked provider within the aggregator unit may be expanded by default (so the #1 aggregator gets disproportionate attention).
This creates a familiar pattern from other search features: a “winner takes more” dynamic, where being second isn’t close to being first.
3.2 The supplier unit: direct businesses alongside the aggregator
The supplier unit, as described in SEJ’s reporting, appears alongside the aggregator unit and shows the businesses themselves. Importantly, the supplier unit only appears when an aggregator unit does (again per SEJ’s summary of Google’s supplier page).
In practice, this means local providers are affected by aggregator presence even if they never asked for it. If an aggregator unit triggers, your visibility could be mediated by this new paired layout.
3.3 “Replaces existing units”: what that signals (and what it doesn’t)
SEJ notes that Google’s documentation says the aggregator unit “replaces existing units” on the results page for local searches, but doesn’t name which ones—and the Search Central pages referenced in SEJ’s extract do not explicitly mention the Local pack or Business Profiles in that context.
We should be careful here: we can’t claim precisely what is replaced or how often these units show, because SEJ explicitly notes Google doesn’t say how frequently the units appear for local queries, nor which aggregators have been approved.
What we can say as analysis: anytime Google introduces a new “replacement” unit, the click distribution changes. Sometimes it’s subtle; sometimes it rewires entire acquisition channels.
4) Who can appear (and what “approval” really implies)
Eligibility is where this becomes either an opportunity or a wall.
4.1 Directories and aggregators: approval + feed requirements
SEJ reports that directories/aggregators must be approved as a vertical search service to appear. For local queries specifically, applicants are directed to the same interest form used for other verticals (hotels, flights, ground transportation).
They also need to provide a point-of-interest (POI) feed containing fields like:
- Business name
- Address
- Phone number
- Category
- Images
- Ratings
There’s a crucial detail in SEJ’s extracted text: Google’s Actions Center documentation indicates that feed data is used only to populate the partner’s own unit and won’t be used for Google’s services or competitors’ units.
From a marketplace standpoint, that’s meant to lower the fear that “giving Google data” means “training my competitor.” But it also means: if you’re a directory, the feed is a product requirement. If you can’t produce a clean POI feed, you can’t compete.
4.2 Local businesses: no additional data required (but don’t misunderstand that)
SEJ reports that businesses themselves don’t have to send anything extra: direct providers don’t need to provide data beyond what Google can crawl, though feeds can enhance results.
This is where many SMEs get complacent. “Google can crawl my site” is not the same thing as:
- Google can understand your services by city
- Google can connect your Brand entity to your addresses consistently
- Users can convert quickly once they land on your page
In a world where a supplier unit appears next to an aggregator unit, your site must do two jobs: (1) be eligible to appear, and (2) close the deal fast when you do.
5) What this does to local SEO: clicks, visibility, and competitive dynamics
Local SEO has always been a competition for limited SERP attention. The EEA change adds a new set of variables that can shift the balance between:
- Directories/aggregators (who often monetize leads)
- Direct providers (who want direct bookings/calls)
- Google’s own surfaces (which may or may not be “replaced” for certain queries, depending on how this rolls out)
5.1 The “middle layer” is back
For years, many local businesses tried to reduce dependency on directories by improving their own sites, reviews, and brand demand. But when Google gives a dedicated unit to approved vertical services, a middle layer reappears in a formalized way.
This doesn’t automatically mean “directories win.” It means:
- Directories can get a more privileged position for certain queries.
- Businesses may still appear, but the context of that appearance changes.
- Click behavior may shift depending on user intent (comparison vs immediate booking).
5.2 Your competitive set may change overnight
If you’re a local business, you may have been competing against three to five local providers and a map-based pack. In EEA markets where these units show, you may also be competing against:
- Major directories that can invest heavily in feed quality and coverage
- Niche vertical sites (e.g., “best salons in X”) that become approved aggregators
- Comparison-style platforms that specialize in availability, pricing, or categories
If you’re an agency, that changes what “Share of Voice” even means. You can’t report only “client rank positions” if the SERP is allocating prime real estate to a different class of results.
5.3 Conversion rates matter more when exposure becomes less predictable
When SERPs are stable, businesses can “outwait” competitors. When SERPs are volatile, you need operational excellence: fast pages, clear calls-to-action, strong trust signals, and content that answers the question immediately.
That’s not theoretical. It’s the difference between:
- Getting the click and getting the booking
- Getting the click and sending users back to the SERP (where an aggregator is happy to catch them)
6) Measurement pitfalls: Search Console, rank tracking, and reporting across locations
SEJ makes a point that many teams will feel immediately: Search Console data and Rank tracking from EEA countries may now reflect a different search experience than the same queries elsewhere.
That sounds obvious, but most businesses still report “SEO performance” as if every country sees the same result layout. Under this change, that assumption becomes dangerous.
6.1 Search Console is not a SERP-layout reporting tool
Google Search Console is essential, but it doesn’t show you a replay of the SERP composition a user saw. If a new unit changes CTR patterns, you may see:
- Impressions staying steady while clicks drop
- Average position becoming harder to interpret
- Query patterns shifting (more brand, fewer generic queries) without obvious causes
The fix is not “panic.” The fix is segmentation plus structure monitoring.
6.2 Rank tracking must be market-specific (and device-specific)
If you track rankings, you must separate:
- EEA countries vs non-EEA countries
- City-level vs country-level intent queries
- Mobile vs desktop (layout differences matter more on smaller screens)
This is also where agencies get burned: a “global report” hides regional SERP features that reduce visibility. If your client is asking why leads dropped in France but not in Canada, the answer may be “SERP structure,” not “content quality.”
6.3 Attribution: directories can steal credit even when you created demand
When directories get more visibility, they can become the click destination even if your marketing generated the demand. The user searches for “Brand + service,” clicks a directory page about you, and then calls you. Now your “SEO lead” looks like it came from a directory—unless you have strong tracking discipline.
SEJ’s page includes references to broader measurement topics (like call attribution in AI-driven discovery). While that’s adjacent to this specific update, the same principle applies: if you don’t name the source, someone else will.
At minimum, SMEs should align on:
- Call tracking and form attribution
- UTM discipline on directory profiles where possible
- Landing-page experience by market
7) Strategy for directories & vertical search services in the EEA
If you run a directory, marketplace, or comparison site, this change is potentially massive—because Google is describing a formal pathway to appear in an aggregator unit for local queries.
But there are constraints. You don’t get to “SEO your way in” casually; you need operational readiness.
7.1 Treat the POI feed like a product, not a marketing task
SEJ notes the POI feed requires standardized business data including categories, images, and ratings. That implies you need:
- Data normalization (addresses, phone formatting, consistent categories)
- De-duplication (multiple listings for the same business will reduce trust)
- Freshness workflows (hours, closures, changes)
- Media governance (image quality and rights)
If your directory’s data is messy, an “approved unit” could amplify that mess in public—making your product look unreliable.
7.2 Optimize for “expanded by default” behavior
SEJ reports the top-ranked provider’s results may be expanded by default. That’s a strong incentive to compete for first place—because user attention will cluster there.
What would I prioritize?
- Clear, normalized categories that match local intent
- Listings that demonstrate trust (ratings with context, not just stars)
- Coverage density in major cities (users judge directories by breadth)
- Fast performance and strong UX (if the click lands on you, you must earn it)
7.3 Build fair value for businesses, or churn will follow
If directories get more exposure, there’s a temptation to raise monetization pressure. The long-term risk: providers will view you as a toll booth and invest in bypassing you.
The smart play is to strengthen your offering:
- Verified availability
- Transparent lead pricing
- Better profile controls for businesses
- Tools that improve conversion, not just “more impressions”
8) Strategy for local providers (SMEs): how to win when the SERP adds layers
If you own or market a local service business in the EEA, here’s the uncomfortable truth: you don’t control whether an aggregator unit appears. But you do control whether you’re a strong supplier and whether your business is resilient if clicks flow through intermediaries.
8.1 Make your service and location reality easy to crawl
SEJ highlights that direct providers don’t need to send extra data beyond what Google can crawl. That puts pressure on your site fundamentals:
- Clear service pages: one primary service per page where possible
- Clear location coverage: location pages or sections that reflect where you actually serve
- Consistent NAP: name, address, phone presented consistently across the site
- Fast and mobile-friendly: especially if the unit shows on mobile
This is “basic SEO,” but it’s the kind that many SMEs still skip—then blame Google when layouts change.
8.2 Build trust signals that survive SERP volatility
When a new SERP layout introduces more comparison behavior, users become more skeptical. They want proof. Your site should make it effortless to confirm:
- What you do
- Where you do it
- What it costs (even ranges help)
- Why you’re credible (photos, reviews/testimonials, credentials)
- How to book (phone, form, calendar—whatever fits your model)
8.3 Don’t ignore directories—manage them strategically
If approved aggregators get more visibility, your directory presence becomes a competitive asset (or liability). You don’t need to be everywhere. You need to be consistent where it matters.
Practical approach:
- Pick your “category leaders”: the directories your customers actually use
- Standardize branding: same name, same phone, same hours
- Control the narrative: services, photos, and descriptions aligned with your site
- Track leads: unique numbers/UTMs where feasible so you know what’s working
8.4 Protect demand: brand searches are the most defensible traffic
If generic local queries become more mediated by aggregator units, the most defensible demand is the demand you generate: brand + service queries, repeat customers, referrals, and direct navigation.
That means investing in:
- Local reputation and review acquisition (within platform policies)
- Content that answers local questions (pricing, timing, service areas)
- Email/SMS retention where appropriate
- Community partnerships and PR that drive branded demand
9) A concrete SME scenario: a clinic, a directory, and a shifting SERP
Let’s make this real with a scenario that mirrors how SMEs experience SERP changes.
Business: a physiotherapy clinic in Barcelona targeting “sports physio near me,” “back pain clinic Barcelona,” and “dry needling Barcelona.”
Before: The clinic mostly competes against other clinics and relies on a mix of map-based visibility, organic pages, and a couple of directory listings that occasionally send leads.
After (in an EEA market where the new units trigger): A directory (approved aggregator) gets expanded by default for local queries. Alongside, a supplier unit shows multiple clinics—including our clinic—based on what Google can crawl and understand.
What can go wrong?
- Click siphon: The directory captures initial clicks because it appears expanded and looks like “the comparison option.”
- Message mismatch: The clinic’s site page is generic, slow, and unclear about pricing. Users bounce back to the directory.
- Attribution confusion: Calls increase, but they’re routed through directory numbers, so the clinic believes “SEO is down” and “directories are up” without a clear view of the real funnel.
What does winning look like?
- Supplier readiness: the clinic’s service pages explicitly cover treatments, who it’s for, and what to expect
- Local clarity: the clinic’s address, opening hours, and neighborhoods served are prominent and consistent
- Conversion speed: booking options are immediate, with trust signals above the fold
- Directory control: top directory profiles are accurate, photo-rich, and align with the clinic’s positioning
- Measurement segmentation: EEA reporting is separated from non-EEA so shifts aren’t “averaged away”
This is exactly where execution discipline becomes the competitive edge. It’s not about “one more blog post.” It’s about systematically fixing the issues that cause leakage when SERPs add intermediaries.
10) A practical action plan (30/60/90 days)
If you operate in EEA markets—or you serve clients who do—here’s a practical plan that doesn’t rely on guesswork.
10.1 Days 1–30: audit what changed and prevent measurement mistakes
- Segment your data by market: separate EEA countries in reporting views.
- Identify queries at risk: list top local-intent queries (services, dining, attractions) and track their SERP composition manually for a small sample.
- Inventory directories: where are you listed today, which profiles drive leads, which are inaccurate?
- Baseline conversions: calls, forms, bookings by landing page and country.
10.2 Days 31–60: improve supplier readiness on your site
- Upgrade core pages: location page + top 3 service pages (or one page per primary service if you’re smaller).
- Clarify service areas: if you serve multiple neighborhoods/cities, reflect that clearly (without creating thin, duplicate pages).
- Strengthen trust: add real photos, credentials, process explanations, and FAQs that match local intent.
- Technical hygiene: fix crawl blockers, ensure mobile performance is acceptable, and tighten internal links so key pages are discoverable.
10.3 Days 61–90: build resilience via authority, reputation, and execution cadence
- Directory strategy: optimize the top 3–5 listings that matter; remove duplicates; standardize NAP.
- Local authority: pursue local partnerships and mentions that reinforce entity trust (community orgs, local press, industry associations).
- Operational cadence: set a monthly loop: monitor → plan → approve → execute → measure.
Notice what’s not on this plan: chasing every new SEO rumor. The change in the EEA is structural. Your response should be structural too.
11) Where AYSA.ai fits: monitoring + approved execution for local search volatility
Most SEO tools stop at insights. The real bottleneck—especially for SMEs and agencies—is execution. Someone still needs to implement changes, and implementation often gets delayed by approvals, dev queues, or uncertainty.
AYSA is designed as an SEO/AEO/GEO execution system: it monitors, prepares prioritized improvements, asks for your approval, and then executes accepted website changes safely.
Here’s how that maps to this EEA local change:
11.1 Monitor what matters (not just rankings)
When SERP layouts shift, you need ongoing monitoring of visibility and page performance—not just a static rank report. AYSA helps teams stay on top of changes without living in spreadsheets.
- AYSA Monitoring to track performance signals and surface issues early
- AI Search Visibility to connect visibility to outcomes as discovery shifts
11.2 Prepare improvements that match the new reality
If supplier visibility depends on what Google can crawl and interpret, then your site structure, content clarity, and local trust signals become the levers.
- Page improvements for service/location clarity
- Internal linking adjustments so key pages are discoverable
- Content updates that answer local intent faster
Explore the broader toolset here: AYSA AI SEO Tools.
11.3 Approved execution: faster shipping without losing control
Local businesses can’t afford risky, unreviewed edits—especially in regulated niches (health, legal, finance) or brand-sensitive markets (hotels, clinics, premium services). That’s why AYSA’s workflow asks for approval before execution.
If you want the operational model (and pricing clarity), see: AYSA Pricing.
11.4 Keep your team aligned with ongoing guidance
This update won’t be the last. If you’re building a durable system, you want continuous learning and playbooks you can reuse:
Bottom line: the EEA change increases the value of teams that can adapt quickly without breaking things. Monitoring plus approved execution is how you do that.
12) What to do next (checklist)
- Confirm scope: list the EEA countries you operate in and segment reporting immediately.
- Review your top local queries: identify which ones are most revenue-critical and monitor SERP composition changes.
- Harden your supplier pages: service clarity, location clarity, trust signals, mobile performance, fast booking/call paths.
- Pick your directory battles: optimize the few listings that matter; ensure consistency; track leads.
- Build defensible demand: brand, reviews, retention, partnerships.
- Adopt an execution cadence: weekly review, monthly improvements, quarterly strategy refresh.
- Use an execution system: implement changes with governance—monitor → prepare → approve → execute.
Sources and further reading
- Search Engine Journal: Google Adds Local Businesses To EEA Search Result Units
- Search Engine Journal: Local SEO section (context and ongoing coverage)
- Search Engine Journal: SEO News section (for related EEA updates)
Note: The SEJ article references specific Google documentation pages (Search Central pages for aggregator/supplier units and a Google Actions Center page). Those direct URLs were not provided in the supplied research context, so I’m not linking them here to avoid inventing sources. If you have the exact Google documentation links, we can add them in a revision for more primary-source grounding.
Continue the AI search topic inside AYSA.
Use these pages to connect the article with AI SEO tools, AI visibility monitoring, AI Overviews and approved website execution.
Turn this topic into a website action plan.
Use these AYSA hubs to move from reading to technical fixes, AI visibility monitoring, research, glossary context and approval-first SEO execution.
