FAQ Schema Generator

Free, no sign-up: add questions and answers by hand, paste them as a list or import them from your page by URL — get FAQPage markup in JSON-LD or Microdata with a visible FAQ block, check it with our schema validator and copy it. Everything is built in your browser. Important: Google has not shown FAQ rich results since 7 May 2026 — the markup is still valid schema.org, but there will be no FAQ snippets in Google.

Since 7 May 2026 Google shows FAQ rich results for no site at all (from September 2023 only government and health sites had them), and in June 2026 it removed the documentation too. Why add the markup then: it is valid schema.org that other systems and parsers read, and the visible FAQ block itself still helps people and AI search find a direct answer. Do not expect more clicks from Google because of it.

Separate pairs with a blank line: the first line is the question, the rest is the answer. “Q:/A:” prefixes are removed automatically.

We take existing FAQPage markup if there is any; otherwise headings and expandable blocks ending in “?” and the text below them (up to 30 questions). JavaScript is not executed.

Page URL (optional)

Language (inLanguage)

Format

Your code

Put the JSON-LD in <head> or at the end of <body>. Questions and answers must be visible on the page itself — markup describes visible text, it does not replace it; use “visible HTML block” (expandable <details>) for that. With Microdata, the markup and the visible block are the same thing. Schema validator by URL

Key facts

Price: Free
Sign-up: Not required
Processing: In your browser — nothing is sent to our server
Input: Questions and answers typed or pasted as a list; import from a URL (server-side, SSRF-protected); code checks run on our server with our schema validator
Limits: Generation is unlimited; URL import 10 a minute and 30 a day without an account; validation 30 a minute, code up to 100 KB
Output: FAQPage code in JSON-LD or Microdata, a visible HTML FAQ block (<details>), warnings about duplicates and unsupported tags, and validator results
Last updated: 2026-10-13

Alternatives

Other tools for the same job, and what each one does well:

TechnicalSEO.com Schema Markup Generator — Merkle’s JSON-LD generator for many markup types, FAQ included, with links to test in Google’s tools.
Schema Markup Validator — The official schema.org validator: checks any markup against the vocabulary, without Google’s rich result rules.

When to choose this tool: When you need to build an FAQ quickly from an existing page or list, get a visible HTML block along with the markup and validate the code at once — with an honest note that Google no longer shows FAQ snippets.

Descriptions checked against each tool's own site in October 2026.

Free FAQ Schema Generator

FAQPage markup describes a question-and-answer block in schema.org terms: each Question with its text and an acceptedAnswer. The generator builds it from your questions — typed in, pasted as a list or imported from a page by URL — as JSON-LD (the recommended format) or as Microdata with a visible HTML block, flags duplicates, empty answers and unsupported tags, and runs the code through our schema validator with one click. Google has not shown FAQ rich results since 7 May 2026, and the page says so up front to avoid false expectations.

JSON-LD or Microdata with a visible <details> block

Import questions from a URL (existing markup or “?” headings)

Paste a list: question/answer pairs separated by blank lines

One-click check with our schema validator

Built in your browser, no sign-up or limits

How to Use

Add questions and answers — by hand, as a list or by URL import
Pick JSON-LD or Microdata; optionally set the page URL and language
Validate, copy the code and place the visible FAQ block on the page

FAQ

No. From September 2023 they were shown only for well-known government and health sites, and since 7 May 2026 for no one; in June 2026 Google also removed the FAQ markup documentation. The markup is not an error — it is valid schema.org.

It ties each question to its answer explicitly for systems that read structured data, and costs almost nothing. But the real value is the visible FAQ block: it answers people’s questions and gives AI search short, quotable answers. If time is short, write good answers first — the markup is secondary.

JSON-LD is easier to maintain — it is a separate script and leaves your layout alone — and it is the format Google recommends. Microdata is handy if you are building the FAQ block anyway, because markup and visible text then match automatically. Do not use both formats for the same questions.

TechnicalSEO.com’s Schema Markup Generator (by Merkle) covers many markup types, and in WordPress Yoast and Rank Math have FAQ blocks. Ours is handy when you want to turn an existing page or list into an FAQ quickly, get a visible HTML block too and validate the code straight away — without signing up.

What FAQPage markup looks like

A minimal valid JSON-LD example: an FAQPage with a mainEntity list of questions:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How much is shipping?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Free on orders over €50, otherwise €5."
    }
  }]
}
</script>

Each question has a name (the question) and an acceptedAnswer.text (the answer). Simple HTML is fine in answers: paragraphs, lists, links, bold and italics.

Google FAQ rich results: what changed

When	What happened
2019–2023	Any site with valid markup could get expandable questions under its result
September 2023	Limited to well-known government and health sites
7 May 2026	FAQ rich results removed from Search entirely
June 2026	Google removed the FAQ markup documentation

The markup did not become an error: it is valid schema.org, Search Console does not flag it, and other systems that read structured data can still use it. Just do not count on extra clicks from Google.

How to write a good FAQ block

Real questions. Take them from support tickets, Google’s People Also Ask box and search suggestions.
A short direct answer in the first sentence, details after. Answers like that are easy for AI search to quote.
One question, one answer. Do not repeat the same thing in different words.
Visibility. Questions and answers must be on the page, not just in code. An expandable <details> block works — the generator gives you one ready-made.
No ads. An answer is not the place for promo copy; a link to the relevant page is fine.

Common mistakes

Two FAQPage blocks on one page (for example, a plugin and the theme) — keep one.
Markup with no visible text, or with text that differs from what is visible.
A trailing comma or “smart” quotes in the JSON — the schema validator shows the line and suggests a fix.
An FAQ where the site asks itself questions (“Why are we the best?”) — it helps neither people nor search.

Improve search rankings

SEO problems may be costing you traffic. Cascade link building will improve site visibility in search.

Learn about cascades

Try Also

Schema Markup Validator

Schema Generator