Case studies / eCommerce
Merchant Center reinstatement & Google ShoppingGoogle says you violated the policy. It won't say which part.
Sky Diamond Co's Merchant Center account was suspended for misrepresentation: the vaguest and most punishing policy Google enforces. One generic notice, roughly twenty possible causes, and every wrong guess burns an appeal. We found it in two appeals and had the account live in five weeks.
A luxury retailer in the most scrutinised category Google has.
Sky Diamond Co sells luxury watches and jewelry online, a category Google polices aggressively because it's also where counterfeit and misrepresentation activity concentrates. Legitimate sellers routinely get caught in the same enforcement net as the sellers Google is actually trying to stop.
Their Merchant Center account had been suspended for misrepresentation with no indication of which part of the policy triggered it, the same generic notice Google sends for roughly twenty different possible causes.
Misrepresentation is a guessing game with a limited number of guesses.
Google sends the same generic notice for every variant of this policy. A missing return policy, a price mismatch between feed and landing page, an unverifiable business address, a third-party feed it can't trace: identical email, identical vague reference. You are told you violated the policy. You are not told which part.
Fix something plausible, submit, wait.
The instinct is to fix the most obvious thing and appeal. If that wasn't the trigger, the appeal fails, the clock restarts, and the account has a rejected appeal on its record. Repeat suspensions and failed appeals attract tighter scoring on everything that follows.
- Diagnosis Guesswork
- Appeals consumed One per guess
- Recrawl delay Repeats each time
- Time to live Months
Work the full list before touching anything.
Roughly twenty distinct conditions can produce a misrepresentation flag. Auditing all of them against the account and the site before submitting anything means the appeal addresses the actual cause rather than a likely one, and it only has to be made once.
- Diagnosis Systematic
- Appeals used 2
- Feed rebuilt before submitting Fully
- Time to live 5 weeks
The vendor hired to make the feed easier was why the account died.
Sky Diamond Co sells luxury watches and jewelry. To populate Merchant Center they had engaged a data management company that pulled product feeds from upstream sources and pushed them into the account.
It's a common arrangement and it looks like a sensible way to handle thousands of SKUs. It's also close to the exact signature Google's verification systems are built to flag.
Four things were working against the account at once.
-
Luxury watches are the highest scrutiny category there is
Misrepresentation and counterfeit suspensions cluster in luxury goods, watches, handbags, sneakers. Google enforces aggressively against counterfeits, and legitimate sellers are routinely caught in the same net. The category starts from a position of suspicion.
-
A third-party feed is hard for Google to verify
When product data arrives via an intermediary, the signals Google uses to confirm a merchant actually controls its inventory get weaker. Image provenance, supplier of origin data, and identity consistency all become harder to establish, and unresolved, that reads as misrepresentation.
-
The notice named the policy, not the cause
One generic email, roughly twenty possible triggers, and no indication which applied. Every merchant in this position is guessing, and the appeals are finite.
-
Nothing could run in the meantime
Suspension isn't degraded performance. Shopping stops entirely. In a category where the alternative acquisition channels are slow and expensive, every week offline has a cost that doesn't appear in any report.
Four steps, and the order was the whole thing.
Nothing downstream mattered until the account could serve. Nothing about the appeal mattered until the feed was actually fixed.
Audit against every trigger, not the likely ones
We worked the full set of conditions that can produce a misrepresentation flag against both the Merchant Center account and the site: identity and business verification signals, policy pages, feed-to-landing-page consistency, product data provenance, checkout, and contact information. The point was to find the actual cause rather than a plausible one, because a wrong guess costs an appeal.
The third-party feed arrangement was at the centre of it.
Rebuild the feed from the ground up
We took the feed off the data management vendor and restructured it entirely: product data, attributes, identity signals, and consistency between what the feed claimed and what the site showed. This is the unglamorous part and it took the bulk of the five weeks.
Every product now traceable to the merchant rather than an intermediary.
Appeal once the crawler had caught up
Google reviews against what its crawler has indexed, not what the site looks like on the day you submit. Appealing before a recrawl means the reviewer is assessing the old version, which is how merchants burn appeals on work they've already done. We timed submission accordingly. As a Google Partner with access to the Elevate program, we also have escalation routes a standard advertiser doesn't.
Reinstated on the second appeal. Five weeks from start.
Then build the campaigns
With the catalog eligible again, we built Google Shopping across the restructured feed and Brand campaigns to defend searches for Sky Diamond Co's own name: traffic a competitor will otherwise intercept, at a fraction of generic keyword cost.
$7,000 a month, running for twelve months.
About that 2000%.
Google Ads reported a 2000% return on ad spend across the engagement. At $7,000 a month over twelve months, that's $84,000 of spend against roughly $1.68 million in reported revenue.
Here's the part that belongs on the same page as that number.
Roughly 90% of orders above $100,000 were fraudulent. They were identified and filtered by Sky Diamond Co's own internal team before fulfilment. They never shipped, and they were never real revenue.
This is not unusual in luxury ecommerce. It is close to universal. High-value jewelry and watch transactions attract stolen card testing at a rate that would be extraordinary in any other category, and a five or six figure order that converts cleanly in the platform's reporting can be reversed days later.
Which means platform-reported ROAS in this category is a gross number, not a net one, and we can't tell you where the 2000% sits on that spectrum, because we didn't run the client's fraud filtering. What we can tell you is that the figure is what Google Ads reported, and that a single fraudulent six-figure order represents several percent of it.
Why we're publishing it that way
We could have written "2000% ROAS" and stopped. Every agency case study in this category does.
But anyone who has actually run paid media for a jewelry retailer knows about the fraud problem, and a page that omits it tells them one of two things: either we didn't encounter it, which would mean we hadn't run the account long enough to matter, or we did and chose not to mention it.
The useful version is the honest one. If you sell high-value jewelry online, your reported ROAS is not your ROAS, and any agency quoting a platform number at you without raising that is either inexperienced in the category or hoping you won't ask.
Four things worth taking from this.
Don't appeal until you know the cause
Appeals are finite and failed ones attract tighter scoring. Audit against every possible trigger before submitting anything, a plausible fix that isn't the actual fix costs you more than the delay would have.
Recrawl timing decides the outcome
Google reviews what its crawler has indexed, not what your site looks like today. Submitting before a recrawl means the reviewer is assessing work you've already replaced.
Third-party feed vendors are a suspension risk
Anything that puts an intermediary between your inventory and your feed weakens the signals Google uses to verify you control what you're selling. Convenient, and increasingly expensive.
In luxury, reported revenue isn't revenue
Fraud rates on high-value transactions are severe enough to distort any platform ROAS figure. Reconcile against fulfilled orders before you make budget decisions on it.
What went into it.
Six of our services, on one account.
Suspended, or worried you're about to be?
If your Merchant Center account is down, don't submit another appeal until someone has audited against every trigger: each failed attempt makes the next one harder. And if you're running a third-party feed in a scrutinised category, it's worth knowing where you stand before Google decides for you. Findings are yours to keep either way.
Read-only access · No obligation · You keep your accounts