Tool · AI Search

FAQ Schema Generator

Free FAQ schema generator. Add questions and answers, get FAQPage JSON-LD and matching visible HTML, with checks for empty fields and HTML. Updated for Google's May 2026 change.

Free, no signup Updated November 11, 2026

An FAQ schema generator turns the questions and answers on a page into FAQPage JSON-LD, the Schema.org markup that labels each question and its answer. Add your questions below, or paste an existing FAQ as text, and copy the script tag. The tool also writes the visible HTML block, because markup should only describe questions that readers can see on the page.

Know this before you start: Google stopped showing FAQ rich results on 7 May 2026, so this markup will not add dropdowns under your Google listing. The section after the tool explains what changed and what FAQ markup can still do. Checked 11 November 2026.

1. Your questions and answers
Paste an existing FAQ as text

Put each question on its own line ending with a question mark, or start it with Q:. The lines under it become the answer. Blank lines between answers are fine.

2. Options
Adds an @id and url so the FAQ is tied to the page
Use JSON only for a CMS field that adds the script tag itself
Questions
0
Errors
0
Warnings
0
Size
0 KB
✍️ Add a question and an answer to build the markup.

    The HTML uses <details> so each answer opens on click. Google's old guidelines accepted answers behind an expandable section, as long as a reader could open them.

    What does FAQPage markup contain?

    Three Schema.org types nested inside each other. The required properties below are the ones Google listed in its former FAQ documentation (archived copy, June 2025); they match the FAQPage and Question definitions on schema.org.

    TypePropertyWhat goes in it
    FAQPagemainEntityA list of Question items. One FAQPage per page
    QuestionnameThe full text of the question, as it appears on the page
    QuestionacceptedAnswerOne Answer. FAQPage is for questions with a single answer written by the site; use QAPage for forums where users post answers
    AnswertextThe full answer. May contain simple HTML: Google displayed h1 to h6, br, ol, ul, li, a, p, div, b, strong, i and em, and ignored other tags

    A minimal block looks like this. The generator adds @id and url when you give it the page address, which ties the FAQ to the page if you also mark up the page as an Article or WebPage.

    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "FAQPage",
      "mainEntity": [{
        "@type": "Question",
        "name": "How long does onboarding take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most teams are live in two weeks."
        }
      }]
    }
    </script>

    What happened to FAQ rich results in Google?

    Google removed them in two steps, three years apart. Every date below is from Google's documentation changelog, read on 11 November 2026, unless the row says otherwise.

    WhenWhat changed
    September 2023The FAQ documentation was updated to say the feature is only shown for "well-known, authoritative government and health websites". Every other site lost FAQ dropdowns.
    7 May 2026FAQ rich results stopped appearing in Google Search, for all sites.
    8 May 2026Google added a deprecation notice to the FAQ documentation. Search Engine Journal quoted it: the FAQ search appearance, rich result report and Rich Results Test support would go in June 2026, and Search Console API support in August 2026.
    15 June 2026Google removed the FAQ rich result documentation, because "the FAQ rich result feature is no longer shown in Google Search results".

    Google gave no reason beyond the notice. The old address of the FAQ documentation now redirects to the changelog. Many FAQ schema generators still say the restriction to government and health sites is the current rule, or show a preview of FAQ dropdowns in Google. Both are out of date.

    Leaving existing FAQ markup in place is safe. Search Engine Journal's report notes Google has said unused structured data does not cause problems, and FAQPage is still a valid Schema.org type. Removing it is also safe. Neither changes rankings.

    Does FAQ schema still matter for AI answers?

    Less than many guides claim. Here is what is on the record, as of 11 November 2026:

    • Google says no special markup is needed. Its guide to optimizing for generative AI features in Search lists "overfocusing on structured data" as a mistake: structured data is not required for generative AI search, and there is no special schema.org markup to add. It still recommends structured data for the rich results that do exist.
    • Microsoft says schema helps its models understand content. Fabrice Canel of Bing said on stage at SMX Munich in March 2025 that schema markup helps Microsoft's LLMs understand content, as Search Engine Roundtable reported. That is about schema in general, for Bing and Copilot. He did not say FAQPage gets a page cited.
    • The other assistants have said nothing specific. We did not find a statement from OpenAI, Perplexity or Anthropic that their products read FAQPage markup or favor pages that have it.

    So treat FAQ markup as a clean label on content that has to earn its place anyway. What answer engines quote is the visible text: a question phrased the way a buyer asks it, and an answer that works on its own in the first sentence, with the number or the name in it. If those are on the page, the markup costs a few minutes and can only help machines parse them. If they are not, the markup will not make up for it. Our guides to generative engine optimization and answer engine optimization cover how answer engines choose sources.

    When should a B2B site use FAQ schema?

    PageUse FAQPage?Why
    Pricing page with a billing and plans FAQYesReal questions with one answer each, and the answers hold facts buyers ask assistants about
    Product or integration page with a short FAQYesSame reason. Keep each answer specific to that page
    Blog post or guide with an FAQ section at the endYes, if the section is visibleMark up only that section, not headings from the article
    Help center article that answers one questionNoOne question is not an FAQ page. Article markup fits better
    Community or forum threadNoUsers post several answers; that is what QAPage is for
    The same FAQ block repeated in every page footerOnce onlyGoogle's old guidelines asked for repeated FAQs to be marked up on one page for the whole site

    How do you add and test FAQ schema?

    1. Write the visible FAQ first. The markup must match what is on the page, word for word or close to it. The HTML box in the tool gives you a block to paste if the page has no FAQ yet.
    2. Paste the JSON-LD into the same page. In WordPress, most SEO plugins have a schema field, or use a block that accepts custom HTML. In Webflow, add it to the page's custom code (before the closing body tag). In Astro, Next.js and similar frameworks, render the script tag in the page component.
    3. Check it parses. Paste the code or the live URL into the Schema Markup Validator. Google's Rich Results Test no longer reports on FAQ markup.
    4. Keep it in sync. When you change an answer on the page, change the markup the same day. If your CMS builds both from one list of questions, as the tool does here, they cannot drift apart.

    FAQ markup is a small part of the technical setup that search engines and AI crawlers meet. Crawlable, fast HTML matters more; our technical SEO guide for SaaS covers the list. If you are setting up files for AI tools, the llms.txt generator builds the other one people ask about, with the same caveats on what it does and does not do.

    Where Growigami fits

    Our AI search and SEO service works on the part that moves AI answers: we track the questions your buyers ask assistants, see which answers name you or a competitor, and write the pages those answers draw on, FAQ sections included.

    Frequently asked

    Does Google still show FAQ rich results?

    No. Google's documentation changelog says FAQ rich results stopped appearing in Google Search on 7 May 2026, and Google removed the FAQ structured data documentation in June 2026. Since 2023 they had only been shown for well-known, authoritative government and health websites. FAQPage markup is still valid Schema.org and does not cause problems if you leave it in place.

    Is FAQ schema still worth adding in 2026?

    Only on pages that have real, visible questions and answers, and for reasons other than Google rich results. It describes the Q&A on the page in a format machines can read, and Microsoft's Fabrice Canel said in March 2025 that schema markup helps Microsoft's language models understand content. Google says structured data is not required for its generative AI features. If adding it takes minutes, add it. Do not expect a visible change in Google.

    Does FAQ schema help you get cited in ChatGPT or AI Overviews?

    There is no published evidence that FAQPage markup by itself gets a page cited. Google's AI optimization guide says there is no special schema.org markup needed for generative AI search. Microsoft has said schema helps the LLMs behind Copilot understand content, but has not said FAQPage changes which pages are cited. What answer engines quote is the visible text, so the questions and answers themselves matter more than the markup.

    What HTML is allowed in an FAQ schema answer?

    Google's former FAQ documentation said the Answer text may contain HTML and that Google Search displayed h1 to h6, br, ol, ul, li, a, p, div, b, strong, i and em, ignoring all other tags. With the rich result gone that list no longer controls any display, but it is still a sensible limit: keep answers to paragraphs, lists, links and bold or italic text.

    Where do I put FAQ schema JSON-LD on a page?

    Inside a script tag with type application/ld+json, in the head or the body of the same page that shows the questions and answers. Use one FAQPage block per page. If the same question appears on many pages of your site, mark it up on one page only, which is what Google's guidelines asked for when the feature existed.

    How do I test FAQ schema now that the Rich Results Test dropped it?

    Use the Schema Markup Validator at validator.schema.org. It checks that the JSON-LD parses and that FAQPage, Question and Answer are used with valid properties. Google removed FAQ support from the Rich Results Test and the Search Console report in June 2026, so those tools will not report on FAQ markup any more.

    Start with one process.

    We learn the business and build your first go-to-market process on us this month.