Google deprecated FAQ rich results on 7 May 2026, according to Search Engine Journal’s report, and has since removed the Search Console FAQ filter, rich result report and Rich Results Test support.
If you came here hoping to earn expandable FAQ boxes under your search listing, that route is closed. FAQ sections are not dead, though. They still help readers find quick answers, they give search and AI systems clean question-and-answer pairs to quote, and FAQPage markup remains valid Schema.org even though Google no longer shows it as a rich result. This guide explains the timeline, what to do with existing markup, and how to write FAQs that deserve to be read.
What Happened to FAQ Rich Results
FAQ rich results were once one of the easiest ways to take extra space in search listings. Google reduced them in April 2023 and, in August 2023, limited them to well-known, authoritative government and health sites. According to the Search Engine Journal report, the feature was then deprecated on 7 May 2026, with Google stating that FAQ rich results no longer appear in Google Search.
Google has also been removing the supporting tools: the Search Console FAQ filter, the rich result report and Rich Results Test support went in June 2026, and Search Console API support followed in August 2026. If you manage a blog, this means you can no longer test or monitor FAQ rich results in Google’s tools.
| Date | Change | Effect on bloggers |
|---|---|---|
| April 2023 | FAQ rich results reduced | Fewer listings showed the boxes |
| August 2023 | Limited to well-known government and health sites | Most blogs lost eligibility |
| 7 May 2026 | FAQ rich results deprecated | No FAQ boxes in Google Search |
| June 2026 | Search Console FAQ filter, rich result report and Rich Results Test support removed | No in-tool testing or tracking |
| August 2026 | Search Console API support removed | No API reporting |
Should You Remove Existing FAQPage Markup?
There is no need to rush. FAQPage is still a valid Schema.org type, and Google has indicated that leaving existing markup in place is harmless. If your template adds it automatically, you can keep it, or remove it during a normal site clean-up. Do not spend a weekend deleting it from hundreds of posts.
Why FAQ Sections Still Make Sense
A well-written FAQ does three useful jobs. It helps readers who skim for one specific answer. It captures the question phrasing people use, which supports long-tail visibility. And it provides short, self-contained answers that answer engines and AI assistants can quote and attribute. None of these depends on a rich result.
The honest framing is this: an FAQ section is a reader feature, not a ranking trick. Judge it by whether it reduces confusion, supports the main topic and keeps people on the page.
How to Write FAQs That Work
Find Real Questions
- Search Console: filter queries with question words and note those with impressions but few clicks.
- People Also Ask and autocomplete: collect the variants Google shows.
- Your inbox and comments: customer and reader questions are the best source.
- Communities: forums and social threads show phrasing and worries.
Write the Answer Properly
- Lead with the answer: the first sentence should respond directly, then add context.
- Stay self-contained: a reader (or an AI system) should understand the answer without the rest of the page.
- Aim for 60 to 100 words: long enough to be complete, short enough to scan.
- Be honest about limits: say when the answer depends on location, product or time.
- Avoid padding and duplicates: do not repeat the article’s own text in a new wrapper.
Place and Format Them
Put the FAQ near the end, after the main content, with each question as a clear H3. Six to eight well-chosen questions are plenty. If you keep structured data, make sure the markup matches the visible text exactly.
How to Check Whether Your FAQs Are Working
Without a rich result report, rely on behaviour. In Search Console, watch queries that match your FAQ questions for impressions, clicks and position. In analytics, check engagement time and whether visitors scroll to the FAQ. If you see questions in the comments or support inbox repeatedly, the answer probably needs to be clearer or placed higher.
Review the section whenever you refresh the post. Remove questions nobody asks, update answers that have aged, and add new questions from the latest queries.
FAQs
Do FAQ rich results still appear in Google Search?
No. According to the Search Engine Journal report, Google deprecated FAQ rich results on 7 May 2026 and stated they no longer appear in Google Search. Earlier changes in 2023 had already limited them to well-known government and health sites, so most blogs had stopped seeing them well before 2026. Many bloggers noticed the drop long before the 2026 announcement, so check your own Search Console data before assuming anything changed for you.
Should I delete FAQPage schema from my blog?
You do not have to. FAQPage remains valid Schema.org markup, and Google has said there is no need to rush to remove it. Keep it if your template adds it, and remove it during routine clean-up if you prefer. Make sure any markup matches the visible questions and answers. If you edit your theme or SEO plugin settings, test one post first and confirm the page still renders normally for readers.
Are FAQ sections still worth writing?
Yes, if they answer real questions clearly. They help readers find quick answers, reflect how people phrase queries, and give answer engines concise passages to quote. Treat them as a user-experience feature rather than a way to get special search result formatting, which no longer exists. The practical test is simple: if a reader landed on that question alone, would they leave with a clear, usable answer?
How long should an FAQ answer be?
Around 60 to 100 words works well. That is long enough to give a direct answer plus the key condition or caveat, and short enough to read quickly on a phone. Start with the answer itself, then add context, and avoid repeating long passages from the article. Keep the first sentence as the direct answer, because that is the line most likely to be quoted or skimmed.
How many FAQs should a blog post have?
Six to eight is a sensible range for most posts. Choose questions that real readers ask and that add something beyond the main article. If you cannot find enough genuine questions, publish fewer rather than padding the section with repetitive or obvious ones. Keep each answer in your own words with accurate facts, and update it when prices, rules or dates change so it never misleads anyone.
Can FAQs help with AI search and answer engines?
They can help, because self-contained question-and-answer passages are easy to extract and attribute. No one can guarantee citations, and results depend on many factors. Clear writing, accurate facts, named sources and a sensible page structure improve your chances more than any single markup choice. Where possible, link to a primary source for any statistic, so both readers and answer engines can trace the claim easily.
Write FAQs for People First
The end of FAQ rich results removed a shortcut, not a good practice. Questions and answers remain one of the clearest ways to serve a reader who arrives with one specific doubt.
Audit your top five posts this week: delete weak questions, tighten the answers, and add one question taken straight from Search Console.
Sources: Search Engine Journal: Google deprecates FAQ rich results; Google Search Central: FAQPage structured data documentation; Schema.org: FAQPage
