Free FAQ Schema Generator

Most FAQ schema generators still promise the expandable question-and-answer dropdowns under your Google listing. Those are gone. Google retired FAQ rich results for every website on May 7, 2026, then removed the documentation and the testing support that went with them.

FAQPage markup itself is still valid Schema.org vocabulary, though, and it has not become harmful. This page gives you a generator that produces clean FAQPage JSON-LD together with the matching visible HTML, and a straight answer on when that markup is worth adding, when to leave it alone, and when to remove it.

What Is an FAQ Schema?

An FAQ schema is structured data that tells machines a page contains a list of questions, each with one answer written by the site owner. Schema.org defines FAQPage as "a WebPage presenting one or more 'Frequently asked questions'".

It uses three types nested inside each other: a FAQPage contains several Question items, and each question has an acceptedAnswer of type Answer. The usual format is JSON-LD, a small block of code inside a <script type="application/ld+json"> tag. Visitors never see it; search engines and other parsers read it.

FAQ schema example

Here is what the generator produces for a single question:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does shipping take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Orders ship within 1 business day."
      }
    }
  ]
}
</script>

What Is an FAQ Format?

An FAQ format is a list of questions, each followed directly by its answer, usually grouped by topic on a single page. The question is written the way a customer would ask it, and the answer starts with the direct response before adding detail.

On a web page, a good FAQ format has three layers:

• Visible HTML: each question as a heading (or an accordion summary) and the answer as normal paragraph text underneath. This is what people read and what search engines index. The FAQ HTML tab in the tool writes this for you.
• Structured data: the same questions and answers repeated in FAQPage JSON-LD, so machines can read them without guessing.
• Sensible order: the most common or most important questions first, and related questions grouped together (shipping, returns, pricing) on longer FAQs.

If the questions are hidden in an accordion, that's fine, as long as visitors can open them. What matters is that the content exists on the page, not only in the code.

Did Google Remove FAQ Rich Results? The Full Timeline

Yes. The change happened in stages, which is why so many guides are out of date:

Looking for an FAQ rich results schema generator?

Many people still search for an "FAQ rich schema generator" or "FAQ rich snippet generator", hoping to get the dropdown answers under their listing. There is no separate "rich" version of the code. FAQ rich results always used the same FAQPage markup this tool generates, and since May 7, 2026, no markup can bring them back. Any tool that still promises FAQ rich snippets in Google is working from outdated information.

Google has not said FAQPage markup is harmful, and it doesn't penalize pages that still carry it. It simply no longer uses it to build a special search feature.

Does FAQ Schema Still Work in 2026?

FAQ schema still works as valid structured data, but it no longer produces any visible result in Google Search. Search engines can still read it; Google just doesn't turn it into dropdown answers any more. Whether it's worth adding depends on the page, so here is an honest breakdown.

What FAQ schema no longer does

• It won't make your Google result bigger or add dropdown answers.
• It isn't a shortcut to higher rankings. Structured data helps Google understand a page; it doesn't replace useful content or links.
• It isn't a requirement for Google's AI Overviews or AI Mode. Google's own guidance for AI features says there is "no special schema.org structured data that you need to add".

What it can still do

• Label your content unambiguously. A parser doesn't have to guess which line is the question and which paragraph answers it.
• Help outside Google. Speaking at SMX Munich in March 2025, Bing's Fabrice Canel said schema markup helps Microsoft's LLMs understand your content. Bing's index also supports Copilot.
• Give other tools clean data. Structured data is read by more than search engines, and a correct FAQPage block costs nothing to maintain once the FAQ is written.

No public study shows that FAQ schema on its own gets a page cited in AI answers. What those systems clearly need is the visible content: a direct question, a direct answer, and HTML they can read without running JavaScript. Treat the schema as a helpful label on good content, not as a visibility tactic.

Keep, remove, or add? A quick decision guide

Is an FAQ Good for SEO?

Yes, a genuine FAQ section is good for SEO, even though the FAQ schema no longer gets a rich result. The value comes from the content, not the code:

• It answers long-tail searches. Questions like "do you ship to Canada?" or "how long does a guest post take?" are real searches. A clear answer on the right page can rank for them.
• It matches "People also ask". Google's People also ask boxes pull short, direct answers from pages. A well-written FAQ answer is exactly that shape.
• It gives AI answers something to quote. AI Overviews, ChatGPT and Copilot summarize pages that answer questions plainly. A self-contained answer is easy to cite.
• It removes doubts before people leave. Pricing, delivery, refunds and "is this right for me?" questions answered on the page help visitors decide.

An FAQ hurts rather than helps when it's thin or generic: the same five questions pasted onto every page, answers written only to repeat a keyword, or questions nobody actually asks. Write FAQs for the page's actual visitors, and the SEO benefit follows.

FAQPage vs QAPage: Which One Do You Need?

These two are often mixed up. The difference is who writes the answers and how many questions the page covers. Google's QAPage documentation is explicit: "Don't use QAPage markup for FAQ pages or pages where there are multiple questions per page."

How to Generate Schema Markup for Any Page

This tool is a schema code generator for one type, FAQPage. The process is the same for any other type of schema:

1. Pick the type that describes the page. An article is Article, a product is Product, a local business is LocalBusiness, a list of questions is FAQPage. Browse the types on Schema.org.
2. Collect the properties from the page. Only use information visitors can see: the headline, price, address, author, questions and so on.
3. Write it as JSON-LD. Use a generator for the type, or write it by hand following the examples on Schema.org and in Google's structured data documentation.
4. Add it to the page in the <head> or <body>, rendered in the HTML rather than injected later.
5. Check it. Use the Schema.org Validator for any type, and Google's Rich Results Test for the types Google still supports as rich results, such as Product, Article, Review snippet and Breadcrumb.

Where to Add FAQ Schema on Your Platform

The rule is the same everywhere: the JSON-LD goes on the same URL as the visible FAQ, once. JSON-LD can sit in the <head> or the <body>; both are read.

WordPress

Check what you already have before pasting anything. The FAQ blocks in Yoast SEO and Rank Math output FAQPage markup automatically, and some themes and page builders do the same. If your FAQ is built with one of those blocks, you already have the schema, and adding the generator's code on top would create a duplicate. If your FAQ is plain text, add the generated code with a header-and-footer or code-snippet plugin, limited to that one page. Don't paste it into a normal paragraph block, where the editor can alter it.

Shopify

For a single page, the simplest option is a Custom Liquid section on that page's template. If you edit theme.liquid instead, wrap the code in a condition so it only appears on the right page. Shopify themes and review apps sometimes output their own structured data, so view the page source afterwards and make sure there is only one FAQPage block.

Wix

Open the page's SEO settings and add the code under Advanced SEO as structured data markup, which keeps it tied to that page. If you use Wix's FAQ app, check whether it already outputs FAQPage markup first.

Squarespace

Use the page's own settings (Advanced → Page Header Code Injection) rather than the site-wide injection, so the markup only appears on the FAQ page. Code injection is only available on some plans.

Webflow

Paste the code in the page settings under Custom code → Inside <head> tag. For CMS pages, build the JSON-LD from CMS fields so the schema and the visible FAQ always come from the same text.

Next.js, React and other JavaScript frameworks

Render the JSON-LD and the FAQ into the HTML on the server. Google can process JavaScript, but a 2024 study by Vercel and MERJ found that major AI crawlers, including OpenAI's and Anthropic's, fetch JavaScript files without running them. Content that only appears after client-side rendering may be invisible to them.

Plain HTML

Place the generated script block inside the page's <head>, and put the FAQ itself in the body as normal text. The FAQ HTML tab in the tool gives you that body markup, ready to style.

Can FAQ Answers Contain HTML?

Yes, within limits. Google's former FAQ guidelines allowed a short list of tags in the answer text: <h1> to <h6>, <br>, <ol>, <ul>, <li>, <a>, <p>, <div>, <b>, <strong>, <i> and <em>. That is still the safest set to use.

The generator follows it. If an answer contains links or lists, they are kept in both the schema and the FAQ HTML. Anything else, such as images, inline styles, iframes or scripts, is stripped, and the Schema Checks tell you which answer was affected. Links keep only their href.

How to Check FAQ Schema

To check FAQ schema, paste your code or URL into the Schema.org Validator, then confirm the markup appears once and matches the visible FAQ. Since June 2026, Google's Rich Results Test no longer reports FAQPage, and Search Console has no FAQ report. Here are the four checks to run:

1. Syntax: paste your code, or your live URL, into the Schema.org Validator. It confirms the JSON-LD parses and that the types and properties are recognized.
2. Duplicates: open the live page, view the source, and search for FAQPage. It should appear once.
3. Match: compare every question and answer in the markup with the visible FAQ. Same questions, same order, same wording.
4. Rendering: use the URL Inspection tool in Search Console and check that both the FAQ text and the script block are in the rendered HTML.

Rules That Still Apply to FAQ Markup

Google removed the FAQ-specific documentation, but its general structured data policies still apply to every type of markup on your page. The most important one for FAQs: "Don't mark up content that is not visible to readers of the page."

• Visible: every question and answer in the schema must be on the page. Content inside an accordion that visitors can open counts as visible.
• Accurate: the markup should describe the page as it is, not a keyword-stuffed version of it.
• Written by you: FAQPage is for answers written by the site owner. Questions answered by users belong in QAPage.
• Not advertising: answers stuffed with sales copy aren't what FAQ markup is for.

Common FAQ Schema Mistakes

How to Write FAQ Answers People Actually Use

The markup is the easy part. The value is in the questions you choose and how you answer them.

• Collect the questions people ask. Look at the queries in Search Console, the "People also ask" box for your main keyword, and the questions customers send you by email or chat.
• Answer in the first sentence. Start with "Yes", "No", a number or a date, then explain. This helps readers who skim and makes the answer easy to quote.
• Keep each answer self-contained. It should make sense if someone reads only that answer, without the rest of the page.
• Be specific. "Within 30 days of delivery" is more useful than "a generous return window".
• Link to depth. If a full answer needs 500 words, write a short answer and link to the page that covers it properly.
• Keep it current. Update prices, timelines and policies in the visible FAQ and the schema together.

FAQ Schema Is a Small Part of SEO

Structured data helps machines read a page that is already good. It won't rescue thin content or a site with no authority. Before spending time on markup, check that your SEO title and meta description are doing their job, that your important URLs are in an XML sitemap, and that your site is getting links from relevant websites. If you want to understand that last part, start with what link building is and how it works.

Sources

• Google Search Central: Documentation updates
• Google Search Central Blog: Changes to HowTo and FAQ rich results (2023)
• Google: General structured data guidelines
• Google: Q&A (QAPage) structured data
• Google: AI features and your website
• Schema.org: FAQPage
• Vercel: The rise of the AI crawler