FAQ Schema Is Mostly Dead. FAQ Sections Aren't.

TL;DR

• Google restricted FAQ rich results to government and health sites in August 2023. Everyone else lost the dropdown snippet.

• FAQPage schema rarely pays anymore. Service, Organization, and BreadcrumbList schema still do.

• Visible FAQ sections matter more in 2026 because LLM retrieval prefers Q&A-formatted blocks.

• Pew (July 2025) found just 1% of visits click a source when an AI Overview is present. Being quoted beats being ranked.

• Measure FAQ impact through assisted conversions, brand mentions in AI Overviews, and on-page engagement, not impressions.

Is FAQ Schema Still Worth It in 2026?

Short answer: no, for almost everyone. The FAQPage markup that used to bolt a dropdown onto your search result was restricted to authoritative government and health sites in August 2023, as Search Engine Land documented at the time. If you run a brokerage, an agency, a SaaS, a clinic, or a services business, FAQ rich results have not rendered for you in almost three years. Half the SEO blogs still tell you to ship the schema anyway.

The schema is a ghost. The FAQ section on the page is not.

This piece is the 2026 playbook: what to remove, what to keep, what to write, and how to measure it now that the snippet game is over and the retrieval game is the only game.

1. What Google Actually Killed in August 2023 (and What It Didn't)

Google didn't kill FAQPage markup as a spec. It killed the visual treatment. Before August 2023, valid FAQPage JSON-LD could render an accordion of questions directly under your blue link in the SERP — extra screen real estate, extra click-throughs, extra reason to ship it. After August 2023, that treatment is reserved for .gov and authoritative health domains.

For everyone else, three things are true at once:

1. The markup still validates. Search Console will not flag it as broken.

2. The markup no longer produces visible rich results.

3. Google's documentation has quietly demoted FAQPage from "recommended" to a footnote.

Maintaining the schema costs you nothing if it's already there. Building it from scratch in 2026 is engineering effort spent on a dead snippet. The page underneath is where the work belongs.

2. Why Visible FAQ Sections Still Earn Their Place

Three reasons, in order of money.

Objection handling. A service page FAQ is the cheapest sales call you'll ever run. When a prospect lands on our website design service page and asks "how long does this take," they want the answer before they fill the form. An FAQ section answers in their words, in their reading order, without making them schedule a call. The conversion lift shows up in form-fill rates, not impressions.

Long-tail capture. A page that ranks for one head term tends to rank for the long-tail variants in its FAQ block. Question-shaped headings ("how much does X cost," "what's included in Y") match how people actually search and how they actually talk to an AI assistant. The FAQ is the long-tail layer of the page.

LLM retrieval. This is the one most teams haven't priced in yet. When an AI Overview appears on a Google result, Pew Research found in July 2025 that only 1% of visits click through to a cited source. The click economy is collapsing into a quote economy. And Q&A-formatted content — short question, direct answer, named entities — is structurally easier for retrieval systems to extract and cite.

Semrush's AI-search study puts a number on the why: an AI-search visitor was worth roughly 4.4x an organic search visitor in their dataset. Fewer clicks, higher intent. If the choice is being the link nobody clicks or the answer everybody reads, the FAQ is the lever.

The same FAQ block does a different job now. Build for the new one.

3. Writing FAQ Answers AI Search Engines Actually Quote

The retrieval layer rewards a specific shape. We've watched the same page get quoted by Perplexity and ignored by Google's AI Overview based on how the answer was written, not what it said.

The pattern that gets quoted:

• Question as the exact phrase the user would type or speak. "How much does a website redesign cost?" beats "Investment Range for Redesign Projects."

• Direct answer in the first sentence. No "great question." No setup. The first 20 words contain the answer.

• Named entities in the answer. A retrieval model needs handles — product names, units, time-frames, geographies. "Typically 6 to 10 weeks for a 12-page service site" travels. "It depends" does not.

• 40 to 80 words per answer. Long enough to be standalone, short enough to lift as a block.

• One claim per answer. Multi-claim answers get chopped mid-quote and lose meaning.

Write the answer so it can be ripped out of context and still be true. That's the test.

4. Schema That Still Pays: Service, Organization, BreadcrumbList

If the engineering hour is going somewhere, here's where it earns out in 2026.

Service schema. Describes what you sell, who you sell it to, the area you serve, and the offer. This is the schema that AI assistants are using to populate "who does X near me" style answers. On a service page, this is load-bearing.

Organization schema. Names the company, the founders, the social profiles, the logo, the contact points. It's the entity layer — the thing that lets a retrieval system know that the Entropy on this page is the same Entropy mentioned in a podcast transcript and a Crunchbase profile. Entity consolidation is the new backlink.

BreadcrumbList schema. Quiet, structural, and still rendered in SERPs as the path under the title. Cheap to ship, real estate on the result, and it helps crawlers understand site hierarchy.

Notice what's not on the list: FAQPage, HowTo (also restricted in 2023), Article schema beyond basics. Ship the three above and stop.

5. Where FAQs Belong on a Service Page

The placement debate has a right answer for service pages. The FAQ block sits near the bottom, after pricing or process, before the final CTA. It catches the visitor who has read the page, has one remaining objection, and is one answered question away from the form.

A few placement rules from client work:

• 5 to 8 questions is the sweet spot for a service page. More than 10 reads as a wall and dilutes the snippet-ready answers.

• The first question handles the biggest objection — usually price or timeline.

• Each answer links to a deeper resource where one exists. The FAQ is also an internal-linking surface.

• Do not collapse the answers behind accordions if you want LLM retrieval. Hidden text gets less weight from some crawlers and is harder to verify as the source.

If you're still deciding whether to put all services on one page or split them, our piece on one-page vs separate service pages covers that decision. The FAQ logic above applies in both layouts.

For the broader page architecture, service page structure that converts walks the full template.

6. How to Measure FAQ Impact Now That Rich Results Are Gone

The old measurement — impressions and CTR on FAQ rich results in Search Console — is gone. The new measurement is harder, more honest, and closer to revenue.

Four signals worth tracking:

On-page engagement on FAQ block. Scroll depth to the FAQ section, time spent in the block, click-through on in-FAQ links. If 40% of converters touched the FAQ block on the way to the form, the section is doing its job.

Assisted conversions. In your analytics tool, the service-page FAQ rarely gets last-click credit. It does the assist. Configure attribution to surface that.

Brand mentions in AI Overviews and LLM answers. Manually search the questions your FAQ answers in Google AI Overview, Perplexity, ChatGPT search, and Claude. Log whether your domain is cited. This is a weekly 20-minute audit and the closest thing to a leaderboard the AI-search era has.

Query coverage in GSC. Even without rich results, the questions in your FAQ should be appearing as queries that land on the page. If they're not, the answers aren't matching real search language. Rewrite them.

The TL;DR on measurement: stop measuring the snippet. Start measuring the citation.

FAQ

Is FAQ schema still worth it in 2026?

No, for almost every business. Google restricted FAQ rich results to government and authoritative health sites in August 2023, so the dropdown snippet that justified the markup no longer renders for commercial sites. Keep existing schema if it's already deployed, but don't build new FAQPage markup. Put the engineering effort into Service and Organization schema instead.

Did Google remove FAQ rich results entirely?

Not entirely. Google narrowed eligibility to authoritative government and health domains in August 2023. The FAQPage spec still validates and parses correctly, it just doesn't generate the visible accordion in search results for non-eligible sites. For most operators, the schema is technically alive and practically dormant.

Should I delete the FAQ section from my service page?

No. The visible FAQ section is more valuable in 2026 than it was in 2022. It handles sales objections before the form fill, captures long-tail question queries, and gives LLM-based search engines clean Q&A blocks to retrieve and cite. The schema is dead. The section is load-bearing.

How many FAQs should a service page have?

In our client work, 5 to 8 questions is the sweet spot for a service page. Fewer than 4 misses common objections. More than 10 reads as a wall of text and dilutes the answers that matter. Lead with the question that handles the biggest objection — typically price, timeline, or scope.

What schema should I use instead of FAQPage?

Three types still pay in 2026: Service schema for what you sell and where, Organization schema for entity consolidation across the web, and BreadcrumbList schema for site hierarchy and SERP path display. These three cover the structured-data surface that AI assistants and Google actually use to populate answers and panels.

Ship This Week

Audit one service page this week. Strip the FAQPage schema if it's still there. Rewrite the 5 questions underneath so each answer leads with the direct response in the first sentence, names a unit or time-frame, and reads as standalone when quoted. Then watch which of those questions start showing up in AI Overviews over the next 30 days.

If you'd rather we run that audit on your site, say hi.