How to Fix a Missing FAQ Section on Your Website
Your audit found no FAQ section on any crawled page. This means search engines and AI assistants have no clearly structured question-and-answer content to pull from. By the end of this guide you will have a crawlable FAQ block with 4–6 real customer questions, matching FAQPage structured data, and a confirmed pass on the re-run audit.
Why it matters
Short, direct answers to real questions are the content AI answer engines (Google AI Overviews, ChatGPT search, Perplexity) quote most often. They also match long-tail and voice queries you would otherwise miss. Since 2023 Google shows FAQ rich results only for well-known government and health sites. FAQPage markup still helps machines parse your Q&A, though. The visible answers cut support tickets and resolve buying objections right on the page, which can lift conversions.
What you need
Step-by-step fix
Collect 4–6 questions customers actually ask
Pull questions from real sources, not guesses:
- Support inbox and live-chat logs
- Google Search Console > Performance > Search results, filtered by queries containing how, what, can, does or why
- "People also ask" boxes for your main keywords
- Your site's internal search terms
Pick the questions that block a purchase or create repeat support tickets.
Write direct 40–80 word answers
Start each answer with the direct answer, such as "Yes", "No" or a number. Add one or two sentences of context after that. Use plain language and include concrete details like prices, timeframes and limits. Avoid sales copy. Keep one question per item and phrase it the way a customer would type it.
Q: Do you ship internationally? A: Yes. Example Co ships to 38 countries from our EU warehouse. Orders outside the EU arrive in 5–9 business days and cost a flat $14.95. Duties and import taxes are calculated at checkout, so there are no surprise fees on delivery. You can see the full country list on our Shipping page.
Add a visible FAQ section to a key page
Place the FAQ on a page that ranks or converts, such as pricing, a product page, a service page or a dedicated /faq page. Use a clear heading that contains "FAQ" or "Frequently Asked Questions". Mark up each item with native <details>/<summary>. The answers then stay in the HTML source even when collapsed. Do not load answers through JavaScript only after a click, because crawlers may never see them.
<section id="faq" aria-labelledby="faq-heading">
<h2 id="faq-heading">Frequently Asked Questions</h2>
<details>
<summary>Do you ship internationally?</summary>
<p>Yes. Example Co ships to 38 countries from our EU warehouse. Orders outside the EU arrive in 5–9 business days for a flat $14.95. Duties are calculated at checkout.</p>
</details>
<details>
<summary>Can I return an item after 30 days?</summary>
<p>Unused items can be returned within 60 days for store credit, or within 30 days for a full refund. Start a return at example.com/returns.</p>
</details>
</section>Add matching FAQPage JSON-LD
Add a FAQPage script to the same page. Each Question needs a name that holds the question and an acceptedAnswer whose text holds the answer. The text must match the visible copy word for word, or close to it. Google treats markup for hidden or different content as a guidelines violation. Use one FAQPage block per page and do not repeat the same FAQ markup across many pages.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Do you ship internationally?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Example Co ships to 38 countries from our EU warehouse. Orders outside the EU arrive in 5–9 business days for a flat $14.95. Duties are calculated at checkout."
}
},
{
"@type": "Question",
"name": "Can I return an item after 30 days?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Unused items can be returned within 60 days for store credit, or within 30 days for a full refund. Start a return at example.com/returns."
}
}
]
}
</script>Make sure the FAQ page gets crawled
The audit only passes if the FAQ sits on a page it actually crawls. Check the following:
- The page is linked from your main navigation, footer or homepage
- The page is listed in your XML sitemap
- The page has no
noindexmeta tag - robots.txt does not block the page
A standalone /faq page that nothing links to is often missed.
<!-- Footer link example --> <a href="/faq">FAQ</a>
Validate the markup and re-run the audit
Paste the page URL into Google's Rich Results Test (search.google.com/test/rich-results) or validator.schema.org. Confirm that FAQPage is detected with zero errors. Open View Source (Ctrl+U / Cmd+Option+U) and confirm the questions, answers and the FAQ heading appear in the raw HTML. Then re-run the audit and check that it reports "An FAQ section was found."
curl -s https://example.com/pricing | grep -iE 'FAQPage|Frequently Asked'
Platform-specific notes
WordPress
In the block editor, add a Heading block ("Frequently Asked Questions") and then a Details block for each question. Yoast SEO's "Yoast FAQ" block and Rank Math's "FAQ by Rank Math" block both output visible Q&A and FAQPage schema automatically. If you use one of them, don't add a second manual JSON-LD block. For a manual block, use a Custom HTML block or a plugin like WPCode that supports page-specific snippets.
Shopify
In Online Store > Themes > Customize, open the target template and choose Add section > Collapsible content (Dawn and most Online Store 2.0 themes). Set the heading to "Frequently Asked Questions". Collapsible content does not output schema, so add a Custom Liquid section on the same template and paste the FAQPage JSON-LD there. Some FAQ apps add schema automatically, so check before you add it twice.
Wix
Add the Wix FAQ app via Add Elements (+) > Apps, or use a collapsible text/accordion element. For schema, go to the page's SEO settings > Advanced SEO > Structured data markup > Add new markup and paste the FAQPage JSON. Keep that JSON in sync whenever you edit the visible answers.
Webflow
Build the FAQ with Div blocks or a CMS Collection list containing Question and Answer fields, and add an H2 heading. Avoid interactions that remove answer text from the DOM. Add the JSON-LD in Page Settings > Custom Code > Before </body> tag. For CMS-driven FAQs, generate the JSON with an Embed element bound to the collection fields.
Next.js
Render the FAQ as a server component so the Q&A is in the initial HTML. In the App Router, output the schema with <script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(faqSchema) }} /> inside the page component. Build both the visible list and the schema from the same array so they never drift apart.
Check that it worked
✅ How to verify
- Re-run the audit and confirm it reports "An FAQ section was found."
- Run the URL through validator.schema.org or Google's Rich Results Test and confirm FAQPage is detected with no errors
- View the page source (not DevTools Elements) and confirm the FAQ heading, questions and answers appear in the raw HTML
- In Google Search Console, use URL Inspection > Test live URL to confirm Google renders the FAQ content
⚠️ Common mistakes
- Marking up questions in JSON-LD that are not visible on the page, or that use different wording from the visible answers
- Loading answers via JavaScript or fetch only after a click, so crawlers see empty accordions
- Putting the FAQ on an orphan or noindexed page that the crawler never reaches
- Writing marketing fluff or invented questions instead of answering real customer objections in the first sentence
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Does FAQ schema still work in 2026?
FAQ rich results in Google are limited to well-known, authoritative government and health websites, a restriction in place since August 2023. FAQPage markup is still valid Schema.org and helps search engines and AI assistants parse your Q&A. The visible FAQ content itself remains useful for long-tail queries and AI-generated answers.
How many questions should an FAQ section have?
Four to six questions is a good starting point for a single page. That is enough to cover the main objections without burying users. A dedicated /faq page can hold more, but group the questions under subheadings and keep each answer focused on one question.
Should I put the FAQ on every page or one FAQ page?
Put page-specific FAQs on the pages they relate to, such as shipping questions on product pages and billing questions on pricing. Don't copy the same FAQ block and schema onto dozens of pages. Duplicate Q&A adds little value, and each FAQPage block should be unique to its page.
Can I hide FAQ answers in an accordion?
Yes. Collapsed content is fine as long as the answer text is in the HTML when the page loads. Native <details>/<summary> elements or CSS-based accordions work well. Avoid accordions that fetch answers from a server only after the user clicks.