A shop owner adds FAQPage markup to ten product pages, waits three weeks, and sees no FAQ in Google. The markup is valid. The pages are indexed. Nothing is broken. The reason is eligibility, not validity: Google stopped showing FAQ rich results for most sites in 2023. FAQPage markup tells search engines what your questions and answers are. It does not buy you a SERP feature.

Put simply, there are two separate gates. Gate one is validity: does the markup parse and pass the schema.org rules? Gate two is eligibility: does Google's current feature policy allow a rich result for this site and this query? Most people fix gate one and never check gate two.

FAQPage markup describes your Q&A; it doesn't promise a rich result

FAQPage is a schema.org type for a page that contains a list of questions and answers. Schema.org defines it as a page with one or more questions and their answers, marked with Question and Answer types. That definition comes from schema.org/FAQPage. It is a vocabulary, not a promise of display.

Google's own documentation is the second layer. Google Search Central's FAQPage structured data page states that FAQ rich results are now limited to well-known, authoritative government and health websites. For everyone else, the markup is still parsed, but the FAQ feature is not shown.

So the first diagnostic question is not "is my markup valid?" It is "am I in the eligible group?" For most commercial sites, the answer is no.

Five common explanations are usually wrong, and here's why

These are the explanations people reach for first. Each one can be a real problem in other contexts, but none of them explains a missing FAQ rich result on its own.

Claimed causeWhy it's usually not the reasonWhat to check instead
"My markup has an error."Valid markup still shows no FAQ result for most sites. Validity is necessary, not sufficient.Run the Rich Results Test, then check eligibility in Google's FAQPage docs.
"My page isn't indexed."If the page ranks at all, it is indexed. FAQ absence is a feature issue, not an index issue.Search Console URL Inspection, then the Page indexing report.
"I need more FAQs."Adding questions does not change eligibility. The limit is policy, not volume.Confirm the site type against Google's stated eligible categories.
"Google needs more time."Re-crawl can take days or weeks, but waiting does not restore a retired feature.Check the date of the last crawl, then compare against the 2023 change.
"My competitor has it, so it works."The competitor may be a government or health site, or showing a different feature.Inspect the competitor's page source and site type.

Each row in that table is a real check. The point is order: run eligibility first, because it eliminates most cases before you touch the code.

Google narrowed FAQ rich results in August 2023, but the vocabulary still works

Google announced in August 2023 that it would limit FAQ rich results to authoritative government and health sites. The change rolled out through the following weeks. Google's own announcement on the Search Central blog is the primary source; the current FAQPage documentation reflects the restriction.

Two things did not change. The FAQPage type still exists in schema.org. Google still parses the markup, and it can still be used to understand page content. What changed is the display policy, not the vocabulary.

HowTo rich results were retired around the same time. Google's HowTo documentation now states the feature is no longer shown. The pattern is the same: structured data can be valid and still not produce a visual result.

A rich result needs four stages to line up, and FAQ fails at the last one

It helps to see where FAQ markup sits in the pipeline. The path has four stages, and a rich result depends on all four.

  • Crawl: Googlebot fetches the HTML. If the markup is injected by JavaScript, Google must render the page first. Google's JavaScript SEO docs describe this two-wave process.
  • Index: the page is stored and parsed. Structured data is extracted here. A noindex tag stops the page before this stage.
  • Retrieve: the page is selected for a query. Ranking depends on relevance and quality, not on markup.
  • Display: a feature is chosen for the result. This is where eligibility applies. FAQ rich results are gated here.

Most "FAQ schema not showing" tickets are stage-four issues. The page crawled, indexed, and ranked. The feature was simply not available.

One practical consequence: if you use JavaScript to inject FAQ markup, confirm the rendered HTML contains it. Google's Rich Results Test can show the rendered HTML. A server-side render removes that dependency.

Check validity and eligibility as two separate tests

Validity check first. Paste the URL into Google's Rich Results Test. It reports which structured data types it detects and whether they have errors. The Schema Markup Validator at validator.schema.org checks vocabulary rules only; it does not know Google's feature policy.

Eligibility check second. Open Google's FAQPage structured data documentation and read the eligibility section. If your site is not a government or health site, the FAQ feature is not available to you. That is the answer, and no code change alters it.

A third check catches the common JavaScript problem. Use URL Inspection in Search Console and view the rendered HTML. Search for your Question and Answer markup in that rendered output. If it is missing there, Google may not see it either.

Other schema types still earn rich results when the page qualifies

Several types still produce visual features when the markup is valid and the page qualifies. Google's Search Gallery lists the current set. The list below is a practical subset, not a complete catalogue.

TypeTypical resultKey condition
ProductPrice, availability, review starsValid offers and review markup; merchant eligibility rules apply
RecipeImage carousel, cook timeRequired fields present; image accessible
Article / NewsArticleTop stories, enhanced snippetsNews eligibility for Top stories; Article markup for the rest
BreadcrumbListBreadcrumb trail in the URL lineValid hierarchy; matches visible navigation
OrganizationLogo and knowledge panel signalsConsistent name, URL, logo; sameAs links
EventEvent listingDates, location, and status fields valid

Each type has its own eligibility rules. Product markup, for example, has merchant and review policies that change over time. Check the specific documentation page before assuming a result will appear.

Keep FAQ schema in most cases, and remove it in two

Keep it, in most cases. The markup does not harm rankings, and it gives search engines and AI answer engines a clean question-answer structure. Google's documentation confirms the markup is still parsed. Removing it costs you that structure and gains nothing.

The decision changes in two cases. If the markup is wrong, fix it or remove it; incorrect markup can confuse extraction. If the page has no visible FAQ, remove the markup. Google's structured data general guidelines require markup to match visible content.

For AI answer engines, the case for keeping it is stronger. Retrieval systems parse question-answer pairs directly. The markup gives a clean signal, even without a SERP feature.

Shift effort to features that still display, and fix the content itself

If the goal is visibility, shift effort to features that still display. Product, Article, BreadcrumbList, and Organization markup all have live features. Each one has documented requirements on Google's Search Gallery.

Then fix the content itself. A clear question, a direct answer in the first sentence, and a short paragraph do more for extraction than markup alone. This applies to both classic search and AI answers.

Finally, check the technical basics. Confirm the page is indexed, the rendered HTML contains the markup, and the markup matches what users see. Those three checks catch most real problems.

Key Facts at a Glance

  • Google limited FAQ rich results to authoritative government and health sites in August 2023.
  • FAQPage markup is still valid schema.org and is still parsed by Google.
  • Validity and eligibility are separate gates; passing one does not pass the other.
  • The Rich Results Test checks validity, not whether a feature will display.
  • Markup must match visible page content, per Google's structured data guidelines.
Why is my FAQ schema not showing in Google?

Most likely because Google limited FAQ rich results to government and health sites in 2023. Your markup may be valid, but the feature is not available to most commercial sites.

Did Google remove FAQ rich results permanently?

Google restricted them to well-known, authoritative government and health sites. The FAQPage type still exists, and the markup is still parsed. The display feature is what changed.

Should I remove FAQ schema from my site?

Keep it if the markup is valid and matches visible content. It still helps search engines and AI systems understand your questions and answers. Remove it only if the markup is wrong or there is no visible FAQ.

How do I test if my FAQ schema is valid?

Use Google's Rich Results Test for Google-specific checks, and the Schema Markup Validator at validator.schema.org for vocabulary rules. Neither tool confirms that a rich result will display.

What schema types still earn rich results?

Product, Recipe, Article, BreadcrumbList, Organization, and Event are among the types with live features. Each has its own eligibility rules on Google's Search Gallery.