zivooo
FREE FAQ SCHEMA GENERATOR

Free FAQ schema generator: your questions and answers as FAQPage JSON-LD.

Updated

This FAQ schema generator turns the questions and answers on your page into FAQPage JSON-LD. Add as many pairs as the page shows, and the code builds as you type, with a check that every question has its answer.

One thing to know first: Google stopped showing FAQ rich results on 7 May 2026. The markup still labels your answers for any engine that reads it, and this page says plainly what it does and doesn't do now.

  • Free
  • No signup
  • Runs in your browser
Questions and answers
  1. 01
FAQ PAGE JSON-LDEXAMPLE
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does Northwind work with Gmail?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Connect Gmail in Settings and every email to a contact is logged."
      }
    },
    {
      "@type": "Question",
      "name": "Can I import contacts from a spreadsheet?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Upload a CSV file and match its columns to contact fields."
      }
    }
  ]
}
</script>
ValidValid JSON-LD, with every field this type needs.

Google stopped showing FAQ rich results on 7 May 2026. The markup still labels your questions and answers for any engine that reads it.

Good FAQs start from real buyer questions.Zivooo finds the ones AI is asked about your market and writes the answers into articles.
Start free, no card
WHAT THIS TOOL DOES

What the FAQ schema generator writes

A FAQPage block built from your own words, checked before you copy it.

  • One question, one answer, as many as you need

    Add pairs up to 30, remove any, and keep them in the order the page shows.

  • The exact structure Google documented

    A FAQPage whose mainEntity lists each Question with its name and an acceptedAnswer holding the text.

  • A check on every pair

    A question without an answer, or an answer without a question, is named before you copy.

  • Plain text answers

    What you type goes in as text, escaped so a stray less than sign can't break the script tag.

  • Script tag or JSON

    Copy a script tag for the page head, or bare JSON for a plugin's schema box.

  • Nothing leaves your browser

    The questions you type are never sent to us.

HOW IT WORKS

From the FAQ on your page to FAQPage markup.

  1. 01

    Copy a question

    Take it from the page exactly as written.

  2. 02

    Add its answer

    The full answer the reader sees, not a summary.

  3. 03

    Repeat for each pair

    Keep the order the page uses.

  4. 04

    Copy the code

    Paste it into the head of that same page.

WHY IT MATTERS FOR AI SEARCH AND GOOGLE

What FAQ schema does now that Google dropped the rich result

For years, FAQ schema put expandable questions under a page's Google result. Google cut that back to government and health sites in September 2023, and on 7 May 2026 stopped showing the feature at all. If you were adding FAQ schema for those dropdowns, they are gone.

What remains is the label. FAQPage markup tells any parser which text on the page is a question and which is its answer, in a structure no layout can confuse. That matters for AEO, where answer engines lift short, direct answers, and for GEO, where assistants quote pages whose answers are easy to pick out.

So write the FAQ for readers first: real questions buyers ask, answered in a sentence or three. Then mark it up, because it costs a minute and makes those answers unambiguous. Google still asks one thing of all structured data: that it matches what the page shows.

HOW TO READ THE OUTPUT

What makes FAQ schema valid

The check turns green when the JSON parses and every question has its answer. An empty answer, or a question left blank in a pair you started, is named so you can fill or remove it.

Every piece of the block has one job, and the table shows each one. If a validator flags your FAQ markup, it is almost always one of these left out or nested in the wrong place.

A valid block is not a rich result. Google no longer shows FAQ rich results for any site, so judge the markup by whether it matches your page, not by the search result.

PROPERTYWHAT GOES IN ITNEEDED
@type: FAQPageSays the page holds questions and answersYes
mainEntityThe list of questionsYes, at least one
Question.nameThe question, as the page shows itYes, on every question
acceptedAnswerAn Answer for each questionYes, on every question
Answer.textThe full answer textYes, on every answer
HOW TO GET IT RIGHT

The FAQ markup mistakes we see most

  • Marking up questions the page doesn't show.

    Every question and answer in the schema must be visible on the page. Hidden FAQs written only for markup break Google's structured data rules.

  • Two FAQPage blocks on one page.

    A theme and a plugin can each print one. Keep one block with every question in it.

  • Answers cut to a teaser.

    Put the full answer in the markup, as the page shows it, not a line that tells people to read more.

  • Using FAQPage for a forum thread.

    Questions answered by many users belong to QAPage. FAQPage is for questions you answer yourself.

Two questions as the generator writes them:

FAQPAGE JSON-LD
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does Northwind work with Gmail?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Connect Gmail in Settings and every email to a contact is logged."
      }
    },
    {
      "@type": "Question",
      "name": "Can I import contacts from a spreadsheet?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Upload a CSV file and match its columns to contact fields."
      }
    }
  ]
}
</script>
USE CASES

Where FAQ markup still earns its place.

  • A pricing page with common objections: label the answers about trials, contracts and refunds.
  • A support or help page: mark up the questions customers send most.
  • A product page with a short FAQ: add the block beside your Product schema.
  • An article that ends in questions: mark up the closing FAQ so its answers are easy to lift.
  • Cleaning up after a plugin: replace a duplicated or broken FAQ block with one correct one.
GO FURTHER WITH ZIVOOO

Better FAQs come from what buyers ask AI.

Zivooo tracks the questions buyers ask ChatGPT, Gemini and Google about your market every week, plans articles for the ones where you are missing, and writes each with its FAQ section and FAQPage schema in place. $10 a domain a month after 7 days free, no card.

  • Buyer questions tracked weekly on three AI engines
  • Articles planned for the questions you miss
  • FAQ sections and their schema written for you
  • Schema checked on every page of your site
FREE GENERATOR VS OTHER OPTIONS

This FAQ schema generator vs a plugin block

WordPress block editors and SEO plugins can print FAQ schema from an FAQ block, which keeps the markup and the visible text in step automatically; if you use one, you may not need a generator. A generator suits a hand built page, a page builder without FAQ blocks, or a fix to a plugin's broken output. Many FAQ generators still promise the old Google dropdowns. This one says plainly that Google stopped showing them, and keeps the markup honest to what the page shows.

FAQ

FAQ schema, answered.

Is FAQ schema deprecated?

The rich result is. Google stopped showing FAQ rich results in Search on 7 May 2026, after limiting them to government and health sites in 2023. FAQPage is still a valid schema.org type that any engine can read.

Is FAQ schema still worth adding?

If the page has a real FAQ, yes: it takes a minute and marks your answers clearly for answer engines and assistants. If the page has no FAQ, don't add one just for the markup.

How do I add FAQ schema in WordPress?

Use your SEO plugin's FAQ block, which writes the schema for you, or paste the JSON from this generator into the plugin's custom schema field for that page.

Do the questions have to be visible on the page?

Yes. Google's rules for all structured data say the markup must describe what the page shows. Hidden questions risk a manual action and mislead every engine that reads them.

How many questions can I add?

As many as the page shows. Schema.org sets no cap; this generator takes up to 30, which covers any FAQ a reader would scroll through.

Can I use HTML in the answers?

Google allowed a few HTML tags in answers when it showed FAQ results. This generator keeps answers as plain text, which every parser reads the same way.

What's the difference between FAQPage and QAPage?

FAQPage is for questions you answer yourself. QAPage is for one question with answers from many people, like a forum thread.

Answer the questions AI is asked.

Your keys, your costs, $10 a domain. 7 days free, no card.

Start free, no card