FAQ Content and FAQPage Schema: A Practical Guide

Google no longer shows FAQ rich results. Its documentation changelog recorded the deprecation in May 2026, stating that the feature “will no longer appear in Google Search starting May 7, 2026”, and in June 2026 Google removed the FAQ rich result documentation because the feature “is no longer shown in Google Search results” (Google Search documentation updates). Two things did not change. FAQPage is still a valid Schema.org type, and a well-written FAQ section can still be useful content for readers. Keeping those three things apart (reader value, valid vocabulary, Google feature) is what lets FAQ decisions be made on the right grounds.

Three separate questions

The mistake to avoid is collapsing them: adding FAQ sections only to get a rich result, or deleting useful FAQ content because the rich result is gone.

How the feature ended

The change happened in two steps.

1. August 2023: restriction. Google announced that FAQ rich results “will only be shown for well-known, authoritative government and health websites” (Google’s August 2023 announcement). For sites outside those two categories, the rich result stopped appearing then.
2. May 7, 2026: removal. The feature stopped appearing for everyone, and the documentation was removed the following month.

Pages and articles written between 2023 and 2026 that promise FAQ rich results, or describe them as available to “eligible” sites, are now out of date.

What to do with existing FAQPage markup

Google’s 2023 announcement addressed this: “While you can drop this structured data from your site, there’s no need to proactively remove it”, and “structured data that’s not being used does not cause problems for Search, but also has no visible effects in Google Search”. Google said the same about other retired features, such as the sitelinks search box in 2024.

So the decision is practical, not urgent:

• Keep it if it is accurate, matches visible content and costs nothing to maintain. Other systems that read Schema.org may use it, and it does no harm in Google Search.
• Remove it if it is generated automatically for content that is not really an FAQ, if it duplicates or contradicts the visible text, or if keeping it in sync adds maintenance burden.
• Do not add it expecting any visible effect in Google Search.

Whichever you choose, the content-matching rules that apply to all structured data still apply: Google’s structured data guidelines say not to mark up content that is not visible to readers (structured data general guidelines).

When FAQ content is worth writing

An FAQ section earns its place when it answers questions that:

• readers actually ask (from support tickets, sales calls, site search, community forums or Search Console queries);
• the main body of the page does not already answer;
• have short, self-contained answers.

It is filler when it restates the article’s headings as questions, repeats definitions already given, or adds keyword variations of the same question.

A quick test for each question: if this pair were deleted, would a reader lose an answer they could not find elsewhere on the page? If not, delete it.

Writing FAQ answers that hold up

• Answer in the first sentence. Put conditions immediately after.
• Make the answer consistent with the body; if the body says “in most US states”, the FAQ answer cannot say “always”.
• Keep each answer to one question. Two questions folded into one answer read poorly and make the markup ambiguous.
• Date or version answers that can change (prices, policies, product features).

Valid FAQPage markup (illustrative)

For sites that keep the markup for non-Google consumers or for consistency, a minimal valid structure:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Can I return an opened item?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, within 30 days of delivery, if all original parts are included. Shipping costs for returns are not refunded."
      }
    }
  ]
}

The policy figures are placeholders. Validate syntax with the Schema Markup Validator (structured data troubleshooting). The Rich Results Test will not report an FAQ rich result, because Google no longer supports one.

FAQ content vs Q&A pages

Schema.org distinguishes FAQPage from QAPage, and its FAQPage definition points to QAPage as the related type. An FAQ is written by the site and lists its own answers; a Q&A page centers on a single question with answers submitted by users, as on a forum. Marking a site-written FAQ as QAPage to get a different rich result misrepresents the page.

FAQs and AI features

FAQ content can serve as clear, quotable answers wherever search systems look for them, including featured snippets and Google’s AI features. Google’s guidance for AI features, though, says there is no special markup needed to appear in them; eligibility depends on the page being indexed and eligible for a snippet (AI features and your website). FAQ markup is not a route into AI Overviews, and FAQ text helps only in the way any clear, accurate text helps.

A decision checklist

1. List the questions readers ask that the page does not answer. If the list is empty, do not add an FAQ.
2. Write answers that agree with the body text.
3. Decide on markup: keep, remove or skip, using the criteria above. Do not expect a Google rich result.
4. If keeping markup, validate it and make sure every marked-up question and answer is visible on the page.
5. Update old content that promises FAQ rich results.

Pruning generated FAQs from help articles

Take a hypothetical software company whose help articles each end with eight generated FAQs and FAQPage markup, added in 2022 for rich results.

• Audit: five of the eight questions per article repeat headings already answered above them. Two answer real support questions. One contradicts the article (an old pricing answer).
• Content decision: keep the two useful questions, delete the five duplicates, correct the pricing answer.
• Markup decision: the template regenerates markup from the visible FAQ, so it stays accurate; the team keeps it.
• Expectation: no change in Google rich results, because none exist; the improvement is in reader experience and accuracy.

FAQ sections are a writing decision again. Write them for readers, keep the markup honest if you use it, and remove any promise of a feature Google no longer shows.