An FAQ schema generator turns the questions and answers on your page into FAQPage structured data: a small JSON-LD script that tells machines which text is a question and which text is its answer. You type each question, paste its answer, and copy the finished script into your page's HTML. The free FAQ schema generator does this in your browser, and this guide covers everything around it.
Before you add the markup, know what it will and will not do in 2026. Google stopped showing FAQ rich results for every site in May 2026, after limiting them to a small group of sites in 2023. The markup is still valid schema markup, it still describes your page precisely to anything that reads structured data, and it costs a few minutes to add. It just no longer earns the expandable answers under your Google result.
Below you will find what FAQPage markup is, a complete example you can copy, the history of the Google change, the honest case for adding it anyway, a step-by-step way to generate and validate it, and the mistakes that make it invalid.
What FAQPage schema markup is
FAQPage is a type in the schema.org vocabulary, the shared dictionary that search engines and other machines use to read pages. A page marked up as FAQPage says: "this page contains a list of questions, each written by the site, each with one answer written by the site". Nothing about how the page looks changes. The markup sits in a script tag that browsers ignore.
The structure is short. An FAQPage object has a mainEntity property, which is a list of Question objects. Each Question has a name (the question text) and an acceptedAnswer, which is an Answer object with a text property (the answer). That is the whole model.
JSON-LD, microdata or RDFa?
Structured data can be written three ways. Microdata and RDFa add attributes to your visible HTML tags, so the markup is tangled up with your layout and breaks when someone edits the template. JSON-LD is a separate block of JSON inside a <script type="application/ld+json"> tag. Google recommends JSON-LD, it is the easiest to maintain, and it is what every FAQ schema markup generator, ours included, produces.
FAQPage or QAPage?
The two types look alike but describe different pages. Pick the wrong one and the markup describes your page incorrectly.
| FAQPage | QAPage | |
|---|---|---|
| Who writes the answers | The site owner | Users of the site |
| Answers per question | One official answer | Several, often voted on |
| Questions per page | Several | One main question |
| Typical page | Pricing FAQ, help page, product FAQ, a guide's FAQ section | Forum thread, community question, support community post |
If your visitors can post answers, it is QAPage. If you wrote the questions and answers yourself, it is FAQPage.
A complete FAQPage JSON-LD example
Here is valid FAQ structured data for a page with two questions. You can paste it into your HTML as it is and replace the text.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Is there a free plan?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. The free plan includes one project and 1,000 events a month. You can upgrade at any time from the billing page."
}
},
{
"@type": "Question",
"name": "Can I cancel my subscription?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Cancel from <a href='https://example.com/settings'>Settings</a> and you keep access until the end of the billing period."
}
}
]
}
</script>
What each part does:
- @context says the vocabulary is schema.org. Always
https://schema.org. - @type: FAQPage names the kind of page.
- mainEntity holds the list of questions, in the same order they appear on the page.
- name is the full question, word for word as visitors read it.
- acceptedAnswer.text is the full answer, also as visitors read it.
Can answers contain HTML?
Yes, a little. Answers may include basic HTML such as links, paragraphs, line breaks, lists and bold or italic text. Google's documentation used to list the allowed tags as headings, br, ol, ul, li, a, p, div, b, strong, i and em. Keep it simple: a link and a short list are fine; images, tables and scripts are not. Inside JSON, every double quote in your HTML must be escaped as \", or written with single quotes as in the example above, or the whole script becomes invalid.
What happened to Google's FAQPage rich results
For a few years, FAQ schema was a favorite quick win. Add the markup and Google could show your questions as expandable answers under your result, which made the listing taller and pushed competitors down the page. That reward is gone, in two steps.
| When | What Google changed | What it meant for most sites |
|---|---|---|
| Until August 2023 | FAQ rich results could appear for any site with valid markup | Expandable questions under many results |
| August 2023 | FAQ rich results limited to well-known, authoritative government and health websites | Almost every other site stopped seeing them |
| May 2026 | FAQ rich results no longer shown in Google Search for anyone | No FAQ rich results at all |
| June 2026 | FAQ search appearance, the FAQ rich result report and Rich Results Test support dropped | No FAQ reporting in Search Console or the Rich Results Test |
| August 2026 | FAQ support removed from the Search Console API | Reporting scripts that read FAQ data stop returning it |
Two things did not change. FAQPage is still a valid schema.org type, and Google's notes on the retirement indicate the markup can stay on your pages without causing problems. So there is no need to rip it out of existing pages. The question is only whether to add it to new ones.
Is FAQPage structured data still worth adding?
For most pages with a real FAQ section, yes, as a small piece of hygiene rather than a growth tactic. Here is the honest case.
Reasons to add it
- It describes your page without ambiguity. Structured data is the clearest way to say "this text is a question, this text is its answer". Search engines other than Google, AI answer engines and other crawlers can read it. None of them promises to use it, but well-structured facts are easier to extract and quote correctly.
- It costs almost nothing. With a generator it takes a few minutes per page, and it never needs touching again unless the FAQ changes.
- It forces good FAQ writing. Markup only works for questions that are actually on the page and answered in full. That discipline produces the short, direct answers that do well in a featured snippet, which Google builds from your visible text, not from FAQ markup.
- It fits the way AI assistants answer. Pages that state a question and answer it plainly are easy for assistants to cite. Our guide on getting cited by ChatGPT and Perplexity covers the rest of that work.
When to skip it
- The page has no visible FAQ. Never add markup for questions visitors cannot see.
- The questions are written by users. Use QAPage, or nothing.
- You would be adding it only for rich results in Google. Those are gone; spend the time on the content instead.
- The same FAQ block repeats across hundreds of pages. Mark up the one page where it belongs.
One thing FAQ schema has never done is improve rankings directly. Structured data helps machines understand a page; it is not a ranking boost. Treat it that way and you will not be disappointed.
How to use an FAQPage schema generator, step by step
A FAQPage schema generator saves you from hand-writing JSON, which is where most errors come from (a missing comma or a stray quote breaks the whole block). The process takes about five minutes.
- Write the visible FAQ first. Put the questions and answers on the page as normal HTML. The markup describes the page; it never replaces it.
- Open the free FAQ schema markup generator. It runs in your browser, so nothing you type is sent anywhere.
- Add each question word for word. Copy it from the page rather than retyping it, so the two never drift apart.
- Paste each answer. The same answer visitors read, including any link you want to keep.
- Copy the JSON-LD. The tool gives you a complete
<script type="application/ld+json">block. - Paste it into the page's HTML. The head or the body both work. One FAQPage script per page is enough.
- Publish and check the live page, as described in the next section.
Where to paste it in common setups
- Plain HTML or a static site: paste the script just before
</head>or at the end of the FAQ section. - A site builder: most builders have a "custom code" or "code injection" field for a single page. Use the page-level field, not the site-wide one, or the FAQ will be marked up on every page.
- WordPress: many SEO plugins have an FAQ block that writes the markup for you. If you use one, do not paste a second script as well.
- React or Next.js: build the object in code from the same data that renders the visible FAQ, then output it with
<script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(faq) }} />. Generating both from one source is the surest way to keep them identical.
If you need other types too, such as Organization, SoftwareApplication or BreadcrumbList for the same page, the schema markup generator builds those. Use one script per type.
How to validate FAQPage markup
Since June 2026, Google's Rich Results Test no longer reports on FAQ markup, so you need other ways to check it. Do two checks after you publish.
- Check the live page with our schema markup checker. Paste the URL. It finds every JSON-LD block and microdata type on the page, lists each type with its fields, and flags invalid JSON and missing key fields. Confirm that FAQPage appears once and that every question has an answer.
- Check it against the vocabulary with the Schema.org validator. It reports properties that do not belong to the type and values of the wrong kind.
Why FAQ JSON-LD fails
- Invalid JSON. A trailing comma after the last question, an unescaped double quote inside an answer, or two objects side by side without an array. The checker shows where parsing failed.
- Smart quotes. Text pasted from a word processor can turn straight quotes into curly ones. JSON only accepts straight double quotes around keys and values.
- A missing answer. Every Question needs an
acceptedAnswerwith a non-emptytext. - The wrong nesting. Questions must sit inside
mainEntity, not directly on the page object.
FAQPage schema rules and common mistakes
These rules come from Google's long-standing guidelines for FAQ markup and from schema.org's definitions. They are still the right way to use the type, whoever reads it.
| Mistake | Why it is a problem | Fix |
|---|---|---|
| Marking up questions that are not on the page | Structured data must describe visible content; hidden markup can be treated as spam | Only mark up questions and answers visitors can read |
| Different wording in the markup and on the page | The markup no longer describes the page | Copy text across, or generate both from one source |
| FAQPage on a forum or community thread | User answers are QAPage content | Use QAPage for user-generated questions |
| Answers that are adverts | FAQ markup is for information, not promotion | Answer the question; keep sales copy elsewhere on the page |
| The same FAQ marked up on many pages | Repeated blocks add noise, not meaning | Mark up one instance, on the page where the FAQ belongs |
| Two FAQPage scripts on one page | Usually a plugin and a manual script both writing it | Keep one; the checker shows duplicates |
| Only part of the answer in the markup | The answer in the markup should be the complete answer | Include the full answer text |
How to write questions worth marking up
The markup is only as good as the questions inside it. A weak FAQ ("Why is our product great?") helps nobody, with or without schema. Strong questions come from real people.
- Search Console queries. Look at the questions people type before they land on the page. Those are the exact phrases to answer.
- Support and sales. The questions you answer every week by email are the ones new visitors have too.
- "People also ask" boxes. Search your main keyword and note the questions Google shows.
Then write each answer so its first sentence stands on its own: answer first, detail after. Around 40 to 60 words is a good length for most answers. Plain answers like that are what search engines quote and what AI assistants cite, which matters more now than the old rich result ever did. For the wider page work around this, see the on-page SEO checklist and the SEO checklist for a startup launch.
FAQ
What is an FAQ schema generator?
An FAQ schema generator is a tool that turns a list of questions and answers into FAQPage structured data in JSON-LD. You enter each question and its answer, and it returns a script tag you paste into your page's HTML, so you do not have to write the JSON by hand.
Does FAQ schema still work in 2026?
The markup is still valid and still describes your page to anything that reads structured data. What stopped working is the Google rich result: Google limited FAQ rich results to authoritative government and health sites in August 2023 and stopped showing them for all sites in May 2026.
Does FAQ schema help SEO?
Not directly. FAQ schema has never been a ranking factor, and in 2026 it no longer earns a rich result in Google. Its value is clarity: it labels your questions and answers for machines. The visible FAQ text is what can win featured snippets and AI citations.
Where do I put FAQ JSON-LD?
Anywhere in the page's HTML, usually in the head or right after the FAQ section. Use one FAQPage script per page, and put it only on the page whose visible FAQ it describes, not in a site-wide template.
Can I add FAQ schema to every page?
Only to pages that have a visible list of questions with answers written by you. Adding the same FAQ block to every page, or marking up questions that are not on the page, describes your site incorrectly and can be treated as spammy structured data.
What is the difference between FAQPage and QAPage?
FAQPage is for a page where the site owner wrote several questions and one answer for each. QAPage is for a page built around one question where users post the answers, such as a forum thread. Use the type that matches who wrote the answers.
Use the free FAQ schema generator, then check it once
FAQ markup is no longer a trick for a taller Google result. It is a precise label on content you should be writing anyway. Write a real FAQ, generate the script with the free FAQ schema generator, check the live page with the schema markup checker, and move on to the work that moves rankings.
Topics
Written by
Devvrat Hans
Founder
By subscribing, you agree to get our newsletter by email. Unsubscribe any time in one click. See our Privacy policy and Terms.
Related Articles
301 Redirect Generator Guide: 301 vs 302, and Redirect Code for Apache, Nginx, Next.js and Cloudflare
How to use a 301 redirect generator, and when a 301 is the right redirect at all: 301 vs 302 vs 307 vs 308, copy and paste code for .htaccess, Nginx, Next.js and Cloudflare, and how to avoid chains and loops in a migration.
Bulk Domain Authority Checker: How to Compare Many Domains at Once (Free)
When to check domain authority in bulk, how to compare up to 20 domains at once for free, how to read and sort the results, and a link prospecting workflow with spreadsheet formulas.
Canonical Checker Guide: What a Canonical Tag Does and How to Check Yours
How to use a canonical checker, and what it is checking for: what rel canonical means, HTML and HTTP header examples, when to use a canonical tag, the mistakes that drop pages from Google and how to read Search Console's canonical reports.