Google Stopped Showing FAQ Rich Results. Here's What FAQ Schema Still Does.

Most Shopify stores have an FAQ page. Almost none of them get anything from it in search.

For a few years the standard fix was a block of structured data — FAQPage markup that let Google show your questions and answers directly in its results. That is over. Google limited FAQ rich results to well-known government and health sites in 2023, and in 2026 stopped showing them in Search altogether.

So the old promise — add the markup, get a bigger search result — no longer holds. What the markup still does is quieter, and for some stores still worth an afternoon. This is what it is, what it is not, and how to decide.

Search engines read your page the way a person does — they see text and try to work out what it means. Structured data removes the guessing. It is a block of JSON, invisible to visitors, that states plainly: this is an FAQ page, here are the questions, here is the answer to each one.

The format is JSON-LD, and the vocabulary is schema.org. For an FAQ the type is FAQPage, containing a mainEntity list of Question objects, each with an acceptedAnswer.

It sits in a script tag in the page head or body. It does not change how the page looks. It changes what a machine reading the page can be certain about.

Not a rich result. Anyone still selling FAQ schema as a way to get your questions shown in Google is describing a feature that no longer exists.

What remains is certainty. The markup states, without interpretation, which questions the page answers and what the answers are. Any system that reads schema.org structured data — other search engines, and the AI assistants that increasingly summarise a page instead of linking to it — can take that at face value instead of guessing from your layout.

That is a real but modest benefit, and it is not a ranking factor. Treat FAQPage markup as good housekeeping for a page that already answers real questions well — not as a way to make a thin page perform.

Markup that has drifted from the content is the big one. A merchant updates their returns policy on the page, and the JSON-LD still describes the old one. Anything reading the page now has two contradictory statements about it, and the machine-readable one is the one it can quote.

Duplicated markup is the second. An SEO app adds FAQPage schema, the theme already emitted some, and the page ends up with two competing blocks. Validators will usually flag this, which is why testing before you add anything matters.

The third is marking up things that are not FAQs. Product specifications, feature lists and shipping tables are not questions and answers, and dressing them as such to chase a search feature is exactly the behaviour the guidelines exist to prevent.

The markup is the easy half. The reason most FAQ pages underperform is that they answer the questions the merchant wishes people asked.

Look at your support inbox. The five questions that arrive most often are your FAQ, in that order, whether or not they are flattering. "Why is delivery so slow to Europe" is a better FAQ entry than "What makes your products special", because one is a real query and the other is marketing.

Write the answer the way you would say it to a customer. Structured data will happily carry a hedged, corporate non-answer into an AI summary, where it will be read by people deciding whether to buy from you.

You do not need software for this. If your FAQ content is stable, a developer can add the JSON-LD to the theme template in under an hour, generated from the same page content so the two stay aligned.

An app earns its place when the content changes often, when several people edit it, or when you want the markup generated automatically rather than maintained. The failure mode of the manual approach is not that it is hard — it is that it silently goes stale.

Either way, the important part is the same: the markup should be produced from the content, not maintained beside it.

Open the Schema Markup Validator, paste your FAQ page URL, and see what comes back. It takes fifteen seconds.

If nothing is detected, decide whether it is worth adding. For a page with real questions and real answers, it is an afternoon's work. If the FAQ itself is thin, fix the content first — markup will not rescue it.

If something is detected, read it carefully and check the questions still match what is on the page. Stale markup is more common than missing markup, and harder to notice.