FAQ Rich Results Are Gone: Should You Delete FAQPage Schema?

Did Google remove FAQ rich results, and what changed?

FAQ rich results are the expandable question and answer lines that Google used to show under a search listing. Google stopped showing them in Search on May 7, 2026. FAQPage remains a valid Schema.org type, but it no longer earns extra space on the results page.

So if your pages carry FAQ markup, there is no need to panic. However, the extra visibility that markup once bought is gone. In this guide we explain what happened, which sources confirm it, and what we would do on real sites.

We took the facts from Google Search Central. Google added a deprecation notice to its FAQ structured data documentation. Then, in June 2026, the Search Central changelog recorded that Google removed the feature's documentation.

Our team has implemented FAQ markup on client sites for years. For that reason we treat this change as a practical question, not only as news.

When did FAQ rich results disappear, step by step?

The change did not happen in one day. Google first restricted the feature in 2023, then ended it in 2026. Knowing the timeline also explains why your old markup may not have produced a rich result for a long time.

The changelog gives no exact dates for Search Console, the Rich Results Test or the API. Because of that, we suggest you check those tools in your own account. We prefer not to guess at dates.

The takeaway is simple. The feature had been shrinking for years, so for most sites May 2026 is less a new loss than an official closing.

Is FAQPage schema still valid?

Yes, FAQPage is still a valid Schema.org type. The Schema.org definition is still in place. What changed is that Google no longer turns this markup into a special search appearance.

This distinction matters. Valid markup and a visible reward in Google are two different things. Also, Google's notice does not ask you to delete your markup; it only says the result feature is over.

Other search engines and AI systems may read schema data in their own ways. We know of no official guarantee about how any of them do it. Therefore, a flat claim such as "schema boosts AI visibility" would not be honest.

Should you delete FAQPage schema from your site?

For most sites there is no rush to delete it. If the schema mirrors the FAQ section on the page, it does no harm. However, if the markup describes answers that the page does not show, or answers that are out of date, you should fix or remove it.

When we decide, we ask four questions:

• Do visitors see the same questions and answers that the markup describes?
• Are the answers current and correct?
• Does someone maintain the schema, or does it come from an old plugin?
• Does the schema code add page weight or template complexity?

If all four answers are positive, you can leave the markup in place. If you hesitate on even one, put that page on your audit list. That way you decide from evidence instead of deleting blindly.

Will losing FAQ rich results hurt your traffic and clicks?

It might, but the size of the effect depends on your site. FAQ rich results took vertical space on the results page, so on some pages they lifted visibility. That extra space is gone now, so a small drop in click-through rate is possible.

On the other hand, Google already limited the feature for most sites in 2023. As a result, many sites will see no measurable effect from the May 2026 change. Do not guess; look at your own data first.

We do not quote a percentage, because Google has not published one. Instead, compare page-level clicks and impressions in Search Console. The next section shows how.

How do you measure the impact in Search Console?

First, list every page that carries FAQ markup. Then compare clicks, impressions and average position for those pages before and after May 7. A raw date comparison is not enough, so you also need to account for seasonality.

1. Open the Performance report and compare the period before May 7 with the period after it.
2. Filter by page so that only URLs with FAQ markup remain.
3. Note the change in clicks, impressions and CTR, then compare with the same period last year.
4. Look at queries: did question-style searches drop?
5. Read the result next to any other site updates that happened in the same window.

In this analysis the FAQ row may no longer appear in the search appearance filter. That is normal. Keep your own page list instead of relying on the filter, and save the results in a table so a check in three months takes minutes.

How do you audit the pages that use FAQ markup?

The audit has three stages: inventory, content quality and technical checks. First, crawl your site and list the pages that contain FAQPage. A crawler or a simple source search is enough for this.

Second, read the questions and answers on each page and ask whether they really help the visitor. For example, copying the same three questions onto hundreds of product pages adds no value. It also creates a maintenance burden and makes pages harder to tell apart.

Third, check that the JSON-LD is valid. Our schema generator can produce a clean structure that you can compare with your current code. Broken code is a bigger problem than the loss of a feature.

What should you check in schema plugins and CMS settings?

Many sites produce FAQ markup through a plugin or a theme block instead of by hand. The real risk is then not the code itself but that nobody remembers who switched the setting on. Look for an FAQ block or a question and answer module in your plugin settings.

• Check whether the plugin adds FAQ markup to every page automatically.
• Look for hard-coded JSON-LD in your template files.
• Test whether two plugins mark up the same question twice.
• Compare the page source before and after each plugin update.

Before you switch a setting off, try it on a few pages. Some plugins also remove other schema types when you disable the FAQ output, so a small test saves a lot of trouble.

Why is an FAQ section still worth keeping on the page?

An FAQ section completes the visitor's decision or research. Google's rich result never changed that value. If users find the answer on your page, they do not need to go elsewhere.

The section is also a natural way to capture long-tail queries. On a service page, answering "how long does it take", "who is it for" or "what does it cover" makes the topic of the page clearer.

• The visitor resolves a question without leaving the page.
• Your support team receives fewer repeated questions.
• The page answers a wider cluster of related queries.
• Objections soften before the sales conversation.

A good answer can also become a candidate passage for featured snippets and AI summaries. Our guide on how to win featured snippets covers this. We cannot promise results, but paragraphs that answer the question directly always help.

Does FAQ schema help with AI search visibility?

There is no firm, evidence-based answer here. Google says markup can help it understand a page, but we know of no official document showing that ChatGPT, Perplexity or Gemini reward FAQPage schema specifically.

So treat claims that present schema as an "AI trick" with caution. AI systems mostly read the text on the page. The real job is to write answers that are clear, short and sourced.

Our approach is simple: we build the content first and treat schema as a supporting signal. For the wider picture, read our article on SEO vs GEO vs AEO and our guide to writing content for AI Overviews.

How do you write a strong FAQ section?

A strong FAQ section starts from real customer questions. Sales conversations, support tickets and search data are the most reliable sources. Collect the questions instead of guessing them.

• Give each question one intent; do not open two topics in a single question.
• Let the first sentence of the answer respond directly.
• Keep most answers between 40 and 70 words.
• State concrete facts such as price, time and scope only if you can keep them current.
• Keep the list between 5 and 8 questions, because nobody reads a long one.

This structure gives both visitors and search systems a clear passage. Short answers also keep the page from bloating. Review the questions every quarter, since an outdated answer is worse than no answer.

For example, take the question "how long does a website take to deliver" on a web design page. A good answer states the time first and then explains what it depends on. A weak answer only says "it depends on the project".

Which mistakes should you avoid when removing FAQ markup?

The most common mistake we see is deleting all schema in a panic. If you delete the FAQ section along with the markup, you lose the real value. Removing the schema does not mean removing the content.

The second mistake is skipping tests at template level. After you switch off one plugin setting, you may discover later that other schema types vanished too. So try the change on a few pages first.

• Keep the FAQ text on the page; only trim the markup you do not need.
• Back up the page source before you change a plugin or theme setting.
• Check that other schema types are still in place after the change.
• Write down the change date so you can interpret later traffic swings.

Finally, do not leave the change to the developers alone. The content owner should also know why each question was marked up, because then the decision makes sense to both sides.

When should you keep FAQPage schema, and when should you remove it?

Every site is different, so we use a simple decision table. The suggestions below come from our field experience; they are not a Google rule.

In short, markup that matches the page and gets maintained can stay, while you should clean up the rest.

What if your competitors still use FAQ schema?

Seeing FAQPage in a competitor's source does not prove that it works. Most sites never change old plugin settings. Instead of copying their code, focus on the questions your own users ask.

Also judge why the competitor ranks above you by looking at page quality and link profile. Schema is rarely the reason for the gap. Answer depth, page speed and trust signals decide far more.

• Compare the depth of the answers with your own page.
• Measure page speed and mobile experience on both sides.
• Look at internal links and topic coverage.
• Keep schema as the last item on the list.

It also helps to look at the results page yourself. Our Google SERP preview tool shows how your own title and description will look in a listing.

How should e-commerce and service sites position their FAQ?

On a shop, the FAQ should remove buying obstacles such as returns, shipping, sizing and warranty. Giving this information before the cart is one of the most important conversion jobs. Schema now comes second.

On service sites, the FAQ answers questions about price, duration and process. For example, on an SEO consulting page, an honest range for "when do results show" builds trust. If you want to see what we offer, visit our SEO consulting page.

You can also collect general questions on one central page, which is how our FAQ page works. Questions about a specific product or service, however, belong on the relevant page.

A practical tip is to group questions by product type. In shoes, sizing questions come first; in electronics, warranty and compatibility do. That split answers the visitor's actual need.

Which structured data types still earn rich results?

This list changes over time, so we suggest you check the current source. Google's search gallery lists the supported types and the required fields. The end of one type does not mean the others will end too.

There is still a lesson: never assume any rich result is permanent. Google can update its guidelines and supported types. So use schema not only for visibility but also to describe the page accurately.

To see the big picture of schema types, our guide on what schema markup is is a good start. On the official side, Google's general structured data guidelines are the first document to read.

When you choose a type, look at what the page actually says. A product markup fits a product page and an article markup fits an article. Adding markup that does not match the page type rarely helps.

What did HowTo and other rich result changes teach us?

In August 2023, Google removed HowTo rich results from desktop and limited FAQ to well-known government and health sites. That was a sign of today's decision. In other words, narrowing features over time is no surprise.

For this reason, do not tie your strategy to one feature. A rich result is a bonus; the core job is content and technical health. If FAQ is gone today, another appearance may change tomorrow.

Our team plans schema work as "clarity of meaning" and not as a "visibility bonus". That way you lose nothing when a feature disappears. This example also teaches that Google tends to simplify its results page, so plan for removal as a normal scenario.

What should this change alter in your SEO strategy?

Three small adjustments are enough. First, put your schema in an inventory and give someone ownership. Second, rework the FAQ content around visitor needs and search intent.

Third, follow new rich result options regularly. Google's documentation and changelog are the primary sources for that. Rely on the official notice more than on social media commentary.

• Review the schema inventory every quarter.
• Keep FAQ content in line with real customer questions.
• Assign one person to watch official announcements.
• Report on clicks and conversions instead of rich result counts.

These adjustments need no extra budget. What you need is a habit of regular upkeep instead of setting markup once and forgetting it. To run technical and content work together, our AI SEO and GEO service offers a framework built for changes like this.

What should you do in the next 30 days?

The plan below suits small and mid-sized sites. No step should take longer than a week. On large sites the inventory stage may take more time.

1. In week one, list every page that carries FAQPage markup.
2. During week two, compare the on-page FAQ with the markup and flag mismatches.
3. By week three, fix or remove broken, unmaintained or duplicated markup.
4. Finally, prepare the before and after comparison in Search Console.
5. Afterwards, review the schema inventory every three months.

At the end you have a clean inventory, current FAQ content and a measured impact report. If you have hundreds of pages, start with the top fifty by traffic and spread the rest over the following months.

What are the common myths about FAQ rich results?

Whenever Google announces a change, wrong information spreads fast on social media. We saw the same with FAQ. The list below compares the most common beliefs with the official sources.

• "Google penalizes FAQ schema." We found no such claim in the documentation; the notice only says the appearance is over.
• "All structured data is useless now." That is wrong; only the FAQ feature ended, and you should check other types separately.
• "An FAQ section is pointless." Also wrong, because the content still helps visitors.
• "If I remove the schema, my rankings fall." No official statement supports this.

Most of these beliefs come from assuming that when a feature ends, the content behind it loses its value. The appearance and the content are two separate things. When in doubt, go back to the official documentation.

Which sources did we use to verify this?

The factual claims in this article rest on Google's own documentation. We checked the deprecation notice in the FAQ documentation, the June 2026 changelog entry and the 2023 Search Central blog post. We also reviewed the Schema.org definition separately.

• FAQ structured data documentation with the deprecation notice (Google Search Central).
• Updates and changelog page (Google Search Central).
• Post about HowTo and FAQ changes, August 2023 (Search Central Blog).
• Schema.org definition of FAQPage.

Official statements about how engines use markup internally are limited, so we made no firm claims there. If the situation changes, we will update this article.

What happens to FAQ schema next, and what should you do?

In short, FAQ rich results are over, while FAQPage remains a valid Schema.org type. Current, page-specific FAQ content on the page still has value. Unmaintained or mismatched markup, however, needs cleaning.

Do not rush the decision. Build the inventory first, then judge the pages one by one and measure the effect with your own data. This order also protects you from deleting things you did not need to delete.

If you want to audit your schema setup with us, get in touch. In our experience, this kind of audit usually produces a clear roadmap in a short time.