You answered the same question on the phone again this week. Someone asked how long the job takes, whether you work in their area, or what they need to have ready before you start. You answered it last Tuesday too, and you will answer it next week. So, you start wondering whether a page on your site could do that talking for you. That is the real question behind a search for a faq page for website visitors: not what an FAQ page is, but whether one would save you the interruptions and help customers decide, and what to put on it without building something nobody keeps current. Usually a small business does not need a huge standalone FAQ page. It needs clear answers to the questions customers keep asking, placed where those customers are deciding. You can find those questions in about ten minutes, and the list will tell you which answers belong on one page and which belong on your service pages.
Key Takeaways
List the ten questions your staff answer most by phone and email, then check which ones your website already answers clearly.
Company-wide questions go on one central page; questions that decide whether someone picks a particular service go on that service page.
Since August 2023, Google shows FAQ rich results only for well-known, authoritative government and health sites, so FAQPage markup is not a reason to build the page.
A short, real FAQ beats a long, imagined one
Customers read an FAQ to settle a worry before they call, book or buy. A page that answers the worries they actually have does that job. A page padded with questions nobody asks does not. Nielsen Norman Group's guidance on FAQs says short and medium lists work well as a list of questions followed by answers, and that longer collections may need topic pages. The practical rule for a small business is to publish the useful questions you can answer accurately and stop there.
That also keeps the page maintainable. Every answer is a promise about your price, timing, policies or process, and every one of them can go out of date. Ten answers that someone checks are worth more than forty that nobody does. You will also find that a few of your ten questions fit better on pages you already have, such as your contact page, your pricing page or your booking flow, and need no new page at all.
Pick your questions from what customers already ask you
The best source of FAQ questions is your own inbox and phone. Nielsen Norman Group recommends using incoming questions and customer-service data to shape an FAQ, then placing the important answers on the pages that generate the questions. Useful places to look include:
- Phone calls and voicemails
- Sales emails and contact-form messages
- Chat transcripts and support tickets
- Review language, where customers describe what surprised them
- Search Console queries, which show the words people typed before reaching your site
- Questions your staff answer out loud at the counter or on a site visit
Rank what you find by how often it comes up, how much it matters to the decision, and how hard the answer is to find today. Keep the customer's own wording for the question, and write the answer in precise business language. Remove anything that is not genuinely common or useful, and do not copy a competitor's list; their customers asked their questions, not yours.
The ten-minute check shows what your site is missing
Set a timer for ten minutes and write down the ten questions your staff answer most often. These are the ones that come up for almost any business:
- What does the business provide?
- Who is the service for?
- How much does it cost, or what determines the price?
- How long does it take?
- What areas or customers do you serve?
- What does the customer need to provide?
- What happens after the first contact?
- How do customers book, buy, request a quote or start?
- What payment, cancellation, return, warranty or contract rules apply?
- What makes this business different from the alternatives?
Replace any of these with the real ones from your own calls. Then search your website for each question, as a stranger would. Mark every answer as clear, partial, outdated or missing. Missing and outdated answers are your first publishing list. Partial answers usually need a number, a time frame or a next step.
General questions go on one page and deciding questions go on the service page
Nielsen Norman Group's hub-and-spoke model for customer-service information says an FAQ should offer an alternative view of that information in common-question form, while the relevant information should also sit on the pages where people need it. Baymard Institute's product-page guidance holds that FAQs answer detailed concerns without making the main description unwieldy. For a small business, that turns into a simple split between a central page and your service pages.
| Question type | Best home | Examples |
|---|---|---|
| Company-wide | Central FAQ page | Service area, how booking works, payment and cancellation rules |
| Decides a specific service | That service page | Who it fits, what you need to provide, timing, what affects price |
| Next step | Beside a button or form | How to request a quote, what happens after you reach out |
| Rare or one-off | Answer by phone or email | Anything fewer people ask than it is worth maintaining |
The service-page questions matter most, because that is where a visitor is deciding. If someone is reading about a particular service and has to leave to find out how long it takes, you have asked them to do your work. Put the answer where the question comes up, and link from there to your contact route.
Write each answer so it ends with something the customer can do
A good FAQ answer gives the direct answer first, then the qualification, then the next step. "The job takes two days, longer if the surface needs repair first. Send us a photo with your quote request and we will confirm the timing" does all three. Compare that with a vague answer that promotes your business and leaves the question open.
Check each answer for the same few problems:
- It answers a question nobody actually asks.
- It leaves out the price, the timing, who it is for or what is required.
- It sounds promotional and has no next step.
- It repeats another page without linking to it.
- It is hard to scan on a phone, with long blocks of text and no visible question.
Visible question text, short paragraphs and links to the relevant service or contact page fix most of these. Test the page on your own phone before you call it done.
Markup for FAQs is not a reason to build the page
Guides often tell you to add FAQPage structured data so Google shows your questions in expanded results. Google's August 8, 2023 announcement says FAQ rich results from FAQPage structured data "will only be shown for well-known, authoritative government and health websites." For other sites, Google says the rich result will no longer be shown regularly. The same announcement says you may leave the markup in place, and that structured data that is not used "does not cause problems for Search, but also has no visible effects in Google Search." You can read the original in Google's announcement on HowTo and FAQ rich results.
So, the reason to publish an FAQ is the customer: clearer expectations, fewer repeated explanations and a page that works while your office is closed. Google's people-first content guidance says content should be created primarily for people, not to manipulate rankings. If you do add markup, it should describe the questions and answers visible on the page, and it should never be treated as a promise of how Google will display them. Schema.org defines FAQPage as a page of frequently asked questions with one answer per question. Our post on schema markup for a local business covers markup more broadly.
Clear answers help search and AI answer systems understand you, with no promises
An FAQ can make your policies, process and qualifications easier for people and automated systems to understand. Google says AI Overviews and AI Mode use links from its Search index, and that a page must be indexed and eligible to appear with a snippet. Google also says there are no additional technical requirements or special optimizations for inclusion in AI features, as described in its documentation on AI features and your website.
That means plain fundamentals are your best tools: clear question headings, direct answers, text that search engines can read, accurate internal links and first-hand information about how your business works. None of that guarantees a citation, traffic or a sale, and a generic list of keyword variations adds nothing. Specific answers are what give someone a reason to visit your site instead of reading a summary. Service area, turnaround time, pricing factors, cancellation rules and what happens after a form is submitted are facts only you can give.
Upkeep is where FAQ pages fail, and each failure has a plain fix
The common problems are operational, not technical. This table shows what each one takes to fix.
| Problem | What fixing it involves | Size of job |
|---|---|---|
| Questions nobody asks | Review calls, emails and reviews, then swap imagined questions for real ones | Small content job |
| Service answers only on a general page | Move or repeat a short answer on the service page | Small to medium |
| Vague answers with no next step | Add the specifics and a clear action | Small content job |
| Price, timing or rules missing | You decide the policy first, then write it | Medium |
| Hard to scan on a phone | Visible questions, short paragraphs, links | Small design job |
| Answers out of date | Name an owner and set a review date | Ongoing |
The last row is the one that quietly breaks FAQ pages. Give one person ownership of the page and set a regular review date, and update the answers whenever your services, policies, hours, eligibility or process change. A page that contradicts your current policy is worse than no page.
Hiring help makes sense when the work is deciding where answers belong
You can run the ten-minute check yourself, and you may find that two or three answers on existing pages are all you need. That is a good outcome, and it costs nothing. Help becomes worth paying for when the harder work begins: separating general questions from service-specific objections, deciding which page answers each one, reconciling conflicting answers from different staff members, writing precise copy for pricing and policy topics, testing the page on a phone, connecting answers to your contact or booking step and assigning someone to maintain it. The reason to hire help is a clear, maintainable site that supports real decisions, and not a promised FAQ rich result.
Check your FAQ plan
Pick an answer to begin.
1. Where should a question about how long a specific service takes go?
2. What does Google's August 2023 change mean for a small business that adds FAQPage markup?
3. What is the best place to find your FAQ questions?
Frequently Asked Questions About faq page for website
Do I need a standalone FAQ page?
Usually only if customers ask recurring questions that span several services, policies or processes. Otherwise, answer the questions on the pages where they come up.
Should FAQs go on service pages?
Yes, when the question affects the decision to choose that service, such as fit, requirements, timing, price factors or what you deliver.
How do I choose which questions to include?
Start with repeated calls, emails, chats, reviews and sales questions. Rank them by how often they come up and how much they matter to the decision.
How many questions should I publish?
Publish the useful questions you can answer accurately. A short set that someone keeps current is better than a long list of imagined questions.
Does FAQ schema guarantee a Google rich result?
No. Since August 2023, Google has limited FAQ rich results to well-known, authoritative government and health websites.
How often should I update my FAQ page?
Update it whenever your services, policies, pricing factors, hours, eligibility or process change, and review it on a set schedule.
Final Thoughts
An FAQ page earns its place when it answers questions your customers really ask. Start with the ten questions you answer most often, check what your site already says, and decide for each one whether it belongs on a central page, on a service page or in your booking flow. Company-wide answers go in one place, and the answers that decide a particular service go beside it.
Google's 2023 change means the markup is not a promise of expanded results, so build the page for the customer who is deciding right now. Name someone who keeps the answers current, test the page on a phone, and add the next step to every answer. You may find the whole job is a few paragraphs on pages you already have.
If you would rather have help deciding where each answer belongs and writing them, Web Leveling designs and builds sites around the questions your customers actually ask, and our web design work includes structuring that content so it stays accurate. If the ten-minute check shows you can fix it yourself, we will tell you so. We work with small and medium businesses across the country and overseas. Send us the questions your customers keep asking, and we will help you decide where they belong.
Terms
FAQ words in this post
Tap a term to see what it means.
FAQ page. A page of common customer questions with a short answer to each.
FAQPage markup. Structured data that describes the questions and answers visible on a page; Google limits FAQ rich results to well-known, authoritative government and health sites.
Rich result. An expanded search listing that shows extra details beyond the usual title and description.
Hub-and-spoke model. Nielsen Norman Group's approach of keeping customer-service information on a central hub while also placing it on the pages where people need it.
Service page. A page about one specific service, where a visitor decides whether to contact you.
Search Console. Google's free tool that shows which searches bring people to your site.
