RoborankFAQ Schema Generator
Paste your questions and answers, get FAQPage JSON-LD you can drop straight into the page. Everything runs in your browser, so nothing is sent anywhere.
Your FAQ schema
Add a question and an answer to see your schema.
Nothing is uploaded. The schema is built in your browser as you type.
Schema is one page. Roborank watches the whole site.
Connect your CMS and Search Console and Roborank finds the pages that are slipping, writes the fix, and applies it.
See how Roborank worksWhat FAQ schema actually does now
FAQ rich results used to show a stack of expandable questions under your listing for anyone who asked for them. In August 2023 Google cut that back to health and government sites, so for most pages the extra listing height is gone.
The markup is still worth adding, for two reasons that have nothing to do with the old rich result. The first is that it tells a machine, unambiguously, which text on your page is a question and which text answers it. Search engines and AI assistants both work with that. When ChatGPT or an AI Overview quotes a source, structured question and answer pairs are easier to lift cleanly than the same content buried in prose.
The second is that Google still uses it internally for understanding, even where it shows nothing. You are not gaming anything by adding it. You are describing your own page accurately, which is what all structured data is for.
How to use the generator
- Put in the questions exactly as they appear on the page. The markup has to match the visible content, and Google spot-checks this.
- Write full answers. An answer under about twenty characters gets ignored, and a one-word answer looks like spam.
- Add the page URL if you have it. It is optional, but it anchors the schema to a specific page, which helps when a site has several FAQ blocks.
- Copy the output, wrapped in a script tag, and paste it into the page. Anywhere in the HTML works. The head is tidiest.
The rules Google applies
The content must be visible
Every question and answer in the markup has to appear on the page a visitor sees. Schema for content that only exists in the JSON is a structured data violation.
One FAQPage per page
If a page has two FAQ sections, put all the questions in one FAQPage block rather than adding two. Multiple blocks confuse the parse.
The site writes the answers
FAQPage is for questions the site answers itself. If the answers come from users, that is QAPage instead, and it has a different shape.
No ads or promotion in answers
Answers that are mostly a sales pitch, or that carry advertising markup, get the page filtered out of any rich result it might otherwise qualify for.
Where to put the code
Paste the generated block into the page's HTML. In WordPress, a custom HTML block at the bottom of the post works, or your SEO plugin's schema field. In Webflow, use an embed or the page-level custom code panel. On a static site, drop it into the template. There is no wrong position in the document, and it does not need to sit next to the visible FAQ.
Then check it. Paste the page URL into Google's Rich Results Test and the Schema Markup Validator. Both are free, and both will tell you within seconds if something is malformed.
Frequently asked questions
Is this FAQ schema generator free?
Yes, completely, with no signup and no limit. The whole thing runs in your browser, so your questions and answers are never sent to a server.
Does FAQ schema still work in 2026?
The rich result is limited to health and government sites since August 2023, so most pages no longer get the expandable questions under their listing. The markup still helps search engines and AI assistants understand which part of your page answers which question, which is why it is still worth adding.
What is the difference between FAQPage and QAPage schema?
FAQPage is for questions the site asks and answers itself, like a product FAQ. QAPage is for a single user question with answers from other users, like a forum thread. Using the wrong one is a common cause of a page being ignored.
Can I use HTML inside the answers?
Yes. Simple formatting like paragraphs, line breaks, lists and links is allowed inside an answer. Scripts, iframes and forms are stripped, so leave them out.
How many questions should an FAQ page have?
There is no minimum or maximum in the spec. Write the questions people actually ask and stop there. Padding the list with questions nobody asks makes the page worse, and the markup does not compensate for that.
Where do I paste the JSON-LD?
Anywhere in the page HTML, wrapped in a script tag with type="application/ld+json". The head of the document is the tidiest place. It does not have to sit near the visible FAQ.
Do the questions in the schema have to match the page exactly?
Yes. Google requires that every question and answer in the markup is visible to a visitor on that page. Marking up content that is not there risks a manual action against the site.