FAQ Schema Generator

Generate valid FAQPage JSON-LD for platforms and systems that support structured data. Google stopped displaying FAQ rich results in May 2026, so this markup should not be expected to create an enhanced Google search result.

Questions & Answers

0 questions

JSON-LD Output

// Add questions above to generate schema

When to Use FAQ Schema

FAQPage schema is a standards-based way to describe visible question-and-answer content on a page. It can be useful for platforms, internal systems, site search, and other tools that consume Schema.org structured data.

Google stopped displaying FAQ rich results in May 2026. Use this generator for valid markup and content clarity, not as a tactic for enhanced Google search listings.

Best Practices

  • Only use FAQ schema for pages that genuinely have FAQs — Google may penalize misuse.
  • Every question must have a corresponding answer visible on the page.
  • Keep answers concise and accurate — each answer should be complete on its own.
  • Don't use FAQ schema for advertising or promotional content.
  • Validate your markup with a structured data validator after deployment.
  • Use self-referencing canonical URLs on pages with FAQ schema.
  • Include only questions that are genuinely answered on the visible page.

Frequently Asked Questions About FAQ Schema

What is FAQ schema markup?

FAQ schema (FAQPage) is structured data you add to your webpage to describe question-and-answer content in a standards-based format. Google stopped displaying FAQ rich results in May 2026, so this markup should not be expected to create an enhanced Google search result.

How do I add FAQ schema to my website?

Add your questions and answers above, click "Copy JSON" to copy the JSON-LD code, then paste it into the <head> or <body> section of your HTML page. Alternatively, click "Copy HTML" to get the full <script> tag. Validate the syntax with Schema.org tools or another structured data validator used by your platform.

Does FAQ schema help with SEO?

FAQ schema can help describe Q&A content for systems that consume structured data, but it should not be treated as a Google rich-result or click-through-rate tactic. Google stopped showing FAQ rich results in May 2026. Use it only when the page contains genuine, visible questions and answers.

What is the difference between FAQPage and QAPage schema?

FAQPage is for a single page that lists questions and answers (like a FAQ page). QAPage is for user-generated Q&A content where users submit questions and answers (like a forum or community page). Use FAQPage for your own content, and QAPage for community-driven content.

Can I have multiple FAQ sections on one page?

Yes, you can have multiple FAQ sections on a single page. Combine all FAQ items into one JSON-LD block with a single FAQPage schema containing all questions and answers. Do not use separate FAQPage schemas for different sections — merge them into one.

Should I hide FAQ answers behind a click?

Google recommends that both questions and answers be visible to users on the page without clicking. While you can use accordion-style expand/collapse for a cleaner design, the content should be present in the HTML markup. Don't hide answers behind a separate page or require user interaction to reveal them.

How many questions should I include in FAQ schema?

There is no strict schema limit. Include high-quality questions that address genuine user needs, and make sure each answer is visible on the page and complete on its own.

FAQ Schema Examples: Valid vs. Broken Markup

Use these examples to understand what clean FAQPage JSON-LD looks like and what common validation problems look like.

Valid example

Add three real Q&A pairs from a service page, such as pricing, service area, and scheduling questions. Each answer should be visible on the page and match the JSON-LD text.

Example question: How long does a basic SEO audit take?
Example answer: A basic page-level audit usually takes a few minutes after the URL is accessible.

Broken example

Create one blank question, one answer that is only promotional copy, and one Q&A pair that does not appear on the page. This shows why schema should not be used for hidden or misleading content.

How to Interpret the Output

  • mainEntity should contain one item per visible question.
  • acceptedAnswer.text should contain the same answer users can read on the page.
  • Blank fields should be fixed before copying the JSON-LD.

Common Failure Cases

  • Hidden FAQs: schema describes questions users cannot see.
  • Advertising disguised as answers: answers are promotional rather than helpful.
  • Wrong schema type: use QAPage for user-submitted answers, not FAQPage.

Download sample FAQ schema report

Reviewed Jun 2026 · Sources and limitations

Review details: 2026-06-10 · Marc LaClear · v1.0

Reference sources:

Known limits:

  • Checks are based on publicly fetchable HTML, response headers, and browser-side input. They do not use private Google Search Console, analytics, or ranking data.
  • Scores and warnings are diagnostic aids, not guarantees of ranking improvement or Google indexation.
  • Pages blocked by robots.txt, login walls, bot protection, heavy JavaScript, or network timeouts may return incomplete results.
  • Validate critical fixes with official Google tools such as Search Console, Rich Results Test, Lighthouse, and your own crawl data.

Report an issue with this tool