FAQ schema won't win the sale. A useful answer still can.

An audit recommends FAQ schema so your product pages can occupy more space in Google. Before commissioning the work, ask for the current source behind that promise.

Google stopped showing FAQ rich results in May 2026 and subsequently removed the feature documentation. That does not make product answers useless. It changes the reason to invest in them: resolve the buying question clearly, rather than promise a search appearance that no longer exists.

Google records the change in its Search documentation updates. Checked 11 October 2026.

The buying question survives the search feature

A shopper wants to know whether a replacement filter fits a particular machine. If the page gives a verified model list, they can decide. If it says only “compatible with many popular models”, more markup cannot supply the missing evidence.

Start with questions from customer service, returns and product specialists. Publish concise answers with the relevant model, measurement, conditions and exceptions. Avoid repeating your product description under five artificial questions.

When a fact belongs in an attribute or specification, put it there too. Q&A should expose missing product information, not become a second place your team must keep an essential measurement current.

QAPage isn't a replacement label for any Q&A section

Google's QAPage documentation describes pages focused on a single question and its answers. A product page containing multiple questions is not that use case. Switching the type does not create eligibility; the markup must describe the page you actually publish.

For an e-commerce product page, keep supported product structured data accurate where relevant, including the visible offer. A mismatch between price markup and the customer's offer creates a more consequential problem than the absence of FAQ markup.

What helps AI systems understand an answer?

Make the subject explicit. “Yes, it fits” depends on nearby context. “This sleeve fits devices up to the stated internal dimensions; include the case when measuring” is more self-contained. Add verified dimensions rather than expecting a machine to infer them from a photo.

Separate product facts, conditions and opinion. Link to authoritative supporting documents where they add evidence. Keep important answers available in readable page text and update them when the product changes.

Google's AI feature guidance says no special schema or AI text file is required for its AI search features. Clear, accessible content is a practical editorial choice; it does not guarantee a citation, recommendation or ranking in any AI service.

Keep or remove existing FAQPage output deliberately

Do not confuse a retired Google rich result with the disappearance of the schema.org vocabulary. Decide whether existing output serves your wider implementation and whether it duplicates another module's markup. You do not need to remove useful visible questions because you stop emitting a particular schema type.

Our Product Q&A module can output FAQPage JSON-LD for approved FAQ items with store answers, and has a setting to disable that output. Customer answers are not included. Keep the visible answers even if you disable the markup.

Measure the customer result

Look at repeated support questions, unanswered submissions and the purchase journeys affected by the missing information. Improvements in those measures are a stronger business case than predicting a richer search listing.

If your pages lack a managed question workflow, read our moderation guide and try Product Q&A. Bring one real customer question to the demo. The quality of the answer should be the centre of the decision.