How to Write an FAQ Page for Your Small Business Website
A practical guide to building a small-business FAQ page from real customer questions, with a copyable template, worked examples and what changed with FAQ schema in 2026.

A good FAQ page answers the ten to twenty questions your customers actually ask before they buy, in their words, in a few sentences each. This guide shows you where to find those questions, how to structure and write the answers, what changed with FAQ schema in 2026, and gives you a template and worked examples you can copy today.
Key Takeaways
- Build your FAQ list from real sources: support emails, sales calls, reviews, chat logs and search queries, not from what you wish people asked.
- Lead every answer with the direct answer in the first sentence, then add detail. Keep most answers under 80 words.
- Group questions by stage (before buying, ordering, after buying) and put the top five on top.
- Google no longer shows FAQ rich results in search as of May 2026, so write the page for people first. FAQPage markup is still valid schema.org vocabulary but will not earn you expandable snippets.
- Review the page every quarter. An FAQ with an outdated price or policy does more damage than no FAQ at all.
What an FAQ Page Is For (and What It Is Not)
An FAQ page does three jobs for a small business. It removes doubts that stop a sale, it cuts repetitive support work, and it gives search engines and AI assistants clear, quotable answers about your business. A plumber who answers “Do you charge for estimates?” on the site will get fewer calls asking that, and more calls from people who already know the answer and are ready to book.
What an FAQ page is not: a dumping ground for marketing copy dressed up as questions. “Why are we the best bakery in Austin?” is not a question anyone asked. Readers spot these instantly and stop trusting the rest of the page. It is also not a substitute for clear product pages. If the same question comes up about one product, answer it on that product page and keep the FAQ for business-wide topics.
Do you even need one?
Most small businesses do. You probably need an FAQ page if any of these are true:
- You or your staff answer the same five questions by email or phone every week.
- You have policies people care about before buying: shipping, returns, cancellations, deposits, service areas.
- Your service has a process that is not obvious, such as how a consultation works or what happens after a deposit.
- Your pricing has conditions, like minimum orders, travel fees or rush charges.
If your business sells one simple product and every question is already answered on the product page, a separate FAQ page adds little. Put a short FAQ block on that page instead.
Where to Find the Real Questions
The single biggest mistake is inventing questions at a desk. Spend an hour collecting real ones. You will usually end up with 40 to 80 raw questions, which you then trim to the 15 to 25 that matter most.
| Source | What to pull | Time needed |
|---|---|---|
| Support inbox | Search the last 6 months for “?” and common words like “how”, “can I”, “do you”. Note repeats. | 30 minutes |
| Sales calls and front desk | Ask staff for the five questions they hear most. Write their exact wording. | 15 minutes |
| Reviews (yours and competitors’) | Complaints often reveal missing information: “I didn’t know there was a delivery fee.” | 20 minutes |
| Live chat or social DMs | Export or scroll the last 100 conversations. | 20 minutes |
| Google search | Type your service plus “how”, “can”, “cost” and read the “People also ask” box and autocomplete. | 15 minutes |
| Site search and Search Console | Queries people type on your site, and question-style queries that already bring impressions. | 15 minutes |
Keep the customer’s wording. If people ask “Do you deliver to Brooklyn?” do not rewrite it as “What is your delivery coverage area?” Plain wording matches what people search for and what they scan for on the page.
Score and trim your list
Give each question two scores from 1 to 3: how often it is asked, and how much it affects a buying decision. Multiply them. Anything scoring 6 or 9 goes on the page, near the top. Anything scoring 1 or 2 probably goes nowhere, or onto a specific product page. Merge near-duplicates: “Can I return a gift?” and “What is your gift return policy?” become one question.
How to Structure the Page
Structure matters more than design. Someone landing on an FAQ page has one question in mind and wants to find it in seconds.
- A one-line intro. “Answers to the questions we hear most about orders, delivery and returns. Can’t find yours? Call us at…” No welcome speech.
- The top five questions first. Put the highest-scoring questions in a short “Most asked” group at the top. Most visitors will not scroll further.
- Grouped sections. Use 3 to 6 groups with clear labels. Typical groups: Pricing and payment, Ordering or booking, Delivery or service area, Returns and cancellations, About us.
- A contact fallback at the end. Phone, email, hours, and expected reply time.
Each question should be a real heading (an H2 or H3 on the page), not bold text inside a paragraph. Headings help screen readers, help people scan, and help search engines understand which text answers which question.
Accordions or open text?
Collapsible accordions keep a long page tidy, and they are fine to use. Two cautions. First, make sure the answer text is in the page HTML when it loads, not fetched only after a click, so search engines can read it. Second, if you have fewer than about 12 questions, leave them open. Clicking to reveal each answer is extra work for the reader when the whole page would fit on two screens.
How to Write Answers People Trust
Use this formula for every answer: direct answer, then the one or two details that matter, then a link if there is more.
- Start with yes, no, a number or a time. “Yes, we deliver to all five boroughs.” “Standard shipping takes 3 to 5 business days.” Never open with “Great question!” or “At [Business], we believe…”
- Keep most answers to 40 to 80 words. If an answer needs 300 words, it probably deserves its own page, with the FAQ answer summarizing and linking to it.
- Use specifics. Prices, dates, distances, hours. “Small fee” is vague; “$15 within 10 miles” is useful.
- Write in second person. “You can cancel up to 48 hours before” reads better than “Customers may cancel…”
- Admit limits. “We don’t ship outside the US yet” builds more trust than a vague dodge.
- Match your policies exactly. If your FAQ says 30-day returns and your terms say 14, you have a customer service and possibly a legal problem. Copy the policy numbers from the source document.
Before and after
Here is an illustrative example for a fictional home cleaning company.
Before: “Do you bring your own supplies? At Sparkle Home, we pride ourselves on delivering a premium experience. Our team uses only the finest products to ensure your home is spotless and you’re delighted with the result every single time.”
After: “Do you bring your own supplies? Yes. We bring all cleaning products and equipment, including a vacuum. If you prefer we use your products (for allergies or a specific floor finish), leave them out and tell us when you book.”
The second version answers the question in one word, then handles the follow-up question most people would have next.
FAQ Schema in 2026: What Changed
For years, adding FAQPage structured data could give your search listing expandable question-and-answer drop-downs. That is over. Google first limited FAQ rich results to well-known government and health sites in 2023, and its Search Central documentation now states that FAQ rich results stopped appearing in Google Search in May 2026, with the FAQ structured data documentation removed in June 2026. FAQPage no longer appears in Google’s structured data search gallery of supported features.
What this means in practice:
- Do not add FAQ markup expecting a rich result. You will not get one from Google.
- Existing markup is harmless. If your theme or SEO plugin already outputs FAQPage markup, you do not need to rush to remove it. It is still a valid type on schema.org, and other systems may read it.
- Never mark up content that is not visible on the page. That was always the rule and it is still good practice for any structured data.
- The page itself still matters. Clear question headings with short direct answers are exactly the kind of text search engines and AI assistants can quote. Google’s guidance on creating helpful, people-first content applies here more than any markup does.
Search features change often. If you rely on any structured data for traffic, check Google’s current documentation before you build around it.
FAQ Page Template You Can Copy
Fill in the brackets, delete groups you do not need, and keep the order.
| Section | Example questions |
|---|---|
| Most asked (top 5) | How much does [service] cost? How soon can you start? Do you serve [area]? Do you offer [guarantee/warranty]? How do I book? |
| Pricing and payment | Do you charge for quotes? What payment methods do you accept? Is a deposit required? Are there extra fees for [rush/weekend/travel]? |
| Ordering or booking | How far ahead should I book? Can I change my order? What information do you need from me? |
| Delivery or service | How long does delivery take? Do you ship to [state/country]? What happens on the day of service? |
| Returns, cancellations, problems | What is your return policy? How do I cancel? What if I am not happy with the result? |
| About the business | Are you licensed and insured? How long have you been in business? Where are you located? |
| Still have questions? | Phone, email, hours, typical reply time. |
Worked Examples by Business Type
Local service business (illustrative: an HVAC contractor in Ohio)
Top questions likely include: Do you offer emergency service on weekends? Is there a trip charge? Do you service all brands? How long does a furnace tune-up take? Do you offer financing? Each answer should name the actual numbers, such as the trip fee and the service radius, and link to the booking page.
Online store (illustrative: a candle shop selling nationwide)
Expect questions about shipping times and cost, holiday cutoff dates, gift wrapping, returns on used candles, ingredients and burn time. Seasonal questions, like “Will my order arrive before Christmas?”, should sit in the top five from November and come down in January.
B2B or professional service (illustrative: a bookkeeping firm)
Buyers want to know which software you use, how onboarding works, what a monthly package includes, contract length, and who sees their data. These answers often decide whether a prospect books a call, so make them specific.
The media FAQ many businesses forget
If you send out news or get press inquiries, a short “For media” group helps journalists: who handles press questions, how fast you respond, where to find logos and photos, and approved company facts. If you need a refresher on what reporters expect from company announcements, our guide on what a press release is covers the basics, and this group can link to your newsroom page.
Common FAQ Page Mistakes
- Questions nobody asked. Promotional questions erode trust.
- Answers that hedge. “It depends” without explaining what it depends on.
- Stale facts. Old prices, old hours, a closed location, last year’s holiday cutoff.
- No owner. Nobody is responsible for updates, so nothing gets updated.
- Burying the contact option. If someone cannot find an answer, make it easy to ask.
- Duplicating whole pages. Copying your entire returns policy into the FAQ creates two versions that drift apart. Summarize and link.
- Vague page titles. “FAQ” alone is fine for navigation, but the page title tag can say more, such as “FAQ: Pricing, Booking and Service Area | [Business]”. You can test how a title will look in results with our SERP preview tool.
Keep it current: a simple maintenance routine
- Name an owner. One person updates the page.
- Keep a running list. Staff add any new repeated question to a shared document.
- Review quarterly. Check every number, date and policy against the source. Add new questions that hit the scoring threshold. Remove questions nobody asks anymore.
- Do a seasonal swap. Before holidays or busy seasons, move timely questions to the top.
- Show the date. A “Last updated: [month year]” line tells visitors the information is current.
Track whether it works. If support emails about shipping drop after you publish a clear shipping answer, the page is doing its job. If people still ask, the answer is either hard to find or unclear.
Frequently Asked Questions
How many questions should an FAQ page have?
Most small businesses do well with 15 to 25. Fewer than 8 rarely justifies a separate page; more than 40 usually means some answers belong on product or policy pages instead.
Should I still add FAQ schema markup?
Not for Google rich results, which Google stopped showing in May 2026. Existing FAQPage markup is not harmful if it matches visible content, but your effort is better spent on clear headings and direct answers.
Where should the FAQ page link sit in my site navigation?
The footer is standard, and many businesses also link it from the main menu under “Help” or “Support”. Link to specific answers from checkout, booking and contact pages where questions come up.
Is it OK to have FAQ sections on several pages?
Yes. A product or service page can have its own short FAQ about that item. Just avoid copying the same question and answer word for word across many pages; link to one source instead.
How long should each answer be?
Aim for 40 to 80 words, with the direct answer in the first sentence. If you need much more, write a dedicated page and link to it from a short summary.
Can AI tools write my FAQ page?
They can help draft wording, but they cannot know your real questions, prices or policies. Collect the questions yourself and check every fact before publishing.
Your First Hour Starts Now
Open your inbox, search the last six months for question marks, and write down every question you see more than twice. Score them, write the top ten answers using the direct-answer formula, and publish. You can add the rest next week. A short, accurate FAQ page that goes live today beats a perfect one that sits in a draft folder.


