"410 Gone" is the most expensive response code on a large catalogue
A 404 asks a crawler to check again later. A 410 asks it to forget the page. On a catalogue where product URLs move, that one difference removes the store from search.
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.
Nothing here is published yet. The four below are in draft, listed so the index and the post template are designed against real subjects rather than placeholder text. None of them links anywhere, because there is nothing to link to until one is finished.
A 404 asks a crawler to check again later. A 410 asks it to forget the page. On a catalogue where product URLs move, that one difference removes the store from search.
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.
Until these are finished, the two case studies are the longer read.