Generating Schema

Generating FAQ schema

SuperSchema builds FAQPage schema from the real questions and answers on your page. It looks for a Frequently Asked Questions section and pairs each question with its answer. Here is how it decides a page is an FAQ, and how to fix the pairs if they look wrong.

View as plain text Updated 2026-07-07

FAQPage schema marks up a list of questions and their answers so Google and AI can present them directly, sometimes as an expandable FAQ block in search. SuperSchema reads your page, finds the question-and-answer content, and assembles the FAQPage for you. The important rule: it builds the FAQ from questions and answers that genuinely appear on the page, not invented ones.

How SuperSchema finds your FAQ #

SuperSchema looks for a heading that reads like "FAQ" or "Frequently Asked Questions", then walks the content underneath it until the next heading of the same or higher level. Within that section, it pairs each question with the text that answers it.

  • A question is text that ends in a question mark, or starts with a question word like what, how, why, when, where, which, who, is, are, can, do, does, should, would, will, or could.
  • A common pattern it reads well is a paragraph that leads with the question in bold (a strong or b tag) followed by the answer text.
  • Answers shorter than about 20 characters are skipped, so stray fragments do not become fake answers.
  • Duplicate questions are removed, and it collects up to 10 question-and-answer pairs from the section.

When Auto mode chooses FAQPage #

If you let SuperSchema pick the schema type automatically, it only chooses FAQPage when the page really looks like an FAQ destination, not just because it has a few collapsible sections. It weighs signals like these together:

  • The URL path looks like an FAQ (for example it contains faq or frequently-asked-questions).
  • The page title or an H1 reads like an FAQ.
  • One of the top section headings reads like an FAQ.
  • There are at least a couple of genuine question-and-answer pairs on the page.
Note Accordions alone will not trigger FAQPage in Auto mode. Accordions are often used for general page details, requirements, or pricing, so unless the page is clearly an FAQ by its URL, title, or headings, an accordion is not treated as a FAQ.
Tip If your page is an FAQ but Auto mode did not pick FAQPage, generate again with the FAQ type selected. That tells SuperSchema to build FAQPage from the question-and-answer content it finds, even when the automatic signals were borderline.

If the questions look wrong #

FAQ schema should mirror the Q&A actually on your page. If a generated question or answer does not match your content, you can correct it directly in the Schema Editor. The questions live in the mainEntity array, each as a Question with its answer inside an acceptedAnswer.

  1. Open the schema in the editor and find the mainEntity array.
  2. Each item is a Question with a name (the question) and an acceptedAnswer whose text holds the answer.
  3. Edit the name or acceptedAnswer text to match your page, or delete a pair you do not want.
  4. Let the editor auto-save, and check the Google Search Preview to see how the FAQ would render.
Tip For the cleanest result, generate FAQ schema on a page that presents its questions and answers as clearly structured visible content, with real question headings or bolded questions followed by their answers.
Warning Only mark up FAQs that genuinely appear on the page. FAQ schema must represent real, visible question-and-answer content. Do not add invented questions to try to win a rich result, as that goes against Google's structured-data guidelines.
Related
Schema Generation Paste a URL and SuperSchema reads your real page content, then writes the correct JSON-LD for you. No manual data entry and no Schema.org documentation to hunt through. It also produces clean AI-readable Markdown and plain-text versions of the page alongside the schema. Editing schema The Schema Editor is a full JSON-LD code editor with syntax highlighting, live validation, and auto-save. Change any field by hand, watch for errors and warnings as you type, and your edits save automatically a few seconds after you stop typing. Choosing a type By default SuperSchema picks the best schema type for your page for you. You can also open the Primary Schema Type selector and force a specific type when you already know what the page should be. Rich results preview The Google Search Preview panel shows an approximation of how your schema could appear as a rich result, and badges which of your schema types are eligible for one. Eligibility means it is possible, not guaranteed. Google decides what to actually show.

Still have questions?

Can't find what you're looking for? Our support team is here to help.

Contact Support