FAQPage schema is one of the easiest structured data types to add, and almost nobody adds it. We pulled FAQ schema presence across 1,219,994 classified US business websites in Stackra's corpus, cross-referenced with business type and platform. The overall adoption rate is 2.3%, or 28,308 sites out of 1,219,994 checked. Every figure in this article includes the raw count, not just the percentage.
What this data shows: adoption rates. What it does not show: whether having FAQ schema improves rankings, AI citations, or traffic. We have no before/after, no control group, and no outcome metric in this dataset. Treat the adoption numbers as fact and the discussion of why it might matter as a separate, unproven argument.
What changed with Google, and what we don't know about AI tools
Google removed FAQPage rich results from Search entirely in May 2026, the final step in a rollback that started in August 2023 when eligibility was restricted to healthcare and government sites. If you are optimizing for a Google rich result, FAQPage no longer gets you one, on any site type. Separately, FAQPage markup is machine-readable content that tools like ChatGPT and Perplexity are technically capable of parsing when they crawl a page. That a tool *can* read structured data is not evidence that having it changes whether your content gets cited. We are not aware of a study showing FAQ schema presence correlates with AI citation rate, and this corpus does not measure citations at all, only whether the markup exists on a page.
FAQ schema by business type
If FAQ schema adoption tracked business logic, you would expect industries with genuinely high question volume (healthcare, legal, financial services) to lead. They do not. SaaS and home services lead, and the gap between the top and bottom of the list is roughly 25x.
| Business Type | FAQ Schema Rate | Sites with FAQ Schema | Total Sites Checked |
|---|---|---|---|
| SaaS | 7.4% | 990 | 13,377 |
| Home Services | 7.3% | 4,884 | 66,899 |
| Professional Services | 5.0% | 2,202 | 44,049 |
| Healthcare | 3.8% | 4,034 | 106,148 |
| Automotive | 3.3% | 1,962 | 59,445 |
| Government | 0.5% | 187 | 37,373 |
| Nonprofit | 0.4% | 352 | 88,023 |
| Religious | 0.3% | 97 | 32,474 |
Source: Stackra US business corpus, 1,219,994 classified sites, June 2026. Business types shown are the highest and lowest of the categories with n > 5,000. Sites with FAQ Schema column derived from the listed percentage applied to total sites checked.
Healthcare sitting in the middle of the pack, not the top, despite being the one category Google specifically carved out an exception for during the 2023-2026 rollback period, is the clearest evidence that this is not demand-driven. SaaS and home services companies are not inherently more curious about FAQ schema than religious organizations. They are more likely to be running a platform or plugin stack where adding it is one settings toggle, not a code change.
FAQ schema by platform
This is where the pattern resolves. Adoption correlates almost perfectly with whether a platform's template layer exposes an FAQ schema setting, not with how website-savvy that platform's typical user is.
| Platform | FAQ Schema Rate | Sites with FAQ Schema | Total Sites Checked |
|---|---|---|---|
| Duda | 4.9% | 1,666 | 34,242 |
| Webflow | 3.6% | 708 | 19,835 |
| WordPress | 3.0% | 15,253 | 505,521 |
| Shopify | 2.1% | 1,491 | 72,063 |
| BigCommerce | 1.9% | 93 | 4,840 |
| Wix | 0.7% | 662 | 100,061 |
| Squarespace | 0.6% | 576 | 89,196 |
| Weebly | 0.2% | 46 | 19,674 |
| GoDaddy Website Builder | 0.0% | 1 | 22,186 |
Source: Stackra US business corpus, 1,219,994 classified sites, platform_hint field, June 2026.
GoDaddy Website Builder is the extreme case: 1 site out of 22,186 has FAQ schema. That is not 22,186 GoDaddy customers independently deciding FAQ schema is not worth their time. It is a closed template builder that does not expose a way to add it. WordPress lands in the middle at 3.0% despite having the largest, most mature plugin ecosystem of any platform here (Yoast, RankMath, and others all support FAQ blocks), which tells you that even where the capability exists, most site owners never find or activate it without a default doing it for them.
The takeaway: this is a settings gap, not a strategy gap
The 2.3% adoption rate does not mean 97.7% of businesses evaluated FAQ schema and decided against it. The platform breakdown makes that clear: it tracks template defaults, not informed opt-outs. Almost nobody is given the option by default, and very few go looking for a manual fix. What we can say with the data in this article: adoption is low and driven by platform, not industry. What we cannot say: that fixing it will move your rankings or AI visibility. FAQ schema is low-cost to add if you have real FAQ content already, which makes it a reasonable bet even without proof of payoff, but it is a bet, not a documented result.
Out of 1,219,994 sites checked, 28,308 have FAQ schema. That tells you adoption is low and uneven by platform. It does not tell you what adding it is worth.