Tag: Rich results
All blog posts with this tag.
Google removed FAQ rich results: should you still add FAQs to articles?
For years, many sites added FAQ blocks to the end of articles in the hope of earning a rich result in Google Search. That tactic gradually lost value, and Google made a clear change in 2026: FAQ rich results no longer appear in Search starting 7 May 2026, and the related documentation was later removed. Does that mean every FAQ should disappear? No. But FAQs should no longer be treated as a shortcut to search visibility. An FAQ can still be useful if it answers real objections, clarifies a complex topic, improves navigation or turns a long article into a more usable resource. It is less useful when it repeats the article, stacks artificial questions or exists only to occupy more SERP space. What Google changed In its Search Central changelog, Google states that the FAQ rich result feature no longer appears in Google Search starting 7 May 2026. In June, Google also removed the documentation associated with that feature. The Search Console data anomalies page also notes that the disappearance of this appearance can cause a drop in impressions associated with FAQ rich results. This matters for reporting: a fall in FAQ appearance impressions does not necessarily mean that pages lost overall organic audience. In other words, if a report shows a break in FAQ appearance data, the first hypothesis is not a penalty or a quality drop. It is likely an interface and reporting change. FAQs should no longer be written for the rich result The issue was never the FAQ format itself. The issue was the mechanical use of the format. Examples of weak practices include:repeating the title as a question; adding five generic questions with no new information; hiding keyword variants in artificial answers; writing answers that are too short to be useful; reusing the same FAQ across several articles; making markup the main purpose of the block.With FAQ rich results gone, those tactics lose their tactical justification. They remain bad for the reader experience. Good reasons to keep an FAQ An FAQ remains relevant when it has a clear editorial function. Clarifying limits On privacy, compliance and analytics topics, an FAQ can answer questions that should not interrupt the main article. Examples:“Does cookieless mean no consent is needed?” “Is aggregated data always anonymous?” “Is a Search Console report a measure of sessions?”These answers can prevent misunderstandings without making the article heavier. Addressing objections A reader may understand the article and still have a practical objection: cost, complexity, DPO involvement, loss of data or reporting impact. A good FAQ addresses these objections directly. Improving navigation In a long guide, an FAQ can act as a shortcut. It helps a busy reader find the answer to a common question quickly. Making the article more reusable A well-written FAQ makes an article easier to quote, share or turn into internal guidance. It can also feed a knowledge base or sales enablement brief without changing the core content. When to remove or rewrite an FAQ Remove the FAQ if every answer repeats an existing section. It should not become a second conclusion. Rewrite it if the questions are disguised keywords. A useful question sounds like a real reader hesitation, not a search query with a question mark. Merge it if several questions receive the same answer. That is often a sign that the article needs a better summary section, not an FAQ block. Keep it if it adds precision, caution or action. In privacy-first content, FAQs are especially useful for avoiding overly broad compliance claims. FAQ structured data: what now? The end of a rich result does not mean all structured data is useless everywhere. But for FAQs, the goal should no longer be to win an appearance that Google Search has removed. A practical rule:visible content should remain written for readers; markup should not promise a display that no longer exists; teams should avoid maintaining code only for a retired feature; changes should be tested on a sample before a large cleanup.If your CMS or theme automatically adds FAQ markup, check whether it still creates technical debt: testing errors, inconsistencies between visible text and markup, maintenance overhead, or internal reports that no longer matter. How to adapt SEO reporting Teams that tracked FAQ impressions should change their dashboards. Keep tracking:organic clicks by page; total web impressions; average position, interpreted carefully; main queries; conversions or useful actions on site; performance of articles that contain FAQs, independently from the old appearance.Remove or annotate:targets for FAQ rich result impressions; unannotated 2025/2026 comparisons; reports attributing a drop in FAQ appearance to content decline; automatic recommendations such as “add an FAQ to win more space in Google”.When a display format disappears, reports should be annotated, especially when non-SEO teams read the dashboard. FAQs in generative search Google says SEO best practices remain relevant for its generative AI features. Helpful, original and non-commodity content remains the foundation. Google also says there is no special markup to add for appearing in generative AI features in Search. This reinforces a simple idea: FAQs should not be treated as a visibility hack. They should make content clearer, more verifiable and more useful. A well-written FAQ can improve understanding of a complex topic. An artificial FAQ does not become more valuable in a generative interface than it was in classic search results. A page-by-page decision method For each article with a FAQ, ask five questions:Does the FAQ answer questions the article body does not address clearly? Do the answers add nuance, limits or action? Are the questions phrased like real reader questions? Does the block improve mobile reading? Is maintaining the markup still justified?If the answer is no to three or more questions, the FAQ should be removed or rewritten. Conclusion The end of FAQ rich results is not the end of editorial FAQs. It ends a bad incentive: adding FAQ blocks only to take up more space in Google. For analytics, SEO and privacy content, FAQs remain useful when they serve understanding. They should clarify, reduce misunderstandings, answer objections and make the article more actionable. The right decision is not to keep or remove every FAQ. The right decision is to treat FAQs as an editorial component, not a SERP shortcut. SourcesGoogle Search Central - Latest documentation updates Google Search Central - Search Console data anomalies Google Search Central - A new resource for optimizing for generative AI in Google Search Google Search Central - AI features and your website