SEO for a storefront that is published rather than rendered

Most ecommerce SEO advice is about content. The things that actually destroy traffic are structural, they happen during migrations and redesigns, and they are entirely preventable.

Redirects are the migration

When a URL changes, the ranking attached to the old one transfers only if the old address tells search engines where the page went. Without that, you have not moved a page — you have deleted one and published another, and the new one starts from nothing.

Redirects are held as records and applied on request, which is the only arrangement that works for a static storefront. This is worth understanding: a redirect implemented inside an application is a redirect a published static site cannot honour, because there is no application in the path when a visitor asks for the old URL.

So redirects are part of publishing rather than a routing table in an app that the storefront never consults.

The sitemap has to be true

A sitemap listing products that no longer exist, or missing half the ones that do, is worse than no sitemap — it teaches search engines that your sitemap is unreliable, and they treat the rest of it accordingly.

It is generated as part of publishing, from what is actually being published. It cannot list a page that was not published, and it cannot miss one that was, because it is derived from the same operation rather than maintained alongside it.

Structured data, and the one that matters

Product structured data is what produces the price and availability shown directly in search results. Those results are more prominent and better qualified — the person clicking has already seen the price.

Availability is the field to be careful with. Marking something in stock when it is not gets your listings demoted, and it is exactly the failure a shared stock figure prevents: the structured data reads the same number the shop does, so it cannot claim availability the shop disagrees with.

Speed, which you get for free here

Page speed is a ranking factor and, more importantly, a conversion factor. A storefront served as static files from a node near the visitor is fast by construction rather than by optimisation — there is no application boot and no database query between the request and the response.

This is the one area where the static approach gives you something you would otherwise spend years chasing.

What no platform can do for you

Rank you for a term you have not written about. Structural SEO stops you losing traffic you have earned and makes sure what you publish can be found — it does not create demand.

The pages that earn traffic are the ones answering a question a buyer actually typed, written by someone who knows the product. That part is yours.