Product and FAQ structured data: what it earns you now

Aug 29
3 min read

Updated: 2 days ago

Introduction

Structured data is sold as a way to get a richer listing in search results, and businesses add it expecting stars, prices and expandable questions to appear beneath their link.

Sometimes they do. Often nothing visible changes, because what search engines choose to display shifts over time and eligibility is not a guarantee. The markup still has value — it describes your page unambiguously rather than leaving it to be inferred — but the expectation needs setting honestly before anybody spends a week on it.

1. Product and FAQ structured data describe a page in a machine-readable format

Understand what is actually being added.

A block of code stating explicitly that this is a product, this is its price, this is its availability, or that this page contains these questions and these answers. Nothing visible changes on the page itself.

2. Know that eligibility is not a promise

The expectation to set first.

Correct markup makes a page eligible for enhanced display; it does not oblige a search engine to use it. What is shown varies by query, by device and by search engine policy, and it changes without notice.

3. Product markup earns its place on shops

Where the return is most reliable.

Price, availability, currency and review data help a listing communicate before anybody clicks, and they feed shopping surfaces as well as ordinary results. For an online shop this is the highest value item of the two.

4. Be realistic about FAQ markup

Its display has been reduced substantially.

Expandable questions beneath a listing were widely shown and are now restricted to far fewer sites. The markup remains valid and still describes your content accurately, but adding it to fifty pages expecting a visible result is likely to disappoint.

5. Only mark up what is actually on the page

The rule that keeps you out of trouble.

Questions in the markup must be visible to the reader, and prices must match what the page shows. Describing content that is not there is the one reliable way to have enhancements withdrawn from an entire site.

6. Let your platform generate it where it can

Avoid hand-written code.

Shop platforms produce product markup automatically from the fields you already fill in, and content systems have plugins for the rest. Hand-maintained blocks fall out of step with the page within months.

7. Validate before and after publishing

A short check that catches most errors.

Testing tools report whether the markup parses, which fields are missing, and whether the page is eligible. Run it on a live page rather than a draft, because what is served may differ from what was written.

8. Add the basics before the ambitious items

Sequence by return.

Business details, breadcrumbs and article markup are simple, stable and broadly used. They are worth more than a complicated implementation of something whose display is uncertain.

9. Do not expect a ranking change

The honest limit.

Structured data helps a listing be understood and sometimes be displayed differently; it is not a ranking factor in itself. Where results improve, it is generally because the listing attracted more clicks, not because the position moved.

Re-validate after site changes. Template edits, plugin updates and platform migrations break markup silently, and a shop that quietly lost its price data months ago will look identical to everybody inside the business.

Conclusion

Treat structured data as a way of describing your page unambiguously rather than as a route to a better position.

Understand that eligibility is not a promise of display, prioritise product markup because its return is the most reliable, keep expectations low for FAQ markup given how much its display has been reduced, mark up only what is genuinely visible on the page, let your platform generate it rather than hand-writing blocks, validate on the live page, add the simple stable types before the ambitious ones, expect no ranking effect, and re-validate after every site change.