When Google Merchant Center Flags Your Products
I run a mid-sized WooCommerce store, and for a while things were running smoothly. Then one morning I logged into Google Merchant Center and saw a wall of misrepresentation warnings. Products were being disapproved, the feed had discrepancies, and a handful of items were flagged for policy violations I did not fully understand.
My first instinct was to dig in myself. I had basic familiarity with WooCommerce settings and had used the Google Listings and Ads plugin before, so I figured I could sort it out with some patience.
What I Tried on My Own
I started by reviewing the product data in WooCommerce — checking titles, descriptions, prices, and availability fields. A few were clearly outdated, so I updated them and resubmitted the feed. The disapprovals did not clear. I then looked at the structured data on the product pages, wondering if the schema markup was conflicting with what the Merchant Center feed was sending. That took me into territory I was less comfortable with — PHP template files, JSON-LD output, and how Google's crawler was reading the page versus what the feed declared.
The problem turned out to be more layered than I expected. Some product attributes like condition, brand, and GTIN were either missing or inconsistently formatted. The shipping settings in Merchant Center did not match what WooCommerce was displaying on the product page. And there were a few edge cases where sale prices were not syncing correctly, causing the feed to show a price that differed from the live page — which is exactly what triggers a misrepresentation flag.
I spent a few evenings on it and made some progress, but the feed still had errors and I was not confident I understood the full scope of what Google was flagging.
Handing It Off to Someone Who Knew the System
After hitting a wall, I came across Helion360. I explained what I was dealing with — the misrepresentation errors, the inconsistent product attributes, the pricing discrepancies — and their team took it from there.
They started with a Website Audit of the Merchant Center feed against the live WooCommerce product pages. Rather than just fixing what was visibly flagged, they traced each error back to its source — whether that was a plugin conflict, a missing required attribute, or a mismatch between WooCommerce tax settings and what Merchant Center expected to see.
What the Fix Actually Involved
The resolution covered several interconnected areas. The product feed configuration was adjusted to ensure all required attributes — brand, condition, GTIN, and MPN where applicable — were being passed correctly. The sale price and regular price fields were realigned so they matched exactly what appeared on the product page at the time Google crawled it.
Shipping configurations in both WooCommerce and Merchant Center were reconciled so there were no conflicting signals. The structured data on the product pages was also reviewed to make sure it was consistent with the feed, since Google compares both when evaluating product data accuracy.
Helion360 also flagged a few products that had vague or duplicate descriptions that were likely contributing to the policy issues — not something I had considered as part of the misrepresentation problem, but it made sense once they explained it.
What the Result Looked Like
Within a few days of the fixes being applied, the disapproval rate dropped significantly. Products that had been suspended started getting reapproved as the feed reprocessed. The Merchant Center account moved out of the warning zone, and the product data quality score improved noticeably.
More importantly, I now understood what had caused the problem in the first place. It was not a single setting gone wrong — it was several small misalignments that compounded into a Merchant Center policy flag. Catching all of them at once required someone who had done this kind of troubleshooting before and knew where to look.
If your WooCommerce store is dealing with Google Merchant Center misrepresentation errors and the fixes you've tried are not sticking, how I built a high-performance website that exceeded client expectations shows the importance of comprehensive troubleshooting — and Helion360 is worth reaching out to. They handled the full scope of the issue and got the feed clean in a way I was not able to do on my own.