FAQ Schema Generator (JSON-LD)
Generate FAQPage JSON-LD schema for FAQ sections with Question and Answer nodes.
Maintained by Aygul Dovletova
FAQ Schema Generator (JSON-LD)
The FAQ schema generator builds FAQPage JSON-LD with Question and Answer nodes. Paste one question-and-answer pair per line, separated by a pipe character, and the tool emits the full <script type="application/ld+json"> block ready to drop into the <head> of your page. Everything runs in your browser, so your FAQ copy never touches a server.
FAQPage Schema After 2023
Before August 2023, almost any site with valid FAQPage markup was eligible for the expandable FAQ rich result in Google's SERP. That feature was restricted in August 2023 to "well-known, authoritative government and health websites." Commercial sites lost the visible carousel even though the markup stayed valid. This change has two consequences for you:
- The FAQPage JSON-LD on a commercial site no longer produces an expandable accordion in the SERP. Do not invest in FAQ schema expecting that specific feature back.
- The markup is still worth adding. It helps voice assistants extract Q&A content, feeds AI Overviews and Bing's answer cards, and signals to crawlers that the page is structured question-answer content.
If you run a government, educational, or health site that might still qualify for the rich result, structured data is the first requirement - schema quality, content authority, and domain trust decide the rest.
Format Rules for Questions and Answers
- Questions must be actual questions - phrased in natural language, not keyword stuffed, not ending in a period. "How does Schema Markup affect SEO?" not "schema markup seo effects".
- Answers must be complete - one or two sentences minimum, written as standalone answers that make sense out of context. Voice assistants often read the first one or two sentences aloud verbatim.
- No promotional content - Google policy explicitly forbids advertisements inside FAQ
acceptedAnswerbodies. Marketing copy ("Try us risk-free for 30 days!") inside the answer can drop rich-result eligibility for the entire site. - Answer must match the visible content - every Q&A pair in the JSON-LD must appear verbatim on the rendered page. Hidden Q&A that only lives in the structured data is a policy violation.
- HTML is allowed in answers - paragraph tags, lists, and links are valid inside
answer.text. Image tags and script tags are stripped by Google and other consumers.
When FAQPage Is the Wrong Choice
Several content types look like FAQ but actually map to different schemas. Picking the wrong one costs you eligibility:
- QAPage is for pages where users post a single question and one accepted answer (Stack Overflow, Quora threads). Not for pre-authored Q&A.
- HowTo is for step-by-step tutorials. Even if the steps are phrased as questions, the right schema is HowTo with
HowToStepnodes. - Article is for long-form editorial content that happens to contain questions. If the FAQ is a section within a larger article, use Article on the whole page and do not add FAQPage unless the FAQ is substantive (5+ items).
Difference From the Generic Generator
The generic Schema Markup Generator handles all eight types. This page lands with FAQPage pre-selected and focuses on FAQ-specific guidance (2023 policy change, voice search behaviour, formatting) that would be out of place on the generic page. For Product, Article, or Organization schema, switch types or jump to the dedicated sub-pages.
Testing and Deploy Checklist
Run the generated JSON-LD through Google's Rich Results Test to confirm Google parses all Q&A pairs. Then paste the block into <head> and ensure the visible FAQ section of the page matches the structured data word-for-word. After deploy, request a recrawl via Search Console if the page is already indexed; new FAQPage markup takes 24-72 hours to propagate.
Frequently Asked Questions
Will adding FAQPage schema bring back the expandable rich result on my site?
Not unless your site is a recognised government or health authority. Google restricted the FAQ rich result in August 2023 to exactly that narrow set of domains. Valid FAQPage markup on a commercial or personal site no longer triggers the expandable accordion in the SERP. The markup is still worth adding because voice assistants, AI Overviews, and Bing's answer cards use it to extract Q&A content, but the specific visual feature you may remember from 2021-2022 is gone for most sites.
How many questions should a FAQPage have?
Schema.org accepts any number, but practical advice: at least three, no more than about twenty. Fewer than three and the page is not meaningfully an FAQ. More than twenty and the JSON-LD block becomes large enough to slow time-to-first-byte on cold caches. If you need more, split by topic across multiple pages, each with its own smaller FAQPage.
Does the FAQ on the page have to match the JSON-LD exactly?
Yes, word-for-word. Google's structured data policies require the Q&A visible on the page to match what is in the JSON-LD. You cannot hide answers in schema to game voice search, and you cannot embellish the on-page copy while keeping the schema short. If they drift apart, Google treats it as policy violation and the rich result (for domains still eligible) disappears.
Can I use HTML inside the answers?
Yes. Google parses <code><p></code>, <code><ul></code>, <code><ol></code>, <code><li></code>, and <code><a></code> tags inside <code>acceptedAnswer.text</code>. Script and style tags are stripped. Images are generally ignored by rich-result rendering but survive in the raw JSON. The generator accepts plain text by default; if you edit the raw JSON-LD to add HTML, make sure the page body uses the same markup.
Should each question be its own page?
Only if each question has substantial unique answer content (several paragraphs, images, maybe code samples). For one-or-two-sentence answers, keep them on a single FAQPage. Splitting thin Q&A across many pages is a classic thin-content pattern and can trigger manual actions. A cluster of detailed how-to questions is better modelled as multiple HowTo pages or a long-form Article.
What is the difference between FAQPage and QAPage?
FAQPage is for pre-authored Q&A sections where the publisher supplies both question and answer. QAPage is for user-generated threads where one user posts a question and the community supplies answers (Stack Overflow, Quora). For a help-centre article you wrote yourself, use FAQPage. For a forum thread, use QAPage. Using QAPage on authored content is not a violation but it will not trigger the features you expect.
Can FAQ schema hurt my rankings?
Only if the markup violates policy. Invalid or missing data is logged in Search Console as errors but does not penalise the page. Policy violations (fake Q&A, promotional content in answers, hidden content that does not match the page) can trigger manual actions affecting the whole domain. Stick to real questions your users ask, answered honestly on-page, and you have no downside.
Does this tool store or log my FAQ content?
No. The generator runs entirely in your browser. Your Q&A pairs are parsed into JavaScript objects, formatted with JSON.stringify, and shown in the output pane. There is no network request, no server-side processing, no analytics beacon per keystroke. Open the Network tab in DevTools and confirm: zero outbound traffic while you type or click buttons.
More SEO & Web Tools
Meta Tag Generator
Generate complete HTML meta tags including Open Graph and Twitter Card tags.
Open toolOpen Graph Preview
Preview how your page looks when shared on Facebook and LinkedIn.
Open toolRobots.txt Generator
Generate robots.txt files with user-agent rules, allow/disallow paths and sitemap.
Open toolXML Sitemap Generator
Generate valid XML sitemaps from a list of URLs with changefreq and priority.
Open toolKeyword Density Checker
Analyze word frequency with single words, bigrams and trigrams with density percentages.
Open toolGoogle SERP Preview
Preview how your page appears in Google search results with character count indicators.
Open tool