MerchantCure Free Quick Scan

Google Merchant Center · suspension recovery

Your account is suspended for misrepresentation. Something specific caused that.

We find what it was, prove it with evidence you can attach to an appeal, and hand you the fixes.

If we look at your shop and cannot help, we say so and you pay nothing.

Free Quick Scan What it costs

The scan starts when you press the button and finishes in under a minute, while you wait. No booking, no call, no waiting for office hours — it is three in the morning somewhere, and that is usually when people read this.

Self-service the whole way: scan, price, pay, diagnosis. Nobody has to get back to you. The scan is also our triage — it is how we find out whether we can help at all.

Suspended for something else? Shipping and returnsUntrustworthy promotionsContact informationBusiness identityPrice mismatchRestricted products

3 fields we will ever write in your shop Product description, short description, name — and only the ones you approve. Price, stock and visibility are never written.
Free for the first look, and for a no The Quick Scan costs nothing, including when we decline the case.
13 policy references, every one linked Google's own page, with the clause quoted verbatim.
Critical

Feed and page disagree on currency

The page says one currency, the feed says another, on rows that match. Google reads the feed. Your customer reads the page. Only one of them is buying.

Critical

Channel names another domain

The feed declares a different domain as its channel than the one it is served from. Common in country networks, invisible from the shop, and it makes the whole file look like it belongs to someone else.

Medium

Several feed files, one connected

Three files on one server, two of them misconfigured. Which one is actually connected is only visible inside your account, so the check lists them and never guesses.

While it is down

Every day suspended is a day Shopping sells nothing.

A suspended Merchant Center account stops serving Shopping and Performance Max. That part is not a forecast — the ads stop, and they stay stopped until the account is reinstated.

Show figures in
If Google brings you, a day

Your number, our arithmetic. We multiply the figure you picked; we do not claim to know it.

  • The figures above are round numbers to pick from, not a measurement of your shop.
  • We do not know how long your suspension will last. Nobody outside Google does.
  • We do not know what share of your revenue comes from Google. You do.
  • Fixing what we find does not decide the appeal. A reviewer does.
Free Quick Scan

01  /  If this is where you are

Suspended for misrepresentation, and nobody will tell you what for.

This is the ordinary shape of it. If most of these are true for you, you are in the situation this was built for.

  • The notice says misrepresentation and then stops. It does not say which product, which page, or which field.
  • You have read Google's policy page more than once and it describes a category, not your shop.
  • Your storefront looks correct when you open it. Prices are right, the returns page is there, the phone number works.
  • You have appealed at least once and got back text that looks like the first notice.
  • Nobody you have asked will name the specific thing that is wrong.

None of that means your shop is dishonest. Almost no suspended merchant is lying. It means two things in your setup disagree with each other, and an automated comparison found the gap before you did. Something specific caused it, and it can be located.

02  /  What a finding looks like

Not an opinion about your shop. A measurement, and the rule it breaks.

These are real classes of fault from real diagnoses, with every identifying detail removed. The shape is exactly what you receive.

Critical Feed check

The feed and the page disagree about the price — by one constant factor

Google compares your feed against your landing page. When the amounts differ, it treats the offer as misrepresented, and a single systematic factor across many rows reads as a pricing practice rather than a glitch.

Evidence
page
126.79
feed
107.52
ratio
1.17925 — identical on all 53 compared rows

A constant ratio is the finding. It rules out data entry and points at one process: (1 + 25 %) ÷ (1 + 6 %) = 1.17925. The page charges one VAT rate and the feed calculates with another.

Rule Merchant Center: Misrepresentation

Measured 17 August 2026 on a live store.

Critical Feed check

The feed names a different domain than the shop it was generated for

Merchant Center reads the feed as a description of one store. When the channel and the image host point at another domain, the account is describing a business other than the one being reviewed.

Evidence
product links
example-shop.dk  ← correct
channel
example-group.eu  ← wrong
image host
example-group.eu  ← wrong

Some fields right and others wrong in the same file is the tell: three subsystems each decide their context independently.

Rule Merchant Center: website requirements

Illustrative — constructed to show the shape of the fault. The numbers are not from a measured run.

Medium Feed check

Several feed files sit on the server, and only one of them is connected

Nobody can tell from the outside which file Merchant Center actually fetches — that is only visible inside the account. A stale file left in place is a common reason a fix appears not to work.

Evidence

3 product feeds served publicly. 2 misconfigured. 1 connected.

We never guess which one is live. We tell you where to look, and the finding stays labelled unconfirmed until you have looked.

Rule Merchant Center: fix warnings and suspensions

Illustrative — constructed to show the shape of the fault. The numbers are not from a measured run.

Which of these does your shop have? Find out free

03  /  How it works

Diagnosis, fixes, recipe cards, reinstatement dossier.

Four stages, and you approve every change before it happens. Text fixes can be written straight into your shop once you approve them, one change at a time. Prices, stock and visibility are never written — those come as recipe cards you run yourself.

  1. Diagnose, with evidence

    We fetch your shop the way Googlebot meets it — no cookies, no JavaScript — and run seven checks in a fixed order. Every finding carries the exact quote, status chain or measurement it rests on, plus the Google policy it breaches. A finding we cannot show you is a finding we do not report.

  2. Compare the feed against the pages

    The one check that produces a machine-readable proof: your product feed, row by row, against the structured data on the matching page. Price, currency, availability, title. This is the comparison Google itself makes, and it is where the causes usually are.

  3. Text fixes we write, cards you run

    Approved text fixes go straight into a WooCommerce shop — one change at a time, logged with the original value, undoable exactly. Everything else is a recipe card: numbered click-steps, before/after pairs to approve, what the card does not touch, and how you confirm it worked. Prices, stock and visibility are never written.

  4. A reinstatement dossier, dated and measured

    Three to four pages you attach to the appeal. Every item carries a before measurement, an after measurement and the date it was verified. Unresolved items stay in the document — a dossier that lists only wins reads as marketing to the person who has to approve it.

Three kinds of fix, and we say which is which

  1. We write it

    A finished change per product, with the exact text before and after. You approve each one on its own, or reject it. Every write is logged with the original value and can be undone exactly.

    Text fields only, and only where the correction can be calculated rather than judged. Today that is 1 fault class out of 66.

  2. You run the recipe card most of what you get

    Numbered click-steps for your platform, before/after pairs to approve, what the card explicitly does not touch, and how you confirm it worked — logged out, after a cache purge.

    The bulk of what we find: export settings, feed jobs, themes, plugins. Anyone you hand the card to can run it.

  3. Your decision

    We state the fault, the evidence and the policy clause, and stop. No recommendation dressed up as a fact.

    Legal wording, medical claims, which of two contradictory pages is the true one, and anything that needs an account we do not have.

What lands in your inbox

  • A diagnosis report with the evidence for every finding
  • The policy clause each finding breaches, quoted and linked
  • A recipe card per fix, in click-steps a non-technician can follow
  • Before/after text pairs you approve before anything changes
  • A verification pass once you have done the work
  • The reinstatement dossier you attach to the appeal

Length scales with your shop. The run cited on this page produced 33 findings carrying 96 pieces of evidence, measured 17 August 2026.

That is the whole chain. It starts with one URL. Free Quick Scan

04  /  Who is behind this

One person built this, against a shop that was actually suspended.

MerchantCure was built against a live, suspended Merchant Center account in our own group of 30+ shops — not against a theory — and measured against a paid agency audit as an outside yardstick.

Why it exists

Every check in the tool exists because something in that shop broke and had to be found. It was not designed as a product first and pointed at a problem afterwards, which is why the checks are oddly specific — a per cent sign corrupted into a marker string, a brand name translated into a common noun, three feed files where one is connected.

That is also its limit. The measurements on this site come from a small number of real shops, not from a survey, and each figure says which dated run it came from.

Who you are dealing with

The seller is Holm IT AB, registered in Sweden — company number 556980-7307, VAT SE556980730701. Those are in a public register, and you can look them up before you pay anything.

The scan itself is automatic — the same checks run whoever you are, which is the point of a measurement. The person who built the tool is the one who steps in when it cannot do the job: when your shop blocks the scanner, when a finding needs a judgement rather than a rule, and when you write back. There is no support queue and no sales team.

Built against a real suspension. Point it at yours. Free Quick Scan

05  /  Customer reviews

There are none yet. MerchantCure is taking its first paying cases now, and this space stays empty until real customers have written something we can link to.

We would rather show you a hole than a placeholder. If a supplier shows you five glowing testimonials and no way to check them, that is the same category of problem we get paid to find.

06  /  What else you could do

Four other ways to approach this, and what each one hands you.

Three of the four are worth doing, and two of them are free. This is not a list of bad options — it is what each one actually hands you, so you can tell which gap you are trying to close.

Approach Names the specific cause? Gives you something to attach? Does the work? Costs if it does not help?
Appeal again, unchanged Resubmitting the request for review without having changed what caused the suspension. No. The notice is the same category it was the first time. Nothing to attach. No. No money — and this is the one to be careful with. Review requests are a finite resource. One is spent whether or not anything changed, they are read one at a time, and how many an account has left is only visible inside it. The free option is the one that can cost you the most.
Ask Google support Contacting Merchant Center support and asking what is wrong with the account. Support can confirm the policy and the account state. Naming the specific fault on your site is not something they undertake to do. Not in a form you can attach to an appeal. No. Free, and worth doing. It is simply rarely enough on its own.
A general agency or freelancer, by the hour Bringing in someone who knows Merchant Center to look at the account and the shop. Often, and a good one will find things no tool would. It depends entirely on who you get. Sometimes. A written audit is common; a before and after measurement with dates on both is not. Yes — and this is where the approach beats ours outright. They can go into the shop, the theme and the server and change whatever needs changing. Our write access is three text fields. The hours, whether or not the cause was found.
A feed tool or optimisation plugin Software that validates and rewrites your product feed against Merchant Center's specification. Partly. It checks the feed against the spec — a real and useful check. The comparison that causes most misrepresentation suspensions is between the feed and your own pages, which is a different one. Validation output, not an argument a reviewer can follow. Yes, within the feed, and usually automatically. A subscription that keeps running.
MerchantCure A fixed-price diagnosis of the public storefront and the feed, with the evidence for every finding and a dossier for the appeal. Where the cause is visible from outside, yes — with the measurement and the policy clause beside it. Where it is not, we say so and hand it back as a checklist. That is the product. Every finding carries its evidence, and every dossier item carries a before measurement, an after measurement and the date each was verified. Partly, and this is our weakest column. Approved text corrections we write into your shop ourselves. Everything else — export jobs, themes, plugin settings — is a recipe card you or your developer run. If you wanted someone to do all of it, an agency is the better fit. Nothing. The Quick Scan is free, including when we decline.

The one measured comparison we have

Benchmarked against a paid agency audit of one store: our scanner reproduced 4 of its 6 findings independently, the 2 it missed were built afterwards, and it found 7 things the audit did not.

One audit, one store. We have not surveyed the market and we do not claim to be alone in it — this is the only alternative we have actually measured against, and it is a good one.

Or let the scan answer it in under a minute. Free Quick Scan

07  /  How long it takes

Five steps, and only one of them has a number we can promise.

Where we know the time, it is stated. Where we do not, it says why — including the last step, which is not ours to time.

  1. 01

    The free Quick Scan

    Under a minute

    You enter the shop URL. The scan starts immediately and runs while you wait: we fetch the storefront the way Googlebot meets it and show you what we found. No booking, no call, no waiting for us to get to it.

    Carried out by You, self-service. A human looks by hand only if your shop blocks the scanner.

  2. 02

    The diagnosis

    Not published yet

    The full run: seven checks in a fixed order, the feed compared against your pages row by row, every finding with its evidence and the policy clause it breaches, plus a recipe card per fix and the order to do them in.

    The full run starts the moment payment clears and needs nothing from you. How long it takes scales with your catalogue, and we have not published a standard figure because we have not run enough shops of enough sizes to promise one that holds. A delivery time that slips is worse than a longer one that does not.

    Carried out by Automatic. You are told when it is done.

  3. 03

    You carry out the fixes

    Yours to schedule

    The cards are written as numbered click-steps, with before/after text pairs for you to approve first. Free and zero-risk work comes first; anything needing a database backup is scheduled for when nobody is stressed; feed regeneration goes last so it carries every correction at once.

    This one is yours, and it depends on your shop and who does the work. Most of it is settings rather than code. Where code is needed, the card carries the complete block.

    Carried out by Split. Approved text fixes we write for you, one at a time. Everything else is yours or your developer's — and prices, stock and visibility are never written by us.

  4. 04

    Verification and the dossier

    Not published yet

    We re-scan and produce the same measurements again, so every claim in the appeal has a before number and an after number with dates on both. Then the reinstatement dossier: three to four pages you attach to the appeal, with unresolved items left in.

    Starts when you tell us the work is done. Same reason as above for why no standard figure is published yet.

    Carried out by Us, once you say the work is done.

  5. 05

    Google reviews the appeal

    Not ours to say

    You submit the appeal with the dossier attached. What happens next is decided by a reviewer at Google.

    We cannot give you a time for this, and neither can anyone else outside Google. Any supplier who quotes you a number for this step is quoting you something they cannot know. What we can say is that the appeal will be answerable: every claim in it carries a measurement, a date, and a way for the reviewer to check it without taking our word for anything.

    Carried out by Google.

Only the first step needs anything from you. Start the scan

08  /  What it costs

Two things you can buy. The first one is free.

There is nothing between them and nothing after them. No retainer, no subscription, no upsell waiting at the end.

Show prices in

Quick Scan

Free

No card, no obligation.

An automatic first look at your storefront, in under a minute, while you wait. It is also our triage: if your case is one we cannot solve, you get told that, and there is nothing to pay.

Start the free scan

Emergency Cure

$500–$1,000 Approximate. You are charged in SEK.
€450–€900 Approximate. You are charged in SEK.
4,995–9,995 kr The exact amount. This is what the invoice says.
  • up to 500 products $500€4504,995 kr
  • 501 – 5,000 products $700€6306,995 kr
  • 5,001 – 25,000 products $1,000€9009,995 kr
  • over 25,000 products, or several domains quotedquotedquoted

One fixed price, paid once. Which tier you land in is decided by the number of products in your feed — a number you can count yourself, and one we agree with you before any work starts.

Start with the free scan → Price table and what it includes

Every Emergency Cure starts with the scan — it is how we confirm we can help before you pay.

We do not sell an Emergency Cure without doing a Quick Scan first. Amounts are invoiced in SEK; VAT is added where applicable.

09  /  On the roadmap

What we would build next, and what is still unsolved in it.

Neither of these exists. They are here so you know the direction — and so you can see that we know what is wrong with the idea before we sell you the idea.

10  /  Why you should believe the findings

The tool is built to be wrong loudly rather than confidently.

7

error classes, each proved from both sides: it fires on a fixture page with the fault planted on purpose, and it must not fire on a clean shop. The second half is the one that matters.

16

regression tests written from false alarms we actually produced. The first time we pointed the scanner at a healthy shop, 3 of 17 findings were wrong. Each one became a test so it cannot come back.

258

test cases across 23 test files in the engine. Not a quality claim — a count. It is the number that decides whether a change to one check quietly breaks another, and it is the reason a fix to the scanner is not a gamble.

See what it says about your shop. Free Quick Scan

11  /  One measurement worth sitting with

3,967 products submitted a day
108 that could actually be shown

That is from the run on 17 August 2026. The rows were rejected before anyone saw a single item-level error, and the merchant had no way to see the shape of it from the account screen. Knowing the number changed what to fix first — and in which order — more than any individual finding did.

12  /  Before you send anything

The questions people actually ask first.

Answered where you are standing, rather than after you have committed to something.

What if you do not find anything?

That is what the free Quick Scan is for, and it happens before you pay. If we cannot see a cause from outside your account, we say so and decline the case. If we do take it and the diagnosis turns up mostly things only you can verify from inside the account, you still get that list — with each item marked as unverified by us. What we do not do is fill a report with findings to justify its length.

Do I need a developer?

Usually not. Most fixes are settings in a plugin or an export job, written as numbered click-steps. Where a fix genuinely needs code, the card carries the complete block, commented, with the backup and dry-run steps before it. If you have nobody technical at all, say so in the scan — it changes which fixes we put first.

Do you write anything in my shop?

Text fixes, yes — once you have approved that exact change. Product descriptions and names, one change at a time, each logged with the value that was there before and undoable exactly. Prices, stock and whether a product is published are never written by us: those move money and shelf space, and they come as recipe cards you run yourself. Approving and writing stay two separate actions, so nothing happens because you read a list. It requires a WooCommerce API key you create and can revoke, and you can delete it from us at any time.

My shop blocks scanners. What then?

It happens, and it is usually bot protection doing its job. The scan says so instead of reporting an empty result as a clean bill of health — an absence of findings is not a finding of absence. When we cannot measure the catalogue we cannot price it either, so those shops get a quote instead of a fixed price, and a human looks by hand. That is still free.

Which platforms do you support?

The write-back is WooCommerce today. Shopify is not built, and we say so rather than list it. Everything else works on any platform: the scan reads your public pages and your feed, and the recipe cards are written for whatever generated what we found. The bulk of what we find lives in feed jobs, themes and settings rather than in product text, so most of the value does not depend on the API at all.

Do you get access to my Merchant Center account?

No. We do not request or accept access to your Merchant Center or Google Ads account, and we never touch them. We read your public pages the way Googlebot does, and any product feed served publicly. Anything that would need account access is handed back to you as a checklist.

What if Google rejects the appeal anyway?

That can happen, and nobody outside Google can tell you otherwise — the reviewer is theirs. Two things are still true afterwards: the faults you fixed are fixed, and a rejection usually points at something, which is information you did not have before. The dossier is built to be resubmitted, with the unresolved items still listed in it.

Can I do this myself?

Yes, genuinely. The suspension-reason pages on this site carry the steps in the order they need to happen, and none of it is secret. What you would be buying from us is the measuring and the writing-down: a crawl without cookies or JavaScript, a row-by-row feed comparison, and a dossier where every claim has a before number, an after number and a date. If you have the time and the patience, do it yourself.

What happens to what I send if I do not buy anything?

Your URL and email go to one inbox and are used to answer you. You are not added to a mailing list, and there is no follow-up sequence. If we do not take the case, we delete the crawl.

Still unsure? The scan costs nothing and answers it. Free Quick Scan

Start with the free scan.

Your URL and the reason Google gave you. The scan runs while you wait — under a minute — and shows what it found and whether we can help. If it cannot, we will tell you that instead of selling you something.

Free Quick Scan See what we typically find

No one outside Google can promise a particular decision — the reviewer is theirs, not ours. Our reporting tool refuses to emit a document that says otherwise, and the build of this website fails if a page claims it.