Quick answer: FAQ schema is structured data (the FAQPage type from schema.org) that tells Google a page contains a list of questions with answers written by the site owner. Since Google announced FAQ rich results in May 2019, pages with valid markup can show expandable questions directly under their search listing. To get them, write real questions and answers that are visible on the page, add FAQPage markup in JSON-LD, test it with the Rich Results Test, and watch the FAQ report in Search Console. Google still decides whether to show the rich result.
What FAQ rich results look like
A normal search result has a title, a URL and a description. When Google shows an FAQ rich result, it adds a short list of questions below that description. Each question expands to reveal the answer you wrote. The listing takes up more vertical space, and the answers can contain links back to other pages on your site.
That extra space is the main reason site owners care. A taller listing is easier to notice, and a good answer can show a searcher that your page covers exactly what they need. The flip side is that some people will get their answer without clicking. For most business sites that trade is fine, because the questions that matter commercially (“How long does setup take?”, “Do you work with small teams?”) usually lead people to want more detail anyway.
Which pages qualify
Google’s guidelines are specific, and following them is the difference between a rich result and a manual action.
Use FAQPage when the page has a list of questions and answers, and you (the site) wrote both. A support page, a service page with a questions section, or a product page with common pre-sale questions all fit.
Do not use FAQPage when users can submit their own answers. A forum thread or a community question with several replies should use QAPage markup instead.
Do not use it for advertising. The markup is for genuine information, not for packing promotional slogans into search results.
The content must be visible. Every question and answer in the markup must appear on the page for visitors. Accordions are fine, as long as the text is in the page and a user can open it.
Mark up each FAQ once. If the same questions appear on several pages of your site, add the markup to only one of them.
Google also reviews pages for general quality. Thin pages with a few filler questions bolted on are unlikely to get the rich result even if the code validates.
Writing questions people actually ask
The markup is the easy part. The questions are where most pages fall short.
Start with sources of real questions: sales emails, support tickets, chat logs, the “People also ask” box for your main keyword, and the search queries report in Search Console. Write each question the way a customer would type or say it. “What does a website audit include?” is better than “Audit Scope Overview.”
Keep answers short and complete. Two to four sentences is a good target. Lead with the direct answer, then add one useful detail. If the topic needs more space, answer briefly and link to the page that covers it in depth. This approach also helps with featured snippets, which reward the same clear, direct style.
Avoid duplicating your whole page as questions. Five to eight strong questions beat twenty weak ones.
How the markup works
Google recommends JSON-LD for structured data. You place a script block in the page that describes the questions and answers. The structure is simple:
- A top level object with
@typeset toFAQPage - A
mainEntityarray containing one item per question - Each item has
@typeset toQuestion, aname(the question text) and anacceptedAnswer - The
acceptedAnswerhas@typeset toAnswerand atextproperty with the answer
The answer text can include a limited set of HTML, such as links, paragraphs, lists and bold text. Google ignores tags outside that set, so keep formatting simple.
The question and answer text in the markup should match what is on the page. Small differences in whitespace do not matter, but do not write a different, keyword-heavy version for the markup only.
Adding FAQ schema to your site
How you add the markup depends on how the site is built.
Hand-coded or custom sites. Generate the JSON-LD from the same data that renders the visible FAQ. If questions live in a database or a content field, output both the HTML and the script from that one source so they never drift apart.
Content management systems. Many CMS platforms now have plugins or modules for structured data. On WordPress, Yoast SEO added FAQ and How-to blocks for the block editor earlier this year, and other SEO plugins are adding similar features. If you are new to blocks, our guide to the Gutenberg editor explains how they work. Check that the plugin outputs FAQPage markup and that it does not add a second, conflicting copy if you already have custom schema.
Tag Manager. You can inject JSON-LD through Google Tag Manager, and Google can read it. It works, but it hides the markup from your developers and can break silently when the page changes. Put it in the template when you can.
Testing before and after you publish
Run the page URL or code through Google’s Rich Results Test. It tells you whether the page is eligible for FAQ rich results and flags missing or invalid fields. The older Structured Data Testing Tool is still useful for checking the general schema.org structure.
After the page is live and crawled, open Search Console. Google added an FAQ report under Enhancements that lists valid items, items with warnings and errors. If you fix an error, use the validate fix option so Google rechecks the affected pages. The Search Console guide covers where these reports sit and how to read them.
Then give it time. Rich results can take days or weeks to appear after Google recrawls the page, and they may come and go depending on the query.
Common mistakes
- Marking up content that is not on the page. This is the fastest way to lose eligibility.
- Using FAQPage on forum or community threads. Use QAPage when answers come from users.
- Repeating the same FAQ sitewide. A shared FAQ in a footer or sidebar should not carry markup on every page.
- Stuffing keywords into questions. Questions that read like ad copy fail the quality bar and annoy readers.
- Multiple conflicting schema blocks. A theme, a plugin and a hand-added script can all output schema. Check the page source for duplicates.
- Forgetting to update. When prices, timelines or policies change, update the visible answer and the markup together.
Does FAQ schema help rankings?
Structured data is not a ranking factor in the direct sense. It helps Google understand the page and makes it eligible for richer listings. Any traffic benefit comes from a more visible listing and a better match with what searchers want. A page that does not rank on the first page for a query is unlikely to see its FAQ rich result shown for that query.
That is why FAQ schema works best as one part of a solid technical SEO checklist, not as a shortcut. Good content, clean crawlability and sensible internal links still do the heavy lifting.
A simple rollout plan
- List your ten most important pages for leads or sales.
- Collect real customer questions for each one.
- Write five to eight clear answers per page and add them as a visible section.
- Add FAQPage JSON-LD that matches the visible text.
- Test each URL in the Rich Results Test.
- Request indexing in Search Console for updated pages.
- Check the FAQ enhancement report weekly for the first month, and track clicks and impressions for those pages.
FAQ
How many questions should an FAQ section have?
There is no fixed number. Most pages work well with five to eight questions that cover real concerns. Add more only if they are useful to readers.
Can I use FAQ schema on every page?
Only on pages that genuinely contain a list of questions and answers written by you. Do not repeat the same FAQ markup across many pages.
Will Google always show my FAQ rich result?
No. Valid markup makes a page eligible, but Google decides when to display it based on the query, the page and overall quality.
Can answers include links?
Yes. Answer text can include links, and those links can appear in the rich result. Link to pages that expand on the answer.
Make your answers do the work
FAQ schema is one of the few structured data types that almost any business site can use, and it rewards something you should be doing anyway: answering customer questions clearly. Start with the pages that bring in leads, write honest answers, and keep the markup in sync with the page. If you want help planning structured data alongside the rest of your search work, take a look at Get found.
