Direct answer: Publish a question and answer when they help a buyer complete a real task. As of November 2026, adding FAQPage markup is not a route to Google's retired FAQ rich result, and Google says no special schema is required for its generative AI features. Neither an FAQ section nor its markup guarantees an AI citation. Google's documentation changelog records the FAQ rich result ending May 7, 2026; its generative AI search guide says there is no special schema for those features.
Two decisions that should not be bundled
Does the answer belong on the site? Suppose buyers ask whether a booking deposit is refundable, whether a product is made to order, or which locations a service covers. The answer should be clear in the page where the decision is made, with exceptions and a route to ask when a case differs. A separate FAQ page can help when several questions belong together, but it should not make the main service or product page depend on a click to reveal a material term. The answer-beside-the-action guide helps locate it.
Is there a supported search feature for this markup? Structured data is useful when it accurately describes visible content and qualifies for a current feature. It does not create a feature that Google has removed. Google's June 2026 update says it removed FAQ rich-result documentation because the feature was no longer shown. Its AI search guidance explicitly says structured data is not required for generative AI Search, although supported structured data remains useful for other eligible rich results. The feature, its eligibility rules, and the visible page should be checked before implementation.
For an actual question, write the answer a customer needs to act. “Yes, cancellations are allowed” is incomplete if the refund cutoff and method matter. Put the operational policy in a maintained source of truth, link to the detailed terms, and assign an owner when prices or rules change. This is a content-governance recommendation, not a claim that Google's systems will quote a particular sentence. The product capability versioning guide shows why stale public facts can confuse both people and answer systems.
A five-minute vendor-claim check
Ask for the exact Google feature the proposal targets, its current official documentation, the page type's eligibility, and the result you will measure. A screenshot from an older FAQ rich result is not evidence of a current opportunity. For AI answers, use the AI snippet and preview controls guide to separate discoverability and control questions. A search feature may select content differently over time, so measure actual appearances and buyer outcomes rather than counting inserted FAQ schema blocks.
An ARCHV website scope can include the customer questions, content owner, page placement, and any supported markup in one review. The goal is an accurate answer at the right decision point; search presentation remains Google’s decision.