FAQ schema generator

Add your questions and answers and this tool writes the FAQPage JSON-LD for you. It is the cleanest way to tell search engines and AI tools exactly which questions a page answers, and what the answers are.

Your questions

FAQPage JSON-LD · 2 questions

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you offer free consultations?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. The first 20-minute call is free, by phone or video, and there is no obligation."
      }
    },
    {
      "@type": "Question",
      "name": "What areas do you serve?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We work across Calgary and nearby towns, including Airdrie, Cochrane and Okotoks."
      }
    }
  ]
}
</script>

Only complete pairs are included. The same questions and answers must be visible on the page.

Want me to write the FAQ your customers are actually asking?

Tell me your website and I’ll suggest five questions your page should answer, with draft answers. Free.

No newsletter. Just what you asked for, from me. Privacy

How to use it

  1. Write each question the way a customer would ask it.

  2. Answer it directly in the first sentence, then add detail.

  3. Make sure the same questions and answers are visible on the page.

  4. Copy the JSON-LD into the page and check it with the Schema Markup Validator at validator.schema.org.

Why it matters

Google limited FAQ rich results to a small set of government and health sites in 2023, and in May 2026 it stopped showing them in Search altogether. So FAQ markup won’t add expandable questions under your listing. Google says it still reads the markup to understand pages, and FAQPage remains valid schema.org.

FAQ content is still one of the most useful things a page can have. Clear question-and-answer pairs are easy for AI search tools to quote, and the markup removes any doubt about where a question ends and its answer begins.

The rule that matters: the questions and answers in the code must be visible on the page. Hidden FAQ markup is against Google’s guidelines and helps no one.

Good to know

  • Answer first

    The first sentence of each answer should stand on its own. That is the part most likely to be quoted.

  • Real questions only

    Use questions customers actually ask you. Your inbox and your phone are the best keyword research.

  • Plain text is safest

    Keep answers as plain text. Links are allowed, but simple answers are easier for every tool to read.

FAQ

FAQ schema generator: questions

  1. Google stopped showing FAQ rich results in May 2026, so it won’t change how your listing looks. The markup is still valid schema.org and still describes your answers clearly for machines, so I keep using it where a page genuinely has FAQs.

  2. As many as the page genuinely needs, usually three to eight. Long lists of thin questions are worse than a few good ones.

  3. Only on pages that show a list of questions and answers to visitors. Don’t add it to pages without a visible FAQ.

  4. No. FAQPage is for questions you answer yourself. QAPage is for a single question with answers from users, like a forum thread.

Keep reading

Let’s begin

Let’s build something you’re proud to share.

Let’s Talk