FAQ schema: markup for questions the page actually answers

Only mark up visible question-and-answer pairs

The question and the answer in the schema should match the text in the document. Hidden FAQs, questions stuffed into the footer of every URL, and answers that contradict the article will fail a careful review even if they pass a syntax check.

Use FAQ schema on pages that are genuinely a set of answers. A single aside at the bottom of every guide can be valid. The same five questions repeated sitewide are a template, not a FAQ.

Write answers that close the question

Each answer should be specific enough to stand alone. ‘It depends’ without the conditions is a weak answer for a reader and a poor passage for a result.

Link out when the full procedure lives on another page. The FAQ can state the decision and point to the guide. It should not pretend to be the whole manual.

• Visible questions only.
• Answers that match the schema word for word.
• No sitewide duplicate FAQ block.

Expect fewer FAQ rich results than before

Search shows FAQ rich results more selectively than it once did. The markup is still useful as a clear question-answer structure on the page. Do not add FAQs only in the hope of extra lines in the result.

If a report says the page is ineligible, read the policy note before adding more questions. Eligibility is often about the page type, not a missing comma.

Will FAQ schema make a page rank higher?

It can change how a result looks when a rich result is shown. It does not add relevance that the page lacks.

Can the same FAQ appear on every page?

The same markup repeated everywhere is low value and can be ignored. Keep questions specific to the page.