How to write FAQs for SEO and AI answer engines

The questions were never the weak part. The answers were.

What changed for FAQs in 2026?

Google no longer shows FAQ rich results, and it says AI Overviews and AI Mode need no special markup. Its documentation gives FAQ content no special treatment, so a good FAQ is now just helpful text on an indexed page.

Google’s Search Central changelog has two entries that matter (Google Search Central, documentation updates, accessed 22 Oct 2026).

The second fact comes from Google’s page on AI features in Search. A page is eligible as a supporting link if it is indexed and eligible to be shown with a snippet, with no additional technical requirements.

The same page says there are “no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary,” and no special schema.org structured data to add. The page was last updated 10 Dec 2025 (Google Search Central, AI features, accessed 22 Oct 2026).

Do FAQs still help SEO?

Indirectly, and the evidence is thinner than most vendors admit. An FAQ adds visible text that answers follow-up questions. Nothing Google documents says FAQ sections rank pages, so we sort the claims you will hear into three groups.

What Google documents: the FAQ rich result is gone, AI features need no special markup, and structured data must match visible content. Snippets are primarily created from the page content itself (snippets, accessed 22 Oct 2026). You cannot choose a featured snippet (featured snippets, accessed 22 Oct 2026).

Our view, from practice: an FAQ is the cheapest place to answer what a buyer wonders just before calling. It also keeps objections out of the main copy, where they would bloat a page that should stay focused.

Theory we have not tested: that engines favor short question-and-answer blocks. Google’s documentation says no special optimization is needed, so we would not build a strategy on it.

Google’s people-first guidance backs the middle group. It says content should leave readers feeling they learned enough to reach their goal. It also says content that leaves readers to search elsewhere is a warning sign (Google Search Central, helpful content, accessed 22 Oct 2026).

For the wider schema debate, see our post on whether schema helps SEO at all, which separates documented effects from folklore.

How do you find questions worth answering?

Start with what real people asked you, not with a keyword tool. Sales calls, emails, chat logs, reviews and Search Console queries carry the exact words customers use, which is what an FAQ question should sound like.

We work through the sources in this order, starting with the ones closest to the customer’s own wording:

1. Sales and support conversations. Ask whoever answers the phone for the five questions they answer every week, and write them down verbatim.
2. Search Console. In the Performance report, filter queries for words like “how,” “what,” “can,” “does,” “cost” and “how long.” Questions your page already earns impressions for are strong candidates.
3. Objections. Price, timing, warranties and disruption make prospects hesitate, and each one is a question.
4. Related searches: the People Also Ask box and related searches give ideas only. In our experience the box changes by query and by day, so we never treat it as a spec. See People Also Ask.

Then cut. A question stays if all three of these are true:

• A real prospect asks it before buying.
• You can answer it accurately today.
• The answer will still be true in six months.

Take a hypothetical tally. A plumber’s front desk logs 20 inbound calls in one week. Of those, 8 ask about cost, 5 about same-day availability, 3 about permits, 2 about warranty and 2 about brands.

The first four questions cover 18 of the 20 calls, or 90%, so they become the FAQ. Brands gets a sentence in the body only if the company really installs a limited range.

Here is the same hypothetical tally as a chart.

• Cost8 calls
• Same-day availability5 calls
• Permits3 calls
• Warranty2 calls
• Brands2 calls

Source: Hypothetical example

View the data as a table

Item	Value
Cost	8 calls
Same-day availability	5 calls
Permits	3 calls
Warranty	2 calls
Brands	2 calls

Our content brief generator can turn a target query into a draft outline, including a question list to check against your own call notes.

How do you write one FAQ answer?

Answer first, add the conditions, then give the next step. The opening sentence has to work if it is the only sentence anyone reads. Everything after it supplies the “it depends” that keeps the answer honest.

The method below is our own practice and not a Google specification, so adjust the numbers to your market:

1. Phrase the question the way a customer would. “How much does a water heater replacement cost?” beats “Pricing.”
2. Put the answer in sentence one. That means the actual answer or an honest “it depends on X and Y,” with no warm-up and no restated question.
3. Add the one or two conditions that change the answer. A number without its conditions is a trap.
4. Name things. “A 50-gallon gas tank water heater” is quotable and unambiguous. “Your unit” is neither.
5. Date anything that can change. Prices, rules and policies get “as of October 2026.”
6. End on the next step or stop. A link to the relevant page is fine, and a sales pitch is not.
7. Hold it to 40 to 90 words. Under 40 usually drops the conditions. Over 90 usually means you are writing a section.
8. Strip references to the rest of the page. Phrases like “as mentioned above” break the moment someone meets the answer alone.

1. Phrase it like a customerUse the words a customer would use for the question.
2. Answer in sentence oneNo warm-up and no restated question.
3. Add the conditionsInclude the one or two things that change the answer.
4. Name thingsBe specific and quotable, not vague.
5. Date what can changePrices, rules and policies get an as-of date.
6. End on the next stepA link to the relevant page is fine. A sales pitch is not.
7. Hold it to 40 to 90 wordsShort enough to stand alone, long enough to keep conditions.
8. Strip page referencesAvoid phrases like as mentioned above.

Google adds one warning sign worth keeping in mind (Google Search Central, helpful content, accessed 22 Oct 2026). It asks about content that promises an answer to a question with no answer, such as suggesting there is a release date. If you do not know, say what is known and what is not.

What do good FAQ answers look like in practice?

They name the variables, carry a date where rules change, and say who decides. The three rewrites below are illustrative, written for a made-up plumber in Phoenix. They are not client work, and we did not capture how any of them rendered in AI Overviews or People Also Ask.

Question 1: cost

Before (25 words):

At Acme Plumbing we pride ourselves on transparent pricing and quality service. Every home is different, so contact us today about your water heater needs.

After (61 words):

Water heater replacement costs vary depending on four things: tank size, fuel type (gas or electric), whether the venting has to change, and permit fees. We give a written quote after a site visit at home. Ask that the unit’s model number, the labor and the haul-away of the old tank appear as separate lines, so you can compare quotes fairly.

The first version contains no answer. The second names the variables, explains how quoting works and hands the reader a checklist. It carries no dollar figure on purpose, so add one only with a date and a source.

Question 2: timing

Before (17 words):

Our expert technicians work quickly and efficiently to get your water heater replaced in a timely manner.

After (61 words):

A tank replacement can be a same-day job when the new unit is in stock and the old one sits somewhere easy to reach. Moving a gas line, upgrading the venting or pulling a permit can add a day or more. We confirm the expected timeline when we book the visit, and we tell you if a permit inspection changes it.

Vague adjectives became conditions, which is what lets a skeptical reader believe the claim. Publish only timing your crew will actually honor.

Question 3: a rule that changes

Before (13 words):

Do you need a permit? Rules vary, so please check with your city.

After (58 words):

Water heater replacements often need a permit, but the rule depends on your city and county. Call your local building department before work starts, and ask your plumber whether they file the permit or you do. This is a general answer for a hypothetical Phoenix service area, so check it against your own city.

Last checked: October 2026.

The rewrite admits the limit, says who decides and carries a date. When a rule changes, the date tells you which answer to revisit.

What the three rewrites share

Each rewrite does the same three things. It names the variables, carries a date where rules change, and says who decides.

Use those three checks on your own answers:

• Does the answer name what changes the result?
• Does it carry a date if a rule or price can change?
• Does it say who decides, such as the city or the plumber?

Ask these questions before you publish, and again at each quarterly review.

Where should FAQs go on a page?

After the main content of the page they support, with the one objection that blocks the sale pulled up into the body. A separate FAQ page that gathers unrelated answers usually helps neither readers nor search.

• Service pages: five to eight questions at the bottom, with pricing and timing first, because those decide whether the visitor calls.
• Blog posts and guides: only what a reader would ask after finishing. Don’t recycle the headings as questions.
• Location pages: only genuinely local questions, such as permits, utility rules and seasonal timing. Swapping the city name into the same ten answers is how doorway pages get made.

Keep answers visible. Google’s structured data guidelines say not to mark up content that readers cannot see (Google Search Central, structured data policies, accessed 22 Oct 2026).

In our view a collapsed accordion is fine for readers. Check the page source, though, to confirm the answer text is there on load and not fetched only after a click.

Our post on FAQ pages and SEO covers the standalone-page question. The service page SEO guide shows where the FAQ sits in the full layout.

Should you still add FAQ schema?

Only if the markup stays identical to the visible text. FAQPage markup is optional, earns no rich result now and is not required by Google’s AI features. Mismatched markup carries risk and no payoff.

Google says its AI features need no special schema, and its structured data rules require markup to describe visible content. At best, clean FAQPage markup is a tidy record of your own content.

Whether to keep markup comes down to who maintains it, and we decide with three rules:

• If your CMS generates the markup from the visible FAQ block, leave it on.
• If someone has to hand-write JSON-LD for each page, skip it. It will drift out of sync within a quarter.
• If the markup contains text that is not on the page, remove it now.

One piece of our own evidence, with limits. Our case study (a B2B site) records FAQ schema on 343 posts. It also records Google clicks of 4,802 in September 2026 against 1,637 in April 2026, from Search Console (case study).

The case study does not isolate the markup’s effect, so we cite it as context and not as proof that FAQ schema works.

On the markup side, read our FAQ schema for AI post and the structured data for services guide.

How do you check whether your FAQs are being used?

Run a dated check on a fixed list of queries and write down what you see. Nobody outside Google can see which sentences feed an AI Overview, so an observation log is the honest method. Treat it as observation, not proof.

The protocol takes about an hour to set up and a few minutes per check afterward:

1. Pick 10 to 20 queries that match your FAQ questions.
2. Search in a logged-out, private window on one device and location. Note the date and time.
3. Record whether an AI Overview appears, which sources it links, and whether your page is among them.
4. Record whether a People Also Ask box shows your question or a close variant.
5. Repeat on a fixed schedule, such as every two weeks, with the same queries.
6. Change one thing at a time, and write the change next to the date.

The steps repeat, so it helps to see them as a loop.

1. Pick the queriesChoose a fixed list that matches your FAQ questions.
2. Search and note the dateUse a logged-out, private window on one device and location.
3. Record what you seeNote any AI Overview, its linked sources and any People Also Ask match.
4. Change one thingEdit one item at a time and write the change next to the date.
5. Repeat on scheduleRun the same queries again, such as every two weeks.
6. Back to step 1

A simple log needs only these columns, one row per query per check, in any spreadsheet:

One snapshot proves little. Google says AI Overviews appear only when its systems determine they are additive to classic Search. So an empty result on a given day may only mean none was triggered.

Search Console helps in a limited way. Google says traffic from AI Overviews and AI Mode is counted in the Performance report under the Web search type. So it is not labeled separately (Google Search Central, AI features, accessed 22 Oct 2026).

For tooling and its limits, see our guide to measuring AI visibility and the post on GEO measurement limits.

What mistakes do we see in FAQ sections?

Most weak FAQs answer questions nobody asked, restate the question, and bury the answer under marketing copy. These seven are the ones we fix most often, each with its fix.

1. Questions invented from keywords. “What is the best HVAC company?” is not something customers ask your own page. Use the call log instead.
2. One FAQ pasted on every page. Identical blocks add no information. Write a different set for each page’s job.
3. Answers that open with “At Company X, we…” The reader asked about their problem. Open with the answer.
4. Superlatives and promises. “Fastest, cheapest, guaranteed” answers nothing. Replace each with the condition behind it.
5. Numbers with no date or condition. They go stale and mislead, so add “as of” and the variable.
6. Markup that no longer matches the page. Recheck after every template change.
7. No owner. Name one person to review FAQs every quarter, and sooner when prices, rules or services change.

What does the data not show?

We have not run a dated AI Overview or People Also Ask capture for before-and-after FAQ rewrites. So we cannot say that any rewrite earned a citation. The examples above are illustrative.

Three things remain unproven. No source we opened shows that short question-and-answer blocks are cited more often by any AI system. None shows FAQ schema helps AI visibility, and Google says no special schema is needed.

The 40 to 90 word range is our working choice, picked so answers carry their conditions and still stand alone. If you test a rewrite, keep the log above and record the misses too.

Frequently asked questions

Next step

Take your most important service page and list the five questions callers ask before booking. Rewrite each answer with the method above, starting from our content brief generator.

For the wider approach to AI search, see our AI search optimization service, the AI search optimization guide and how to rank in AI Overviews.

Get Your Organic Growth Plan

Sources

• Google Search Central, “Latest Google Search Documentation Updates” (FAQ rich result deprecation 8 May 2026 and removal 15 Jun 2026): https://developers.google.com/search/updates (accessed 22 Oct 2026)
• Google Search Central, “AI features and your website”: https://developers.google.com/search/docs/appearance/ai-features (accessed 22 Oct 2026)
• Google Search Central, “Creating helpful, reliable, people-first content”: https://developers.google.com/search/docs/fundamentals/creating-helpful-content (accessed 22 Oct 2026)
• Google Search Central, “General structured data guidelines”: https://developers.google.com/search/docs/appearance/structured-data/sd-policies (accessed 22 Oct 2026)
• Google Search Central, “Snippets”: https://developers.google.com/search/docs/appearance/snippet (accessed 22 Oct 2026)
• Google Search Central, “Featured snippets”: https://developers.google.com/search/docs/appearance/featured-snippets (accessed 22 Oct 2026)