Do FAQ Sections Still Help SEO After Google Dropped FAQ Rich Results? (2026)
Do FAQ sections still help SEO in 2026?
Yes, but not for the reason most guides still give. The visual reward is gone: Google stopped showing FAQ rich results in Search on 7 May 2026 and removed the feature’s documentation in June, after limiting them to “well-known, authoritative government and health websites” back in August 2023. So FAQ markup no longer earns you extra lines under your result. What still works is the section itself: short, direct answers to the questions your customers really ask, written on the page where they make sense. Those help readers, and they give Google clear text that matches how people phrase their searches. Below: what changed and when, whether to keep the markup, how to write an FAQ that earns its place on a small business blog, and when to leave it out.
What Google changed, and when
| Date | Change | What it means for a small business site |
|---|---|---|
| August 2023 | FAQ rich results limited to well-known, authoritative government and health sites | Most business sites stopped seeing FAQ dropdowns in results |
| 7 May 2026 | FAQ rich results no longer appear in Google Search | No site gets the dropdowns any more |
| June 2026 | FAQ search appearance, rich result report and Rich Results Test support removed; documentation deleted | Search Console no longer reports on FAQ markup |
| August 2026 | FAQ support removed from the Search Console API | Reporting tools that pulled FAQ data need updating |
None of these dates touched rankings directly. FAQ markup was a display feature, never a ranking signal, so losing it changed how some results looked, not where pages ranked.
Should you remove FAQ schema from your pages?
No need. When Google first limited the feature in 2023, it wrote: “there’s no need to proactively remove it. Structured data that’s not being used does not cause problems for Search, but also has no visible effects in Google Search.” FAQPage is still a valid schema.org type. Our own posts keep FAQ markup that mirrors the visible questions word for word, and that is the one rule worth keeping if you leave it in: the markup must match what readers see on the page. For the markup that still matters on a blog post, see structured data for a small business blog.
What you should stop doing is adding FAQ blocks for the markup. A page with eight padded questions written to win dropdowns is now just a page with eight padded questions.
Why a good FAQ section still earns its place
- It answers the follow-up questions. Someone reading about a boiler service wants to know how long it takes and whether they need to be home. Answering on the page saves a phone call, or wins it.
- It matches how people search. Customers type questions. A heading that states the question and a two-sentence answer underneath is the clearest possible match, and Google’s helpful-content guidance asks whether a page provides “a substantial, complete, or comprehensive description of the topic.”
- It catches objections before checkout. On a service or pricing page, an FAQ about cancellation, timing or what is included removes the last reasons to leave.
- It is easy to keep current. Updating one answer when a policy changes is quicker than rewriting a whole page, which suits the refresh routine in our guide to deciding whether to refresh a post or write a new one.
How to write an FAQ section for a small business blog post
- Take questions from real sources. Customer emails, calls, reviews, and the questions Google’s “People also ask” box shows for your topic. Not questions you invented to repeat a keyword.
- Keep it to three to five. If you have ten, half of them belong in the body of the post, or in a separate post.
- Answer in the first sentence. “Yes, if…” or “About two hours.” Then one or two sentences of context. Short answers are the point.
- Do not repeat the article. Each answer should add something the body did not already say, such as a cost factor, a timing detail or an exception.
- Put it near the end. Lead with the main answer and the full explanation; the FAQ catches what is left.
- Mark it up honestly, or not at all. If you add FAQPage markup, copy the visible text exactly.
The same answer-first habit helps the rest of the post; our guide to how long a small business blog post should be explains why a complete answer beats a target word count.
A worked example
Illustrative, for a fictional local business. A gardening company writes a post on “When should I prune roses?” Weak FAQ: “What is rose pruning?”, “Why prune roses?”, “Is pruning roses important?” Each repeats the post and none answers a decision. Strong FAQ:
- Can I prune roses in autumn? A light tidy, yes; the main prune waits until late winter in most climates. Then why.
- What if I missed the right month? What still works and what to skip this year.
- Do you prune climbing roses the same way? No, and the one-line difference.
- How much does a professional prune cost? What the price depends on, and a link to the service page instead of an invented figure.
The strong version answers the next decision the reader faces, and the last question leads naturally to the business.
When to leave the FAQ out
| Situation | Better choice |
|---|---|
| The post already answers one narrow question fully | No FAQ; end with a next step |
| The only questions you can think of repeat headings | Skip it |
| You have more than five strong questions | Make the best ones into H2 sections or a separate post |
| Answers depend on a quote or inspection | Explain what the price depends on and link the contact page |
How PilotaSEO handles FAQs
PilotaSEO is a done-for-you SEO blog service by GSPTeck (our service): it writes SEO posts for your site and publishes them automatically, in English or Italian, with internal links to your pages and primary sources. Each post answers its main question first and ends with a short FAQ only where real follow-up questions exist, with markup that matches the visible text. Plans are Autopilot at €322 a year and Growth at €8,250 a year; see the PilotaSEO plans and what each includes. Honest limit: no service can promise rankings, and an FAQ will not change that on its own. Bylines matter in the same way, as our post on whether author bios help SEO explains.
FAQ
Does Google still show FAQ rich results?
No. Google stopped showing FAQ rich results in Search on 7 May 2026, after limiting them to authoritative government and health sites in 2023.
Will FAQ schema hurt my rankings?
No. Google has said unused structured data does not cause problems for Search. Keep it only if it matches the visible questions and answers exactly.
How many questions should a blog FAQ have?
Three to five is enough for most posts. More than that usually means some answers belong in the body or in their own post.
Should every blog post have an FAQ?
No. Add one when readers have real follow-up questions the post does not answer. If every question repeats a heading, leave it out.
Sources
- Google Search Central: documentation updates, FAQ rich result deprecation (May and June 2026) (checked 2026-10-23)
- Google Search Central Blog: changes to HowTo and FAQ rich results (2023) (checked 2026-10-23)
- Search Engine Journal: Google drops FAQ rich results from Search (checked 2026-10-23)
- Google Search Central: creating helpful, reliable, people-first content (checked 2026-10-23)
- Schema.org: FAQPage type (checked 2026-10-23)