Free tool for FAQ sections

FAQ Schema Generator for any page

Type your questions and answers and this generator writes the FAQPage JSON-LD and a matching FAQ block in HTML. Paste both into your page. It runs in your browser, so nothing you type leaves it.

Your questions and answers

  1. 01
  2. 02

Answers can use p, br, ul, ol, li, a, b, strong, i, em and h1 to h6. Everything runs in your browser.

0 questions in the markup. Paste this script tag in the page's head or body.

Add at least one question with an answer to see the code.

What the generator does

  1. 01FAQPage JSON-LDA schema.org FAQPage with a Question and Answer for each pair, in a script tag ready to paste.
  2. 02Matching visible HTMLA details and summary block with the same questions and answers, so readers see what the markup says.
  3. 03Clean answer HTMLKeeps headings, paragraphs, line breaks, lists, links, bold and italic. Strips every other tag and attribute.
  4. 04Escaped outputCharacters that could break the script tag or the page are escaped.
  5. 05Warnings as you typeFlags a question without an answer, repeated questions and answers over 120 words.
  6. 06Edit existing markupPaste FAQ JSON-LD from any page to load it back in and change it.

Everything runs in your browser. Nothing you type is sent to Draftly or stored.

Does Google still show FAQ rich results?

No. Google stopped showing FAQ rich results on May 7, 2026, and removed the FAQ documentation in June. Since 2023 they had only appeared for well-known government and health sites.

So FAQ markup won't put expandable questions under your search result. If someone sells it to you that way, they're out of date.

Source: Google Search Central documentation changelog

Why add FAQ markup anyway

FAQPage is still a valid schema.org type. Any crawler that reads JSON-LD can pick out your questions and answers without guessing from the layout, and that includes the bots behind AI search tools.

No search engine or AI company has promised to rank or cite a page more because of it. Think of the markup as a clear label on content that has to be good on its own.

The part that does the work is the FAQ itself. Real questions your customers ask, each with a short, direct answer, are easy for a reader to scan and easy for an AI assistant to quote.

How to add FAQ schema to a page

Add your questions and answers above. Copy the visible HTML into the page where you want the FAQ to show.

Copy the JSON-LD script tag into the same page, in the head or anywhere in the body. In WordPress, a Custom HTML block works for both.

Keep the two in sync. Google's structured data guidelines say markup should only describe content readers can see on the page, and that applies to every schema type.

Then check the page with the Schema Markup Validator at validator.schema.org.

Sources: Google's general structured data guidelines, Schema Markup Validator

Draftly writes the post and its FAQ

  • Draftly writes blog posts in your brand's voice. With the FAQ setting on (it is by default), a post's FAQ uses questions readers actually ask, answered from the post itself.
  • Every FAQ answer is checked for length. Answers over three sentences get flagged before you publish.
  • Drop the finished FAQ into this generator for the schema, and publish the post to WordPress, Shopify, Webflow, Ghost, Squarespace or HubSpot.
Generate Free PostYour first post is free. No credit card.

Draftly is for US businesses and writes blog posts only. See plans and prices.

More free tools

Frequently asked questions

Is the FAQ schema generator free?

Yes, with no sign-up. It runs in your browser, so nothing you type is sent to Draftly or stored.

Does FAQ schema still work in Google?

Google stopped showing FAQ rich results on May 7, 2026. The markup is still valid schema.org, and other crawlers, including AI search bots, can read it.

Where do I put FAQ schema on a page?

Paste the script tag into the page's HTML, in the head or the body. Put the visible FAQ where readers will see it. Both should have the same questions and answers.

Can I use HTML in FAQ answers?

A little. The generator keeps headings, paragraphs, line breaks, lists, links, bold and italic, the tags Google's FAQ documentation allowed. Other tags are removed and their text kept. Questions are plain text.

How many questions should an FAQ have?

Three to eight is typical. Use questions customers really ask you, and answer each one in one to three sentences.

Can I add FAQ schema to every page?

Only to pages with a real FAQ that readers can see. Questions invented to repeat a keyword don't help the reader, and they won't help the page.

Updated October 2026 by at Draftly.

Keep reading