FAQ pages have a bad reputation because many of them are filler: ten invented questions nobody asks, answered with marketing slogans. A useful FAQ is the opposite. It collects the questions real buyers ask before they commit, answers each one directly, and points to the page with the full detail. That format happens to match how people search with full questions, and how AI assistants pick short passages to cite.
1. Collect real questions, not invented ones
Spend an hour gathering questions from sources that reflect real demand:
- Emails, chat logs, contact form messages and call notes from the last six months.
- What your sales team and front desk answer every week.
- "People also ask" boxes and related searches for your main services.
- Question queries in Google Search Console, filtered for who, what, how, can, does and is.
- Reviews, including competitors' reviews, where customers mention confusion or surprises.
- Reddit threads and community groups in your industry and city.
Our keyword research guide shows how to estimate which of those questions have meaningful search volume.
2. Decide what belongs on the FAQ and what deserves its own page
Group the questions into themes: pricing, process, timing, eligibility, aftercare, policies. Then sort them. Questions with a short, stable answer belong in an FAQ. Questions that need several hundred words, comparisons or examples deserve a dedicated page or guide, with a one or two sentence summary in the FAQ that links to it. This keeps the FAQ scannable and avoids burying important topics where they cannot rank on their own.
Consider whether one central FAQ page or FAQ sections on each service page serves visitors better. Most businesses benefit from both: service specific questions on the service page, where the buyer already is, and general questions about payment, booking and policies on a central page.
3. Write each question the way a customer would say it
Use the customer's words, not your internal terminology. "How much does a bathroom renovation cost in Toronto?" is better than "Pricing information". "Can I cancel my appointment?" is better than "Cancellation policy". Full natural questions match conversational searches and voice queries, which our voice search guide covers in more depth.
Make each question an actual heading, such as an H2 or H3, rather than bold text. Clear heading structure helps search engines and AI systems understand where each question and answer begins.
4. Answer in the first sentence, then add detail
Start every answer with the direct answer: yes, no, a number, a range or a timeframe. Then explain conditions, exceptions and next steps. A strong answer to "How long does a website redesign take?" opens with "Most small business redesigns take 6 to 10 weeks from kickoff to launch," and only then explains what makes a project faster or slower.
Keep most answers between 40 and 120 words. Shorter is often too vague to be useful. Longer usually means the topic deserves its own page. Avoid answers that only say "contact us", because they help nobody and give search systems nothing to quote.
5. Be specific and honest about the uncomfortable questions
The questions customers hesitate to ask are often the ones that decide the sale: real price ranges, what is not included, how long until results, what happens if something goes wrong. Answering them honestly builds trust and filters out poor fit leads before they cost you time. Give ranges with the factors that move the price. State what you do not offer. Explain your guarantee and its limits in plain language.
6. Use FAQPage markup the way Google now supports it
Since August 2023, Google shows FAQ rich results in search only for well known, authoritative government and health websites, as announced in its update on FAQ and HowTo rich results. For most businesses, adding FAQPage markup will not produce the expandable questions in search results it once did.
The markup is still valid and harmless when it accurately reflects visible questions and answers. It gives machines a clean, labelled version of your content. Follow Google's FAQPage guidelines: the full question and answer must be visible on the page, each question should appear once, and the content must not be advertising. Never mark up questions that are hidden or that users cannot see. Our schema markup guide explains how to add it with JSON-LD.
7. Link answers to deeper pages
Each FAQ answer is a natural place for an internal link. "Do you offer financing?" can answer the question and link to the financing page. "Which areas do you serve?" can link to your service area or location pages. These links help visitors continue, and they help search engines understand the relationship between your pages. See internal linking and site structure for anchor text tips.
8. Make it easy to scan and keep it current
- Group questions under theme headings, with a short jump menu at the top on long pages.
- If you use accordions, make sure the answer text is in the HTML when the page loads, not fetched later by a script.
- Add a "last reviewed" date and update answers when prices, policies or services change.
- Review support tickets every quarter and add any question that came up more than a few times.
- Track which FAQ entries get clicks in GA4 if you use accordions, and promote the popular ones higher.
Sources and further reading
See Google's FAQPage structured data documentation, the 2023 announcement changing FAQ rich results, and the guide to featured snippets.
Frequently asked questions
Does FAQ schema still work in 2026?
FAQPage markup is still valid, but since August 2023 Google shows FAQ rich results only for well known, authoritative government and health sites. For most businesses it will not create expandable results in search, though it remains a clean, accurate description of visible content.
How many questions should an FAQ page have?
As many as customers genuinely ask, usually between 8 and 30 for a small business. Group them by theme. If a question needs a long answer, give it a dedicated page and summarize it in the FAQ with a link.
Should FAQs go on one page or on each service page?
Most businesses benefit from both. Put service specific questions on the relevant service page where buyers already are, and keep general questions about booking, payment and policies on a central FAQ page.
How long should an FAQ answer be?
Aim for about 40 to 120 words. Lead with the direct answer in the first sentence, then add conditions and a link to more detail if needed.
Can FAQ pages help with AI search?
Yes. Clear question headings with direct, self-contained answers are easy for AI assistants to understand and cite. Accuracy and specificity matter more than markup.