The ad platform tax: what owning your traffic actually takes
Every year the same buyer costs more to rent. How organic visibility compounds into an asset you own, where the compounding comes from, and…
Product schema doesn’t change your rankings — it changes what your listing looks like in search. Here’s what it needs, and why catalog-wide coverage beats a handful of perfect pages.
The short version
- Structured data doesn't change rankings directly — it changes what the listing looks like.
- Product schema is what makes price, stock status and star ratings eligible to show in search.
- Coverage across the whole catalog matters more than perfecting one product's markup.
- Rich results still have to be earned — eligibility isn't a guarantee of display.
Two identical products can rank next to each other in search results and get very different click-through rates,
simply because one shows a price, a star rating and “In stock” underneath the title, and the other shows a plain
blue link. That difference is structured data — specifically, Product schema.
It doesn’t move you up the rankings. What it does is make your listing eligible for the visual treatment search
engines reserve for pages that clearly describe what they’re selling.
What Product schema actually needs to include #
The minimum for rich results eligibility is narrower than most implementations assume — but the fields that
actually earn a rich result are specific, and missing even one commonly disqualifies the whole listing.
- Name and image — the product itself, unambiguously identified
- Offer — price, currency, and availability (in stock, out of stock, preorder)
- Aggregate rating — a genuine average built from real reviews, not a placeholder
- SKU or GTIN — increasingly expected for shopping-adjacent rich results
Why catalog-wide coverage beats a perfect single page #
It’s tempting to hand-craft schema for a handful of hero products and leave the rest of the catalog untouched.
The problem is that most of a store’s organic traffic comes from the long tail — the hundreds of products nobody
thought to prioritise individually.
The rich result that moves revenue is the one on the product nobody remembered to mark up.
Adlux growth team
Template-level implementation — schema generated automatically from the same fields already in the product
database — is what makes coverage realistic across a catalog of any size. Stock status and price update
automatically as the underlying data changes, instead of drifting out of date on a page nobody revisits.
Validating before it ships #
Structured data testing tools catch syntax errors, but not eligibility issues — a technically valid schema can
still fail to earn a rich result if a required field is empty or a rating looks synthetic. Spot-checking a sample
of live pages after rollout catches what the validator alone won’t.
Frequently asked questions #
No — it makes the page eligible. Whether the rich result actually displays depends on the search engine’s own criteria and can vary by query and by device.
No — price and availability fields work fine without reviews. Just omit the aggregate rating field until genuine reviews exist rather than leaving it empty or fabricated.
It should reflect live inventory in real time if the implementation is template-driven from the same product data. Stale stock status in schema is a common cause of rich results disappearing.
The takeaway #
Product schema is one of the few SEO changes with a visible, immediate effect on how a listing looks in search.
Catalog-wide coverage, built from accurate underlying data, is what turns that into a click-through rate
improvement rather than a handful of hand-marked-up hero products.
Written by the Adlux team from live account work. If you want this thinking applied to your catalog, the audit is free and the findings come in writing.