FAQPage structured data is a Schema.org type implemented in JSON-LD that signals to search engines a page contains questions with 1 official answer each. Google's documentation governed its eligibility, content rules, and required properties across 3 major milestones between 2019 and 2026.
What Is FAQPage Structured Data?
Google Search documentation covers the official details in Structured data markup that Google Search supports.
FAQPage structured data is a standardized JSON-LD markup that declares questions and their answers as machine-readable entities within a page's code. It uses the Schema.org FAQPage type, which was jointly developed by Google, Microsoft, Yahoo!, and Yandex. Schema.org published version 29.4 in December 2025, which remains the active specification.
Structured data does not directly affect rankings. It makes a page eligible for rich results and helps search engines interpret content with greater precision.
Stop Words in Keywords SEO: 5 On-Page Rules, Common Examples, and When Google Uses Them
What Weekly SEO Metrics Should You Measure: 8 Indicators, Benchmarks, and Tools
What Is the Difference Between FAQPage, QAPage, and HowTo?
There are 3 distinct Schema.org types for FAQ-style content. Each serves a different content structure:
| Schema Type | Use Case | Answer Structure |
|---|---|---|
| FAQPage | Multiple questions with 1 official answer per question | Fixed, authoritative answers |
| QAPage | 1 question where users can submit multiple answers | Community-generated answers |
| HowTo | Step-by-step procedural instructions | Sequential steps, not Q&A |
Per Google's Search Central documentation, using FAQPage on a page where users submit their own answers is a content guidelines violation. Use QAPage instead.
What Did Google's 2025 FAQPage Documentation State?
In 2025, Google's FAQPage structured data documentation restricted FAQ rich results to well-known, authoritative government-focused and health-focused websites only. Commercial, marketing, agency, and general-purpose websites were ineligible for FAQ rich results regardless of implementation quality or markup accuracy.
This restriction took effect in August 2023. It remained Google's stated policy throughout 2025. The documentation specified 3 eligibility conditions for the remaining FAQ rich result:
- The site must be government-focused or health-focused
- The site must be well-known and authoritative
- Eligibility is determined by Google automatically, not by publisher request
Google's 2025 documentation also confirmed that for all ineligible sites, FAQ markup that was not being used produced no visible effects in Google Search. Unused structured data did not cause penalties or errors. The Google Search Central Blog confirmed this in its August 2023 announcement: "there's no need to proactively remove it."
By June 2025, Google deprecated 7 additional structured data types, including Practice Problems and refinements to Dataset scope. FAQPage remained in the documentation for eligible government and health sites throughout this period.
How Do You Implement FAQPage Structured Data in JSON-LD?
Implement FAQPage structured data in JSON-LD by placing a script tag in the page's <head> or <body> that declares the FAQPage type, lists each question using the Question entity, and provides its answer using the Answer entity.
JSON-LD is the only format Google recommends for structured data. Microdata and RDFa are supported by Schema.org but are error-prone and harder to maintain.
A compliant FAQPage JSON-LD block follows this structure:
“json <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What is structured data?", "acceptedAnswer": { "@type": "Answer", "text": "Structured data is a standardized format that helps search engines classify page content and make it eligible for rich results." } }, { "@type": "Question", "name": "What format does Google recommend for structured data?", "acceptedAnswer": { "@type": "Answer", "text": "Google recommends JSON-LD as the preferred format for structured data markup." } } ] } </script> “
What Are the Required FAQPage JSON-LD Properties?
Per Google's Search Central documentation, FAQPage markup requires 5 properties to be valid:
- @context set to
https://schema.org - @type set to
FAQPage - mainEntity containing an array of Question objects
- name within each Question object (the full text of the question)
- text within each Answer object (the full text of the answer)
There must be exactly 1 FAQPage type declaration per page. The acceptedAnswer property wraps the Answer object inside each Question. Both item_id and item_name equivalents in FAQPage are name and text respectively. Omitting either produces a validation error in the Rich Results Test.
What Are Google's Content Guidelines for FAQPage Markup?
Google's FAQPage content guidelines require that all question and answer text visible in the markup exactly matches the content visible to users on the page. Declaring content in JSON-LD that does not appear on the page is a spam policy violation that can result in a manual action.
Per the Search Central documentation, FAQPage markup is prohibited from containing 6 categories of content:
- Obscene or profane language
- Sexually explicit content
- Graphically violent content
- Promotion of dangerous or illegal activities
- Hateful or harassing language
- Promotional or advertising content
The documentation further specifies that FAQPage markup cannot be used for advertising purposes. Internal links within answer text are permitted under the schema specification. The answer text field supports basic HTML.
Has Google Deprecated FAQPage Rich Results?
Google ended all FAQPage rich results on May 7, 2026. This included the remaining government-focused and health-focused eligibility window that had been in place since August 2023.
The deprecation followed 3 milestones:
- August 2023: Google restricted FAQ rich results to government and health sites. All commercial sites lost eligibility.
- June 2025: Google deprecated 7 additional structured data feature types in search appearance, reducing the total set of rich result formats.
- May 7, 2026: Google ended all FAQ rich results with a notice added to the top of the Search Central FAQPage documentation. No blog post or webmaster announcement accompanied the change.
The timeline for the full deprecation rollout:
| Date | Action |
|---|---|
| May 7, 2026 | All FAQ rich results removed from Google Search |
| June 2026 | FAQ search appearance, rich result report, and Rich Results Test support removed from Search Console |
| August 2026 | Search Console API support for FAQ rich result data removed |
Per the deprecation notice, site owners are not required to remove existing FAQPage markup. Leaving it in place does not generate Search Console errors or affect Google rankings.
Does FAQPage Structured Data Still Have Value After the 2026 Deprecation?
FAQPage structured data retains value for 3 purposes after the Google rich result deprecation: entity declaration for indexing, visibility in AI-generated answers, and processing by other search engines.
The 3 remaining use cases are:
- Entity declaration: Each Question and Answer pair in FAQPage JSON-LD is a machine-readable entity that Google uses to understand what topics a page covers. This understanding affects how Google indexes the page regardless of whether a rich result appears.
- AI Overview and generative engine visibility: Per Semrush's 2025 structured data analysis, pages with valid structured data are 2.3 times more likely to appear in Google AI Overviews compared to equivalent pages without markup. Princeton's GEO research found that content with structural signals, including schema markup, achieved up to 40% higher visibility in AI-generated responses.
- Bing and alternative search engines: Bing processes FAQPage markup independently. Sites that retain FAQPage JSON-LD may continue to receive rich result treatment from Bing and other engines that have not made equivalent deprecation announcements.
How Do You Validate FAQPage Structured Data?
Validate FAQPage structured data using 2 tools: Google's Rich Results Test and the Schema Markup Validator.
- Rich Results Test (search.google.com/test/rich-results): Confirms whether Google can read the markup and whether the page is eligible for a rich result. After the June 2026 Search Console update, FAQ-specific data will no longer appear in Rich Results Test outputs.
- Schema Markup Validator (validator.schema.org): Confirms whether the JSON-LD conforms to the Schema.org specification, independent of Google's eligibility rules.
Use both tools together. The Rich Results Test confirms Google compatibility. The Schema Markup Validator confirms specification compliance. A page that passes both has correctly implemented and technically valid FAQPage structured data.
Waleed Qamar holds a BSc in Computer Science from Purdue University and has spent the years since turning that technical foundation into something the curriculum never covered: figuring out why websites rank, why they fall, and why most businesses never find out until it is too late.
Pakistan-born and based between the United States and South Asia, he has managed search visibility for e-commerce stores, local service businesses, and SaaS startups across two continents. He started in SEO when guest posting still worked, survived the Penguin update, and has rebuilt client sites from scratch after algorithm hits more than once.
He has watched good businesses get sold packages that looked like progress and delivered nothing lasting. He has also seen the right approach quietly double a site’s traffic without a single press release about it.
His writing on SEO By Highsoftware99 covers Google algorithm updates, autocomplete optimization, semantic SEO structure, and the widening gap between what agencies promise and what Google actually rewards in 2026.
He knows what a traffic cliff looks like in Search Console on the morning you discover it.
