How do you write an FAQ section that wins featured snippets?

A plumber in a mid-size city added six questions to the bottom of a service page and started appearing in Google’s “People also ask” box within three weeks. To write an FAQ for featured snippets, phrase each question exactly as people search it, answer it in the first two sentences in 40 to 55 words, and keep every answer standalone.

What exactly is a featured snippet, and why does an FAQ win them?

A featured snippet is the boxed answer Google pulls to the top of the results page, above the regular blue links. Google doesn’t write it — it lifts the text from a page that already answers the question cleanly. An FAQ section wins snippets because it hands Google a pre-formatted question and a pre-formatted answer.

There are four snippet formats worth knowing: paragraph, list, table, and video. FAQ sections almost always compete for the paragraph snippet, which is the most common type on the results page.

The same structure feeds a second surface: “People also ask.” That accordion of related questions sits mid-page on most searches, and Google populates it from pages where a heading asks the question and the text right below it answers the question.

Both surfaces reward the same thing. Google needs a 40 to 60 word block of text that makes complete sense when it’s torn out of your page and shown alone.

And in 2026 the stakes are higher than a blue link. The same extractable blocks are what ChatGPT, Gemini, and Google AI Overviews quote when someone asks for a recommendation in your city. One FAQ answer can serve a snippet, a PAA box, and an AI answer at the same time.

That is why FAQ work pays off faster than most on-page SEO tasks. You are not trying to outrank a national brand on a broad keyword — you are answering a long, specific question that most competitors never wrote down.

How do you find the right FAQ questions to answer?

Pull your FAQ questions from four places: Google’s own “People also ask” boxes, autocomplete suggestions, the questions customers type into your inbox, and your Google reviews. Never invent questions from imagination — invented questions have no search volume and win nothing.

Start with the search bar. Type your core service plus your city, then read every PAA question Google shows. Click one open and Google loads more — that tree is a free map of what real people ask.

Next, mine your reviews. Reviews are the only place where customers describe your business in their own vocabulary, including the worry they had before booking and the thing that surprised them after. A review that says “I was nervous about the price but they sent a written quote first” is telling you the question is “do you give written quotes before starting work?”

Your inbox and phone log are the third source. Write down every question you answer more than twice a week — those are the questions costing you time and the ones your competitors also ignore.

The fourth source is your booking objections. Parking, payment methods, cancellation windows, how far you travel, whether you handle emergencies on Sundays. These feel too mundane to publish, which is exactly why there is so little competition for them.

One rule on phrasing: keep the question the way a human typed it, not the way a marketer would write it. “How much does a boiler service cost?” wins snippets. “Boiler servicing pricing information” wins nothing. If you want more help turning review language into content, our guide on how to ask customers for Google reviews covers how to collect the specific, detailed feedback that makes good FAQ source material.

Your reviews already hold the questions

KAIRO reads your public Google reviews and turns the questions customers actually ask into articles with FAQ sections built to be quoted. You keep running the business.

See how KAIRO works

What are the featured snippet formatting rules for FAQ answers?

Follow five formatting rules: put the question in an H3 heading, answer in the very first sentence, keep the full answer to 40 to 60 words, write two to three sentences maximum, and make the answer readable with zero context from the rest of the page.

The word count matters more than people expect. Google’s paragraph snippets average roughly 40 to 50 words, and answers longer than about 60 words get truncated or skipped. Write the answer, then cut it down.

Sentence one carries the complete answer. Sentence two adds the supporting detail — a number, a condition, an exception. Sentence three gives an example or the next step. That is the whole shape.

Avoid pronouns and back-references at the start of an answer. “It usually takes about two weeks” is useless out of context; “A standard kitchen install usually takes about two weeks” survives extraction.

Keep each question on its own heading level and never bury an answer inside a long paragraph that also covers three other ideas. One question, one heading, one tight answer block, then move on.

A few more mechanics that help: use digits for every number and price, name your city in at least two answers, and skip hedging words like “typically it may depend.” Google prefers a confident sentence with a specific range over a careful sentence that commits to nothing.

Finally, place the FAQ where it belongs — at the bottom of a page that already covers the topic in depth. A standalone FAQ page with 40 unrelated questions performs worse than six questions attached to the service page they relate to.

Is FAQ schema still worth adding in 2026?

Yes, FAQ schema is still worth adding, but for a different reason than it was in 2021. Google stopped showing FAQ rich results for most sites in 2023, so you will rarely see the accordion in search results. The markup still helps machines parse your page, and that matters for AI answers.

Here is the honest version. FAQPage structured data no longer reliably produces the expanded dropdown under your listing unless you are a government or health site. The visual perk is mostly gone.

What hasn’t gone is the parsing benefit. Schema tells a crawler, unambiguously, “this string is a question and this string is its answer.” That is exactly the pairing large language models need when they assemble an answer and pick a source to cite.

The critical rule: your schema must match your visible text word for word. Markup that describes content a visitor can’t see on the page is a spam signal, and it can get structured data ignored sitewide.

So the order of priority is clear. Write the visible FAQ properly first, then mark it up. Schema on a badly written FAQ wins nothing; a well-written FAQ wins snippets even with no schema at all.

If your goal is AI citation specifically, the markup is one input among several — reviews, consistency across pages, and a crawlable site all count too. Our guide on how to get cited in Google AI Overviews walks through the rest of the picture.

What does a good FAQ section look like, with real examples?

A good FAQ section has four to six questions, each phrased as a real search query, each answered in 40 to 60 words, and all of them relevant to the page they sit on. Here is what that looks like for three kinds of local business.

Restaurant

Question: “Do you take walk-ins on Friday night?” Answer: “We hold a few tables for walk-ins every Friday, but the dining room is usually full after 7 p.m. If you’re a party of four or more, book ahead — we take reservations up to 30 days out by phone or through the website. Bar seating is always first come, first served.”

Dental clinic

Question: “How much does a dental cleaning cost without insurance?” Answer: “A standard cleaning for a new patient without insurance runs in the range we quote at booking, and the price is confirmed before any treatment starts. The appointment includes the exam, the cleaning, and a written treatment plan if we find anything. Call for a current quote.”

Auto shop

Question: “How long does a brake pad replacement take?” Answer: “Front brake pads on most cars take 60 to 90 minutes, and we can usually do it the same day if you call before noon. Rotors add about 30 minutes. We send a photo of the worn pads before we start, so you see what you’re paying for.”

Notice the pattern in all three. The first sentence answers the literal question, the second adds a number or a condition, the third removes a worry. None of them need the rest of the page to make sense.

Notice also what is missing: no slogans, no “we pride ourselves on,” no sentence that could belong to any business in the category. Specifics are what get quoted.

How do you keep an FAQ section working month after month?

Treat the FAQ as a living list. Review it every quarter, delete questions that no longer get asked, add the new ones your customers started asking, and check which answers are actually winning snippets. An FAQ written once and forgotten loses ground in about a year.

Start with measurement. In Google Search Console, filter your queries by ones starting with “how,” “what,” “can,” and “do” — those are question searches. If a question gets impressions but almost no clicks, Google may already be reading your answer in a snippet, which is a win worth protecting.

Then look for gaps. Any question you answered by phone this month that is not on the site is a gap, and a gap is a page a competitor can take.

Pair the FAQ work with the rest of your local presence. FAQ answers, Google Business Profile posts, and your review volume all push the same signal, which is why our guide on how to rank in the Google Maps local pack is a useful companion read.

Be realistic about timing. New FAQ content on an established site often starts showing in PAA boxes within three to eight weeks; a newer domain usually needs three to six months of consistent publishing, as we break down in how long does local SEO take.

This is where most owners stall. Writing six good answers takes an hour; writing six good answers every month for a year takes a system, and the business owner is never the right person to run it.

At KAIRO, that is the job we took on. We read every Google review a business has received, pull the real questions out of them, and publish 4 SEO/AEO articles a month to the client’s site — each one checked by our own quality gates, each one with an answer-first FAQ built in, plus Google Business Profile posts and a monthly proof report you can check. One subscription, no contract, cancel anytime. If you want to see what your own reviews would produce, request a personalized quote.

Snippet-ready articles every month

If writing six tight answers sounds like one more job for Sunday night, KAIRO publishes the articles for you — formatted for snippets, PAA boxes and AI answers.

Start with KAIRO

Frequently asked questions

Can you give me some examples of FAQ questions?

Good FAQ questions are the ones customers actually type: “how much does a cleaning cost without insurance,” “do you take walk-ins on Friday night,” “how long does a brake pad replacement take,” “do you give written quotes before starting work.” Each one names a service, a price, a time, or a condition. Pull yours from Google’s “People also ask” box and from your own reviews rather than inventing them.

How do you write FAQ?

Write each FAQ as a question in a heading followed by a 40 to 60 word answer that opens with the answer itself. Use two to three sentences: the direct answer, a supporting number or condition, then an example or next step. Avoid pronouns at the start so the block still makes sense when Google shows it alone.

What does a good FAQ look like?

A good FAQ has four to six questions, all relevant to the page they sit on, each phrased in real search language and answered in two to three tight sentences. Answers include specific numbers, prices, or timeframes instead of slogans. The whole section sits at the bottom of a page that already covers the topic in depth.

Is FAQ schema still relevant?

FAQ schema is still relevant for machine parsing, but it rarely produces visible rich results anymore — Google restricted FAQ rich snippets to government and health sites in 2023. The markup still tells crawlers and AI models which text is a question and which is its answer. Keep it, make sure it matches the visible text word for word, and prioritize the writing over the markup.

How long does it take for an FAQ to win a featured snippet?

On an established site with existing rankings, a well-formatted FAQ answer can appear in a featured snippet or “People also ask” box within three to eight weeks. A newer domain usually needs three to six months of consistent publishing before Google trusts it as a source. You generally need to already rank in the top 10 for the query before a snippet is available to you.

Should my FAQ be a separate page or part of each service page?

Put your FAQ at the bottom of the page it relates to, not on one catch-all FAQ page. Google reads the question and the surrounding topical content together, so six questions on your brake service page outperform 40 mixed questions on a single FAQ page. Use a central FAQ page only for general policy items like payment, parking, and hours.