FAQ Schema Generator
Paste in the questions your page answers, along with the answers. The tool writes the code that lets search engines and AI assistants recognise them as question and answer pairs rather than ordinary paragraphs.
Your details
Questions and answers
Paste the block anywhere inside <head> or <body>, then confirm it parses with the schema validator.
What is FAQ schema, and is it still worth adding?
FAQ schema is a block of code, invisible to visitors, that labels the questions and answers on your page as exactly that. To a search engine, a heading followed by a paragraph is just a heading followed by a paragraph. This markup says: that heading is a question, and this paragraph is its answer.
The honest answer on value has changed. Until 2023, this markup got you an expandable accordion under your search result, and everyone added it for that reason. Google then restricted those rich results to government and health sites, and most sites lost the visual payoff overnight. Plenty of guides still promise you the accordion. They are out of date.
What replaced it is arguably more useful. AI Overviews, ChatGPT, Perplexity, and voice assistants all need to find a direct answer to a direct question, and a clean labelled pair is the easiest thing in the world for them to lift. If you care about being the source that gets quoted rather than the tenth blue link, this is cheap groundwork.
Two rules. The questions must genuinely appear on the page, visible to a reader. And use it where the page really does answer questions, not as a block bolted onto every page to farm markup. That pattern is exactly what spam systems look for.
What This Tool Generates
FAQPage JSON-LD
Valid mainEntity array of Question and Answer nodes
Unlimited pairs
Add as many questions as the page genuinely answers
HTML sanitising
Strips every tag outside Google's permitted list
Copy-ready script tag
Wrapped in application/ld+json, ready to paste
Write the answers for the reader, not the markup
The answers that get lifted into AI Overviews and assistant responses are the ones that answer the question in the first sentence and then add context, not the ones that warm up for three lines before committing. Lead with the answer. Keep each one under about fifty words if you can. Once the block is live, run the page through the schema validator to confirm it parses.
Frequently Asked Questions
Does FAQ schema still show rich results in Google?
Rarely, and only for government and health sites. In August 2023 Google restricted FAQ rich results to what it calls well-known authoritative sources, so most sites no longer see the accordion in search results. The markup still has value, it just is not the reason it used to be.
Then why bother adding it?
Because rich results are not the only consumer. AI Overviews, ChatGPT, Perplexity, and voice assistants all parse structured data to find direct answers, and a clean question-and-answer pair is the easiest thing for them to lift. FAQ schema is now less about the blue links and more about being quotable everywhere else.
What HTML can I use inside an answer?
Google permits h1 through h6, br, ol, ul, li, a, p, div, b, strong, i, and em. Everything else is stripped or invalidates the markup. This tool removes unsupported tags automatically as it builds the JSON, so pasting formatted text will not silently break your markup.
Do the questions have to be visible on the page?
Yes. Structured data must describe content a visitor can actually see. Marking up questions that are hidden, collapsed behind a tab that never opens, or absent from the page entirely is a violation of Google's structured data guidelines and can earn a manual action.
Can I put FAQ schema on every page?
Technically yes, sensibly no. Use it where the page genuinely answers questions: product pages, service pages, pricing, support articles. Bolting a generic FAQ block onto every page to farm markup is the pattern Google's spam systems look for, and it makes the page worse for readers too.
What is the difference between FAQPage and QAPage?
FAQPage is for questions the site author wrote and answered, a support page or a pricing FAQ. QAPage is for pages where users ask and other users answer, like a forum thread. Using FAQPage on user-generated Q&A is a mismatch that Google will ignore at best.
Other schema tools
Local Business Schema Generator
Tell Google your business name, address, phone, and opening hours in the format it reads literally. Type your details, copy the code, paste it into your site.
Use toolProduct Schema Generator
Give Google your price, stock status, and star rating so they can show under your listing in search. Fill in the product details, copy the code.
Use toolEvent Schema Generator
Get your event date, venue, and ticket link into Google's event listings and Maps. Handles in-person, online, and hybrid events correctly.
Use toolBreadcrumb Schema Generator
Replace the raw URL under your search result with a readable trail like Home > Guides > Technical SEO. Enter each level, copy the code.
Use toolArticle Schema Generator
Tell Google who wrote your article, when, and for whom. The author link is the part that carries E-E-A-T, and most sites leave it out.
Use toolFind every page missing structured data
CrawlRaven crawls your whole site, validates the schema on every page, and ranks the gaps by the impressions each page already earns in Search Console.