Does FAQ schema still do anything?
The visible rich result for FAQ markup was largely retired for most sites, so the SERP benefit that made it popular is mostly gone. Structured data still earns its place as machine-readable context: it states unambiguously what question a page answers, who published it, and when it was last updated. Mark up for correctness and durability, not for a rich result that may never appear.
What changed and what did not
FAQ rich results were shown broadly, then narrowed sharply. Teams that had added the markup purely for the extra SERP real estate saw that disappear and concluded schema was dead.
The underlying function did not change. Structured data is how you tell a machine what a page is without asking it to infer from prose. That job matters more now, not less, because more systems than search engines are reading your pages.
What is worth marking up on an answer hub
- FAQPage or QAPage. Declares the question and the answer explicitly. Use FAQPage when your page presents question-and-answer pairs you authored.
- Article with datePublished and dateModified. Freshness signals that are stated rather than guessed at.
- Organization and publisher. Ties the content to a real entity with an address, phone and profile. This is what lets a system attribute an answer to your business rather than to nobody.
- BreadcrumbList. Makes the cluster structure explicit instead of leaving it to be inferred from URLs.
The rule that keeps you out of trouble
Markup must match what a human sees on the page. Marking up questions and answers that do not appear in the visible content is a straightforward violation and has been for years, and it is easy to do accidentally when schema is generated from a database field rather than from the rendered page.
Generate structured data from the same source that renders the page. If the answer text lives in one record and both the HTML and the JSON-LD are built from it, they cannot drift apart. That is a small architectural decision that removes a whole class of ongoing audit work, and it is the same principle behind any durable data integration: one source, many outputs, no manual duplication.
Where it actually pays off
Attribution and disambiguation. When several sites say roughly the same thing, being the one that clearly declares who published it, when it was updated and what entity stands behind it is a small advantage that costs nothing to maintain.
It also future-proofs. Marking up correctly today means you are already eligible when a system starts consuming a format you did not anticipate. That is most of the argument for treating schema as part of how content is built rather than as a plugin someone installs later.
Topics: schema markup · structured data · FAQPage · technical SEO
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.