Skip to content
Bold PilotBold Pilot
Get started

FAQ Schema Generator

Questions in, valid FAQPage JSON-LD out. Free, no sign-up.

Start from a page that already has the FAQ

1
2

Page URL (optional, for the @id)

FAQPage JSON-LD · 1 question

Download
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Is the tool free?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Every check runs without an account or a card."
      }
    }
  ]
}
</script>

Paste it anywhere in the page’s HTML — head or body — on the same page the questions are visible on. Then run it through the schema markup validator.

1 question, valid FAQPage. The markup parses, every question has an answer, and the structure matches what Google and Bing document. Remember: the same questions and answers must be visible on the page.

Worth knowing. Since August 2023 Google shows FAQ rich results only for well-known government and health sites. The markup still appears in Bing, and it hands AI answer engines the most quotable unit there is: a question with its answer.

Markup is the easy half.

Bold Pilot checks every keyword against its live results page, writes the article, and publishes it — week after week.

Try Bold Pilot

Structured data guide

FAQ schema in 2026: what it still does, what it stopped doing, and how to write it right

FAQ schema is a block of JSON-LD that tells search engines and answer engines “this page contains these questions, and these are the answers”. The generator above writes it from the pairs you type, or pulls them out of a page that already has the FAQ, and checks the result against what Google and Bing document.

What the markup looks like

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Can I cancel any time?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Cancel from Settings and the plan ends at the period's close."
      }
    }
  ]
}
</script>

One FAQPage per page, one Question per entry, each with exactly one acceptedAnswer. The answer may carry a little HTML — links, lists, bold, paragraphs, line breaks — and the generator strips anything else, attributes included.

The 2023 change, plainly

In August 2023 Google stopped showing FAQ rich results — the expandable questions under a listing — for most sites. They now appear only for well-known, authoritative government and health pages. If you add this markup expecting the accordion in Google results, you will not get it, and no generator changes that.

Three things the markup still does:

  • Bing shows it. Bing’s FAQ rich results were not withdrawn, and Bing is what Copilot reads.
  • Answer engines quote it. A question with its answer is the most liftable unit of text on the web. ChatGPT, Perplexity and Google’s AI features all favour pages that answer a specific question in one clean block, and structured question–answer pairs are that block with a label on it.
  • It disciplines the page. Writing the pairs forces short, direct answers, which is what the visible FAQ needed anyway.

The rules that still apply

  1. The questions and answers must be visible on the page. Markup for text a visitor cannot see is the one thing that reliably earns a manual action.
  2. One answer per question, written by the site. Pages where visitors post answers are QAPage, a different type.
  3. No advertising inside answers, and no answers that are mostly a link.
  4. Don’t repeat the same FAQ across many pages. Put it where the questions are answered, once.
  5. Keep the question a question. “Pricing” is a heading; “How much does it cost?” is something an engine can match against what people ask.

Importing from an existing page

Paste the URL of a page that already has an FAQ and the generator reads it two ways. If the page carries a FAQPage block, that block is taken as the page’s own statement of its questions. If not, headings that end in a question mark — in sections, accordions or definition lists — become questions, and the text up to the next heading becomes the answer. Either way the pairs land in the form, editable, before anything is generated.

Where to put it

  • Any HTML page: paste the script tag into the head or the body of that page. Position does not matter.
  • WordPress: a “custom HTML” block at the end of the page, or the schema field in Rank Math or Yoast.
  • Next.js, Astro, Nuxt: render the JSON into a script tag from the page component, the way this site does for its own pages.
  • Shopify, Webflow, Squarespace: the page’s custom code or embed field.

Then confirm with the schema markup validator, which checks the block against Google’s requirements rather than schema.org’s vocabulary. For the other types — Article, Product, How-to, Organization — the schema markup generator covers eight.

Frequently asked

Does FAQ schema help rankings?

Not directly; structured data is not a ranking factor. It helps engines understand and display the page, and it makes the page easier to quote. Rankings come from the page.

How many questions should a page have?

As many as it genuinely answers. Three good pairs beat fifteen thin ones; the generator warns on answers under about 40 characters for that reason.

Can the answers contain links?

Yes — <a href> is allowed, along with lists, bold, italics, paragraphs and line breaks. Anything else is stripped.

Microdata or JSON-LD?

JSON-LD. Google recommends it, it lives in one block instead of being woven through the HTML, and every generator and validator handles it.