Notes on the parts of this work that are hard to find written down. Response codes on large catalogues, edge caches that hide your own fixes, and checkout in a market where the usual payment stack is not available.
Drafts are listed too, so you can see what is coming. They do not link anywhere until they are finished.
A store with 18,608 products was answering 43,080 requests a day with a status code that means removed on purpose, for good. Nobody had noticed, because nothing inside the admin panel showed it.
Two correct fixes stayed invisible to Google for months because the edge kept serving an older copy. What to check, and in what order, before telling a client something is done.
The queries I run on a PrestaShop or WooCommerce catalogue before pricing anything, and why the product count the client gives you is rarely the number in the table.
Configuring checkout for a market where Shopify Payments is unavailable and card transactions carry a surcharge, without inviting fake orders.
The three case studies are the longer read.
