FAQ Schema That Actually Qualifies

FAQ schema is one of the most abused structured data types on the web. Plugins apply it automatically. Agencies add it to pages that have no real FAQ content. Developers copy templates from documentation without checking whether the answers are visible. The result is that most FAQ schema in the wild either fails Google's eligibility requirements, gets suppressed without any warning, or produces rich results that confuse buyers rather than helping them.

Getting FAQ schema right is not complicated — but it requires understanding what Google actually checks, and what AI systems need from FAQ content that is different again.

Google's exact eligibility rules — what actually disqualifies FAQ schema

Google is explicit about what makes FAQ schema eligible for rich results. The rules are not ambiguous. The enforcement is.

• The questions and answers must be visible on the page — not hidden behind JavaScript toggles that fail to render, not collapsed inside accordions that do not expand in the DOM, not present only in the markup
• Each answer must contain real information — not 'Contact us to find out more' or 'It depends on your situation'
• The markup must match the visible content — if the page shows a 50-word answer and the schema has a 200-word answer, that is a mismatch
• The FAQ page must be a genuine FAQ page — not a service page where someone added a FAQ section for SEO reasons with questions that nobody actually asks
• The content must not be promotional — FAQ schema on pages designed purely to capture keyword traffic without genuine buyer utility will be suppressed

In site scans we've run, the most common disqualifying issue is FAQ schema on pages where the answers are invisible to Google's crawler — either because they are loaded by JavaScript after page render or because the answers are inside closed accordion states that the crawler cannot open.

What a disqualifying FAQ implementation looks like

// BAD — FAQ schema that will likely be suppressed
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What services do you offer?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We offer a wide range of professional services tailored to your needs. Contact us to learn more."
      }
    },
    {
      "@type": "Question",
      "name": "How much does it cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Pricing varies depending on your requirements. Please get in touch for a custom quote."
      }
    }
  ]
}
// Problems: answers are non-answers. They contain no information.
// Google's quality threshold will suppress these.
// AI systems will ignore them entirely.

What valid FAQ schema looks like — a German law firm example

Here is FAQ schema from a Munich employment law firm that meets every eligibility requirement. The answers are specific, visible on the page, and answer real buyer questions.

// GOOD — FAQ schema for Northside Legal GmbH, Munich employment law practice
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Wie lange dauert ein Kündigungsschutzverfahren in München?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Ein Kündigungsschutzverfahren vor dem Arbeitsgericht München dauert in der Regel zwischen 3 und 9 Monaten bis zum ersten Gütetermin. Bei strittigen Fällen, die in die Kammerverhandlung gehen, kann das Verfahren 12 bis 18 Monate in Anspruch nehmen. Wir empfehlen, spätestens innerhalb von 5 Tagen nach Erhalt der Kündigung rechtliche Beratung in Anspruch zu nehmen, da die Klagefrist 3 Wochen beträgt."
      }
    },
    {
      "@type": "Question",
      "name": "Was kostet eine arbeitsrechtliche Erstberatung bei Northside Legal?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Eine Erstberatung bei Northside Legal GmbH kostet pauschal 150 Euro zzgl. MwSt. und dauert bis zu 60 Minuten. Bei Beauftragung mit der weiteren Vertretung werden die Kosten der Erstberatung auf das Honorar angerechnet. Für Arbeitnehmer mit Rechtsschutzversicherung übernehmen wir die direkte Abrechnung mit dem Versicherer."
      }
    },
    {
      "@type": "Question",
      "name": "Vertreten Sie auch Arbeitgeber im Kündigungsschutzrecht?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Ja. Northside Legal GmbH berät und vertritt sowohl Arbeitnehmer als auch Arbeitgeber im Kündigungsschutzrecht. Für Unternehmen bieten wir auch präventive Beratung zu rechtssicheren Trennungsverfahren, Abfindungsverhandlungen und der Gestaltung von Aufhebungsverträgen an. Mandantenkollisionen werden durch interne Prüfung ausgeschlossen."
      }
    }
  ]
}

Notice what makes this work: every answer contains specific information that a buyer actually needs. The questions are real questions that real clients ask. The answers match what is written on the page word for word.

FAQ schema for AI surfaces — different rules from Google

AI retrieval systems like ChatGPT and Perplexity have different requirements from Google's FAQ rich results. Google cares about page eligibility. AI systems care about answer quality and specificity.

For AI surfaces, the most important property is the answer text itself. AI systems will lift FAQ answers nearly verbatim when they are specific, authoritative, and written in the same language as the user's query. That means FAQ schema optimised for AI visibility should:

• Include the business name in at least one answer so attribution is unambiguous
• Provide specific numbers, timeframes, prices, or processes — not qualitative generalities
• Answer the exact phrasing that buyers use when asking AI systems, not the phrasing that was optimised for keyword density
• Be written in the language of your buyers — German-language FAQ schema for German-language buyers performs significantly better than English FAQ schema on German-market sites

Loopful eligibility checking

Before Loopful deploys any FAQ schema block, it runs an eligibility check against the live page. It verifies that the answer text appears in the page's rendered DOM, that the answer length is consistent with the visible content, and that the questions are not generic plugin defaults.

If a FAQ block fails eligibility, Loopful flags it in the review queue instead of deploying it. This prevents the most common category of FAQ schema failure — markup that is technically valid but ineligible — from ever going live.

📸 Screenshot: Loopful FAQ eligibility check showing a service page's proposed FAQPage schema, with two questions marked green (answers found in rendered DOM), one marked amber (answer text in schema is longer than visible answer — possible mismatch), and one marked red (answer text not found on page — schema answer exists only in markup)

Pre-deployment checklist for FAQ schema

1. Open the page in a browser and read every question and answer in the visible FAQ section. If any answer would not satisfy a real buyer, do not mark it up.
2. Check that the answers are visible in the rendered DOM — not hidden, not collapsed, not loaded by JavaScript after the initial render.
3. Compare each schema answer field to the visible answer word by word. Minor differences are acceptable. Major differences are not.
4. Check that the FAQ section is genuinely relevant to the page topic. FAQ schema on a generic service page whose questions are obviously written for SEO will be suppressed.
5. After deployment, check the Rich Results Test to confirm eligibility. Do not assume — verify.

FAQ schema that drifts after content updates is one of the fastest ways to lose rich result eligibility. Add FAQ review to your content publishing process using the framework in Schema Drift Quietly Kills Revenue.