Loading…
Type your questions and answers, get FAQPage JSON-LD ready to paste. Rows can be added and removed freely, empty ones are dropped from the output, and the inline validator confirms the Question and Answer nesting is correct.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": []
}mainEntity FAQPage is missing required property "mainEntity".Copy the snippet first, then paste it into either tool's code tab.
Paste this inside your page's <head> (or anywhere in the HTML). Then check it with the JSON-LD validator.
We will be straight with you: the expandable FAQ dropdowns that made this markup famous are mostly gone. Google restricted FAQ rich results to authoritative government and health sites in August 2023, and that has not been reversed. So why generate it at all? Two reasons that hold up in practice. First, AI assistants and answer engines parse FAQPage markup when deciding what a page can answer, and structured Q&A is easier to quote accurately than prose. Second, the markup is cheap. If the FAQ content already exists on your page, a script tag that mirrors it costs a few minutes and nothing ongoing.
The structure itself is simple: a FAQPage entity with a mainEntity array of Question items, each holding an acceptedAnswer with text. The generator enforces that shape, so the usual hand-rolled mistakes (an answers array, a missing acceptedAnswer wrapper) cannot happen here.
The rules Google enforces on FAQPage are about honesty rather than syntax. The marked-up questions must be visible on the page. Answers must come from the site, which is what separates FAQPage from QAPage. Using FAQ markup for advertising copy, or stuffing answers with keywords the visible text does not contain, invites a manual action. And one FAQPage block per page is the rule; several blocks on one URL confuse parsers and get inconsistent treatment.
Before shipping, run the output through our JSON-LD validator or paste the live URL into Google's Rich Results Test. If you also want the page title and description dialed in, the SERP snippet preview sits right next door.
For most sites, no. Since 2023 Google limits FAQ rich results to well-known government and health sites. The markup still has value: it feeds AI assistants and answer engines structured Q&A they can quote, and it costs nothing to maintain if your FAQ content already exists.
Google allows a small set of tags in the answer text (links, lists, basic formatting), but plain text is the safe default and what this generator produces. If you add HTML by hand afterwards, remember to escape it correctly inside the JSON string.
Yes. FAQPage markup must mirror Q&A content the visitor can read on that same page. Marking up questions that only exist in the script is against Google's guidelines and a common reason for structured data manual actions.
Mark up the full visible FAQ, whether that is three questions or fifteen. Avoid repeating the same FAQPage block across many pages; if the same questions appear sitewide, mark them up once on the canonical FAQ page.
No. FAQPage is for pages where the site itself writes both questions and answers. User-generated threads where visitors post answers belong to QAPage, a separate type with its own rules.
TWR adds AggregateRating schema to your public review page automatically — free. Collect verified reviews inside your app and let us handle the structured data.