Short answer: An FAQ page answers the questions your customers ask, each under its own heading with a short, direct answer. Since May 7, 2026, Google no longer shows FAQ rich results, so FAQ schema won’t win you that result. What still counts is whether the answers help the people who read them.
What changed with FAQ schema
Google narrowed the FAQ rich result first, to well-known, authoritative government and health websites. Then, on May 8, 2026, its changelog added a deprecation notice: the feature would no longer appear in Google Search starting May 7, 2026.
Google later removed the documentation, saying the FAQ rich result is no longer shown in its results. FAQPage itself is still a Schema.org type, defined as a web page presenting one or more frequently asked questions.
How to build each part of an FAQ
| Part | What to do | Our guides |
|---|---|---|
| Questions | Use the ones customers ask, in their words | Five per guide |
| Answers | Short and complete, right under each question | 30 to 40 words in the guide we measured |
| Headings | One heading per question | Each question is an h3 heading |
| Open or folded | If you fold them, follow the W3C accordion pattern | Always open |
| FAQPage markup | Optional: Google shows no FAQ result since May 7, 2026 | Same text as the page |
| Place | Where the questions come up | At the end of each guide |
From Google Search Central’s documentation updates, Schema.org and the W3C accordion pattern, read November 3, 2026. The last column is our own guides that day.
How to write an FAQ page people use
- Collect the questions customers ask you by phone, email and chat.
- Keep the ones that come up again and again, and drop the ones another page already answers in full.
- Write each question as a heading, in the words customers use.
- Answer right below it in two or three sentences, starting with the answer itself.
- If you fold the answers, use the W3C accordion pattern so keyboard and screen reader users can open them.
- Don’t add FAQPage markup to get a rich result, since Google stopped showing FAQ results on May 7, 2026.
- Review the answers whenever your hours, policies or services change.
Our guides to structured data and the Rich Results Test cover the markup Google still uses and how to test it. Our ADA website compliance guide covers the rest of an accessible page.
How our own FAQs are built
We read our own site on November 3, 2026, on the server and as a visitor. 318 of our published pages carry FAQ rows, with 1,678 questions between them, and every guide ends with five questions.
In our keyword stuffing guide, each question is an h3 heading with its answer in a paragraph below, always open, with no accordion. The answers run from 30 to 40 words.
The page also carries FAQPage markup in JSON-LD with the same five questions and the same answers, word for word. We left it in place after Google retired the FAQ result, since it describes exactly what the page shows.
Before you publish an FAQ page
- Every question is one customers have asked you.
- Each answer starts with the answer itself.
- Each question has its own heading.
- Folded answers open with a keyboard and a screen reader.
- Any FAQPage markup matches the visible text.
- Someone owns keeping the answers up to date.
RememberWrite FAQs for the people who ask, not for a rich result: Google stopped showing FAQ results on May 7, 2026.
If you want your site’s questions and answers written from what your customers ask, see our content marketing service.
Quick answers about FAQ pages
Does FAQ schema still work in Google?
Not for a rich result. Google’s changelog says the FAQ rich result stopped appearing in Google Search on May 7, 2026, and Google later removed its documentation. FAQPage markup is still a valid Schema.org type, but Google no longer shows a special result for it.
Should I remove FAQPage markup from my site?
Google’s notice only says the result no longer appears. It doesn’t ask site owners to remove the markup. We left ours in place because it describes the same questions and answers our pages show, word for word.
How many questions should an FAQ page have?
No Google rule sets a number. Use the questions customers ask you, and stop when they’re covered. Our guides carry five questions each, and the answers in the one we measured run from 30 to 40 words.
Should FAQ answers be hidden in an accordion?
They can be, if the accordion is built well. The W3C pattern makes each question a button that says whether its answer is open or closed. Our own FAQ answers stay open, so there is nothing to click.
Is an FAQ page still worth having?
Yes, for the people who read it. Google’s guidance on helpful content asks whether readers leave feeling they’ve learned enough to reach their goal. Short, direct answers to the questions customers ask help with that.
Sources
Read on November 3, 2026. Google Search Central: Latest Google Search Documentation Updates and Creating helpful, reliable, people-first content. Schema.org: FAQPage. W3C Web Accessibility Initiative: Accordion Pattern (Sections With Show/Hide Functionality). Our own case: the FAQ blocks of our site, read on our server and as a visitor on November 3, 2026.