FAQ Schema
Structured data that labels genuine questions and answers already visible on the same page.
Google stopped FAQ rich results on May 7, 2026. FAQ schema now describes genuine same-page Q&A; it is not a Google rich-result tactic.
Schema.org remains usable, but no system must extract, rank, cite, recommend, or send traffic. Use visible equality, one owner, safe serialization, and maintained answers.
What is FAQ schema?
FAQ schema is structured data that uses FAQPage as the page-level type and nests Question and Answer entities for publisher-authored Q&A. Every marked question and its complete answer must be visible on that URL. The markup describes existing content; it should not generate, expand, conceal, or replace the shopper-facing answer.
Schema.org defines FAQPage, Question, and Answer; the structured data definition adds context. These types describe structure, not answer quality or required use.
Publish shopper-first answers about fit, use, shipping, returns, care, warranty, compatibility, or policy; then mark up the same text.
Does Google still show FAQ rich results?
No. Google stopped showing FAQ rich results in Search on May 7, 2026. That change removes the primary Google presentation incentive for FAQPage markup; it does not make the vocabulary invalid. Other systems may choose to interpret Schema.org, but markup cannot guarantee ranking, extraction, AI citation, recommendation, or traffic.
Check Google’s FAQ structured data documentation and structured data policies for current rules. Do not sell FAQ schema as a shortcut to snippets, rankings, answer-engine inclusion, or recommendations.
Keep only useful, current FAQs; thin or outdated questions fail shoppers regardless of rich-result support.
Which content belongs in FAQPage markup?
Use FAQPage only when the publisher supplies both genuine questions and complete answers on one public page. Use QAPage when users can submit competing answers. Forums, reviews, and private support conversations have different authorship and interaction models; converting them into publisher-authored FAQs misstates the content.
| Pattern | Model | Boundary |
|---|---|---|
| Publisher Q&A | FAQPage | One publisher answer |
| User answers | QAPage | Community model |
| Forum | QAPage when eligible | User discussion |
| Review | Review vocabulary | Evaluation |
| Private chat | No FAQPage | Not public same-URL content |
| Published support | FAQPage when truthful | Maintained publisher answer |
Do not add hidden keyword variants or turn reviews into FAQs. Curate support insights into complete, maintained public answers first.
How should visible Q&A map to FAQ schema?
Map the visible FAQ and JSON-LD from the same content source so wording, completeness, order, policies, prices, and returns stay synchronized. Each FAQPage should reference visible Question nodes, and each Question should contain its full visible Answer. Omit anything hidden, generated only for bots, or unavailable on the URL.
| Visible element | Mapping | Rule |
|---|---|---|
| FAQ collection | mainEntity | Visible questions only |
| Question heading | Question.name | Same meaning |
| Complete answer | Answer.text | Include all conditions |
| Answer links or lists | Answer.text | Retain qualifications |
| Page identity | URL and @id | Stable reference |
| Publisher | StoreCited Organization | No Person author |
Maintain prices, shipping, returns, warranty, and availability from one source; update visible content and markup together.
Who should own FAQ markup in Shopify?
Assign one FAQ markup owner across the Shopify theme, sections, apps, tag manager, and custom scripts. Duplicate producers can emit conflicting graphs after rendering even when the initial HTML looks clean. Document ownership, keep a stable page @id, and inspect server output and browser-rendered HTML after every change.
Use Shopify theme sections to connect visible blocks and markup, and the json filter for safe serialization. Disable overlap through supported settings.
The owner must reuse visible answers and remain maintainable; ownership does not improve extraction or ranking.
What is a safe Shopify implementation workflow?
A safe Shopify implementation begins with useful buyer questions, stores each visible answer once, maps that source into FAQPage, and serializes it safely. Pilot one template before expanding. The goal is equality between what shoppers read and what machines receive—not extra keyword variants or invisible answers.
- Choose genuine questions for one page and intent.
- Publish complete answers with current policy and product details.
- Inventory theme, section, app, and script markup emitters.
- Select one owner and one visible content source.
- Map FAQPage, Question, and Answer without adding hidden text.
- Serialize safely and create a stable page
@id. - Test initial HTML, rendered HTML, mobile accordions, and updates.
Use the Shopify FAQ schema guide and FAQ schema generator for implementation, then verify page equality. Product facts belong in Product schema.
How should FAQ schema be validated and monitored?
Validate FAQ schema at three levels: JSON syntax, Schema.org vocabulary, and exact equality with visible content. A parser can confirm structure without confirming truth. Test initial and rendered HTML, compare every marked answer with the page, and monitor Search Console for reported issues while expecting no Google FAQ rich result.
Use this validation checklist:
- JSON parses without manual-escaping errors.
- FAQPage, Question, and Answer relationships are correct.
- Every marked question and full answer is visible.
- Initial and rendered HTML contain one consistent graph.
- Prices, returns, shipping, and policies are current.
- No generated, stuffed, review-derived, or hidden Q&A appears.
Use the Schema.org validator for vocabulary and the StoreCited schema checker for public output. JSON-LD 1.1 defines the linked-data model, while RFC 8259 defines JSON. Google’s structured data introduction explains its processing model.
Use Google’s Search Console guidance when investigating reported issues. Monitoring can reveal errors or policy concerns; it cannot restore the discontinued FAQ rich result or attribute rankings, citations, traffic, and revenue to markup.
What can StoreCited truthfully check?
StoreCited inspects observable FAQ markup and related public output at one point in time. It cannot create or publish FAQs, edit Shopify, identify private theme or app ownership, monitor live prompts or citations, access proprietary indexes, or guarantee extraction, ranking, recommendations, traffic, or revenue. Findings describe the tested public response only.
The scan can flag observable syntax, vocabulary, visibility, equality, or duplicate-output concerns in the response it receives. It cannot prove private configuration, historical rendering, future maintenance, or how any search or answer system will interpret the page later.
Run the free StoreCited readiness scan to inspect public storefront output. Confirm ownership inside Shopify, test shopper-visible answers yourself, and maintain every policy-sensitive answer after launch.