FAQ schema can help machines understand the questions and answers on a page, but most ecommerce sites should not expect it to produce an expanded FAQ result in Google. Google now generally limits FAQ rich results to well-known, authoritative government and health websites. For ordinary online stores, useful visible FAQs still matter for shoppers; the markup should be treated as accurate page data, not a shortcut to rankings or guaranteed search features.
This guide explains when ecommerce sellers should use FAQPage structured data, how to create valid JSON-LD, where to place it and which mistakes to avoid.
What is FAQ schema?
FAQ schema is structured data that identifies a page as containing a list of questions with answers supplied by the website. It normally uses the schema.org FAQPage, Question and Answer types.
The most common implementation format is JSON-LD: a script block added to the page code. Visitors do not read the script itself. Search engines and other systems can use it as a machine-readable description of FAQ content that must also appear visibly on the page.
FAQ schema is different from QAPage markup. Use FAQPage when your business writes each question and its accepted answer. A genuine community question page where users submit multiple competing answers may fit QAPage instead.
Does FAQ schema still help ecommerce SEO?
It can support clear page meaning, but expectations need to be realistic. In August 2023, Google announced that FAQ rich results would generally appear only for authoritative government and health websites. Google also stated that unused FAQ structured data does not cause problems, but may have no visible effect in Search. Read the official Google FAQ rich-results update.
For an ecommerce website, this means:
- Valid FAQ markup does not guarantee expandable questions in search results.
- Adding schema is not a substitute for useful on-page answers, good product information or strong internal linking.
- The visible FAQ can still reduce buyer uncertainty about shipping, sizing, compatibility, returns and product use.
- Accurate structured data can make the page easier for machines to interpret, but you should not promise a ranking increase from the markup alone.
Google’s general guidelines also say that correct structured data does not guarantee a rich result. Treat schema as clean technical labelling for helpful content, not as a trick.
When should an online store use FAQPage markup?
Use it when a page contains several genuine questions with one official answer for each question. Good candidates include:
- A product page with product-specific questions about dimensions, compatibility, care or what is included.
- A category page answering how products differ, how to choose a size or which option suits a use case.
- A shipping page explaining dispatch times, tracking and delivery areas.
- A returns page explaining eligibility, time limits and the return process.
- A service page answering booking, turnaround or deliverable questions.
Avoid copying the same broad FAQ block onto every product page. Repeated generic questions add little value and can make thousands of pages look nearly identical. Put sitewide policies on the most relevant policy page, then link to that page from products.
What makes a useful ecommerce FAQ?
Start with questions customers actually ask before buying. Review support emails, live chat, returns, product reviews and marketplace messages. The best questions remove a specific obstacle rather than repeating promotional copy.
For example, “Is this bottle good?” is vague. “Does this 750 ml bottle fit a standard car cup holder?” addresses a real compatibility concern. Answer directly in the first sentence, then add essential conditions.
Useful product-page FAQ topics include:
- Exact size, weight, materials and included components.
- Compatibility with particular models, devices or accessories.
- Care, washing, storage and expected use.
- Dispatch times, delivery limitations and tracking.
- Return eligibility for opened, personalised or clearance items.
- Warranty coverage and how a customer starts a claim.
Keep factual details consistent with the rest of the page. If the main description says a product is dishwasher safe but the FAQ says hand wash only, the schema merely makes the contradiction easier to detect. Improve the visible copy first. The guide to writing product descriptions that sell can help you structure that core information.
FAQ schema JSON-LD example
Here is a simplified example for a product page:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Does this bottle fit a standard car cup holder?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. The base is 70 mm wide and fits most standard car cup holders. Measure narrow or custom holders before ordering."
}
},
{
"@type": "Question",
"name": "Can I put it in the dishwasher?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The bottle body is top-rack dishwasher safe. Hand wash the lid to protect its seal."
}
}
]
}
</script>Replace every example with the exact questions and answers shown on your page. Do not publish invented dimensions, policies or compatibility claims.
How to generate FAQ schema safely
- Write the visible FAQ first. Make each answer complete and accurate for that page.
- Open the SellersNest FAQ Schema Generator.
- Enter each question and answer. Copy the visible wording rather than creating a separate version only for search engines.
- Generate and copy the JSON-LD.
- Add it once to the relevant page. Use your platform’s custom-code, theme or SEO feature without duplicating existing FAQ markup.
- Validate the result. Check the page with Google’s Rich Results Test and inspect the rendered HTML when possible.
- Recheck after page updates. If a policy or answer changes, update both the visible FAQ and the schema.
If you are also editing the title and description, use the SERP and Social Preview Tool to check how the page metadata may appear before publishing.
Where should FAQ schema be placed?
JSON-LD can usually be placed in the page’s <head> or <body>, provided search engines can access it when rendering the page. Your ecommerce platform may offer a structured-data field, custom code area, theme template or SEO plugin.
Before adding anything, check whether the theme or app already outputs FAQPage markup. Duplicate blocks can create conflicting data. View the rendered source or use a structured-data testing tool rather than assuming an accordion automatically adds valid schema.
Common FAQ schema mistakes
Marking up hidden or missing answers
The questions and full answers should be available to visitors on the page. An accordion is fine when users can open it. Do not add answers only inside JSON-LD.
Using FAQ schema for customer reviews
A customer question with multiple user answers is not a business-authored FAQ. Do not force all question content into FAQPage.
Turning answers into advertisements
Answers should solve the question. Repeating “best quality,” sale messages or keyword-heavy claims makes the section less useful and can violate structured-data quality guidelines.
Publishing inaccurate policies
Return and shipping answers can affect buying decisions. Match the current policy, including exceptions. High return rates may also reveal which questions are missing; use the guide to calculating and reducing ecommerce returns to identify avoidable confusion.
Expecting guaranteed rich results
Passing a validator confirms that the code is technically readable. It does not guarantee a special search appearance, indexing or higher rankings. Google makes the final decision about search features.
Adding the wrong schema type everywhere
FAQ markup does not replace product structured data. An ecommerce product page may need accurate Product and offer information for price, availability, shipping or return features. Use each type only for the content it describes.
How to measure whether the FAQ helps
Measure the page, not just the markup. Compare customer questions, conversion rate, support contacts and returns before and after adding clearer answers. In Search Console, watch impressions, clicks and queries over a meaningful period, but do not assume every change came from FAQ schema.
For a product page, the most useful result may be fewer pre-sale messages or fewer “not as expected” returns. For a shipping page, success may mean customers find delivery answers without contacting support. Those outcomes come from the quality of the visible FAQ, whether or not Google shows a rich result.
Final takeaway
Ecommerce stores can still use FAQ schema when a page contains genuine, visible questions with business-authored answers. Generate clean JSON-LD, keep it synchronized with the page and validate it after publishing. Just be honest about the benefit: Google no longer shows FAQ rich results regularly for ordinary commercial sites, so the main value is better customer answers and accurate page structure—not a guaranteed ranking or oversized search listing.