Match FAQ schema to the visible text

What the scan checks: for every question in your FAQPage schema, it looks for that question’s text on the visible page. Any schema question that is not present in the page text fails the check. (If there is no FAQPage schema, the check is not applicable.)

The answers are checked too, in two ways. First, whether any acceptedAnswer.text appears on the page at all — schema whose answers are nowhere in the visible copy gets discarded. Second, and more often the real problem: whether your schema answers are truncated versions of the page’s answers. The scan measures how much of each on-page answer the markup actually carries; under 70% is reported as truncation.

That second one matters because it is invisible without measuring it. A CMS that cuts schema answers at 100 characters produces markup that passes every “does the text match” test and still gets you cited with half a sentence. Copy the full paragraph into acceptedAnswer.text rather than writing a shortened version for the schema.

Why it matters for AI search visibility

Structured data is a claim about what is on the page, and engines cross-check it. When your FAQPage schema says the page answers “How much does it cost?” but that question appears nowhere in the visible content, that is a mismatch: the markup describes content that does not exist. Validators flag it, and engines treat schema that disagrees with the page as untrustworthy, which can suppress the whole page’s structured data rather than just the FAQ. The fix is cheap and the downside of ignoring it is real, so this is a “clean it up now” item.

How to fix it

Make the schema a faithful copy of the visible Q&A, not a separate rewrite:

• Questions must match. The name of each Question node has to appear as visible text on the page (your <h2>/<h3>/<summary> FAQ headings).
• Answers must match. The acceptedAnswer.text should be the same answer the visitor reads, word for word. Do not write a “schema-only” answer that differs from the page.
• Generate the schema from the content, not by hand. If your CMS renders the FAQ, have it emit the JSON-LD from the same source fields so the two cannot drift apart.
• Remove stale entries. If you delete a question from the page, delete it from the schema in the same edit.

Validate with the Schema.org validator or Google’s Rich Results Test, then spot-check by searching the page for each schema question. Every one should be there. This pairs with adding the FAQ itself (C16).