We respect your privacy.

We use strictly necessary cookies to keep you signed in and to protect against CSRF. With your permission we also use a small amount of first-party analytics to improve the product. We do not sell your data and we do not use third-party advertising trackers. See our cookie policy and privacy policy .

Crawlmind
← All learn topics

Rule page.faq.schema-missing

Mark up your FAQ content with FAQPage JSON-LD

page.faq.schema-missing is a check in Crawlmind's site audit that grades medium-impact issues of this kind. This page explains why the rule matters and the exact fix.

Impact: mediumEffort: low

Why it matters

This page reads like an FAQ — it has several question-shaped headings — but ships no FAQPage or QAPage structured data. AI answer engines extract answers passage-by-passage, and an explicit FAQPage graph hands them each question paired with its answer, which is exactly the shape they cite. Google now limits FAQ *rich results* to government and health sites, so this won't win you a SERP accordion — but the markup still helps ChatGPT, Perplexity, and AI Overviews parse and attribute your answers.

The fix

Add one FAQPage block to the page, listing each question and its answer:

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does a crawl take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most audits finish in under five minutes."
      }
    },
    {
      "@type": "Question",
      "name": "Do you need a credit card to start?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No — the free tier runs five audits with no card."
      }
    }
  ]
}
</script>
```

Keep the `Answer.text` identical to the visible answer on the page — mismatched markup is treated as spam. One FAQPage per page; use QAPage instead if the page is a single user-asked question with community answers.

References