The eligible-not-distributed gap: why Merchant Center approval doesn't guarantee Shopping traffic

Google Merchant Center approving a product and Google Shopping actually showing that product to a searcher are two different events, and merchants routinely treat them as one. “Approved” or “eligible” in Merchant Center confirms only that the listing passed structured-data and policy checks, a narrower bar than actually appearing in a search result. Two separate mechanisms open this gap. Within a single market, an approved product with a duplicate description or a bare SKU-number title can sit at a fraction of its potential share of voice, the pattern a vendor case study documented across a 4,000-product catalog.¹ Across markets, a product can show “eligible” in a country Google just added to Shopping and still draw zero impressions there, because the feed lacks the shipping, tax, or language attributes that country requires, a gap Google opened itself in July 2026 by adding 14 new Shopping markets at once.² Both failures look identical from inside Merchant Center: a green checkmark. If your Shopping traffic looks flat despite a clean feed status, the feed’s data quality is almost certainly where to look, whatever the approval dashboard says.

Eligible means it passed the checks. Distributed means a shopper saw it. Merchant Center only guarantees the first.

Does “approved” in Merchant Center mean your products are visible?

No. Merchant Center’s “approved” or “eligible” status confirms a product listing passed Google’s structured-data and policy checks, has the required attributes, and carries valid pricing. That status says nothing about whether the product ever appears in a Shopping search result, a free listing, or a Shopping ad a shopper actually sees. Visibility and distribution are separate, unmeasured events that the Merchant Center dashboard does not track at all.

Merchant Center’s own diagnostics reinforce the confusion. Its reporting surfaces disapprovals, warnings, and policy violations, because those are data errors from Google’s point of view. There is no diagnostic category for a product that is approved but essentially invisible, because Google’s system considers its job finished once the feed is valid and the policies are satisfied. Confirming whether an approved product is actually being shown means leaving Merchant Center entirely, for Search Console’s Shopping performance filter or a third-party visibility tool, a step most merchants skip because a screen full of green checkmarks reads as success.

This piece calls the space between those two states the eligible-not-distributed gap: the interval where a product is technically valid but structurally invisible. Two separate mechanisms open it. One operates inside a single market, where thin or duplicated feed text buries an approved product against its competitors. The other operates across markets, where a product is freshly eligible for a country’s Shopping results but missing the per-country data that would actually let it show. Both mechanisms produce the identical result on the Merchant Center dashboard: a green checkmark, and a diagnostics screen with nothing flagged.

Why do approved products still get almost no Shopping traffic?

Approved products most often lose Shopping traffic to feed data quality problems that carry no policy violation at all. Duplicate descriptions copied across variants, titles that are nothing more than SKU strings like “123.190001,” and near-identical landing pages all confuse Google about which listing to surface. A vendor case study from feed-audit tool Productrise, covering a 4,000-SKU baby-products store, reported the approved catalog sitting at 5% share of voice across roughly 100 keywords.¹

The store’s feed audit, run through Productrise, surfaced three specific patterns behind the low share of voice. Different product variants pointed to duplicate URLs, which left Google unable to tell which variant should rank for a given search. Product descriptions repeated across dozens of items, sometimes across entire categories, despite real differences in size, material, or age range between the products. Titles were the worst offender: about 20% were bare SKU strings with no product information at all, and most of the rest averaged only 20 to 25 characters, well short of what parents actually search against.¹

None of this tripped a Merchant Center policy violation, because a SKU-string title and a fully descriptive title are both “valid” as far as structured-data and policy checks go. The shortfall sits in relevance: Google’s matching systems need enough text signal to connect a query to a product, and a title with no size, color, or use case gives them nothing to match against, regardless of how clean the feed’s technical fields are.

What does a supplemental feed actually fix (and what it doesn’t)?

A supplemental feed is a secondary data file that Google Merchant Center merges on top of a merchant’s primary feed, overriding specific attributes, commonly title and description, without altering the original feed file or the systems that generate it. Because the primary feed stays untouched, Shopping ads and Performance Max campaigns built against it keep running unmodified while the supplemental layer fixes only the fields responsible for the visibility gap.

In the Productrise case, the store used the vendor’s AI tool to rewrite titles and descriptions for all 4,000 products and loaded the result as a supplemental feed in the first week of January 2026, a job the case study describes as under three hours of setup.¹ One published example: a title that read “4612 Baby Bottle Boy” became “Baby Bottle 250ml Anti-Colic Blue BPA-Free, Newborn Boy 3-6 Months,” trading a four-digit code for size, feature, color, and age range in the same field.¹ Google Search Console’s Merchant Listings filter showed clicks rising from roughly 620 to 1,200 per month, a 90% increase, with share of voice across the same 100 keywords climbing from 5% to 16% within about a month of the change going live.¹ Productrise reports this as one customer’s result: a single case study, reported by the tool’s own vendor, rather than an average across customers or a controlled test against a held-out set of products.

What a supplemental feed does not touch is everything outside the attributes it overrides. The same case study lists its own unresolved backlog after the fix: product-page content, JSON-LD structured data that still needs to match the newly optimized feed values, unaddressed technical SEO and crawling issues, and a thin set of product images.¹ My read: that backlog is itself evidence that a supplemental feed fixes feed-text quality specifically, and leaves page-level content, schema alignment, and cross-market attributes as separate work that a title rewrite cannot reach.

Why is a product “eligible” in a new market but getting zero impressions?

Google added Shopping ads and free listings to 14 new European countries in July 2026, including Bulgaria, Croatia, Estonia, and Malta.² Merchant Center marks a product “eligible” the moment it targets one of these countries in the feed. That flag only means Google will consider showing the product; it does not mean the product carries the shipping, tax, or language data those shoppers and Google’s ranking systems require.

Google’s own setup documentation for multi-country Shopping is explicit about what has to be in place before eligibility becomes an actual impression. On shipping, merchants must confirm delivery policies are set up “in the currency of your product for all the countries” targeted in the data source.³ On tax, the same documentation instructs merchants to “follow the correct tax policies for your target country,” since most markets outside the US and Canada apply value-added tax under different local names (VAT, IVA, TVA, MWST, GST) that the feed’s tax settings have to reflect correctly for that specific country.³ On language, Google’s supported-languages documentation warns that when a product’s title, description, or variant information does not match the feed’s declared data-source language, “your products might have limited performance since the information provided won’t match a user’s search terms and expectations in a given language.”⁴

All three requirements predate the 14-country expansion by years; they are the standing rules for every target country Merchant Center supports, old or new. What changes when Google adds new countries is that a merchant’s existing feed, built and tuned for markets it already sells into, suddenly has a new target country available to flag as eligible, often before anyone has gone back and populated that country’s shipping policy, tax setting, or localized language fields. The eligible flag flips to true. The impressions do not follow, because the underlying data the ranking systems need was never added.

How do you find and price your own eligible-not-distributed gap?

Finding your own eligible-not-distributed gap starts with two counts that Merchant Center itself never computes. First, count how many approved SKUs carry duplicate descriptions or titles under roughly 30 characters, the two patterns the Productrise case flagged as most damaging. Second, for every target country in your feed, count how many required shipping, tax, and language attributes are actually populated rather than defaulted or left blank.

Pricing the gap is the harder half, and it is where confidence has to drop a level. The Productrise case reported a 90% increase in Merchant Listings clicks and a share-of-voice jump from 5% to 16% after a title and description rewrite.¹ That ratio is one store’s outcome, in one niche, over one month, reported by the vendor whose tool produced it. Applying it to a different catalog as a forecast would be a mistake. The honest use of that number is as a directional signal that fixing thin titles and duplicate descriptions on already-approved products can move share of voice by double digits; treating it as a multiplier for a revenue model would overstate what one case study can support.

My read, flagged here as synthesis rather than a finding: this piece leans on a single vendor’s case study and on Google’s own attribute documentation because a first-hand audit, tallying missing shipping, tax, and language fields per target country against actual impression data on a real multi-market feed, has not been run here. That audit would strengthen the claim considerably, and it is the natural next step for verifying the cross-market mechanism specifically. The mechanism itself, that feed data quality and per-country attribute completeness gate distribution regardless of what the approval dashboard shows, is the transferable part. The specific 90% and 5%-to-16% figures belong to one store; treat them as illustrative rather than as a forecast for your own feed.