{"id":43902,"date":"2026-05-10T19:37:10","date_gmt":"2026-05-10T09:37:10","guid":{"rendered":"https:\/\/digitalnomadshq.com.au\/?p=43902"},"modified":"2026-05-19T11:50:50","modified_gmt":"2026-05-19T01:50:50","slug":"google-retires-faqs","status":"publish","type":"post","link":"https:\/\/digitalnomadshq.com.au\/blog\/google-retires-faqs\/","title":{"rendered":"Google Retires FAQ Rich Results: The Schema Still Matters"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t
\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

TL;DR<\/b><\/p>\n

Google has switched off the expandable Q&A boxes that used to appear under some search listings. The change took effect on 7 May 2026.<\/p>\n

This isn’t sudden. Google restricted the feature in 2023 to government and health sites, and has now removed it entirely.<\/p>\n

You don’t need to delete the FAQ code from your website. Google still uses it to understand your pages, even though the visual feature is gone.<\/p>\n

Stop adding FAQ sections just to grab more space in search results. Keep them where the questions and answers are genuinely useful.<\/p>\n

The bigger shift is AI search. Effort that used to go into SERP tricks should now go into being clearly understood by AI Overviews and similar tools.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\n\t\t\t\t\t\t<\/span>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

For nearly a decade, FAQ schema<\/a> has been one of the most overused tactics in SEO.\u00a0<\/p>

Add structured data<\/a>, get an expanded SERP listing, lift your click-through.\u00a0<\/p>

As of 7 May 2026<\/b>, the rich result is gone, and a long-running shortcut has finally closed.<\/p>

Google confirmed the change in its developer documentation.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Google\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

\u00a0<\/p>

FAQ rich results no longer appear in Google Search, and the supporting infrastructure is being retired across the rest of the year:<\/p>

June 2026: FAQ search appearance, the rich result report, and Rich Results Test support all retired<\/b><\/p>

August 2026: Search Console API support for FAQ rich results removed<\/b><\/p>

If your reporting workflows depend on FAQ rich result data, export it now. After August it won’t be retrievable.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

This Was Always Going to Happen\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The 2026 update isn’t a surprise.\u00a0<\/p>

It completes a phase-out Google began in August 2023, when it restricted FAQ rich results to authoritative government and health websites. Commercial sites lost the feature overnight, even with perfectly valid schema in place.<\/p>

The 2023 restriction was a response to abuse.\u00a0<\/p>

FAQ schema had become a SERP real estate hack: sites added artificial Q&A blocks with questions nobody had asked, padded with answers written for Google rather than users.\u00a0<\/p>

The result was a degraded SERP and an SEO industry chasing a tactic that had already lost its meaning.<\/p>

What happened on 7 May simply finishes the job.\u00a0<\/p>

The display feature is now retired for every category of site, including the gov and health domains that kept it alive between 2023 and now.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

The Distinction Most Coverage Is Missing\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The headline story is that FAQ rich results are dead.\u00a0<\/p>

The more important story is that FAQ structured data is not.<\/p>

Google has stated explicitly that the markup will continue to inform how its systems understand pages, even though it no longer renders a visual rich result. That distinction is the one worth holding onto.<\/p>

Schema markup is a comprehension layer.\u00a0<\/p>

It tells Google, in machine-readable form, what a page is about.\u00a0<\/p>

Rich results are a separate display feature that uses some of that data to render visual SERP elements. Google has retired the display.\u00a0<\/p>

The comprehension layer remains, and it’s the one that matters now.<\/p>

This isn’t a small technicality.\u00a0<\/p>

AI Overviews, AI Mode, and the broader AI search ecosystem all depend on the comprehension layer to decide which sources to retrieve and which to cite.\u00a0<\/p>

Clear, well-structured pages get pulled into AI-generated answers.\u00a0<\/p>

Pages that Google can’t parse cleanly do not.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Should You Remove FAQ Schema?\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Our recommendation: leave it in place.<\/b><\/u><\/p>

The markup isn’t doing anything visible, but it isn’t hurting anything either.\u00a0<\/p>

Other search engines may still process it, and Google has explicitly said the schema continues to inform how it understands your pages.\u00a0<\/p>

The cost of stripping it out outweighs the upside. If you keep it, make sure the questions and answers reflect real user intent rather than padding.<\/p>

What you should stop doing is treating FAQ schema as a CTR tactic. The shortcut that defined a lot of SEO templates between 2020 and 2023 has run its course.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

The Bigger Shift This Sits Inside\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

FAQ rich results were always a transitional feature.\u00a0<\/p>

They expanded the snippet, but they still pushed users to your page for the full answer.\u00a0<\/p>

The current direction of search is different.\u00a0<\/p>

Google ingests your content and returns a synthesised response under its own UI, often without an obvious click anywhere.<\/p>

This is the environment our Searchlight framework is built for. Brands that win in AI search are not the ones gaming SERP features.\u00a0<\/p>

They’re the ones publishing genuinely authoritative content with the structural clarity that AI systems can extract, and the entity-level signals that get them recognised across the broader retrieval ecosystem.<\/p>

The retirement of FAQ rich results is a small story. The shift it sits inside is the one worth getting in front of.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

What We're Telling Clients\n\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
  1. Audit pages currently using FAQPage schema and note baseline metrics from before 7 May.<\/li>
  2. Export historical Search Console reports for FAQ-rich appearances before the August 2026 API retirement.<\/li>
  3. Monitor affected pages for CTR changes over the 6 to 12 weeks following 7 May.<\/li>
  4. Stop deploying FAQ blocks as a templated tactic where the Q&A isn’t genuinely useful.<\/li>
  5. Redirect that effort into AI search visibility: clear answers, strong entity signals, and schema that represents what’s actually on the page.<\/li><\/ol>
    \u00a0<\/div>

    If you want a review of where your structured data sits today, and how it’s positioning you for AI search rather than for SERP features that no longer exist, get in touch.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

    \n\t\t\t\t\t
    \n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

    For nearly a decade, FAQ schema has been one of the most overused tactics in SEO. As of 7 May 2026, the rich result is gone. Our editorial take on what changed, why it was always going to happen, and why the schema still matters for AI search.<\/p>\n","protected":false},"author":2,"featured_media":43913,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","footnotes":""},"categories":[71],"tags":[72],"class_list":["post-43902","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-seo","tag-seo"],"acf":[],"_links":{"self":[{"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/posts\/43902","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/comments?post=43902"}],"version-history":[{"count":15,"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/posts\/43902\/revisions"}],"predecessor-version":[{"id":43919,"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/posts\/43902\/revisions\/43919"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/media\/43913"}],"wp:attachment":[{"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/media?parent=43902"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/categories?post=43902"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/digitalnomadshq.com.au\/wp-json\/wp\/v2\/tags?post=43902"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}