🔍 SEO · STRUCTURED DATA

FAQ Schema Generator

Turn the questions and answers on your page into valid FAQPage JSON-LD. Add, reorder and edit questions, check the allowed answer HTML, and copy a ready-to-paste <script> tag.

FAQPage JSON-LD · Answer HTML checks · Updated for Google's 2026 changes
Paste the code anywhere in the page's HTML — the <head> or the <body>.Marking up an article or blog post? Article Schema Generator →
Fill in the form — the JSON-LD and the checks update as you type.
DetailsSaved in this browser
Questions & answers
Page (optional)
Adds url and an @id so other markup can reference this FAQ page.
Preview & checks
    JSON-LD
    ◆ ABOUT THIS TOOL

    FAQPage Structured Data in 2026

    The markup is still valid and still read by search engines — but Google no longer turns it into a rich result.

    FAQPage structured data labels the questions and answers on a page so machines can understand them: each question is a Question with an acceptedAnswer. This generator writes that JSON-LD for you, escapes everything correctly and flags problems before you publish.

    Important: as of 7 May 2026, Google no longer shows FAQ rich results (the expandable questions under a search result) for any site. In 2023 they had already been limited to well-known government and health websites; Google has also announced that the FAQ report and Rich Results Test support are being removed.

    So is FAQ markup still worth adding? Google says it continues to use FAQ structured data to understand pages, keeping it causes no problems, and other search engines and AI assistants can read it too. It's worth having on pages that genuinely are question-and-answer content — help centres, product support, policy pages.

    What it won't do any more is add extra space to your Google listing. Don't add FAQ blocks to pages just for the markup; spend that effort on types that still produce rich results, such as Product, Article and Local Business.

    ✓ RULES

    FAQPage Content Rules

    From Google's FAQPage guidelines — they still describe what valid markup looks like.

    👁

    Visible on the page

    Every question and the full answer must be visible to users on the page itself. Don't mark up content that's hidden or doesn't exist.

    1:1

    One answer per question

    FAQPage is for questions with a single answer written by the site. User-submitted answers (forums, support communities) are QAPage instead.

    </>

    Allowed answer HTML

    <h1>–<h6>, <br>, <ol>, <ul>, <li>, <a>, <p>, <div>, <b>, <strong>, <i>, <em>. Other tags are flagged.

    🚫

    No advertising

    Questions and answers must not be promotional, and the same question shouldn't be marked up on many pages of your site.

    ◐ THREE STEPS

    How to Use the FAQ Schema Generator

    Get your result in under ten seconds.

    1

    Add your questions

    Type each question and its answer exactly as they appear on the page. Use ↑ ↓ to reorder.

    2

    Check the list

    Fix any errors or warnings — missing answers, duplicate questions or HTML tags that aren't allowed.

    3

    Copy the script tag

    Paste the <script type="application/ld+json"> block into the page, then test it with the Schema.org validator.

    ✓ FEATURES

    Why Use the FAQ Schema Generator on Developers Web Tools

    Fast, accurate and private — built for developers.

    ✓

    Always valid JSON

    Quotes, line breaks and special characters are escaped for you — no broken JSON.

    🛡

    Safe script tag

    Text like </script> inside an answer is escaped so it can't break your page.

    </>

    HTML checks

    Answer HTML is checked against the tags Google's guidelines allow.

    ↕

    Easy editing

    Add, remove and reorder questions; your work is saved in this browser.

    📅

    Up to date

    Reflects Google's May 2026 retirement of FAQ rich results — no false promises.

    🔒

    Private

    Everything runs in your browser. Nothing is uploaded.

    FAQ

    Frequently Asked Questions

    No. Google stopped showing FAQ rich results for all sites on 7 May 2026, after limiting them to authoritative government and health sites in August 2023. The FAQPage markup remains valid schema.org vocabulary, and Google says it still uses it to understand pages.

    There's no need. Google has said that leaving it causes no problems. Remove it only if the FAQ section is no longer on the page, or if it was filler content that should go anyway.

    Yes, a limited set: headings, <p>, <br>, lists, links, <div> and bold/italic tags. The generator warns about anything else. Questions should be plain text.

    Anywhere in the page's HTML — inside <head> or <body>. Use one FAQPage block per page containing all of its questions.

    Use FAQPage when the site itself provides the single answer to each question. Use QAPage for pages where users ask a question and other users submit answers, such as a forum thread.

    Paste the code into the Schema.org Validator (validator.schema.org) to check the structure. Google's Rich Results Test no longer reports FAQ results after its June 2026 change.

    Only in your own browser (localStorage), so you can come back to it. Press Reset to clear it.