Emergency Cure
The whole chain, from cause to appeal.
Diagnosis with evidence, recipe cards for each fix, before/after pairs you approve, a verification pass once you have done the work, and the dossier you attach to the appeal.
Every Emergency Cure starts with the scan — it is how we confirm we can help before you pay. It costs you nothing, including when the answer is that we cannot.
01 / What you get
Six things, in this order.
-
The diagnosis report
Three sections, always in this order: what we verified automatically, what requires your confirmation because we cannot see it from outside, and the action plan in priority order. Every finding carries its severity, one sentence on why Google cares, the exact evidence, and the policy it breaches.
The run we cite here produced 33 findings with 96 pieces of evidence attached, measured 17 August 2026. Length scales with your shop.
-
Recipe cards for each fix
One card per fault. Numbered click-steps a non-technician can follow, alternative approaches with the risk of each stated, what the card explicitly does not touch, and how you verify it worked — logged out, after a cache purge.
Where a fix needs code, the card contains the complete block, commented, with the backup and dry-run steps before it.
-
Before/after text pairs to approve
Nothing changes until you have seen both sides. Where a fault affects hundreds of rows, the card shows a dozen examples and a CSV attachment carries all of them — a document with 400 rows does not get read, and a document without them cannot be worked from.
-
The order to do them in
Ordered by risk and dependency, not by severity. Free and zero-risk work first; anything needing a database backup when nobody is stressed; feed regeneration last, so it carries every correction at once instead of being run four times.
-
A verification pass after you have fixed things
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.
-
The reinstatement dossier
Three to four pages you attach to the appeal. Each item: what was wrong, what was done, the measurement before, the measurement after, the date it was verified, and how a reviewer can check it themselves. Unresolved items stay in the document.
It stays locked as a draft until every item is both done and verified, so a half-finished dossier cannot be sent by accident.
02 / Price
One fixed price, decided by one number you can count yourself.
The number of products in the feed connected to Merchant Center. Not hours, not urgency, not the size of your ad budget. We write down which number we used — and if the count puts you in a different tier than we assumed, you hear it before we start rather than on the invoice.
- Paid once A fixed-price engagement, not a subscription and not a retainer.
- Fixed before we start The tier is agreed up front. It is not adjusted afterwards.
- Invoiced in SEK VAT is added where applicable, based on your location and business status.
- Nothing to pay to ask The Quick Scan is free, including when we tell you we cannot help.
| Catalogue size | approx. USDapprox. EURCharged (SEK) |
|---|---|
| S — up to 500 products A focused catalogue, one market. | $500€4504,995 kr |
| M — 501 – 5,000 products The common case. One or two markets, a real catalogue. | $700€6306,995 kr |
| L — 5,001 – 25,000 products Large catalogue, or several markets sharing one generator. | $1,000€9009,995 kr |
| XL — over 25,000 products, or several domains Networks where one misconfiguration repeats across domains. We quote after the Quick Scan. | quotedquotedquoted |
A rounded conversion of the SEK amount, shown so the price is readable — not a price in dollars, and not the amount the invoice will say. Indicative only, at the rate on 17 August 2026.A rounded conversion of the SEK amount, shown so the price is readable — not a price in euro, and not the amount the invoice will say. Indicative only, at the rate on 17 August 2026.The exact amount. SEK is what you are charged, to the krona.
We will publish fixed local prices when we can actually invoice in those currencies, and not before.
Every Emergency Cure starts with the scan — it is how we confirm we can help before you pay.
What the price includes
- The diagnosis report, with the evidence for every finding
- A recipe card for every fix, in steps a non-technician can follow
- Before/after text pairs for your approval
- The order to carry the work out in
- The verification pass once you have done the work
- The reinstatement dossier for the appeal
What it does not include
- Running the fixes. Approved text fixes we write for you, one change at a time. Everything else is a recipe card you or your developer run — prices, stock and visibility are never written by us.
- Submitting the appeal. We do not act as your representative towards Google.
- Anything only visible inside your Merchant Center account. That comes back as a checklist for you, marked as unverified by us.
03 / Triage
When we say no.
The Quick Scan is the triage. Its job is as much to rule us out as to rule us in, and these are the cases we decline.
- Trademark or counterfeit complaints
- That is a rights dispute between you and a rights holder. Nothing we measure on your site resolves it, and a technical audit does not help you.
- Product categories Google prohibits outright
- If the issue is that the product may not be advertised at all, the fix is a business decision about your assortment, not a configuration change.
- Repeated policy violations and previously reinstated accounts
- Accounts with history are judged differently, and we cannot see that history. We will say so rather than take the case and hope.
- Suspensions caused by something only visible inside the account
- Some causes leave no trace on the public site or in the feed. The Quick Scan usually surfaces whether that is the situation — and if it is, our tooling is the wrong instrument.
- Shops we would have to guess about
- If your storefront cannot be fetched without JavaScript or sits behind protection we cannot read, we say so instead of reporting findings drawn from a partial view.
In each of those cases we will tell you what we think is going on and what kind of help would actually be useful, and we will not invoice you for the scan. A referral costs us an hour. A case we cannot solve costs us the only thing we have, which is being right about what we find.
04 / What we will not tell you
What happens after the appeal is Google's decision.
The reviewer is theirs, not ours. Nobody outside Google can promise a particular outcome, and any supplier who tells you otherwise is telling you something they cannot know.
What we can do is make the appeal 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. That is the part we control, and it is the part we are selling.
This is enforced rather than stated. The reporting tool throws an error and refuses to produce a document if a finding or a fix text promises an outcome, and the build of this website fails if any page claims one. That check fired on this very page while it was being written, and the sentence was rewritten rather than the rule relaxed. Quoted text from your own shop is exempt — the rule exists to stop us over-claiming, not to censor you.
05 / On the roadmap
Not included, because it does not exist yet.
Two things we would build next. Neither is in the price above, neither can be bought today, and each is listed with the part of it we have not solved.
-
Done-for-you feed fixes
Not builtCorrections written straight into Merchant Center through Google's own API, instead of handed to you as a card to run.
Approved text fixes are already written straight into a WooCommerce shop. What is NOT built is this: for faults that live in the feed rather than in the shop — a wrong currency, a translated brand name, a price that disagrees with the landing page — Google's Content API for Shopping would allow a corrected value to be submitted directly, with your authorisation and against your account. That would turn a class of card into something we can carry out for you, still item by item and still with your approval on each change.
What is unresolved This is a different system from the shop write-back that exists today: the API would write to your Merchant Center account, not to your storefront, and the two have different consequences. What is unresolved is the harder half: a feed corrected at Google's end while the shop still generates the wrong value is a fix that lasts until the next export run. We will not ship it until the answer to 'and then what happens tomorrow' is written down.
Not built, not priced, and not for sale. It is listed so you know the direction — not so you wait for it.
-
Guard
Not builtA weekly re-crawl with a diff against the previous run, so drift shows up before Google reacts to it.
The Emergency Cure is a photograph. A shop is a moving object: a plugin updates, an export job runs, a theme changes, and a fault that was measured as gone comes back. Guard would re-run the same seven checks on a schedule and report only what changed since last time.
What is unresolved What is worth waking someone up for. An alert that fires on every cosmetic diff gets muted in a fortnight, and a muted alert is worse than none — it is the same false-alarm problem the checks themselves are built to avoid, moved one layer out.
Not built, not priced, and not for sale. It is listed so you know the direction — not so you wait for it.
Start with the free scan.
Your shop URL, the reason Google gave you, and an email address. We answer in under a minute, while you wait. Measurements on this page come from a real run on 17 August 2026.