FAQ Schema Not Showing in Google? Here's Why (2026)

Your FAQ schema isn't showing in Google because Google no longer shows FAQ rich results for any website. The feature stopped appearing on May 7, 2026, and Google removed its FAQ documentation on June 15, 2026, so valid FAQPage markup can't bring the dropdowns back no matter how you fix the code.

This guide is for store owners, developers and SEO leads who were handed a "fix our FAQ schema" ticket. You'll get the timeline, a symptom, cause and fix table, a step-by-step diagnosis that separates "the FAQ box is gone" (expected) from "the whole page is missing" (a real problem), what each testing tool can and can't tell you, and a clear keep-or-remove decision. If you want the background on what FAQ schema is and how to add it, start with our FAQ schema guide.

The short answer: Google retired FAQ rich results

Google's documentation updates changelog has two entries that settle the question. On May 8, 2026, Google added a deprecation notice to its FAQ rich result documentation, saying the feature would no longer appear in Google Search starting May 7, 2026. On June 15, 2026, it removed the documentation, saying the FAQ rich result feature is no longer shown in Google Search results.

That changes the diagnosis. Before 2026, a missing FAQ rich result could mean a markup error, a policy problem or a site that didn't qualify. Now the expected outcome for every site is no FAQ rich result. Rewriting the JSON-LD, switching plugins, requesting indexing or building authority won't change it.

What the retirement does not mean: your page can still rank as an ordinary result, your visible FAQ still helps shoppers, and FAQPage is still a valid type on Schema.org. The retirement removed a display feature, not the page.

Timeline: how FAQ rich results disappeared

Many troubleshooting guides online were written for the 2023 rules, which is why you'll still see advice about "authoritative government and health sites." That exception is gone.

In its August 2023 announcement, Google said FAQ rich results would only be shown for well-known, authoritative government and health websites, and that for all other sites the result would no longer be shown regularly. From that point, most e-commerce stores lost the feature. The May 2026 retirement removed it for the remaining sites, including government and health publishers.

Why advice from 2023 to 2025 misleads you now

• "Make your site more authoritative" only ever applied to the government and health exception, and that exception no longer exists.
• "Check the FAQ enhancement report" assumes a report for a feature Google no longer shows.
• "Use the Rich Results Test to see if you're eligible" assumes Google still tests for a feature it has retired.

Symptom, cause, fix: a diagnosis table

Start with the symptom you actually see. Most "FAQ schema not showing" reports fall into one of these rows, and only some of them need engineering time.

Only the last four rows are real problems, and only the "whole page is missing" row affects rankings. The rest are expected behavior after the retirement.

Is your page missing, or only the FAQ box?

This is the question that decides whether you have a problem at all. Search for a distinctive phrase from the page in Google, or search for the page's main query and look for your URL. Then check Search Console.

If the page appears as a normal result

You're done diagnosing. Your page is indexed and eligible to rank. The missing dropdowns are the retirement. Any further work is about improving the page, not repairing it.

If the page doesn't appear at all

The FAQ markup was never the cause. A page that's missing from Google has an indexing problem, and FAQPage markup has no effect on whether a page is indexed. Common causes on e-commerce sites include a leftover noindex tag from a staging copy, a robots.txt rule blocking a folder, a redirect to another URL, or a canonical tag pointing somewhere else. Our robots.txt tester and redirect checker rule out two of those in a minute.

If Google chose a different canonical

Google's URL Inspection documentation notes that you can only see the canonical Google chose in the indexed data, and that the live test can't predict it. If Google picked a different URL, such as a collection-scoped product URL on Shopify, inspect that version too. You may be checking markup on one URL while Google indexes another.

How to diagnose it, step by step

Work through these in order and stop as soon as you find the answer. Most tickets end at step 2.

1. Write down the symptom and the URL. Note the exact URL, when the FAQ markup went live, and what you expected to see. "No FAQ dropdowns" and "page not in Google" are different tickets.
2. Check the date. If the dropdowns disappeared on or around May 7, 2026, or never appeared after that date, the retirement explains it. Stop here unless something else is wrong.
3. Confirm the page is indexed. Open URL Inspection in Search Console. Check whether the URL is on Google, when it was last crawled, and which canonical Google selected.
4. Confirm the markup is live. Run the live URL through our schema validator or the Schema Markup Validator. Look for exactly one FAQPage block with every question you expect.
5. Compare source and rendered HTML. In URL Inspection, view the crawled page's HTML. If your FAQ or its markup is added by JavaScript, make sure it appears in the rendered version.
6. Match markup to the page. Read each question and answer in the JSON-LD against the visible FAQ. Google's structured data guidelines say not to mark up content that isn't visible to readers.
7. Check you didn't break anything else. When cleaning up FAQ code, make sure Product, Offer, review and breadcrumb markup still validates. Those features are still supported, and they're worth far more to a store than FAQ markup now.

What each testing tool can and can't tell you

A green result from one tool answers one narrow question. Mixing them up is how teams end up chasing a feature that doesn't exist.

A generator can't change any of this either. Our FAQ schema generator produces clean FAQPage JSON-LD, which is useful for accuracy, but no generator can produce a Google feature that's been retired.

Why your FAQ impressions dropped in Search Console

Google documents this one directly. Its data anomalies page for Search Console says that as of May 7, 2026, FAQ rich results are no longer appearing in Google Search, so you'll see a drop in reported FAQ impressions in the Performance report and in the FAQ rich results report.

That's a reporting change, not a penalty. To read your data honestly:

• Annotate May 7, 2026 in Looker Studio, GA4 or wherever you report, so nobody mistakes the drop for a site problem.
• Stop reporting FAQ impressions as a KPI. Report page-level clicks, the queries each page wins, and the revenue those visits produce.
• Compare like periods. Look at the same weeks year over year, and note other changes such as theme releases, migrations and seasonal demand.
• Check clicks, not just impressions. A drop in FAQ impressions with steady page clicks means the retirement cost you screen space, not traffic.

Our Search Console comparison tool lines up two date ranges so you can see whether the pages themselves lost clicks.

Should you keep or remove FAQ schema?

Keep it if it's accurate. When Google first limited FAQ rich results in 2023, it said there was no need to proactively remove the markup, because structured data that isn't used does not cause problems for Search. Nothing in the 2026 retirement changed that. Keep the visible FAQ for certain: it's where the value is.

Those results come from testing the on-page FAQ accordion that shoppers read, not the markup. Removing the FAQ section because Google retired a display feature would throw away one of the most reliable conversion wins in QCK's data. See every result on our A/B test results page.

What about AI answers?

Some teams keep FAQ schema hoping it will get them cited in AI Overviews or ChatGPT. Google's guide to optimizing for generative AI features says structured data isn't required for generative AI search and that there's no special Schema.org markup you need to add. Keep FAQPage for accuracy if you like, but don't treat it as the fix for AI visibility. Clear, specific, crawlable answers are.

What to fix instead

The hours you would have spent on FAQ rich results go further here:

• Product structured data. Price, availability, shipping and return details still feed supported features. Our Product schema guide for Shopify covers it.
• The visible FAQ. Answer real buying questions on product and collection pages. Our Shopify FAQ schema guide shows how to build the section and its markup from one source.
• Indexing hygiene. Canonicals, redirects and noindex tags decide whether pages appear at all.
• Answer quality for AI search. Run key pages through our AEO checker to see how easy your answers are to quote.

If you'd rather have someone check it for you, our technical SEO team can audit your structured data and indexing, or you can book a free call.