FAQ Schema in 2026: Should You Still Use FAQPage Markup?

Google's FAQ rich result is gone.

As of May 7, 2026, Google no longer shows the FAQ rich-result feature in Search. In June, Google removed the FAQ structured-data documentation from Search Central because the feature was no longer supported.

That creates an obvious question for websites that spent years adding FAQPage markup: should you keep it, remove it, or replace it with something else?

The answer depends on why the markup exists. If your only reason for implementing FAQPage was to earn expanded FAQ results in Google Search, that benefit no longer exists. If your site already generates accurate FAQPage markup for other semantic or technical purposes, however, the Schema.org type itself still exists and there is no need to panic-delete it simply because Google stopped displaying its former rich result.

What happened to FAQ rich results?

Google began reducing FAQ rich-result visibility years before removing the feature completely.

In 2023, Google limited FAQ rich results primarily to well-known government and health websites. For most commercial sites, the familiar expanded questions beneath a Google result largely disappeared.

In May 2026, Google went further and retired the feature entirely. Google subsequently removed the FAQ rich-result documentation from Search Central.

This means a valid FAQPage implementation no longer makes a page eligible for a Google FAQ rich result because there is no longer a Google FAQ rich-result feature to become eligible for.

That is different from a structured-data error or manual action. Google did not announce that FAQ content itself was bad, nor did Schema.org eliminate the FAQPage vocabulary. Google simply stopped supporting that particular visual Search feature.

Does FAQPage schema still exist?

Yes.

FAQPage remains part of the Schema.org vocabulary and describes a web page that presents one or more frequently asked questions. A technically valid implementation can still represent the relationship between visible questions and their publisher-provided answers.

A basic JSON-LD implementation can look like this:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you offer weekend appointments?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Saturday appointments are available at select locations."
      }
    },
    {
      "@type": "Question",
      "name": "Can I reschedule an appointment online?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Existing customers can reschedule through the account portal."
      }
    }
  ]
}

That markup can still be valid Schema.org. What you should not say in 2026 is that adding it will produce a Google FAQ rich result.

This is an important example of the distinction covered in our broader schema markup guide: Schema.org contains a wider vocabulary than the structured-data features Google currently supports in Search.

Should you remove FAQPage schema now?

Not necessarily.

If accurate FAQPage markup is already being generated cleanly by your CMS and maintaining it creates little or no operational burden, there is no emergency reason to remove it solely because Google's Search feature disappeared.

But there is also little reason to preserve a complicated FAQPage implementation merely out of fear that removing it will hurt Google visibility.

The better question is whether the markup still has a purpose.

Structured data is only useful when it accurately describes the page and has a reason to exist. The disappearance of a Google search feature is a good opportunity to remove markup that was being maintained only because an old SEO checklist said every FAQ needed schema.

Does FAQ schema help Google AI Overviews or AI Mode?

There is no documented requirement to add FAQPage markup for Google AI Overviews or AI Mode.

Google's current guidance specifically says there is no special Schema.org markup required for its generative AI Search features. Google also cautions site owners against overfocusing on structured data as an AI-search optimization technique.

That means the old argument that FAQPage markup makes an answer more likely to be extracted into an AI Overview should not be presented as established fact.

A useful FAQ can certainly answer a question that someone later asks in Search. The answer may be relevant to an AI Overview just as useful information elsewhere on a page may be relevant. But that is an argument for publishing good information—not evidence that the FAQPage type causes Google to select the answer.

If AI visibility matters to the business, measure it directly rather than using schema implementation as a proxy. Our guide to measuring AI visibility and citation share covers that distinction.

Does FAQ schema help ChatGPT, Gemini, Claude or Perplexity?

There is no universal public rule stating that FAQPage markup causes these systems to cite, quote or recommend content more frequently.

Different AI products use different retrieval systems, indexes, search providers, crawlers and model architectures. Their behavior also changes over time.

Schema.org markup can provide a machine-readable representation of information, but that broad technical fact should not be converted into a promise that an AI system will use a particular FAQ answer because it has been marked up.

The safer principle is the same one we apply elsewhere in LSEO's GEO work: make the visible answer accurate, useful and accessible first. Add structured data when it serves a legitimate technical purpose. Then measure what the external system actually does.

FAQ content and FAQ schema are different decisions

Removing or skipping FAQPage markup does not mean you should remove useful FAQs from a website.

A good FAQ section can still help a prospective customer understand pricing, eligibility, timing, compatibility, policies, implementation or other questions that affect a decision. FAQs can also reduce customer-service friction and allow a page to address useful long-tail questions naturally.

The question to ask is whether the FAQ belongs on that page.

A service page may benefit from a few concise questions that resolve objections before someone contacts the company. A complex product may need questions about compatibility or installation. A large help center may need extensive question-based support content.

By contrast, adding generic questions such as “Why choose our company?” to every page simply because an SEO template expects an FAQ block usually creates repetitive content rather than meaningful information.

The content decision should therefore be made independently of the schema decision.

FAQPage is not the same as QAPage

One tempting response to Google's FAQ deprecation is to replace FAQPage with QAPage. Do not do that unless the content actually fits QAPage.

They represent different content models.

FAQPage describes a page containing multiple frequently asked questions and answers, typically supplied by the publisher.

QAPage is intended for a page focused on a single question and its answers. Google's current QAPage documentation specifically says not to use QAPage markup for FAQ pages containing multiple questions.

Structured data should describe the content you actually have. Changing the label simply because one Google feature was retired creates inaccurate markup rather than a replacement SEO strategy.

Can you still validate FAQPage markup?

Yes, but be clear about what validation proves.

Because Google no longer offers an FAQ rich-result feature, validating FAQPage markup should not be interpreted as evidence that the page can earn a Google FAQ result.

If you intentionally maintain FAQPage markup as Schema.org structured data, a Schema.org validator can help identify syntax and vocabulary problems.

Google's Rich Results Test is best used for structured-data features Google currently supports in Search. A successful structured-data test never proves that a search feature will appear anyway; Google does not guarantee rich-result display even for supported markup.

What should existing websites audit?

If your site implemented FAQPage over the last several years, the 2026 change is a good reason to conduct a simple cleanup.

First, identify where FAQPage is generated. It may come from an SEO plugin, theme, page builder, custom CMS module or tag-management implementation.

Then check whether the markup reflects real visible FAQ content. If a page no longer contains the questions but an old plugin still emits the JSON-LD, the markup should be corrected or removed.

Look for multiple plugins producing competing FAQPage objects. Also check whether answers in the markup still match what customers see after content updates.

Finally, decide whether maintaining the markup has an actual purpose now that Google's FAQ rich result is gone.

This is the same discipline we apply to other structured information. Our data consistency guide explains why duplicate or stale machine-readable facts should be treated as a governance problem rather than left indefinitely because they once supported an SEO tactic.

What should marketers do instead?

Put the effort back into the answer itself.

If customers repeatedly ask a question, answer it where it is most useful. Make the response accurate, specific and easy to find. Link to deeper information when the question requires more detail. Remove old answers when products, policies or regulations change.

For Google Search, continue following normal SEO fundamentals. Google's current guidance for AI Overviews and AI Mode emphasizes useful, original content, crawlability, indexability, internal linking and an overall technically sound website. There is no FAQ-specific AI markup requirement that replaces those fundamentals.

FAQ content can absolutely remain part of that strategy. It simply no longer needs to be justified with promises about a Google FAQ rich result or automatic AI extraction.

Frequently Asked Questions

Did Google discontinue FAQ schema?

Google discontinued the FAQ rich-result feature in May 2026. That is different from Schema.org discontinuing the FAQPage type. FAQPage still exists as a Schema.org vocabulary type, but it no longer makes a page eligible for a Google FAQ rich result because Google no longer shows that feature.

Should I remove FAQPage markup from my website?

Not necessarily. If the markup is accurate, generated automatically and inexpensive to maintain, there is no urgent need to remove it solely because Google retired its FAQ rich result. However, if you are maintaining FAQPage only for Google visibility, or the markup creates technical debt or data-quality problems, removing it can be reasonable.

Does FAQPage schema help Google AI Overviews?

Google does not document FAQPage schema as a requirement or special optimization for AI Overviews or AI Mode. Google says no special Schema.org markup is required for its generative AI Search features.

Can FAQPage schema increase citations in ChatGPT or other AI systems?

There is no universal documented rule showing that FAQPage markup directly increases citations across ChatGPT, Gemini, Claude, Perplexity or other AI products. If AI visibility matters, measure citations and prompt visibility separately rather than assuming schema creates the outcome.

Should I change FAQPage markup to QAPage?

Only if the page actually meets the QAPage content model. QAPage is designed around a single question and its answers. It should not be used simply as a replacement for an FAQ page containing multiple publisher-written questions and answers.

Are FAQ sections still good for SEO?

They can be when they answer genuine user questions and support the page's primary purpose. FAQ content should be judged on its usefulness, relevance and ability to help users—not on whether it receives FAQPage markup.

Can I still use JSON-LD for FAQPage?

Yes. FAQPage still exists in Schema.org and can be represented using JSON-LD. The important distinction is that Google no longer offers the FAQ rich-result feature that historically motivated many sites to add the markup.