FAQ Schema: How to Win Answer Boxes

A few years ago, FAQ schema was the easiest win in SEO. Add the markup, watch dropdowns appear under your listing, and take up twice the screen space of your competitors. Then Google pulled the plug, and most of the advice published since still pretends nothing happened.

The markup did not stop mattering. It stopped mattering for the old reason. We run this playbook for dozens of local businesses, and the pages built with disciplined FAQ content keep getting pulled into AI Overviews, quoted by ChatGPT, and slotted into People Also Ask. Here is what FAQ schema actually does now, and how to make it earn its keep.

Does FAQ schema still help you win answer boxes?

Yes, but not the way it used to. Google stopped showing FAQ rich results for most websites in 2023, so the markup rarely produces dropdowns anymore. FAQ schema still helps because it structures your answers for AI Overviews, ChatGPT, and People Also Ask, which is where answer boxes actually live now.

FAQ schema is structured data code that labels each question and answer on a page so search engines and AI tools can read them as separate, quotable facts. The visible dropdown reward is gone for most sites, but that machine readable structure is exactly what modern answer engines feed on.

What changed with FAQ rich results?

In August 2023, Google announced that FAQ rich results would only display for authoritative government and health websites. For everyone else, the dropdowns disappeared from search listings almost overnight. HowTo rich results were removed completely at the same time. Your plugin still generates the markup and testing tools still validate it, but a local service business should not expect those dropdowns again.

Here is what Google did not do: it did not penalize the markup, and it did not stop reading it. Structured data still feeds Google’s understanding of what a page covers and which questions it answers. The reward simply moved. The answer boxes worth winning in 2026 are AI Overviews at the top of results, People Also Ask boxes in the middle, and the answers inside ChatGPT and other assistants that never show a results page at all.

Where does FAQ schema still pull weight?

Industry studies consistently show that more than half of Google searches now end without a click. If searchers get answers without visiting websites, the businesses that win are the ones whose answers get used. Structured question and answer content improves your odds in several places:

• AI Overviews: clean question and answer pairs are among the easiest content for Google to lift, summarize, and cite
• ChatGPT and other AI assistants: these tools favor pages that answer one question at a time in plain language
• People Also Ask: matching the exact phrasing of a common question is how you capture those slots
• Voice search: assistants read short, direct answers aloud, and FAQ formatting produces exactly that
• Entity clarity: markup that confirms your services, service area, and business details reinforces the same signals in your Google Business Profile

Notice the pattern. The destination for answers changed, but the format that wins never did: short, direct, structured, and specific. FAQ discipline forces you to write that way.

How do you write FAQ content that earns AI citations?

Write each question exactly the way a customer would type it or say it. Then answer it in the first sentence, keep the whole answer between 40 and 60 words, and commit to specifics: real price ranges, real timelines, real city names. AI engines cite sources that commit to an answer, and a page of vague fluff never gets quoted.

Localize wherever it is honest to do so. An answer that says what a service costs in Winchester, Virginia will outperform a generic national answer for every searcher in the Shenandoah Valley. We build FAQ blocks into service pages and city pages, then reuse the strongest answers in the Q&A section of each client’s Google Business Profile. When an AI engine cross references your website against your profile and finds the same answer in both places, your credibility as a source goes up.

How do you implement FAQ schema the right way?

FAQ schema is added as a small JSON LD script in the page code, and you almost never need to write it by hand. On WordPress, plugins like SEOPress, Rank Math, and Yoast generate valid FAQPage markup automatically from an FAQ block. The rules that matter: the markup must match the visible text word for word, every question must actually appear on the page, and each page should carry only one FAQPage block.

After publishing, run the page through Google’s Rich Results Test to confirm the markup parses, then watch Google Search Console for structured data errors. Google Search Console will also show whether impressions grow for the queries your questions target, which is the honest scoreboard now that the dropdowns are gone.

Which pages deserve FAQ markup?

Not one giant FAQ dump. A single page holding forty questions competes with itself and ranks for nothing. Put three to six questions on each service page and location page, specific to that service and that city. A roofing contractor should answer storm damage questions on the storm damage page and pricing questions on the pricing page.

Look at what a local search results page holds today: Local Services Ads at the top, the Google Maps three pack under that, often an AI Overview, then organic listings. Traditional blue links keep sliding down the screen. Owning the answer layer is one of the few ways a small local business gets seen near the top without paying for it.

FAQ

Do I need a plugin to add FAQ schema in WordPress?

No, but it is the easiest path. Plugins like SEOPress and Rank Math generate the markup automatically when you use their FAQ blocks. Hand coded JSON LD works just as well, as long as it matches your visible content.

Will FAQ schema hurt my site now that Google restricts the rich results?

No. Google simply ignores valid markup it chooses not to display, and there is no penalty for keeping it. The only real risk is marking up questions and answers that do not actually appear on the page, which violates Google’s guidelines.

How long should each FAQ answer be?

Aim for 40 to 60 words with the direct answer in the first sentence. That length is complete enough to be useful and short enough to be quoted whole by an AI engine or a featured snippet.

Bottom Line

FAQ rich results are gone for most websites, but the markup and the discipline behind it moved up the funnel: AI Overviews, ChatGPT, People Also Ask, and voice answers all reward the same structured question and answer format. Write real questions, answer them in the first sentence, localize the details, and keep the markup matched to the visible page. That is the difference between publishing content and getting cited. Local Klicks builds this answer layer into every service page and city page we create, and we will show you what it looks like for your business: call (540) 299-2718 for a free consultation.

Related reading: How to Automate Review Requests Without Annoying Customers, How to Build Location Pages That Actually Rank