Google Merchant Center misrepresentation: why the fix is on your website, not your feed

A disapproved attribute is mechanical: a missing GTIN, a wrong price format, a broken image link. Misrepresentation is different. It is Google’s judgement that your store does not present itself honestly or completely enough for shoppers to trust it. That judgement is made by looking at your website, not by parsing your feed file. This is why merchants with a technically clean feed still get flagged, and why re-uploading the feed changes nothing. The policy is about the business you appear to be, not the data you submitted.

• Attribute issues are about the feed data; misrepresentation is about your storefront.
• Google reaches this verdict by visiting your site, not by reading the feed.
• A clean feed does not clear a misrepresentation flag; the site has to pass.

Misrepresentation usually comes down to a handful of trust signals a shopper, and a reviewer, expects from a legitimate store. Treat the list below as an audit of your own site. Each item is something Google can verify by browsing, and each is a place honest stores quietly fall short.

• Business identity: a real About page that says who runs the store, where it operates from, and what it sells, not a stock template.
• Contact methods: a working way to reach you (email, form, or phone) that a shopper can actually find, not buried or absent.
• Return, refund, and shipping policies: clear, findable, and specific enough to act on. Vague or missing policies read as a red flag.
• Price and availability consistency: the price and stock on the product page must match the feed and the checkout, with no surprise at the last step.
• A secure, functional checkout: HTTPS across the site and a checkout that actually completes. A broken or insecure buying flow undermines the whole store.
• Claims you can back up: discounts, guarantees, endorsements, or health and safety statements you cannot substantiate count against you.

None of these live in the feed. They live on the pages Google crawls when it decides whether to trust your store.

When a store is flagged, the instinct is to fix the feed and resubmit. With misrepresentation that rarely works, because Google re-crawls the storefront, not just the feed file. If your About page is still thin or your refund policy is still missing, the flag stays even after a flawless feed upload. The order matters: fix the site first, confirm each change is live on the page a shopper would land on, and only then reconcile the feed so every value matches what is published. The feed and the page have to tell the same story, and Google reads the page to check.

• Fix the storefront first: identity, contact, policies, pricing, checkout, claims.
• Confirm each change is live on the actual page, not just staged or saved as a draft.
• Then align the feed so price, availability, and details match the published page.

Misrepresentation is not a one-time cleanup. Policies drift, a theme update hides a link, a price changes on the page but not the feed, and the store slides back toward a flag without anyone noticing. The stores that stay healthy treat their site and feed as something to audit on a schedule, not something to fix once under pressure. A regular check across both surfaces, the trust signals on the site and the attribute health of the feed, catches the drift early, while it is still a small correction and not an account-level problem. This is where monitoring earns its place: a record of what was flagged and changed, and an alert the moment something new slips. It is an informational check, not legal advice, and it does not guarantee compliance, but seeing the problem coming is most of the work.