EEA Free Product Listings: Why Search Console Fell 63% but Merchant Center Fell 9%
A 531-query study explains why the September 2026 removal of EEA free product listings can produce a sharp Search Console decline while Merchant Center reports a far smaller change.
· 15 min read
A 531-query study across Germany, Austria, Switzerland and the UK found that Search Console merchant-listing clicks for one EEA retailer fell 62.9% after September 15, 2026, while Merchant Center free-listing clicks fell just 9.2%. The explanation is not necessarily a feed failure: EEA free product listings disappeared from a specific part of Google Search, while Merchant Center still measures eligible visibility across several Google surfaces.
For ecommerce teams, the practical payoff is clear: avoid treating a Search Console merchant-listing collapse as a one-number verdict on product visibility. Country-level SERP checks, reporting-scope reconciliation and feed-health monitoring are now necessary to separate an EEA Search-layout change from an actual loss of product demand, feed eligibility or organic performance.
What changed to EEA free product listings in September 2026
Google removed free product listings and the familiar Popular Products carousel from general Google Search results in the European Economic Area (EEA) around September 17-18, 2026. Reporting at the time connected the change to Google's Digital Markets Act (DMA) compliance work, while Google documentation published on September 8 described new EEA-specific aggregator and supplier search units.
The critical qualification is where the change occurred. This was not a universal switch-off of every unpaid product exposure available through Merchant Center. It primarily changed the product-discovery experience in EEA Google Search results, where direct merchant products had previously appeared in rich shopping-style modules.
For retailers, that distinction explains why all of the following can be true at once:
- Search Console's Merchant listings appearance report drops sharply in Germany, Austria or another EEA market.
- Merchant Center reports a smaller decline for free listings.
- Standard organic clicks to product pages remain stable or even rise.
- Google Shopping ads continue to run.
- Product exposure remains possible on non-Search surfaces, subject to eligibility and country availability.
The change is therefore best understood as a SERP-distribution change, not automatic evidence that a merchant's product feed, structured data or indexation has broken.
The 531-query study: methodology and control countries
The original dataset, shared by a TechSEO practitioner with permission-based retailer data, examined 531 non-brand product searches over four days, October 20-23, 2026. It provides a useful model for measuring a visible SERP change without confusing it with seasonal demand or a single retailer's traffic trend.
The study included 274 German-language terms checked in Germany, Austria and Switzerland, plus 257 English-language terms checked in the UK. Queries were selected from 12 product sectors using Keyword Planner volume. Searches were run signed out, with country location set explicitly, on mobile in all four countries and desktop in Germany and the UK.
That created 6,440 result pages. Every product item in the relevant module was counted, including items inside collapsed groups. The researchers also reviewed 2,299 archived SERP captures from April through October to establish the before-state.
Why Germany and Austria matter — and Switzerland and the UK do not
Germany and Austria are EEA markets, so they form the affected group. Switzerland and the United Kingdom are useful non-EEA controls: they can reveal whether a product-query pattern is likely connected to the EEA layout change rather than a broad Google Shopping redesign.
The study used September 15 as the pre-change cutoff even though the visible removal was observed around September 17-18. That is a sensible measurement convention, not a claim that every result changed at midnight on September 15. A cutoff creates two clean reporting windows and reduces the risk of mixing the transition days into both periods.
A similar audit should preserve the same logic: define the affected markets, retain at least one relevant non-EEA control where possible, document device and locale settings, and keep the query set fixed.
What replaced the Popular Products carousel in EEA Search
The study found a major country split in the product blocks shown after the change. On German mobile searches with a product block, 90% of product items led to comparison sites, while only 10% led to Google Shopping entries with stars. Direct links to merchant sites were below 1%.
| Country and device | Searches with product block | Product items leading to comparison sites | Product items leading to Google Shopping | Product items with stars |
|---|---|---|---|---|
| Germany, mobile | 92% | 90% | 10% | 2% |
| Germany, desktop | 53% | 87% | 13% | 4% |
| Austria, mobile | 90% | 46% | 54% | 7% |
| Switzerland, mobile | 95% | 0% | 100% | 73% |
| UK, mobile | 100% | 0% | 100% | 71% |
| UK, desktop | 100% | 0% | 100% | 71% |
Germany's mobile results commonly showed six to eight comparison groups. Across 53,625 mobile product items, no single comparison service dominated: Google Shopping represented 10.0%, testberichte.de 6.6%, billiger.de 6.3%, shopping.de 5.7% and idealo.de 5.5%. The top 10 services accounted for 57% combined.
This matters because “the carousel disappeared” is incomplete. The evidence suggests that in at least some EEA markets, the space did not simply become regular blue links. It shifted towards comparison-shopping destinations, changing both the click path and the competitive set.
Aggregator units, supplier units and Comparison Shopping Services
Google's new EEA documentation uses two important terms: aggregator units and supplier units. An aggregator unit can surface comparison services for a commercial query. A supplier unit is designed to surface direct providers or businesses. Google has also expanded local-business-query support for these units in its documentation updates.
For product retailers, the distinction should not be read as a guaranteed like-for-like replacement for the former free product carousel. Eligibility, query interpretation, country, device and Google's own SERP decisions all affect whether a unit appears and who appears in it.
What a CSS does in this environment
A Comparison Shopping Service (CSS) is a service that can submit and manage shopping offers in Google's European shopping ecosystem. In the post-change EEA result layout, CSS relationships deserve closer attention because comparison destinations are more visibly represented in the observed German product blocks.
Retailers should ask a CSS candidate concrete questions before changing arrangements:
- Which EEA countries and product categories does it actively cover?
- Does it operate only paid Shopping campaigns, or can it support other relevant product-discovery routes?
- What reporting separates merchant-site traffic, comparison-site referrals and paid-media performance?
- Who owns the product feed, merchant account configuration, campaign data and historical reporting if the relationship ends?
- What incremental reach is expected beyond an existing Google Shopping setup?
No CSS can promise appearance in every aggregator unit. Google controls the result page, and the study's country differences show why a Germany-only assumption should not be applied unchanged to Austria or other EEA markets.
Why Search Console shows minus 63% while Merchant Center shows minus 9%
The central lesson from the retailer example is that Search Console and Merchant Center are not measuring the same universe. The retailer, labelled Shop A in the study, saw a 62.9% decline in Search Console merchant-listing clicks for EEA markets from September 21 to October 4 versus September 1-14. Merchant Center free product listings declined 9.2% over the same comparison.
That gap is plausible because the two reports have different scopes.
| Reporting view | What it is useful for | Key limitation in this event |
|---|---|---|
| Search Console: Merchant listings, Web search type | Search-result-specific clicks and impressions associated with the merchant-listing appearance | It is highly exposed to removal of free product modules from EEA Google Search |
| Merchant Center: free listings | Broader unpaid product performance across eligible Google surfaces | It can retain activity from surfaces not affected in the same way as general EEA Search |
| Web analytics | Visits, revenue, assisted journeys and referrers | Attribution rules and channel grouping may obscure the original Google surface |
| SERP sampling | What searchers actually see by query, country and device | A sample measures presence and composition, not every impression or click |
Google's Merchant Center guidance says free listings can appear across Google Search, Maps, Gemini, YouTube, the Shopping tab, Google Images and Google Lens. Google Search Console's merchant-listing reporting, by contrast, is an appearance report tied to Search performance data. That is why a sharp loss in a Search-specific module may be diluted when Merchant Center aggregates broader free-listing activity.
The study adds a useful historical clue: before September 15, Search Console merchant-listing clicks were only about one fifth of Shop A's Merchant Center free-listing clicks. A 63% drop in the smaller, narrower component cannot be mechanically expected to create a 63% fall in the broader total.
This does not mean every retailer should expect a 63% versus 9% split. Feed mix, country mix, Shopping-tab usage, local inventory, images, brand strength and measurement configuration can all change the relationship.
What Shop A's traffic data does — and does not — prove
Shop A's data offers useful context, but it is one anonymised retailer, not a benchmark for the entire EEA. In the first post-change window, product-page organic clicks excluding merchant listings rose 6.5%, while all product-page clicks fell 4.3%. Visits via comparison sites rose 13.3% across all countries and media.
The analysis estimated that stronger ordinary organic traffic offset roughly 57% of the lost merchant-listing clicks on product pages. That is a reminder that a SERP-feature loss and total ecommerce traffic loss are different questions.
Several controls make the timing more persuasive, though not conclusive. Merchant-listing clicks outside the EEA reportedly rose 12%, Bing clicks rose 1%, Shopping ads showed no step-change at September 15, and keyword-demand checks did not show a matching collapse. The largest country declines were between 40% and 70%, with Germany the steepest.
Do not over-diagnose a feed problem
A falling Merchant listings chart immediately after September 15 should trigger a diagnostic process, not an emergency feed rebuild. A feed can still have genuine issues — disapprovals, price mismatches, shipping errors, availability mismatches, missing GTINs or destination problems — but timing alone does not establish causation.
Technical checks still matter. Google recommends merchant listing structured data for product and offer details, while Merchant Center can enrich Google's understanding of product information and is required for some Shopping surfaces. Teams managing variants should also verify that each variant has an appropriate unique identifier and consistent product data.
For related product-page diagnostics, see Audra's guide to canonical issues and Google index exclusions and its analysis of Shopify color variants SEO. These issues will not explain the EEA-wide SERP redesign, but they can compound its commercial impact when important product URLs are already weakly indexed or incorrectly canonicalised.
A reconciliation workflow for Search Console and Merchant Center
The most reliable response is to build a small reconciliation workbook rather than comparing one headline percentage against another. Start with at least four to six weeks before and after the transition where enough data is available, then preserve the same country, product and device views throughout.
Step 1: segment the affected geography
Create separate reporting lines for each EEA country rather than one “Europe” total. Germany and Austria may both be affected markets, but the 531-query sample showed radically different destination mixes: 90% comparison-site items in Germany mobile versus 46% in Austria mobile.
Keep Switzerland and the UK separate if they are commercially relevant control markets. Do not combine them into an EEA figure simply because they use German or English queries.
Step 2: isolate the relevant Search Console appearance
In Search Console Performance reporting, select Web search and the Merchant listings search appearance where available. Compare clicks, impressions, CTR and average position by country, page group and product-query cohort.
Then view ordinary Web performance without using Merchant listings as a proxy for the entire product page. This distinguishes a loss of rich-result exposure from a broader organic-ranking problem. If Google Search Console says only one page is indexed, solve that underlying coverage issue separately using this guide: Google Search Console only one page indexed.
Step 3: review Merchant Center as a broader surface report
In Merchant Center, review free-listing performance separately from paid Shopping performance. Check the date annotations and any changes to Merchant Center's own reporting definitions; the study noted a counting change on August 24, recalculated from July 1, which complicates year-over-year comparisons.
A Merchant Center total should not be described as “Search Console with different numbers.” It is a wider product-performance view, so use it to answer a different question: whether unpaid product activity across Google's eligible surfaces has changed.
Step 4: join data to real landing-page outcomes
Add web analytics for product-page sessions, revenue, conversion rate and comparison-site referrals. Separate direct merchant landing pages from referral journeys where possible. A comparison-site traffic increase may partially compensate for lost direct module clicks, but it can also change conversion quality, margin and attribution.
Step 5: validate the SERP itself
Use a fixed list of non-brand product queries and record country, language, device, logged-out status, date, product block type, visible domains and direct-to-merchant share. Audra can support this broader audit process by pairing AI-search visibility checks with technical SEO, performance, accessibility and link checks in a local desktop workflow, but it should complement rather than replace country-specific manual SERP observation.
Actions retailers should prioritise now
The right response is not to abandon product SEO for paid Shopping. The study found ordinary organic product-page clicks could move independently of merchant-listing clicks, and Google's own documentation still supports product structured data and Merchant Center product information for eligible experiences.
A practical priority order is:
- Protect feed quality. Resolve Merchant Center diagnostics, price and availability mismatches, shipping configuration issues, GTIN gaps and variant inconsistencies.
- Measure EEA markets individually. Report Germany, Austria and other EEA countries separately rather than averaging away SERP differences.
- Build a product-query cohort. Track the same high-value non-brand queries on mobile and desktop, including screenshots or saved SERP records.
- Assess CSS options commercially. Evaluate marginal reach, operating model, data access and cost rather than assuming a CSS restores former free-listing traffic.
- Review paid Shopping separately. Paid ads remained a distinct route through the transition; evaluate incrementality, profitability and auction movement rather than attributing all changes to free listings.
- Strengthen conventional product SEO. Improve crawlability, canonical handling, product copy, internal links, structured data, performance and accessibility.
Teams that need to compare technical crawlers and reporting workflows can also review Audra versus Screaming Frog for XML sitemap audits. The goal is not tool replacement for its own sake; it is finding and documenting the technical constraints that still limit product discoverability after the SERP change.
What remains unknown after the September change
The evidence clearly supports an EEA-specific removal of free product carousel-style exposure in Google Search and a shift toward comparison-service results in the study sample. It does not establish a universal traffic-loss percentage, a single replacement experience across all EEA countries, or a guaranteed path into an aggregator or supplier unit.
Google's result composition can vary by query, device, language, product category and location. The 531-query evidence is substantial enough to guide a measurement plan, but it should not be used to predict that every German retailer will lose 63% of product visibility or that every Austrian retailer will see the same comparison-site mix.
The useful operating principle is simple: describe the exact report, surface, country and date range before drawing conclusions. “Free listings are down” is too broad to drive a feed, SEO or media decision.
FAQ
What changed to Google free product listings in the EEA in September 2026?
Around September 17-18, 2026, Google removed free product listings and Popular Products-style carousels from general Google Search results in EEA markets as part of DMA-related changes. The change was Search-specific rather than proof that every unpaid Merchant Center surface ended. Eligible products may still receive free exposure on other Google surfaces.
Why did free product listings and Popular Products carousels disappear in EEA Google Search?
The removal was linked to Google's implementation of Digital Markets Act requirements. Google introduced EEA-specific aggregator and supplier units for commercial queries, changing how product and comparison-shopping destinations can be presented. The exact result layout still varies by query, country, device and Google's ranking systems.
Why do Search Console merchant-listing impressions fall more than Merchant Center free-listing impressions?
Search Console's Merchant listings appearance is tied to Search-result reporting, so it is directly exposed to the removal of free product modules from EEA Search. Merchant Center free-listing reporting can cover eligible product activity across Google Search, Shopping, Maps, Images, Lens, YouTube and Gemini. The two totals have different scopes and cannot be converted one-to-one.
Are Google Shopping ads and Merchant Center feeds still affected in the EEA?
The September 2026 change did not mean paid Shopping ads or Merchant Center feeds stopped working. Paid Shopping remains a separate channel, while Merchant Center still supports product data used across eligible Google experiences. Retailers should nevertheless monitor destination eligibility, diagnostics, country settings and paid performance separately from free-listing reporting.
Can retailers still receive free product visibility on Google outside EEA Search?
Yes, subject to Google's eligibility requirements and country availability. Merchant Center's current help documentation lists potential free-listing exposure across surfaces including the Shopping tab, Google Images, Google Maps, Google Lens, YouTube and Gemini. That broader surface coverage is the main reason Merchant Center may show a smaller decline than Search Console after the EEA Search change.
Sources
- https://www.reddit.com/r/TechSEO/comments/1xdni52/eea_free_listings_since_sep_15_531_product/
- https://developers.google.com/search/docs/appearance/aggregator-features
- https://support.google.com/merchants/answer/13889434?hl=en
- https://www.seroundtable.com/google-drops-free-product-listings-eea-42113.html
- https://www.string.global/en/insights/google-shopping-eea-free-listings-removed/
- https://developers.google.com/search/docs/appearance/structured-data/merchant-listing