If you manage a WordPress site, you may have noticed something disappear from your Google search listings back in May 2026. Those expandable question-and-answer dropdowns that used to sit under your links are gone. Many business owners took one look at that change and assumed their FAQ page schema was now dead weight. Some are paying developers to strip the code out entirely.
That instinct is understandable, and it is also a costly mistake. The visual feature went away, but the underlying structured data now does something arguably more valuable: it helps AI search engines read, trust, and quote your business. This article explains what actually changed, why the code still matters, and how to structure it so answer engines cite you.
What Google Actually Changed With FAQ Rich Results
On May 7, 2026, Google officially removed FAQ rich results from search listings worldwide. The expandable accordion dropdowns that once appeared under organic results vanished for every website, regardless of industry or size.
Google did not stop there. In June 2026, it removed the FAQ Search Appearance filter and the rich result report from Search Console, ending native tracking for those visual impressions. By August 2026, support was pulled from the Search Console API as well, closing the loop on the visual sunset.
Here is the part that gets lost in the panic. On June 12, 2026, Google updated its official developer documentation to confirm that FAQPage structured data remains fully supported, tested, and validated by its systems. The visual display went away. The data standard did not.
The removal of the visual accordion was Google cleaning up cluttered search listings to prepare for an AI-first index. The machine-readable data underneath became more useful, not less.
Why the confusion spread so fast
When Search Console stopped showing FAQ reports, many site owners assumed Google had abandoned the feature. Losing a dashboard metric feels like losing the whole tool. But reporting and functionality are different. The data still works exactly as designed; you simply cannot watch a specific chart for it anymore.
Why FAQ Page Schema Matters More for AI Search
Structured data is a set of tags you add to your page that describes your content in a language machines understand. Think of FAQ page schema as a translator sitting between your website and the AI systems trying to summarize it. It labels each question and its matching answer, so an engine doesn’t have to guess.
That translation layer has become important because AI Overviews now dominate the results your customers see. As of June 2026, AI Overviews appeared on 67 percent of commercial queries and over 78 percent of local business and healthcare searches, according to BrightEdge tracking. For a roofer, dentist, or fitness studio, that is most of your search traffic.
Citation data is where this gets concrete. A June 2026 study by Launchcodex analyzed 127,000 Google AI Overviews and found that pages with FAQPage schema were 3.2 times more likely to appear as a cited source than pages without structured data.
58.3% of cited sources across those 127,000 AI Overviews contained FAQPage schema (Launchcodex, June 2026).
40% higher selection rate as a source inside ChatGPT for pages using FAQ structured data (Authoritas analysis of 2025 data).
11.2% of total AI citation volume goes to FAQPage schema pages, even though they make up just 3.8% of indexed pages (Profound Strategy, Q2 2026).
Independent research supports the same direction. Frase published an analysis on why FAQ schema still matters for AI search, GEO, and AEO, arguing that the format helps generative engines extract clean question-and-answer pairs. The team at Georion reached a similar conclusion in their breakdown of whether FAQ schema is still worth it after Google’s May update, separating rich-result removal from the schema’s ongoing relevance for citations.
The First-Mover Advantage Hiding in This Change
Something ironic is happening across the industry. While the evidence points to FAQ page schema driving AI citations, many agencies and site owners are deleting their code because the Search Console reports disappeared. They are removing an advantage in the middle of a competitive window.
That window is unusually wide. As of December 2025, Frase estimated that only 12.4 percent of all websites used structured data of any kind. When most of your competitors have no machine-readable data, and some of those who do are now stripping it out, the field opens up for businesses that stay the course.
Consider what this means for a local service provider. If AI Overviews trigger on more than three-quarters of local queries, and structured data helps you get cited in those answers, the businesses that keep clean FAQ schema are positioned to claim answer-box real estate their competitors just walked away from.
The trust angle you cannot skip
E-E-A-T, which stands for Experience, Expertise, Authoritativeness, and Trustworthiness, has moved from a general quality idea to a hard filter for AI citations. Search systems now evaluate trust at the entity level, meaning they assess your business as a defined thing with verifiable details. Structured data is one of the clearest technical trust signals you can send.
A Semrush AI Search Visibility Study from April 2026 found that only 6 to 27 percent of frequently mentioned brands actually get cited by AI engines. The study attributed much of that gap to weak structured-data connectivity. Being talked about is not the same as being quoted, and schema helps close that distance.
How to Implement FAQ Page Schema the Right Way
The preferred format for FAQ page schema is JSON-LD, short for JavaScript Object Notation for Linked Data. It is a small block of code you place on the page that lists each question and its answer in a structure machines parse cleanly. The W3C oversees this standard, and Schema.org maintains the FAQPage vocabulary itself.
You do not need to hand-code anything in WordPress. Most quality SEO plugins and schema plugins let you add FAQ blocks that generate the JSON-LD automatically. The technical part matters less than getting the structure and the matching right.
Here is the sequence that keeps your markup working as an AI citation signal:
Write real questions your customers ask. Pull them from sales calls, emails, and your contact form. Vague filler questions will not earn citations.
Answer each one directly in the first sentence. AI engines extract concise, self-contained answers. Lead with the answer, then add context.
Make the questions and answers visible on the page. The text a human reads must match the text in your schema.
Generate the JSON-LD with your plugin. Let the tool build the code from your visible content so the two stay aligned.
Validate the markup. Use Google’s Rich Results Test or the Schema.org validator to confirm the code parses without errors.
If you want a fuller walkthrough of the code and setup decisions, this step-by-step schema markup guide for AI-powered SEO covers the implementation details for WordPress owners in depth.
The mismatch trap that quietly hurts you
The most common mistake in 2026 is putting questions in the JSON-LD that don’t appear in the visible page text. It feels efficient to stuff extra questions into the code to cover more ground. It backfires.
AI engines require a strict match between your schema and what a human actually sees. When the code claims a question that is not on the page, systems flag it as mismatched, and that damages the trust signal you were trying to build. Schema is a translator, not a place to hide content you did not write.
This is also the reason schema alone is not a shortcut. An Ahrefs test in May 2026 found that adding JSON-LD by itself did not produce an immediate citation lift when the visible content was thin. The lesson is not that schema fails. It is that schema amplifies strong, well-structured, visible answers rather than replacing them.
Where FAQ Schema Fits in Your Broader AI Strategy
FAQ page schema works best as one piece of a connected structured-data setup, not a standalone trick. It pairs naturally with Generative Engine Optimization (GEO) and Answer Engine Optimization (AEO), practices that shape content so generative systems and answer engines can use it directly.
To understand how these tags describe your business, it helps to know the broader schema markup definition and its role in local AEO. FAQ markup answers customer questions, while other schema types define your business identity, location, services, and reviews. Together they form the machine-readable profile AI engines rely on.
For a wider look at how these tags map your business as an entity that engines can verify, this overview of website schema markup shows how the pieces connect across a full site.
A quick checklist before you publish
Every question in the schema also appears visibly on the page.
Each answer opens with a direct, self-contained response.
The JSON-LD passes validation with no errors or warnings.
Questions reflect language your actual customers use.
The page covers a focused topic rather than a grab bag of unrelated questions.
Conclusion: Keep the Code, Sharpen the Content
The visual accordion is gone, and it is not coming back. But the underlying data behind your FAQ page schema is doing more for your visibility now than the dropdowns ever did. It translates your real expertise into a format AI systems can read, trust, and cite in the answers your customers now see first.
The businesses deleting their code are handing you an opening. With AI Overviews appearing on more than three-quarters of local searches and only a small slice of websites using structured data, keeping clean, accurate, well-matched schema is a practical way to stay visible. Write honest answers, keep them on the page, match your markup, and validate it.
At AgenticPress, we build WordPress sites with dual optimization in mind, covering both traditional SEO and AI search from the ground up. If you are unsure whether your current FAQ schema is helping or quietly hurting you, a structured-data audit is a sensible next step. Keep the code, strengthen the content behind it, and let AI engines find the answers your customers are already asking for.
Frequently Asked Questions
What happened to the visual FAQ dropdowns in Google search results?
Google removed the expandable FAQ dropdowns that previously appeared under some search results. This change, which took effect in May 2026, was part of Google's effort to clean up search listings and prepare for an AI-first index.
Does FAQ page schema still work if the visual dropdowns are gone?
Yes, FAQ page schema still works and is fully supported by Google's systems. While the visual display was removed, the underlying structured data now plays a more crucial role in helping AI search engines understand, trust, and cite your content.
Why should I keep my FAQ page schema if Google removed the reporting in Search Console?
You should keep your FAQ page schema because the data standard itself remains functional and valuable for AI search. Although Search Console no longer provides specific reports for FAQ rich results, the structured data significantly increases the likelihood of your content being cited in AI Overviews.
How does FAQ page schema help my website get cited by AI?
FAQ page schema acts as a translator, labeling questions and answers in a format that AI systems can easily read and trust. Pages with FAQPage schema are 3.2 times more likely to be cited as a source in AI Overviews compared to pages without it, according to studies.
What is the most common mistake people make with FAQ page schema implementation?
The most common mistake is including questions in the JSON-LD code that do not also appear visibly on the webpage. AI engines require a strict match between your schema markup and the on-page content; mismatches can damage your trust signal.