MerchantCure Free Quick Scan

Find Fix Prove

Case — eleven shops

The same generator, eleven shops, and a reversal file for every change

One text generator had written the catalogue for eleven shops in eleven markets, and the same kinds of fault came back in shop after shop — in different mixes, and not all four everywhere. This is what the sweep found and what it changed, shop by shop.

The sweep

Nine shops with a written checklist, shop by shop.

Eleven shops were run. Nine of them have a checklist file with the figures written down the day the import was prepared, and those nine are the ones in this table. The other two were run the same way on the same dates, but their figures were never written into a checklist — so they are not here.

Rows, depublications, reversal rows and melatonin text changes per shop
Shop Rows Depublished Reversal rows Melatonin text Run
Shop A 12,207 5,227 5,227 0 25 September 2026
Shop B 13,073 4,667 4,667 226 sentences in 47 products 25 September 2026
Shop C 12,287 5,286 5,286 51 products depublished 25 September 2026
Shop D 11,443 4,985 4,985 172 sentences 24 September 2026
Shop E 11,816 5,286 5,286 246 sentences 24 September 2026
Shop F 9,947 4,369 4,369 236 sentences 24 September 2026
Shop G 13,463 6,295 6,295 15 products depublished 25 September 2026
Shop H 12,501 4,963 4,963 6 products depublished 25 September 2026
Shop I 12,474 5,436 5,436 0 25 September 2026

Every figure above was measured on the date in the last column, from our internal log — the checklist written for that shop the day its import was prepared.

What the generator left

Six shops have the text figures too.

Leaked generator text is the model's own instructions shipped inside the description. Code fences are the markdown wrapper it was handed back in. Neither is a judgement call — both are text that was never meant to be read by a customer, and both were visible in the live shop.

Generator text struck, code fences removed, finished text swapped in, and rows rescued from being emptied
Shop Generator text struck Code fences removed Finished text swapped in Rescued from emptying
Shop A 78 0 2,260 42
Shop B 115 2 2,326 36
Shop C 344 0 2,293 34
Shop G 74 0 2,295 33
Shop H 114 472 0 0
Shop I 714 533 2,311 27

Our own run-order document gives two of these totals differently — 13,463 against 13,301 for one shop, 12,287 against 12,286 for another. The difference is exactly the number of products with no title at all, which are handled in a separate file and a separate step. The two documents count different things, and we would rather explain that than quietly pick one.

Read this part

What this sweep does not prove.

  1. None of these eleven shops was suspended. This case is about what a catalogue looks like before Google notices, not about lifting a suspension.
  2. The figures are what the import files change. They are not a claim about what the shops looked like a week later — a catalogue is a moving object, and a measurement is a day.
  3. Two of the eleven are missing from the tables. They were run the same way on the same dates, but their figures were never written into a checklist, and a number we cannot point at does not go on a page.

What we got wrong

Four of them, and one could have deleted a shop's text.

  1. In six of the shops, 172 rows would have been left with an empty description once the leaked text was struck. An empty field does not mean 'unchanged' in a WooCommerce import — it deletes the text in the shop. Those rows kept their original text instead, and they are listed separately because they still need reading by a human.
  2. In one shop the finished replacement text did not exist at all, so 12,501 rows went through with the code fences removed and nothing swapped in. That is a smaller job than the other ten got, and the checklist says so rather than reporting it as a completed pass.
  3. In one shop 1,515 product titles still had words from another language in them after the run. Machine translation is not what that needs, so they were left for a human and counted.
  4. Eighteen rows in one shop had a strike reversed, or a claim still standing after the pass. They are in a file called FOR-HAND — by hand — because a rule that gets a sentence wrong eighteen times out of ten thousand is still a rule that gets it wrong.

That first row is also the last column of the table above. A fault is recoverable; a deletion across five thousand products is not, so the rule is that the original text wins whenever the correction would leave the field empty.

The same pass on your catalogue

You get the import files and the reversal files, and you run the import yourself. We never write to your shop. Every product the pass could not resolve comes back marked with the reason rather than filled in with something that looks finished.

Buy the diagnosis · from €220 or free scan first Buy