Skip to content
All articles

Google Shopping

Google Shopping feed errors that quietly cap sales

The Shopping feed errors most likely to cap sales are price or availability mismatches, missing product identifiers, policy disapprovals, invalid images, weak titles and incomplete attributes. Fix the shared source rule first, then confirm affected products are approved again.

12 September 2026 · 8 minute read

An ecommerce worker sorting correct products into blue trays and mismatches into coral trays

A disapproved product cannot sell through Shopping. A limited product can be harder to spot: it remains active, but missing or weak data narrows the searches and placements it can reach. Both deserve attention before another bidding change.

Start with the size of the problem

In Merchant Center, separate disapproved, limited and approved products. Sort issues by the number of products affected. One broken rule in an ecommerce platform can create the same error across hundreds of items, so fixing the source beats editing products individually.

Price and availability mismatches

Google checks feed data against the landing page. If a sale ends, VAT is handled differently, variants show another price, or stock changes between updates, the values disagree. Increase update frequency and make sure structured data on the page matches what a customer can actually buy.

Missing or incorrect identifiers

Branded products normally need the correct GTIN and brand. Do not invent a GTIN or reuse one from another variant. Own-brand or genuinely custom products may use an MPN and brand instead, with identifier settings that reflect reality.

Images that fail quietly

  • Use a clear main image showing the product being sold.
  • Remove promotional text, watermarks and borders.
  • Keep image links reachable by Google.
  • Give each variant the image that matches its colour or style.
  • Use additional images for context rather than replacing the clean main shot.

Titles that make good products invisible

A title can be technically valid and commercially weak. Put the words shoppers use near the front: brand, product type and the attribute that distinguishes the variant. Remove internal codes and promotional filler unless the code is genuinely searched.

Policy issues need the exact reason

Do not keep requesting reviews without changing anything. Read the affected destination, country and policy reason. Check the product page, delivery, returns and business information as well as the feed. Once the cause is fixed, request or await reprocessing and confirm the product returns to approved status.

How AdKing handles feed work

AdKing reads Merchant Center issues alongside campaign performance, previews the proposed data change and turns approved recurring fixes into versioned rules. That keeps a catalogue refresh from erasing the work and places feed opportunities in the same ranked queue as campaign improvements.

Common questions

What is the difference between a disapproved and limited Shopping product?

A disapproved product cannot serve in the affected destination. A limited product can still serve, but an issue may reduce where or how effectively it appears.

Why does Google say my product price is wrong?

The feed price and landing-page price may differ because of sales, variants, VAT, currency, stale updates or structured data. Both must reflect the price a shopper can actually pay.

Should I fix Shopping feed errors by hand?

Fix an isolated product by hand if necessary, but repeated issues should be corrected in the source feed rule. Otherwise the next catalogue export can overwrite the work.

Want this looked at every night?

AdKing connects insight, ranked improvements, ad creation, Shopping feed work and reporting in one workflow. Nothing goes live until you approve it.