A buyer is three questions deep into a Google search before they ever land on a website: how much does this cost, how long does it take, do you handle the permits. Adding FAQs to your website that answer those exact questions, in your own words, is what gets you remembered when that buyer is finally ready to call.
FAQs used to earn extra real estate directly inside a Google search result, which is part of why so many businesses built them in the first place. That reason went away in 2026. The reason to keep building strong FAQ content did not.
This guide covers what actually changed with FAQ rich results this year, where FAQ content belongs on a home service, builder, or solar website, how to write questions real buyers type instead of the ones a business wishes they asked, and whether FAQPage schema is still worth the effort.
Yes, but not for the reason most sites originally added them. Google retired the FAQ rich result from search entirely in May 2026, so FAQ content no longer earns extra space directly in the results page. FAQ content still helps by answering a buyer's real questions on the page itself, feeding clean, quotable information to AI answer engines like AI Overviews and ChatGPT, and giving both Google and AI systems clearer signals about what a business actually does and where it operates.
Google had already restricted FAQ rich results to a narrow band of authoritative government and health sites back in August 2023. For nearly every home service, builder, and solar business, the rich result had been functionally invisible since that update. In May 2026, Google's own structured data documentation confirmed the feature is retired across every site and vertical, with reporting support in Search Console following in June and API support ending in August.
Here is the part worth understanding: the FAQPage schema type itself was not deprecated, only the visible search feature it used to power. Google has stated that structured data which is not actively used does not cause problems for a site, so there is no urgency to strip existing markup. What changed is the payoff. Chasing FAQ schema purely for a rich result is no longer a reason to build FAQ content. Answering real buyer questions still is, which is exactly the shift our breakdown of how AI is changing SEO gets into in more depth.
Working with a specialist
FAQ content is one page. A revenue system is the whole site.
If you'd rather have a team write FAQ content, structure it so both buyers and AI answer engines actually use it, and connect it to the rest of your marketing and CRM, that's exactly what the Momentum Revenue Growth System is built to do.
How the Momentum Revenue Growth System works →Most businesses build a single generic FAQ page, link it once from the footer, and consider the job done. That page rarely gets found by the buyer who needed it, because that buyer was reading a specific service page, not browsing the site map.
FAQ content works better broken apart and placed where the question actually comes up. A roofing company answers insurance and permit questions on the roof replacement page, not on a general FAQ page. A solar company answers financing and net metering questions on the financing page. A custom home builder answers process and timeline questions on the process page, which is exactly the kind of placement our custom home builder SEO guide recommends for FAQPage schema specifically. A tree service company answers permit, insurance, and disposal questions on the removal page, where the buyer is already deciding.
A question written the way a marketer thinks about a service rarely matches the question a buyer actually types. The gap between "What is your process?" and "How long does a custom home actually take to build?" is the gap between a page that gets skipped and one that gets read.
Good FAQ questions usually come from a short list of real sources, not a brainstorm:
Write the question the way the buyer would say it out loud, not the way it would appear in a services brochure.
AI answer engines pull from pages that give a direct, self-contained answer before they give the full explanation. Lead with the direct answer in the first sentence or two, then use the rest of the paragraph to add the detail a buyer who is actually ready to decide wants. Google's own research on AI search behavior points to the same pattern: buyers move faster between discovery and decision now, which rewards content that answers clearly instead of building up to the point.
Keep each answer to a single, complete idea. An answer that tries to cover cost, timeline, and process in one paragraph is harder for both a skimming buyer and an AI system to extract cleanly. Split it into three questions instead.
If you already have FAQPage schema in place and it accurately describes visible content on the page, leave it. Google has confirmed unused or legacy structured data does not create problems. If you are building a new page, adding lightweight FAQPage markup still costs very little and gives structured, machine-readable signal to Bing, Perplexity, and other crawlers that never adopted Google's rich result restrictions in the first place.
What is no longer worth doing is building an entire content strategy around chasing a rich result that does not exist anymore. Build the FAQ content because it answers the question. Add the schema because it is nearly free, not because it is the point.
A handful of patterns show up across almost every underperforming FAQ section:
Fixing any one of these usually improves how the page performs. Fixing all of them is what turns a page that technically has FAQs into a page that actually answers questions and earns the call - and building that kind of system across an entire site is exactly where a specialist makes the difference.
Content built to convert
Good FAQs answer questions. A system turns those answers into booked calls.
The Diamond Group builds FAQ content, service pages, and structured data as one connected system, then ties it to the CRM and reporting that shows which content is actually driving calls.
See how Momentum works