Daily SEO Note — September 21, 2026: Google Extends EEA Aggregator Units to Local Business Queries

Monday edition, covering a 72-hour window from Friday 18 September 06:00 UTC through Monday 21 September 2026 06:00 UTC. One theme carried the window: Google kept rebuilding what a European search result page looks like. The only change in the window confirmed by primary documentation landed quietly in the regional-features docs, not on the Search Central blog.

1. SEO for Content Writers

The most consequential editorial change today: Google's aggregator and supplier units now cover local business queries in the EEA. A whole category of service-provider and "near me" intent has moved into a multi-provider unit where directories, marketplaces and individual businesses compete side by side. It shipped on 18 September 2026 as a documentation changelog entry with no accompanying blog post, which is exactly the kind of change that moves traffic before anyone writes about it.

Aggregator and Supplier Units Now Cover Local Business Queries

What changed: Google added local business queries to the list of query types served by the aggregator unit and the supplier unit. Both pages carry a last-updated stamp of 18 September 2026 UTC. Rollout status: live, and limited to users in the EEA. Previously these units covered hotels, flights, ground transportation and products; local businesses are the new addition.

Who it affects: any publisher or business competing for EEA local-service intent. That splits into two roles. If you are a directory, marketplace or comparison site, you are an aggregator and you compete for a slot inside the unit. If you are the business itself — a clinic, a plumber, a single hotel — you are a supplier, and the supplier unit is the surface built for you. The distinction matters because the two have completely different entry requirements.

What to do differently in the next brief: for EEA local-service pages, write the page so a single location's core facts — service offered, city or neighbourhood served, address, opening hours, service area — appear as plain text in the body copy, not only in a widget or a map embed. The supplier unit draws on what Google can already crawl, so the brief should treat those facts as body content with a named owner, not as a design element bolted on at template level.

What to stop doing: stop writing one national "our services" page and expecting it to carry every city. A unit that resolves local business queries rewards a page that is unambiguously about one place. Stop burying the address and hours in a footer partial shared across the whole site — that gives Google no per-page signal to attach to a local query.

Free Product Listings Disappeared From EEA Results — Reported, Not Documented

Labelled unconfirmed. On 18 September 2026 it was reported that free product listings and popular-product carousels had dropped out of Google Search across the EEA, described as Digital Markets Act compliance and confirmed by Google's Ads Liaison in a LinkedIn comment. There is no corresponding entry in Google's documentation changelog and no Search Central blog post, so this does not yet meet the bar of a primary citation of record. Treat it as a strong signal, not as settled fact, and verify against your own EEA impression data before acting.

If your commerce content serves EEA markets, the editorial consequence is that organic product visibility inside Google's own shopping surfaces can no longer be assumed. That raises the value of the destination page itself: comparison copy, first-hand testing notes, specification tables and genuine buying guidance are what survive when a carousel stops doing the selling for you. Until it is documented, keep this out of any client-facing forecast.

No Core or Spam Update Is Running Right Now

The Search Status Dashboard reported no incidents across crawling, indexing, ranking and serving as of 20 September 2026, 23:10 PDT. No core update, no spam update and no ranking system rollout is active or recently completed in this window. Rollout status: none in progress.

The editorial instruction here is restraint. If EEA rankings or revenue moved over the weekend, the likely cause is the structural change to the results page described above, not a quality reassessment of your writing. Do not commission a rewrite of pages that lost visibility to a surface change — the copy was not the problem, and rewriting it will cost you the historical baseline you need to measure the real cause.

The Supplier Unit Rewards Plain Crawlable Copy, Not More Markup

This item is written for writers here and for engineers in section two. Google's supplier unit documentation states that you do not need to provide additional data beyond what is accessible through web crawling in order to appear in the feature. Optional supplier feeds can enhance the result, but they are not the price of entry.

For an editorial team that is unusually good news, because it means eligibility is a content problem you already own rather than a data-engineering dependency you have to queue. The concrete instruction: when you brief an EEA location or service page, require the writer to state the business name, the service, and the place in prose within the first screen of content. Stop treating those as metadata to be filled in later by whoever configures the CMS.

Apply to Your Next Brief

• Add a line to the brief template: for EEA local pages, name the business, the service and the location in body prose above the fold.
• Split any national service page that is trying to rank for multiple cities into one page per genuine location, with real local detail rather than a swapped city name.
• Move address, opening hours and service area out of a shared footer partial and into per-page content.
• Decide explicitly whether each property is an aggregator or a supplier in Google's terms; brief the two page types differently.
• For EEA commerce pages, strengthen on-page comparison and first-hand testing content rather than relying on Google's shopping surfaces for discovery.
• Freeze rewrite decisions on EEA pages that dropped this weekend until the cause is separated from the results-page restructure.

2. SEO for Developers

The most consequential engineering change today is that Google's Regional differences in Search experience page was updated on 18 September 2026 UTC and is now the canonical map of which Search features exist in which region. It names three regions with divergent behaviour — the EEA, South Africa and Türkiye — which means "what does our result look like" is now a per-market question your templates and tests have to answer separately.

Supplier Unit Needs No New Structured Data, But Location Facts Must Be in the HTML

Identifier and date: supplier unit documentation, last updated 18 September 2026 UTC, EEA only. Non-breaking, but with a real symptom if ignored: an EEA location page whose name, address and hours are injected client-side can be excluded from a surface it would otherwise qualify for, because the documented bar is what is accessible through web crawling.

The setting to change is your location template: render the identity block server-side and keep LocalBusiness structured data in the initial HTML response rather than appending it from a client effect. The JSON-LD is not required for supplier unit eligibility, but it costs nothing and it is what feeds the rest of the local result stack.

<!-- Server-rendered. Must be present in the initial HTML response. -->
<h1>Bakkour Plumbing — Antwerpen</h1>
<p>Emergency and scheduled plumbing across Antwerpen and Berchem.</p>
<address>
  Lange Nieuwstraat 12, 2000 Antwerpen, Belgium
</address>
<p>Open Monday to Friday, 08:00–18:00</p>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Bakkour Plumbing — Antwerpen",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Lange Nieuwstraat 12",
    "addressLocality": "Antwerpen",
    "postalCode": "2000",
    "addressCountry": "BE"
  },
  "areaServed": "Antwerpen",
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
    "opens": "08:00",
    "closes": "18:00"
  }]
}
</script>

Aggregator Unit Entry Runs Through a Feed, Not Through Markup

Identifier and date: aggregator unit documentation, last updated 18 September 2026 UTC, EEA only. This is the half of the change that is not a template fix. The aggregator unit documentation states that participation requires providing data through direct feed integrations or real-time APIs, and for the newly added local business queries that path is the Local Point of Interest Feed. Adding structured data to your listing pages will not get a directory into this unit.

Non-breaking, but the symptom if ignored is a silent absence: a qualifying EEA directory simply never appears in a unit it is eligible for, with nothing in Search Console to explain the gap. The action is procurement and integration work, not an SEO ticket — express interest through Google's form, then schedule the feed build. Treat this as a watch item with an owner and a date rather than something to ship this afternoon.

Verify Location Pages Render Without JavaScript

This is the regression guard for the item above, and it is worth wiring into CI rather than checking once by hand. Fetch the raw HTML of each location URL and assert that the address, the locality and the JSON-LD block are present before any script executes. The check below is deliberately dumb so it can run as a build step in any stack.

#!/usr/bin/env bash
# Fails the build if a location page needs JS to expose its local facts.
set -euo pipefail

URLS=(
  "https://example.com/locations/antwerpen"
  "https://example.com/locations/gent"
)

fail=0
for url in "${URLS[@]}"; do
  html=$(curl -sS -m 30 -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "$url")

  for needle in "<address" "application/ld+json" "LocalBusiness" "openingHoursSpecification"; do
    if ! grep -qF "$needle" <<<"$html"; then
      echo "MISSING: $needle -> $url"
      fail=1
    fi
  done
done

exit "$fail"

Adjacent Items Dated Just Outside the Window

Two changes fall two days outside the 72-hour window and are flagged here rather than counted as today's news. Schema.org 30.1 was released on 16 September 2026, adding vocabulary for EU Digital Product Passport discovery and for common eCommerce product data. Separately, Google published a guide on adding a Search profile badge on 16 September 2026. Both are non-breaking and neither is urgent; the badge in particular is a self-contained snippet you can drop into a footer partial once someone has claimed the profile.

<!-- Requires a claimed Search profile. Keep the touch target at least 44x44 px. -->
<a href="https://profile.google.com/@example"
   aria-label="Find us on Google Search">
  <img src="/assets/google-search-badge.svg"
       alt="Google Search"
       width="48" height="48">
</a>

Verified Negatives for This Window

Recording what did not change is part of the audit. The Cloudflare developer changelog carried entries on 17 and 18 September 2026, none of them touching AI crawler controls, bot rules, WAF enforcement or cache behaviour. Google's common crawlers documentation still carries a last-updated date of 14 July 2026, so no user-agent or Google-Extended change landed this weekend. No reviewed npm advisory published between 18 and 21 September 2026 affected a sitemap, metadata, crawler or SEO package. Next.js shipped only canary builds in this window, so there is no stable metadata or caching change to act on.

Ship Today

1. Audit EEA location templates and move name, address, hours and service area into the server-rendered HTML response.
2. Move LocalBusiness JSON-LD out of any client-side effect and into the initial document.
3. Add the no-JavaScript location check to CI so a future refactor cannot silently remove the local facts.
4. Classify each EEA property as aggregator or supplier, and record the decision where the team can see it.
5. If you run an EEA directory or marketplace, open the aggregator interest form today and book the Local Point of Interest Feed work.

Method note: every dated claim above traces to a primary source — Google's own documentation and status dashboard, or the Schema.org release log. The EEA free product listings item is the single exception and is labelled unconfirmed, because it currently rests on reporting and a spokesperson comment rather than documentation. All timestamps are normalised to UTC unless a source publishes in another zone, in which case the source's zone is stated.