Google stopped showing FAQ rich results in Search starting May 7, 2026, and recorded the change in its Search Central documentation updates on May 8. If your pages carry FAQPage markup, the first thing to do is open a few of them and confirm that every marked-up question and answer is visible on the page.

The change reaches ordinary commercial, editorial and nonprofit sites. Google had already limited the feature in August 2023 to well-known, authoritative government and health websites. The May notice retires the feature in Google Search altogether.

You do not need to delete anything today. Valid FAQPage markup left in place does not create a Google Search error, and FAQPage remains a valid Schema.org type. What changes is the decision: keep, trim or remove the markup page by page, and keep the visible FAQ itself, because readers still use it.

Key takeaways

  1. FAQ rich results endedFAQ rich results stopped appearing in Google Search on May 7, 2026, and Google removed the feature documentation on June 15, 2026.
  2. Confirm what is visibleConfirm every marked-up question and answer is visible on the page, and look for duplicate FAQPage blocks from a plugin or theme.
  3. Keep, trim or removeDecide page by page. Keep accurate, inexpensive markup, trim stale entries, and remove markup when the visible FAQ is gone or inaccurate.
  4. Valid markup causes no errorFAQPage remains a valid Schema.org type, and leaving valid markup in place does not create a Google Search error.
  5. Keep the visible FAQKeep useful questions and answers on the page, because readers still use them. Update the text and the markup together when a price or policy changes.
  6. Reports will changeGoogle planned to drop the FAQ report and Rich Results Test support in June, and Search Console API support in August. Expect that data to stop appearing.

What Google changed and when

Google's documentation updates page lists the change under May 8, 2026. The entry reads: "Added a deprecation notice to the FAQ rich result documentation," and gives the reason as "This feature will no longer appear in Google Search starting May 7, 2026." The notice on the FAQ page itself begins with a plain statement that FAQ rich results are no longer appearing in Google Search.

The same notice describes what follows. Google planned to drop the FAQ search appearance, the FAQ rich result report and support in the Rich Results Test in June, and to remove FAQ support from the Search Console API in August, so that people who call the API have time to adjust. Expect those reports and tests to stop showing FAQ data on that schedule.

The earlier step matters for context. In its August 8, 2023 announcement, Google said FAQ rich results from FAQPage markup would be shown only for "well-known, authoritative government and health websites." It also said other sites could leave the markup in place, because unused structured data did not cause problems in Search, even though it had no visible effect there.

How Google's FAQ rich results changed

  1. August 8, 2023Google limited FAQ rich results to well-known, authoritative government and health websites.
  2. May 7, 2026FAQ rich results stopped appearing in Google Search, as the May 8 entry describes the effective date.
  3. May 8, 2026Google added a deprecation notice to its FAQ rich result documentation.
  4. Announced May 8, 2026Google planned to drop the Search Console appearance, report and Rich Results Test support in June, and API support in August.

Check that every marked-up answer is visible

Start with the pages that matter most to you, such as top service pages, product pages and policy pages. Open the page as a visitor would, find the FAQ section, and compare it with the Question and Answer entries in your JSON-LD. Each question should appear on the page, and the text of each answer should match the visible answer closely.

A bearded man in a cardigan compares a laptop screen with a printed sheet at a dental office reception desk in the evening
Figure 1. Compare each marked-up question with what visitors can actually read on the page.

Google's general structured data guidelines say structured data should represent the page and should not describe hidden content. That applies whether or not a feature still exists. Markup that lists answers nobody can see, answers hidden with CSS, or questions that were deleted from the page months ago is the first thing to fix.

Many sites also carry the same FAQ block on dozens of pages, often added by a theme, an SEO plugin or an app. Look for duplicates, including two FAQPage blocks on one page, one from a plugin and one pasted by hand. If you are unsure what your platform outputs, view the page source and search for FAQPage. The guide on fixing missing field schema warnings shows how to read what a page actually contains.

Decide page by page: keep, trim or remove

Once the markup matches the page, the decision is about upkeep and usefulness, not about Google alone. The visible FAQ is the asset. The markup is a machine-readable description of it, and it earns its place only where it stays accurate and costs little to maintain.

  • Keep the markup where the FAQ is visible, accurate, useful and inexpensive to update. Valid markup is a reasonable way to describe the page for tools that read Schema.org.
  • Trim it where the page repeats questions, carries stale answers or holds thin entries that add nothing for a reader.
  • Remove it where the visible FAQ is gone, the answers are inaccurate, the markup is hidden or duplicated, or the upkeep outweighs its likely value to tools other than Google.

Do not remove useful FAQ content because Google retired the display. Questions and answers still help visitors understand products, services, policies and procedures, answer objections before they contact you, and cut down repeat support questions. Do not keep markup only because it might help some unnamed AI system either, since no provider promises a result from FAQPage.

What happens to valid markup you leave in place

FAQPage is still defined by Schema.org as a web page presenting one or more frequently asked questions, with Question and Answer describing the entries. A valid Schema.org type and eligibility for a particular search feature are separate things, and the Google FAQ feature was only ever one consumer of the vocabulary.

So, leaving the markup does not automatically cause an error. It remains machine-readable data about your page, and it should be corrected or removed whenever the underlying FAQ changes or disappears. It should not be treated as a ranking, traffic or AI citation guarantee, because no provider promises one. The guide on whether schema markup helps SEO explains the difference between valid markup, eligibility and what searchers actually see.

Bing reads Schema.org and JSON-LD annotations, so the same FAQPage block serves it too; its structured data guide says annotations may improve or supplement search results but do not guarantee a rich result. Yandex does not support every Schema.org type and says markup must be correct, indexed and moderated before it can contribute to snippets (semantic markup FAQ).

For ChatGPT search, allow OAI-SearchBot to crawl the site; placement is not guaranteed. Perplexity's crawler guide covers crawler access and robots.txt handling. Keep pages crawlable and the visible answers clear, and read whether AI systems use schema markup for the full comparison.

Before and after markup

The markup itself does not need to change when Google retires a display. This is the kind of FAQPage block many sites added for Google, with fictional values on a reserved example domain. Both questions must also appear as visible text on the page.

json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does the Example Widget work without an account?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. The Example Widget works without an account on example.com."
      }
    },
    {
      "@type": "Question",
      "name": "How long does setup take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A typical setup takes about ten minutes."
      }
    }
  ]
}

Google's former FAQ documentation required FAQPage with mainEntity, each Question with name and acceptedAnswer, and each Answer with text. Those were requirements for the retired Google feature, not tests of Schema.org validity in general, so there are no current Google FAQ feature requirements left to meet.

Now suppose the second question is stale because the setup steps changed and nobody has time to rewrite it. Trimming means keeping only the entry that is still accurate, visible and worth maintaining, and deleting the other entry from the markup and from the page together.

json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does the Example Widget work without an account?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. The Example Widget works without an account on example.com."
      }
    }
  ]
}

If the whole visible FAQ comes off a page, remove its FAQPage markup too. To build a block for a FAQ that is visible and worth keeping, the FAQ schema generator writes valid JSON-LD from the questions and answers you enter, and you replace the example values with the text that appears on your page.

A page card with two rows linked by thin blue lines to matching rows on a code panel, with one unconnected dashed row
Figure 2. Markup should describe what the page shows, and an entry with no matching text is the one to remove.

Reports and tests that will change

Because Google planned to drop the FAQ search appearance, the rich result report and Rich Results Test support in June, a page that once showed FAQ data in Search Console will stop showing it. That is the announced change rather than a fault in your markup, and it should not send you looking for an error. The Search Console API follows in August, so anything that reads FAQ rich result data through the API should be adjusted before then.

When you check a page afterwards, use tools that fit the question. A JSON syntax check tells you whether the code parses. A Schema.org check tells you whether the types and properties exist. Neither says that a search engine shows anything, since displays are each provider's decision. If you are working through leftover warnings, the guide on fixing missing field schema warnings separates errors that matter from those that do not.

Before May 2026 and after May 8, 2026

Hover over or tap a row to highlight it. On small screens the table scrolls sideways.

AreaBefore May 2026After May 8, 2026
Google displayA visible FAQ with FAQPage markup could be eligible, subject to Google's restrictions.Google FAQ rich results no longer appear.
Search ConsoleReported FAQ enhancement and appearance data.Google announced removal of the FAQ appearance and report.
Rich Results TestSupported FAQ testing.Google announced removal of FAQ support from the test.
Reason to keep markupOften maintained for Google visibility.Keep it only if accurate, visible and worth maintaining for other tools.
Visible FAQ for readersHelped users on the page.Still helps users on the page.

Keep the visible FAQ accurate

A short maintenance routine is enough. Review each FAQ when the page it sits on changes, because a changed price, policy or process makes an old answer wrong in both the text and the markup. Remove questions nobody asks, merge near-duplicates, and keep answers short enough to scan.

If markup is generated by a plugin, theme or app, check its settings before editing anything by hand. Turning off a block in one place and leaving a second copy elsewhere is a common cause of duplicated FAQPage data. Whichever way you decide for a page, keep the visible text and the markup saying the same thing.

Update, June 15, 2026

Google removed its documentation for the FAQ rich result feature on June 15, 2026. The documentation updates page records the reason as "The FAQ rich result feature is no longer shown in Google Search results, as announced in the changelog entry in May 2026."

The advice above still holds. Keep useful FAQ content visible on the page, and keep, trim or remove FAQPage markup according to accuracy, visibility, other consumers and the cost of maintaining it.

Questions people ask

Will leaving FAQPage markup cause errors in Search Console?

Valid FAQPage markup does not automatically create an error because Google retired its FAQ display, and Google said in 2023 that sites could leave unused structured data in place. The FAQ appearance and report are among the items Google announced it would drop, so you should expect to stop seeing FAQ data there.

Does Bing support FAQPage markup?

Bing's structured data guide says Schema.org and JSON-LD annotations may help it understand a page but do not guarantee a rich result. The visible FAQ and accurate markup are the parts you control.

Does ChatGPT Search require FAQPage markup?

OpenAI says ChatGPT Search eligibility depends in part on allowing OAI-SearchBot to crawl your site, and that placement is not guaranteed. Check your robots.txt rules if you want the site to be eligible; adding markup is a separate choice.

Does Google AI Mode need special FAQ schema?

Google says pages must be indexed and eligible for a normal Search snippet, and that AI features have no additional technical requirements or special Schema.org markup. It also says structured data should match the visible text on the page.

Is this decision different on WordPress, Shopify, Wix, Squarespace or Webflow?

The decision is the same on any platform, because it depends on the visible FAQ and its upkeep. What differs is where the markup comes from, so find out whether your theme, app or SEO plugin adds it before you edit anything.

Quick check: validity and eligibility

Choose an answer to see feedback. Nothing is scored or saved.

Question 1 of 3

Does Google retiring FAQ rich results make FAQPage an invalid Schema.org type?

Question 2 of 3

Should a useful visible FAQ be deleted because the rich result is gone?

Question 3 of 3

What should FAQPage markup describe?

FAQ markup terms in plain language

Select a term to see its definition.

FAQPage. A Schema.org type for a web page presenting frequently asked questions.