Free FAQ Schema Generator

FAQ schema is structured data that labels a list of questions and answers on a page, using the FAQPage type from schema.org. It is usually written as JSON-LD: a block of JSON inside a script element that visitors never see but search engines and other machines read.

The markup has three layers. A FAQPage holds a mainEntity list. Each item in that list is a Question whose name is the question text, and each Question has an acceptedAnswer of type Answer whose text is the answer. That is the whole structure this generator writes, with nothing added that Google does not use.

No. Google stopped showing FAQ rich results, the expandable questions under a search result, on May 7, 2026, and removed their documentation in June 2026. From August 2023 until then they appeared only for well-known government and health websites. No site gets them now, however valid its markup is.

FAQPage is still valid schema.org markup, and adding it does not hurt a page. It labels which text on the page is a question and which text answers it, in a form any program that reads structured data can parse: other search engines that read schema.org data, AI assistants and answer tools that read page markup, and your own site search or help widgets that can reuse the same JSON. Whether a given search engine or assistant uses it is up to that service.

So treat FAQ schema as a clear, machine-readable copy of content that already earns its place on the page, not as a way to get extra space in search results.

You add FAQ schema by pasting one JSON-LD script element into the page's HTML, either in the head or anywhere in the body. The steps:

1. Write the questions and answers on the page itself first, where visitors can read them. The markup must match visible content.
2. Enter the same pairs in the generator above. Reorder them to match the page, and remove any you do not show.
3. Keep "Wrap in a script tag" ticked and copy the output.
4. Paste it into the page. In WordPress, use a custom HTML block or your SEO plugin's schema field; in a framework such as Next.js, render the JSON inside a script element with type application/ld+json.
5. Publish, then test the live URL with a structured data validator to confirm the markup is read without errors.

The rules below come from Google's FAQ documentation, before it was removed in 2026, and from its general structured data guidelines, which still apply to all markup. They come down to honesty and a short list of format rules. Breaking the general guidelines can get markup ignored or, in bad cases, a manual action.

• Every question and answer in the markup must appear on the page, in full. Do not mark up text that is hidden from visitors or exists only in the JSON.
• Use FAQPage only when the site wrote both the question and its single answer. A page built around one question that visitors answer, such as a forum or support thread, uses QAPage instead.
• Do not use FAQ markup for advertising. Questions written only to repeat a sales pitch break the guidelines.
• If the same FAQ appears on many pages, mark it up on one of them only.
• Answers may contain these HTML tags and no others, the list Google's FAQ documentation gave: h1 to h6, br, ol, ul, li, a, p, div, b, strong, i and em. The generator removes anything else, keeping the text inside.

Use FAQPage when you publish a list of questions with one official answer each, and QAPage when a page is built around one question that visitors answer. A page where visitors post many questions fits neither type.

Most broken FAQ markup fails for one of a handful of reasons, and a validator will name most of them.

• Invalid JSON from an unescaped quote or line break pasted into an answer by hand. The generator escapes these for you.
• A stray </script> inside an answer, which ends the script element early and spills the rest of the JSON onto the page. The generator writes it in an escaped form that cannot do this.
• Answers that differ from the visible text because the page was edited and the markup was not. Regenerate the JSON whenever the FAQ changes.
• Two FAQPage blocks on one page, often one from a plugin and one added by hand. Keep a single block that lists every question.
• Empty questions or answers left over from a template. The generator drops any pair that is not complete.