Fix product-feed data that doesn't match your store.
We investigate your primary feed, any supplemental feeds, the store data behind them and your product pages, then correct the data so all of them say the same thing. Correct data is within our control. Google's approval is not.
Why feed accuracy matters
Google compares three versions of each product: the data in your feed, what a shopper sees on the landing page, and what they pay at checkout. Google's Merchant Center policies expect these to agree. When they don't, products can be disapproved, limited, or shown with information that turns into a poor experience at checkout.
Most feed problems are not mysterious. They come from a mapping decision made once, years ago, that no longer fits how the store is run: a sale price that the feed never learned about, a variant structure that changed, or a stock rule that doesn't account for pre-orders.
Attribute mapping
We trace each important attribute from its source to the feed:
| Feed attribute | Typical source on the store | What we check |
|---|---|---|
id |
Product or variant ID, or SKU | Stable, unique per variant, not changed by an app reinstall |
title and description |
Product title and body | The right variant detail, no promotional text |
price and sale_price |
Variant price and compare-at or sale price | Currency, tax treatment, sale dates |
availability |
Inventory level and stock policy | Per variant, including back-order and pre-order rules |
gtin, brand, mpn |
Barcode field, vendor, SKU | Manufacturer-issued values, not internal codes |
image_link |
Main product or variant image | Reachable, the right variant, no overlays |
item_group_id |
Parent product | Variants grouped correctly |
shipping |
Account shipping settings or feed values | Matches what checkout charges |
The source of the feed matters: a platform app (such as Shopify's Google and YouTube app, or a WooCommerce Google extension), a third-party feed app, a scheduled file or a direct connection through Google's API. Each has its own mapping options and limits.
Price, stock and variant issues
- Price. Sale prices in the store but not the feed, prices with or without VAT inconsistently, or currency conversion apps showing a different price on the page. See price mismatch.
- Stock. Feeds that update less often than stock changes, products that sell out between updates, or "continue selling when out of stock" settings that the feed reads differently from the page. See availability mismatch.
- Variants. A landing page that opens on a different variant from the one in the feed, so price, colour or stock no longer match. We check that each variant's
linkselects that variant.
Identifier and image checks
- GTINs. Must be the manufacturer-issued barcode, in a valid format, with a correct check digit. Internal SKUs placed in the GTIN field cause invalid-identifier issues. Where products genuinely have no GTIN, such as custom or handmade goods, Google's product data specification provides for that case. See missing or invalid GTIN.
- Brand and MPN. Consistent, and not your store name unless you are the brand.
- Images. Image URLs that load for Google's crawler, are not blocked, show the product without promotional overlays or watermarks, and match the variant. Google's image requirements are updated from time to time, so we check them against the current product data specification rather than older guidance. See image issues.
Structured data
Google can read price and availability from schema.org Product and Offer markup on your product pages, and can use it to check or update your feed data. We check that the markup:
- shows the same price and currency as the visible page and the feed;
- shows the availability of the selected variant, not just the first one;
- is not duplicated by a theme and an app that both output it.
An illustrative example of a conflict we look for:
Feed: price 40.00 GBP availability in_stock
Page shows: £32.00 (sale) "In stock"
Page markup: "price": "40.00" "availability": "https://schema.org/InStock"
Result: sale price missing from feed and markup
Validation
- Correct the data at its source where possible, so the fix survives the next sync.
- Use supplemental feeds or feed rules only where the source can't be changed, and document them.
- Spot-check corrected products on the live page, in the markup and in the feed.
- Confirm in Merchant Center that the updated data has been processed and issue counts have changed.
- Hand over what changed, which products were affected and what to watch for.
Correcting data and obtaining approval are different things. We can make your data accurate and consistent. Google decides whether products are approved and when.
Scope and pricing
Feed and Merchant Center diagnostic
From £399
Affected products, causes in the feed, store data or pages, and a list of corrections.
Request a diagnosticDefined data or feed correction
From £495
One agreed correction or cohesive set of corrections, validated after processing, with a handover.
Check my product feedSeveral feed sources
Quoted after review
Several feeds, several countries or account-policy issues. Scope agreed in writing first.
Merchant Center disapprovalsNot included unless quoted: rewriting product copy across the catalogue, photography, ongoing feed management, or Merchant Center account appeals. See pricing.
Introductory pricing. These are introductory prices for our current service packages. We agree the scope and price with you before work starts. Future prices may change, but an accepted quote won't change without your agreement.
FAQ
Do I need a paid feed app?
Not always. Many issues can be fixed in the store data or with the platform's own Google integration. We recommend a paid app only when the evidence shows it is needed.
Will this improve my Shopping ad performance?
Accurate data can keep eligible products showing, but we don't promise performance. Bidding, budgets and competition decide the rest.
Not sure what's wrong?
Send us your store address. Mikael will look at the public pages and tell you what he can see, and what he can't.