FAQ content, more useful than it has been in years.

When rich result support for FAQ markup was reduced, plenty of sites removed it. Understandable if the only goal was a bigger snippet, and unfortunate, because question-and-answer content is close to the ideal format for a system that extracts passages.

Why the format suits answer engines

A question and its answer is a self-contained unit with the query attached. It requires no inference about what the passage addresses and no surrounding context to make sense.

That is precisely the shape that gets lifted into a generated answer. Whatever happened to rich results, the underlying content format became more valuable rather than less.

What changed with FAQ rich results

In August 2023 Google limited FAQ rich results to well-known, authoritative government and health websites. For almost every business, FAQ markup stopped producing the expandable questions under a search result. That is the change people remember, and it is why so much FAQ content was quietly deleted.

What did not change is that Google still documents FAQPage as supported structured data, and that question-and-answer content is still easy for any system, Google's or anyone else's, to understand. The loss was a display feature. The format's usefulness for answer engines is a separate question, and on that one the answer is still yes.

Doing it properly

• Real questions. From sales calls, support tickets and search data. Invented questions read as invented and answer nothing anyone asked.
• Complete answers. Each answer should stand alone. “See our services page” is not an answer.
• Specific answers. Numbers, ranges and conditions. Hedged answers are unquotable.
• One FAQPage block per URL. Multiple blocks are generally not all honored, so the extra ones are wasted work.
• Valid JSON. An unescaped quote inside an answer invalidates the entire block silently.

Where to put them

In-page FAQ sections on commercial pages usually outperform a standalone FAQ page, because they answer objections at the moment they arise and they attach question-shaped content to the page you want cited.

A central FAQ page still has a role for general questions about your business, but it should not be the only place questions are answered.

Where the questions should come from

The best FAQ content is mined, not brainstormed. Sources worth a look:

• Call recordings and intake notes: the questions people ask before booking.
• Sales emails and proposals: the objections that come up late in a decision.
• Search Console queries phrased as questions (filter for who, what, how, why, can, does).
• The “People also ask” boxes and AI Overview follow-up questions for your main services.
• Reviews, which often answer a question implicitly (“I was worried it would be expensive”).

Write each answer as if it will be read on its own, because in an AI answer it will be. Lead with the direct answer, add the condition or range, and stop.

Keeping FAQ markup accurate

Markup has to match what is visible on the page, word for word or close to it. When an answer changes, change both. If you generate FAQ markup from your CMS, make sure the same source feeds the visible text and the JSON-LD, so they cannot drift apart.

Validate after every edit. The most common failure is an unescaped quotation mark inside an answer, which breaks the JSON and silently removes the whole block. A quick check with a structured data validator after publishing catches it.

An example of a good FAQ answer

Question: “How long does a roof replacement take?” Weak answer: “It depends on many factors; contact us to learn more.” Strong answer: “Most asphalt roof replacements on a typical house take one to two days. Steep roofs, multiple layers to remove or rotten decking can add a day or two. We confirm the schedule in your written quote.” The strong answer is quotable and useful; the figures here are illustrative.

Frequently asked questions

Do FAQ pages still help SEO?

For rich results their impact was reduced. For AI search they matter more than before, because a question with a complete self-contained answer is close to the ideal format for a system that extracts passages.

Should FAQ schema be on every page?

On pages with genuine questions and answers, yes, with one FAQPage block per URL. Multiple blocks on a single page are generally not all honored, and invented questions add nothing.

Where should FAQs live on a website?

In-page sections on commercial pages usually outperform a standalone FAQ page, because they answer objections at the point they arise and attach question-shaped content to the pages you want cited.

Is FAQ schema still worth adding?

Yes, on pages with genuine visible questions and answers. It no longer produces rich results for most sites, but it describes the content unambiguously, costs little, and supports how answer engines read the page.

How many FAQs should a page have?

As many as buyers genuinely ask about that topic, usually three to eight. Padding with invented questions weakens the section for readers and machines alike.