EthicalFusion

FAQ Schema Generator

Turn questions and answers into FAQ JSON-LD schema for rich results.

Was this tool helpful?

Thanks for the feedback!

FAQ Schema Generator converts questions and answers written in plain text into FAQPage structured data in JSON-LD. Instead of hand-writing nested JSON, you type each question with its answer underneath and the tool builds the markup for your page's FAQ section.

Input format

Write each question on its own line with the answer on the line or lines below it, and leave one blank line between question-and-answer pairs:

Do you deliver outside Bengaluru?
Yes, we ship across India.
Delivery takes 3-5 working days.

Can I pay by UPI?
Yes, all major UPI apps are accepted.

If an answer spans several lines, they are joined with spaces into one paragraph. A block with only one line, such as a question with no answer, is skipped without a warning, so compare the number of questions in the output with your list.

The generated markup

The example above becomes:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you deliver outside Bengaluru?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, we ship across India. Delivery takes 3-5 working days."
      }
    },
    {
      "@type": "Question",
      "name": "Can I pay by UPI?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, all major UPI apps are accepted."
      }
    }
  ]
}

Quotation marks inside your text are escaped for you. Place the output inside <script type="application/ld+json"> tags on the same page where the questions appear.

Will this give me FAQ rich results?

For most websites, probably not. In August 2023 Google limited FAQ rich results, the expandable questions under a search listing, to well-known, authoritative government and health websites. For everyone else the markup is still valid schema.org data that describes the page's questions and answers in a machine-readable way, but it no longer produces the dropdowns in Google's results. It's worth knowing before you spend hours adding FAQ schema across a site expecting a visible change.

Rules that still apply

  • Visible content only. Every question and answer in the markup must appear on the page for visitors.
  • Written by you. FAQPage is for questions answered by the site owner. Forums and pages where users post answers should use QAPage instead.
  • No advertising. Google's guidelines exclude FAQ content used purely for promotion.
  • Repeated FAQs. If the same questions appear on many pages, mark up only one instance.

Before publishing

Run the page through Google's Rich Results Test or validator.schema.org, and if you edit the JSON by hand, check it with the JSON Validator, since one missing comma breaks the whole block. For the article itself, the Article Schema Generator creates a separate block that can sit on the same page.

Frequently asked questions

Why don't my FAQs show as dropdowns in Google anymore?
Since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites. The markup remains valid, but most sites no longer get the dropdowns.
Why is one of my questions missing from the output?
Each block needs at least two lines, a question and an answer. A block with a single line is skipped, often because the answer was missing or a blank line split a pair.
Can an answer have more than one paragraph?
The generator joins all answer lines into one paragraph separated by spaces. Keep answers compact, or edit the text value in the JSON by hand.
Where should I add the FAQ JSON-LD?
On the same page as the visible questions, inside a script tag with type application/ld+json, in either the head or the body.
Can I use FAQ schema for product reviews or user questions?
No. FAQPage is for questions answered by the site owner. User-submitted questions and answers should use QAPage markup instead.

Related tools

Embed this tool on your site

Paste it into any blog or website. Free, with a credit link.