3 November 2026
Product schema is not a magic switch: an ecommerce SEO audit for 2026
A product page can pass a structured-data test and still give a customer the wrong information. If the price in the markup is different from the price at checkout, a green validation result is not the result that matters.
Google’s support for richer product information has continued to develop. Loyalty programme support was announced in June 2025, and shipping-and-returns settings in Search Console were expanded in November 2025. For merchants reviewing their SEO in 2026, the opportunity is to get the details right, not to bolt more code onto an unreliable page.
Choose the right product feature
Google distinguishes product snippets from merchant listings. A page that reviews a product is not the same as a shop page where someone can buy it. Read the requirements for the feature that matches your page before copying a template from another site.
Structured data helps explain information to Google and may make a page eligible for richer search appearances. Eligibility does not guarantee that those appearances will be shown, and it is not a promise of higher rankings.
Check what the shopper can actually see
Take a small sample of live product pages: a popular product, an out-of-stock item, a discounted item and one with several variants. Compare the visible price, currency, availability and product identity with the information in the markup and any product feed.
For a UK shop, check that currency and delivery information reflect the offer a UK customer receives. If the price changes when a variant is selected, make sure the rest of the page does not continue describing a different product. This is partly a search task and partly a customer-experience task.
Treat variants as related products, not an afterthought
Size, colour and other variations can complicate a catalogue. Google documents ProductGroup and properties including hasVariant, variesBy and productGroupID to help explain relationships between variants.
Before implementing them, decide how your site presents the variations and check the documentation against that setup. The useful question is whether Google and the shopper can understand which option is being described, not whether the page contains the greatest possible number of properties.
Review delivery, returns and loyalty details together
Google’s November 2025 announcement expanded shipping-and-returns settings in Search Console to identified online merchants, including those without a configured Merchant Center account. Google says those settings take precedence over website structured data. Check the settings as well as the code.
Loyalty information has another decision point. Google’s June 2025 guidance recommends Merchant Center for defining a loyalty programme when the merchant already has an account. Structured data provides another route, particularly for businesses without one. Use the route appropriate to your setup and keep the description aligned with the actual programme.
Validate a sample before changing everything
Run representative pages through the Rich Results Test and inspect how Google sees the URLs. Testing only a perfect demonstration product misses the catalogue problems that tend to appear with stock changes, sales and variations.
After a change, allow for crawling and re-indexing. Check the live pages again when a price or policy changes. A validation exercise should become part of maintaining the shop, not a one-off task filed away after launch.
The practical priority
Fix the information before chasing the appearance. Accurate product details help customers even when no rich result is displayed. Unreliable details remain a problem even if Google briefly shows a more elaborate listing.
For a wider review of your search direction, see Craig’s SEO consultancy. Teams that want to understand the work behind these checks can also explore SEO training.