Skip to content
Viken Patel
Get an Audit

FAQ Schema Generator

Paste your FAQ content, get valid FAQPage JSON-LD, ready to drop into your site. Structured data is one of the clearest signals AI assistants use to understand and cite a page. This makes sure yours is correct.

Your questions

  1. 01
  2. 02

Generated JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does the audit take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "10 working days from kickoff to delivered report."
      }
    }
  ]
}
</script>

1 question included. Paste this into the <head> of the page the questions appear on. The answers must also be visible on that page, or the markup is invalid.

Everything happens in your browser. Nothing you type is sent anywhere, stored, or logged. There is no server involved in this page beyond serving it to you.

How it works

How to use this FAQ schema generator

  1. Copy each question and answer exactly as it appears on your page. The markup has to match what visitors can see.
  2. Add a pair for every question. The FAQPage JSON-LD updates as you type, and incomplete pairs are left out.
  3. Copy the output and add it to that page, using one of the methods below. Then test it before you publish.

Definition

What is FAQ schema?

FAQ schema is FAQPage structured data, written in JSON-LD. It marks a set of questions and their answers so search engines and AI assistants can read them as data rather than guessing at plain page text.

The markup does not change what a visitor sees. It sits in the page source and gives a machine a clean, labelled question-and-answer pair. That is the whole job.

Is it still worth it

Is FAQ schema still worth adding?

Yes, but not for the reason most tools still give. In 2023 Google limited FAQ rich results to well-known, authoritative government and health sites. For everyone else, those expandable snippets in search results are gone.

The value moved rather than vanished. Answer engines read structured data to retrieve and cite a page, and a marked-up question and answer is easier to quote than the same text buried in an accordion. This is the core of answer engine optimization.

So treat FAQ schema as an AI-search signal now, not a Google rich-result trick. If you want to know which of your pages assistants already cite and which they skip, that is what an AI visibility audit measures.

Implementation

How to add FAQ schema to your site

  1. Generate the JSON-LD above from the questions and answers already published on the page.
  2. Paste it into the <head> of that page, inside a <script type="application/ld+json"> tag. Google Tag Manager works too if you cannot edit the template directly.
  3. Use one FAQPage block per page, and keep the markup in sync with the visible text. If you edit an answer on the page, edit it in the schema.

By platform

Adding FAQ schema in WordPress, Webflow, Shopify and Google Tag Manager

WordPress. Yoast SEO and Rank Math both include an FAQ block that outputs FAQPage schema from the questions you write in it. If you already have the questions on the page, paste the generated code into the page using a header-code plugin instead, so you do not end up with two FAQ blocks.

Webflow. Open the page settings and paste the code into the custom code field for the head. On CMS template pages you can build the JSON-LD from collection fields, so each item carries its own questions.

Shopify. Add the code to the relevant template or section in your theme, or to a product or page template if the FAQ is specific to it. Check your theme or apps first, because some already output FAQ markup.

Google Tag Manager. A Custom HTML tag works, and Google can read JSON-LD added this way. Many AI crawlers do not run JavaScript, though, so markup injected by a tag may be invisible to them. Put it in the page source where you can. Why that matters is covered in technical SEO for AI crawlers.

Example

FAQ schema example

A minimal, valid FAQPage with a single question. Each extra question is another object in the mainEntity array.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does the audit take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "10 working days from kickoff to delivered report."
      }
    }
  ]
}
</script>

Validation

How to test your FAQ schema

Before you ship it, confirm the markup parses cleanly with one of these:

Google’s own FAQPage documentation is the reference for the required fields and the current eligibility rules.

Mistakes

Common FAQ schema mistakes

  • Marking up content that is not on the page. Every question and answer in the markup must be visible to visitors.
  • Two FAQPage blocks on one page. A plugin block plus pasted code is the usual cause. Keep one.
  • Letting the markup drift. An answer edited on the page but not in the schema leaves two versions of the truth.
  • Using it for sales copy. Questions written as adverts are not what the type is for, and they are rarely quoted.
  • Copying one FAQ across the site. Identical blocks on many pages add nothing and dilute the pages that matter.
  • Expecting the old rich result. For most sites Google no longer shows it. Judge the markup on clarity, not on a snippet.

FAQ

Common questions about FAQ schema

What is FAQ schema?
FAQ schema is FAQPage structured data written in JSON-LD. It marks a set of questions and their answers so search engines and AI assistants can read them as data, not just page text.
Does FAQ schema still show rich results in Google?
For most sites, no. Since 2023 Google has shown FAQ rich results only for well-known, authoritative government and health websites. For everyone else the snippet no longer appears, though the markup is still worth adding for AI answer engines.
Does FAQ schema help with AI search?
It helps, but it is not a switch. Structured data makes a question and answer unambiguous to any system that parses it, and a clean, visible answer is easier for ChatGPT, Perplexity or Google AI Overviews to quote. The visible text does most of the work. The markup removes doubt about what it is.
Where do I put the FAQ schema code?
Paste it into the head of the page the questions appear on, inside a script tag with type application/ld+json. The body works too, but the head is conventional. Use one FAQPage block per page, and put it in the server-rendered HTML so crawlers that do not run JavaScript still see it.
Do the questions have to be visible on the page?
Yes. The questions and answers in the markup must match content a visitor can actually see on the page. Marking up hidden, missing or invented content breaks Google's guidelines and can get the page flagged.
How do I test that my FAQ schema is valid?
Run the page through Google's Rich Results Test or the Schema.org validator. Both parse the markup and report errors and warnings before you ship it.
Can I use HTML or links inside FAQ schema answers?
Yes, a limited set. Google's FAQPage documentation allows headings, paragraphs, line breaks, lists, links, and bold or italic tags inside answer text. Keep answers mostly plain text so every parser reads them the same way.
Can I add FAQ schema to every page on my site?
Only to pages that genuinely publish a set of questions and answers. Repeating the same FAQ block across many pages adds nothing and can look like spam. Each page's questions should be specific to that page's topic.
Does FAQ schema improve rankings?
Not directly. Structured data is not a ranking factor on its own. It helps search engines and AI assistants understand the page, which supports how the page is shown and quoted, but the content still has to earn the position.
Is JSON-LD better than microdata for FAQ schema?
For most sites, yes. JSON-LD sits in one script block, separate from your HTML, so it is easier to add, update, and validate. Google supports both formats and recommends JSON-LD.
What is the difference between FAQ and QA schema?
FAQPage is for a page where you publish the questions and their single correct answer. QAPage is for a page where users post a question and others submit competing answers, like a forum thread.

Go deeper

Structured data is one signal, not the whole job

Valid FAQ schema helps an answer engine read a page it can already retrieve. It will not rescue a page nobody can find. The structured data section of the SEO in the AI era guide covers what AI systems actually read, and where entity signals matter more than markup.

For writing the questions themselves, see optimizing FAQs for AI search. For the other types worth adding, see schema markup for AI, and if markup has not changed anything for you, read why schema isn’t helping.