FAQ markup in 2026: why the code is paying off right when SMBs are stripping it

Why FAQ schema in 2026 is the markup most operators are about to delete by mistake

This month Google finishes the second phase of its FAQ rich-result deprecation. The FAQ search appearance filter, the FAQ rich-result report, and the FAQ check inside the Rich Results Test (Google's free developer page for previewing how a URL renders in search) are being removed from Search Console (Google's free dashboard that shows how your site appears in search). The Search Console API support for FAQ rich results follows in August 2026. The visible "collapsible questions" rich result (the special-looking version of a Google result, often with extra elements like expandable questions or star ratings) has been gone from the regular search page since May 7, when Google switched it off for every site.

Most SEO trade reporting this month is reading those changes the same way: the FAQ markup is dead, time to strip it off the pages. That reading misses what the FAQ code is doing in 2026.

FAQPage schema (the machine-readable code under a page's FAQ section that tells search systems each question and its answer) is not deprecated. Google Search Central confirms the search systems still read FAQPage to understand a page. More to the point for a service business, the same Q-and-A structure FAQ markup carries is the format AI Overviews (the AI-generated answer that shows at the top of a Google search), ChatGPT, Perplexity, Gemini, and Bing Copilot now pull from when they answer a customer's question. SEO research summaries circulating this spring put the appearance lift at roughly 3.2 times: a page with FAQ markup shows up inside Google AI Overviews about three times as often as a similar page without it. (Search Engine Land, Get Passionfruit, and The HOTH all covered the timeline and the surviving AI use case.)

The deletion is happening anyway. The site audit a new SEO contractor runs in June will not see a rich result, will not see a feature in Search Console, and will pull the FAQ code as housekeeping. The page stops showing up in AI Overviews about six weeks later, and the operator never connects the missing audit work to the booking drop.

The 3.2x AI Overview lift, translated into bookings

The 3.2x lift is the input number. The output an operator cares about is bookings, and AI-search referral traffic converts at roughly 4.4 times the rate of regular Google organic, per the Adobe Analytics 2026 cross-client benchmark.

Run the math against a dental practice. A page that earns three AI Overview appearances a month after the FAQ blocks go in, where it earned one a month before, picks up two extra appearances. If each one of those drives a typical AI-search session into a booking funnel at the published 4.4x premium, and the practice books at roughly 15 percent on an AI-search visit, two extra appearances per month covers something on the order of a single booked patient at a USD 280 lifetime value (the total revenue one patient spends with the practice over the relationship). Across a year that is several thousand dollars of revenue tied to a few KB of FAQ JSON on the page. The math runs higher for an HVAC business on a USD 600 service plan and higher still for a medspa selling a multi-month treatment package.

Why the FAQ blocks usually need a rewrite even when the code stays

Most FAQ blocks on a 2023-era service page were written for the old rich result. The questions read like SEO copy. "What are the benefits of professional teeth cleaning?" The answer reads like SEO copy too. That was fine when the markup's job was to win a search-page dropdown.

The format AI Overviews and the chat engines reward is customer phrasing. The five real questions a dental practice gets on the front desk are closer to "does the cleaning hurt," "do you take my insurance," "how long does the visit take," "what does it cost out of pocket," and "can you see me this week." Those are the questions an AI Overview is paraphrasing and pointing at a citation for. The FAQ block on the cleaning page that mirrors those five exact phrasings earns more pickups than the SEO-styled block that does not.

The same pattern runs across the verticals Vyzz audits. HVAC customers usually open with "why is my AC blowing warm air" long before they search "what HVAC services do you offer." Medspa visitors want to know how long Botox lasts, and a vet clinic's website traffic typically arrives via natural customer queries like "what shots does my puppy need at twelve weeks." The closer the question on the page is to what the customer types, the higher the AI Overview pickup rate.

The five-minute review for every operator this month

One. Open Search Console while the FAQ section is still there. Run URL Inspection on three of your service pages. Confirm Google sees the FAQPage block on the page. While the rich result is gone, Google still parses the code.

Two. Open Bing Webmaster Tools. Read the AI Performance report. Microsoft added it in February 2026. The report shows citation counts for your indexed pages across ChatGPT and Microsoft Copilot answers. Note your monthly count and the pages picking it up.

Three. Pull your front-desk log, your email inbox, or the call notes from the last month. Write down the next three customer questions on each top service page. Use the customer's words. Add those three questions to the FAQ block on the matching service page.

Four. Walk the FAQ blocks on the service pages and confirm the answers are direct, dated where the data is time-sensitive, and at most one short paragraph each. AI Overviews pull the shortest grammatical answer that actually answers the question. AI Overviews tend to paraphrase longer 200-word FAQ answers, and they quote concise 40-word answers closer to verbatim.

Five. Do not delete the code. Despite the reporting changes in Search Console, the schema itself remains in use for 2026 AI search.