FAQ schema for product pages: patterns that survive RAG chunking

FAQ sections are the highest-ROI GEO surface on most PDPs. They convert support tickets into retrieval-friendly Q&A pairs that RAG systems prefer over marketing paragraphs.

Each Question entity needs acceptedAnswer text that matches what shoppers see in the accordion or visible list—not hidden SEO divs. Questions should use natural buyer phrasing: "Does this fit a 2022 Tesla Model Y?" beats "Compatibility FAQ #3."

• Sizing / dimensions with units
• Materials and care
• Compatibility or fit
• Shipping time by region
• Returns and warranty
• Authenticity or certification (if category requires)

One FAQPage node per PDP; do not aggregate unrelated products. Keep answers 40–120 words—dense enough for facts, short enough for chunk inclusion. Link to policy pages for legal detail instead of duplicating legalese in schema.

Duplicate questions across SKUs with identical answers when specs differ. FAQ content that contradicts Product schema (e.g., schema says InStock, FAQ says "backorder 6 weeks"). Machine-translated questions without localized shipping facts.

How many questions per PDP? Five to eight strong Q&As beat twenty thin ones.

Does FAQ schema help Google rich results and AI? Overlap exists but not guaranteed; optimize for citation either way.

Can I pull FAQs from Zendesk? Yes—map top macros to on-page Q&As and schema.

Validate FAQPage output in Visora /audit alongside Product nodes—mismatch between accordion and JSON-LD is a frequent citation blocker.