Schema.org FAQ Markup Generator

JSON-LD RICH SNIPPETS SEO SCHEMA.ORG STRUCTURED DATA
Share:
By Checked against sources by , Founder & Architect, RECATOOLS Published Updated Last reviewed

Generate valid schema.org FAQPage markup as JSON-LD, escaped so it is safe to paste into a page. Add Q/A pairs; copy the script tag. Google no longer shows FAQ rich results (since 7 May 2026).

RT-SEO-015 · SEO & Marketing
Your browser is too old for this tool’s interactive features. Please update to Safari 13.1, Chrome or Edge 80, Firefox 74 or newer.

Schema.org FAQ Markup Generator

<script> block to paste in <head> 
/* Schema will appear here after you add Q/A pairs */
Raw JSON-LD 
/* Add at least one Q/A pair with both question + answer filled in */
Add Q/A pairs above to generate JSON-LD
Advertisement
After results · AD-W1Responsive · Post-tool — peak engagement

How to use the Schema.org FAQ Markup Generator

Add your Q/A pairs

Click "+ Add Q/A pair" for each question and type the question and its full answer. Write them as a reader would ask and want answered; the markup should describe the FAQ that is really on the page.

Mirror the FAQ that is on the page

Google's structured-data rule is "Don't mark up content that is not visible to readers of the page." Build the visible FAQ section first, then copy the same questions and answers here, word for word.

Copy the <script> block

The <script type="application/ld+json"> block can go in the <head> or the <body>. The tool writes every < as \u003c, so an answer that mentions </script> cannot close the block early — JSON parsers read the escape back as the same character.

Validate the markup

Paste the block or the page URL into the Schema Markup Validator at validator.schema.org to check the markup. Note that Google no longer shows FAQ rich results in its search results (since 7 May 2026), so there is no Google preview to wait for.

Advertisement
After how-to · AD-W2Responsive

Schema.org FAQ markup — the free CTR boost most pages skip

FAQPage is a schema.org type — in schema.org's words, "a WebPage presenting one or more 'Frequently asked questions'". Marked up as JSON-LD, each question becomes a Question with an acceptedAnswer, in a form software can read without parsing your HTML. This tool builds that markup from your questions and answers.

Google no longer shows FAQ rich results

For years the reason most people added FAQ markup was Google's FAQ rich result: expandable questions under a search result. In 2023 Google limited it to well-known, authoritative government and health websites. Then its Search Central changelog, on 8 May 2026, announced that the feature "will no longer appear in Google Search starting May 7, 2026", and in June it removed the documentation, because the FAQ rich result "is no longer shown in Google Search results". This page used to promise the rich result and quote click-through gains for it; it no longer does. The markup is still valid schema.org, and still describes your page to software that reads structured data — but it will not change how your Google result looks.

FAQ markup still describes your page. Since 7 May 2026 it no longer changes how that page looks in Google.

The escaping bug we fixed

JSON-LD sits inside a <script> element, and a browser ends that element at the first </script it meets — even inside a JSON string. The old generator wrote plain JSON.stringify() output, which does not escape <, so an answer explaining where to paste "</script>" broke the block: the rest of the JSON landed on the page as text. Since 30 September 2026 every < is written as \u003c. RFC 8259, the JSON standard, says "any character may be escaped", so the data reads back unchanged.

Rules that still apply

Google's general structured-data guidelines still govern any markup on a page Google crawls: mark up only content that is visible to readers, keep it up to date, and don't mark up misleading content. Google recommends JSON-LD over Microdata and RDFa where a site can use it, as the easiest to implement and maintain.

FAQPage in schema.org, Google's 7 May 2026 removal, and \u003c

01

schema.org defines FAQPage as "a WebPage presenting one or more 'Frequently asked questions'"; each item is a Question with an acceptedAnswer.

02

In 2023 Google limited its FAQ rich result to well-known, authoritative government and health websites.

03

Google's changelog of 8 May 2026 announced that the FAQ rich result "will no longer appear in Google Search starting May 7, 2026"; the documentation was removed in June.

04

The markup is still valid schema.org after Google's change — what ended is Google's special display of it.

05

Google's structured-data guidelines: "Don't mark up content that is not visible to readers of the page."

06

Google recommends JSON-LD, where a site can use it, as the easiest structured-data format to implement and maintain.

07

A browser closes a <script> element at the first </script, even inside a JSON string — which is how an unescaped answer can break a page.

08

RFC 8259 says "any character may be escaped" in a JSON string, so \u003c reads back as < exactly.

09

The Schema Markup Validator at validator.schema.org checks schema.org markup of any type, independent of any search engine's features.

10

This tool keeps your questions in your browser's local storage, so a draft survives a reload on the same device — and nothing is uploaded.

Frequently Asked Questions

  • Not for a Google rich result: Google stopped showing FAQ rich results entirely on 7 May 2026. Add it if you want your page's questions and answers available as structured data to software that reads schema.org — it is valid markup and costs one script block — but don't expect it to change your Google listing.
  • Google does not describe structured data as a ranking factor; its documentation presents it as a way to describe a page and, for supported types, to become eligible for rich results. FAQ is no longer one of those types.
  • In the <head> or the <body> of the page that shows the same questions and answers. JSON-LD is read from either place.
  • As many as the visible FAQ on the page has — no more. The markup describes what is on the page; questions that are not visible break Google's structured-data guidelines.
  • The tool writes answers as plain text in the JSON. schema.org's text property is text; if you include tags, they are carried as characters, and the tool's escaping keeps them from breaking the script block.
  • Only where the same questions and answers are visible on each of those pages. The markup must describe the page it is on.
  • It won't: Google stopped showing FAQ rich results on 7 May 2026, and the feature's Search Console reports and documentation went with it.
  • schema.org defines many types — HowTo, Article, Product, BreadcrumbList and more — and a page can carry several. Which of them produce a special display in a search engine changes over time; check the engine's current documentation before relying on one.

  • No. All data lives in your browser's localStorage and persists across sessions on the same device + browser. Open DevTools → Network and confirm zero outbound requests. Q/A content stays on your device. Safe for confidential or unpublished content planning.

  • The Schema Markup Validator (validator.schema.org) checks any schema.org markup. For types Google still supports, Google's Rich Results Test and Search Console report what Google makes of them.

Method & sources

What this tool implements

  • Until this review JSON.stringify() output went straight into the <script> block, so an answer containing </script> ended it early. RFC 8259 §7: any character may be escaped, so \u003c reads back unchanged.
  • Google Search Central changelog, 8 May 2026: the FAQ rich result "will no longer appear in Google Search starting May 7, 2026"; documentation removed in June. The page had promised rich snippets and quoted 20-50% CTR gains; it now says so plainly.
  • Google's structured-data policy still applies to any markup: "Don't mark up content that is not visible to readers of the page." Google recommends JSON-LD.

Sources

Advertisement
Pre-footer · AD-W3 728 × 90