What FAQ schema is, and what it is for
A short FAQ answers the questions that stop people from trying your product: price, setup, privacy, cancellation. FAQ schema is the same list written as FAQPage JSON-LD, the structured data vocabulary of schema.org. It tells any software that reads your page where each question starts and which text answers it. The generator writes that code for you, with the right types and escaping.
Start from real questions: the ones people ask in support emails, in launch comments and in sales calls. Four to eight good questions are better than twenty generic ones. Write each answer so it makes sense on its own, in two or three sentences.
Does FAQ schema still work in Google?
Be clear about what to expect. In 2023 Google limited FAQ rich results, the expandable questions under a search result, to well-known government and health websites. Its Search Central changelog then announced that the feature stopped appearing in Google Search on May 7, 2026, and the documentation was removed in June 2026 (checked on 24 October 2026).
So FAQ schema will not give your page a special look in Google. It is still valid structured data that describes your content accurately, and it costs nothing to keep. What brings visitors is the visible FAQ itself: clear answers on the page that a reader, or any assistant quoting your page, can use.
Where to paste FAQ schema
Structured data should describe what visitors can read. Put the same questions and answers in a visible FAQ section of the page, then paste the generated code on that page only. Do not mark up content that is hidden or that lives on another page.
- In plain HTML, paste the Script tag version in the head or at the end of the body.
- In a site builder or a CMS, look for a custom code field for the page or a custom HTML block, and paste the script tag there.
- In a framework that renders JSON-LD for you, copy the JSON only version into its structured data setting.
After publishing, open the page source and search for FAQPage to make sure the code is present once. You can also run the page through a structured data validator, such as the Schema.org validator, to confirm the syntax.
How to write answers that work on the page and in the markup
The same text serves two readers: the visitor who opens the question, and the software that reads the JSON-LD. Plain sentences work best for both. Answer the question in the first sentence, then add the detail that removes the doubt: the price, the limit, the condition. Avoid answers that only say “contact us” or link elsewhere, because they leave the question open.
- Keep one FAQPage block per page, listing the questions that page shows.
- Use it for questions you answer yourself. A page where visitors post their own answers, like a forum thread, is a different schema.org type (QAPage).
- Do not copy the same questions and answers on every page of your site: put them where they help, usually the pricing page or the product page.
Why the code is escaped
If an answer contains a sequence like </script>, it could close the tag early and break your page. The generator escapes the less-than sign inside the JSON, which keeps the data identical once parsed.
Good practices
- Keep answers factual. Never promise results you cannot guarantee.
- Update the code when you change the visible FAQ.
- To describe the product, the company or an article on the same page, use the schema markup generator: it writes those types and checks the properties Google asks for.
- Check your page title with the SERP simulator and follow the launch checklist before you launch.