Google Merchant Center management: feeds, disapprovals, and Shopping-ready product data
Shopping ads and Performance Max can only be as good as the product data underneath them. When Merchant Center
fills with warnings, the cause is rarely bidding. It's titles, identifiers, prices, policy pages, or a feed
still pointing somewhere it shouldn't.
We audit and fix product data against Google's product data specification: titles, GTIN, MPN and brand,
price, availability, shipping, returns and images.
Google treats misrepresentation as an egregious violation and can suspend accounts without warning, so
business details and policies are fixed before any appeal.
Custom integrations must move to Merchant API: the Content API for Shopping reached sunset on August 18,
2026, with intermittent failures from September 1 and shutdown planned for early 2027.
Feeds are structured for Shopping and Performance Max with custom labels for margin, seasonality and stock.
Proof: we cleared misrepresentation warnings for a client with a corrected store URL and a custom XML feed
built from live Shopify data.
Who this is for
Stores with a growing list of item disapprovals or "limited performance" warnings.
Merchants whose account was suspended or warned for misrepresentation.
Advertisers running Performance Max on a feed nobody has looked at since setup.
Businesses on custom platforms, or with in-house scripts that called the Content API for Shopping.
Stores selling internationally that need different price, tax and return rules per country.
What's included
Diagnostics review. Account-level issues (policy, verification, business information) and
item-level issues grouped by root cause, with the number of products each one affects.
Product data fixes at the source. Corrections made in your store platform or feed generator,
not as one-off edits in Merchant Center that the next sync overwrites.
Identifier cleanup. GTINs checked against the GS1 registry, MPNs separated from internal
SKUs, and identifier_exists used only where it's true.
Shipping and returns. Shipping settings and return policies configured in Merchant Center,
with exceptions labelled per product, matching what your site says.
Structured data alignment. Product, Offer and ProductGroup markup on your pages agreeing with
the feed on price, availability and identifiers.
Feed rebuilds and API migration. Custom or supplemental feeds when a plugin can't produce
compliant data, and rewrites of Content API integrations onto Merchant API.
Suspension recovery. A documented fix list and the appeal itself, timed for when the site has
actually changed.
The campaigns themselves are covered on our paid search page; this service
makes sure they're fed clean data.
How we fix a Merchant Center account
Read the diagnostics
Account-level issues first (policy, verification, business information), then item-level issues grouped by
cause rather than by product.
Fix at the source
Corrections go into the store platform or the feed generator so they don't come back with the next sync.
Rebuild the feed if needed
When a plugin or app can't produce compliant data, we build a custom feed — often a small serverless
function that reads live store data and outputs exactly the attributes Google requires.
Verify and request review
Spot-check items against landing pages, then request reviews or appeals with the fixes documented.
Monitor
Weekly diagnostics checks so new problems are caught within days, not at the next campaign review.
Common Merchant Center mistakes
identifier_exists set to "no" on products that have barcodes.
A platform's Google channel and a third-party feed both submitting the same products.
Sale prices updated on the site but not in the feed.
US-style tax-exclusive prices submitted for UK or EU targets, where Google expects VAT included.
A return policy that only covers defective items, sits behind a login, or contradicts the policy in Merchant
Center.
AI-written titles submitted in title instead of structured_title.
A domain change without updating the store URL and re-verifying.
Appealing a suspension before anything on the site has changed.
1–150 characters; must describe the same product as the landing page and distinguish variants. Titles
written with generative AI go in structured_title
Strongly recommended where a manufacturer-assigned GTIN exists
Left blank on branded products, or invented
mpn
Required only if the product has no manufacturer GTIN; an incorrect MPN gets the product disapproved
Internal SKUs submitted as MPNs
identifier_exists
Set to "no" only when identifiers genuinely don't exist; saying "no" when they do risks disapproval
Set to "no" across the whole catalog to silence warnings
price
US and Canada: exclude all taxes. Most other countries, including the UK and EU: include VAT or GST, and
show the same price on the page and at checkout
Feed price differs from the page after a sale ends
availability
Must match the landing page, checkout and structured data
Feed says in stock, page says sold out
custom_label_0–4
Five free-form labels for segmenting campaigns; not shown to shoppers
Unused, or filled with values that never change
On titles, Google notes that people usually notice only the first 70 or so characters, so we put brand, product
type and the deciding attribute first and use the rest of the 150 for detail.
Misrepresentation: what Google is looking for
Google's
misrepresentation policy
covers listings that leave out relevant information or mislead users about products or the business.
Unacceptable business practices are treated as egregious: Google says accounts are suspended upon detection
without prior warning, and reinstated only in compelling circumstances. Its examples include presenting a false
identity or contact information, hiding where the business or its fulfillment is actually located, and refusing
returns despite a stated return policy.
Before any appeal, we work through a checklist so the second review sees a different business:
The same business name, address and phone number on the site, the Business Profile and Merchant Center.
Visible, specific shipping, return and refund policies, and a real contact page.
Prices and availability that match between feed, product page and checkout.
Claims removed if you can't substantiate them.
The store URL in Merchant Center matching the domain the feed actually links to.
That last item is not hypothetical. On the Squeaky Clean Turf project the Merchant Center store URL still
pointed at the old WooCommerce domain after the move, which was part of what triggered the warnings.
Return policies Google will verify
Return policies set in Merchant Center can appear on ads, free listings and Gmail, and Google verifies them
before use, showing each one as verified, pending or rejected. Google's
return policy requirements
are specific:
The policy must cover general returns such as buyer's remorse, not only defective products.
It must be reachable without logging in, signing up or entering personal information.
It must match across Merchant Center, the returns page, the footer and any banners.
It should state the return window, method and any return or restocking fees.
Products that can't be returned, or have a shorter window, get an exception policy and a
return_policy_label in the feed. We publish the same terms in MerchantReturnPolicy markup so Search
and Merchant Center read one version.
The Merchant API migration
Google's
deprecation notice
sets the timeline: the Content API for Shopping reached its sunset date on August 18, 2026; from September 1,
2026, requests without an approved extension start failing intermittently with HTTP 410; full decommissioning is
planned for early 2027. Those artificial errors don't count against API quota, and retrying sometimes works, but
Google is explicit that retries aren't a long-term fix because failures become more frequent.
If you connect through an ecommerce platform, the platform handles the migration. If you have custom scripts,
internal tools or a bespoke feed service calling the Content API directly, they need to move to
Merchant API. Google offers an extension request for more time, but extensions don't run past decommissioning. We audit
those integrations, check logs for the 410 error, and rewrite them.
Feed structure for Shopping and Performance Max
Custom labels for margin tier, best sellers, seasonality and clearance, so campaigns and
asset groups can be split by business value rather than by category.
Titles built as brand, product and the attributes people search for, within the 150-character
limit and describing the same product as the landing page.
Supplemental feeds to enrich or correct data without overwriting what your store platform
sends.
One source of truth. Two competing feed sources for the same products cause flip-flopping
data and warnings. Pick one.
Pricing and engagement
Cleanup and suspension work is a fixed-fee project. Ongoing feed management is a flat monthly
fee, or included when we run your Google Ads under our flat-fee managed service, which covers Performance Max
(see the pricing page). No percentage of spend, and no long contracts.
We corrected the store URL that still pointed at the old domain, wrote a custom XML product feed as a
Cloudflare Pages Function pulling live Shopify data with the identifiers, measurements and shipping
attributes Google required, re-verified the domain, and removed a half-configured Google channel that was
fighting the feed.
Our open-source audit framework connects to Merchant Center alongside Google Ads, GA4 and Search Console, so
feed problems show up next to the campaign data they affect.
John Williams has written on feed-driven Google Ads performance for Feedonomics, and has managed paid media for
feed-heavy advertisers, including General Motors' Vehicle Listing Ads — see about and our
paid search portfolio.
Frequently asked questions
Why are my products disapproved in Merchant Center?
Usually one of a few causes: missing or wrong identifiers, prices or availability that don't match the landing
page, titles over 150 characters or describing a different product, or a policy issue. The diagnostics view
groups items by issue; fix the cause at the source so it doesn't return next sync.
My account was suspended for misrepresentation. What should I do?
Don't appeal straight away. Google treats misrepresentation as egregious and reinstates accounts only in
compelling circumstances. Fix business information, policies, pricing consistency and unverifiable claims
first, then appeal with the changes documented.
Do I need GTINs?
Google strongly recommends submitting the manufacturer's GTIN wherever one exists. If a product genuinely has
no GTIN, submit brand and MPN, or set identifier_exists to no. Never invent identifiers.
Should my feed prices include tax?
It depends on the target country. For the US and Canada, leave all taxes out of the price attribute. For most
other countries, including the UK and EU members, include VAT or GST and show the same price on the page and
at checkout.
Does the Content API for Shopping sunset affect me?
Only if you or a vendor built a custom integration that calls it directly. Platform integrations are migrated
by the platform. Custom scripts started failing intermittently from September 1, 2026 and will stop entirely
in early 2027.
Should I use Shopify's Google channel or a custom feed?
Start with the native channel; it's simpler. Move to a custom or supplemental feed when the channel can't
output the attributes you need. Don't run both for the same products.
Can you run the Shopping and Performance Max campaigns too?
Yes. Our paid search team manages Shopping and Performance Max on a flat monthly fee, using the same feed we
maintain.
Get your Merchant Center reviewed
Tell us your store platform, roughly how many products you list, and what Merchant Center is flagging.
John, Kristy, or Sandeep will reply.One of the three of us will respond personally within 1 business day. No SDR queue.
Message received.
One of us will reply directly within one business day. While you wait, run a free
Buddy audit on your account.
Top 25 references
The primary sources, standards, research, and tools we rely on for this work. Every link was checked on
2026-10-11. We aren't affiliated with these publishers unless noted.
Official documentation
Product data specification— Google Merchant Center Help Every product attribute Google accepts, with required, recommended and conditional rules; the document we
audit feeds against.
Misrepresentation— Google Merchant Center Help What Google treats as misleading or egregious, including the statement that unacceptable business practices
are suspended without prior warning.
GTIN [gtin]— Google Merchant Center Help When a GTIN is expected, which formats are valid, and why invented or reused identifiers cause
disapprovals.
Identifier exists [identifier_exists]— Google Merchant Center Help The narrow cases where setting identifier_exists to no is correct, and the risk of using it on products
that do have identifiers.
Custom label 0–4 [custom_label_0–4]— Google Merchant Center Help The five free-form labels used to segment Shopping and Performance Max by margin, seasonality or
stock.
About Performance Max campaigns— Google Ads Help How Performance Max uses a Merchant Center feed across Google's inventory, and why feed quality limits
what it can do.
Content API for Shopping: deprecation and sunset— Google for Developers Sunset on August 18, 2026, intermittent HTTP 410 errors from September 1, 2026, and full decommissioning
planned for early 2027.
Manage your products (Merchant API)— Google for Developers How product inputs, data sources and processed products work in Merchant API, the model replacing Content
API calls.
Merchant listing structured data— Google Search Central On-page Product and Offer markup that has to agree with the feed on price, availability and
identifiers.
Product variant structured data— Google Search Central ProductGroup markup for size and color variants, the on-page counterpart to item_group_id in the
feed.
Merchant return policy structured data— Google Search Central How to publish return policies in markup so Search and Merchant Center see the same terms.
Verified by GS1— GS1 GS1's registry of brand-owner product data, the kind of source Google and retailers check identifiers
against.
Offer— Schema.org The vocabulary for price, availability and seller details that merchant listing markup is built on.
MerchantReturnPolicy— Schema.org The schema type for return windows, fees and methods referenced by Google's return policy
markup.
Industry reports & benchmarks
Performance Max study— Optmyzr An October 2024 analysis of 9,199 accounts and 24,702 Performance Max campaigns, including how feed
presence and structure relate to results; one tool vendor's dataset.
Leading tools
GS1 US company database— GS1 US Look up which company a GTIN prefix is licensed to, the quickest way to spot a reused or resold
barcode.
Merchant API code samples— Google on GitHub Google's official Java, Python and PHP samples, the starting point for rewriting a custom Content API
integration.
Google & YouTube app— Shopify App Store Shopify's native Merchant Center connection, which should be the only feed source when it's in
use.
Productsup— Productsup A feed management platform for transforming one product catalog into channel-specific feeds when a native
integration can't.
Expert guides
Shopping news and updates— The Keyword (Google blog) Google's own announcements for Shopping and Merchant Center features, worth reading before third-party
summaries.
AI disclosure: This page was drafted with AI assistance and edited by a human. Third-party facts
link to the official source they came from (checked 2026-10-11); platform names and logos belong to their owners
and do not imply a partnership or endorsement.
