How to add FAQ schema to a page

What does FAQ schema do today?

Structured data is code that labels the content on a page so machines can read it. FAQ schema uses the schema.org type FAQPage.

In 2023 Google limited FAQ rich results to well-known, authoritative government and health sites. Most businesses will not see the expandable questions in search anymore.

The markup is still valid. It tells any parser exactly which text is a question and which is the answer.

Google says there is no special markup for AI Overviews. Normal SEO best practice applies. So add FAQ schema for clarity, not as a trick.

When should a page use FAQ schema?

FAQPage fits a narrow pattern. Use it only when all of these are true.

• The questions and answers are visible on the page to every visitor.
• You wrote both the questions and the answers.
• Each question has one answer, not a thread of replies.
• The answers inform rather than advertise.

How to add FAQ schema in six steps

You can do this by hand, through your CMS, or with a structured data plugin.

1. 1

   Write the visible FAQ

   Add three to eight real questions your customers ask. Answer each in two to four plain sentences.

2. 2

   Copy the exact text

   The markup should match what visitors see. Small formatting differences are fine; different meaning is not.

3. 3

   Write the JSON-LD

   JSON-LD is Google's recommended structured data format. Use one FAQPage with a Question for each pair.

4. 4

   Add it to the page

   Paste it in a script tag in the page head or body. Many CMS platforms have a field or plugin for this.

5. 5

   Validate it

   Run the URL through the Schema Markup Validator and Google's Rich Results Test. Fix any errors they report.

6. 6

   Publish and request indexing

   Use URL Inspection in Google Search Console to ask Google to recrawl the updated page.

A FAQPage JSON-LD example

This example is for a fictional clinic. Add one object to mainEntity for each question on your page.

Accordions are fine. Answers inside a collapsed section still count as visible, as long as they are in the page HTML.

Use plain text in the answer field. Simple links are allowed, but avoid pasting whole blocks of styled HTML.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you offer emergency appointments?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We keep same-day emergency slots on weekdays. Call before 10am to book one."
      }
    },
    {
      "@type": "Question",
      "name": "Do you treat children?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We see children from their first tooth onwards, with longer appointments for nervous patients."
      }
    }
  ]
}
</script>

How to check it worked

Paste the live URL into the Schema Markup Validator at validator.schema.org. It should list FAQPage with every question and answer.

Run the Rich Results Test too. It may confirm the markup is valid without promising a rich result. That is expected for most sites.

View the page source, not just the browser inspector. If the JSON-LD only appears after JavaScript runs, some crawlers may miss it.

Recheck after any redesign or theme change. New themes often strip structured data or add a duplicate copy.

The free WebValet check looks for structured data on your homepage as part of its AI readiness scan.

Common FAQ schema mistakes

Most FAQ schema problems are about honesty and accuracy, not code.

• Marking up questions that are hidden or missing from the page.
• Repeating the same FAQ block across every page of the site.
• Using FAQPage for user forums. QAPage is the right type for those.
• Breaking the JSON with trailing commas or curly quotes pasted from a word processor.
• Stuffing answers with keywords or sales lines.

Questions people ask