Your website should have FAQs when customers repeatedly ask questions that genuinely affect whether they buy, enquire or understand the service. You do not need an FAQ section simply because somebody told you it is good for SEO.
Useful FAQs reduce uncertainty.
Bad FAQs add clutter.
That is the distinction.
Start with questions customers actually ask
The best FAQ source is not a keyword tool.
It is the business.
What appears repeatedly in emails?
What do people ask on the phone?
What stops a quote moving forward?
What causes confusion after somebody books?
Those questions are commercially useful because the customer already proved they care about the answer.
If ten clients have asked:
Do I need to supply all the website content?
that deserves consideration.
If nobody has ever asked:
What makes your company uniquely positioned to deliver excellence?
do not invent it as an FAQ.
FAQs can remove objections before contact
A visitor may be interested but uncertain.
Do you serve my area?
How long will the project take?
Can I use my existing domain?
Do you require a deposit?
What happens after I enquire?
Can I update the site later?
Clear answers reduce the amount of ambiguity between interest and action.
That is why FAQs can support website conversion without behaving like aggressive sales copy.
They answer the question the visitor was already asking themselves.
Put the answer near the relevant subject when possible
Not every question needs to live in one giant FAQ block.
If a question is specifically about pricing, it may belong beside pricing.
If it is about one service, answer it on that Services page.
If it is about delivery, it may belong near the process.
This is often better for the visitor because they receive the answer at the moment it becomes relevant.
A separate FAQ section is useful for recurring questions that do not fit naturally elsewhere.
Worth knowing
I would never add twenty invented FAQs simply because somebody said Google likes questions. If the questions are real, answer them. If the answer is important enough to the buying decision, it may belong in the main page rather than being buried in an accordion. Useful content first; FAQ formatting second.
Do FAQs help SEO?
They can help a page become more useful and cover real customer language.
That can support search visibility indirectly because the content answers relevant questions.
But the SEO value comes from the usefulness of the information.
Not from the fact that it is formatted as "Question / Answer".
This distinction has become even more important.
Google stopped showing FAQ rich results in Search in May 2026 and removed its FAQ rich-result documentation the following month.
So creating dozens of FAQs in the hope of earning special Google result treatment is now an outdated strategy.
Write FAQs for customers.
Not for a search-result feature that no longer exists.
Should I add FAQ structured data anyway?
For an ordinary small-business FAQ section, I would not build the strategy around it.
Google no longer shows the FAQ rich-result feature that made FAQPage markup attractive to many site owners.
Structured data still has valid uses elsewhere, and Google continues to support other rich-result types where applicable.
But the question here is simpler:
Does the customer need the answer?
If yes, publish the answer clearly.
That is enough reason.
FAQs can reveal weak main content
This is a useful diagnostic.
If the FAQ section has to explain basic information that should have been obvious on the page, the page may be the problem.
For example:
What services do you offer?
should probably not require an FAQ on a Services page.
The service should already be clear.
Likewise:
Where are you based?
may belong in the main business information.
FAQs should handle useful secondary questions, not compensate for vague core copy.
They can also qualify leads
Suppose you do not provide a certain type of work.
Answering that can prevent unsuitable enquiries.
Suppose projects begin at a particular level.
Explaining the scope can help visitors decide whether they are a fit.
Suppose the business only works within a certain area.
Making that clear saves everybody time.
Good FAQs do not only create more leads.
They can create better-informed leads.
That fits the wider lead-generation journey.
What I'd do
I would build the list from actual friction: messages, calls, quote requests, objections and things customers repeatedly misunderstand. Start with five genuinely useful questions rather than twenty generic ones. If the same question keeps appearing, that is evidence the website should answer it more clearly.
How many FAQs should I have?
As many as are genuinely useful.
That may be four.
It may be twelve.
It may be none.
There is no correct SEO number.
If you find yourself inventing questions because the section looks too short, stop.
A short useful FAQ is better than a long generic one.
This is part of the wider Built by Gavin content philosophy: pages and sections should earn their place.
What makes an FAQ answer good?
Answer the question directly.
Do not hide a yes/no answer behind three paragraphs of marketing copy.
If the answer has an important condition, explain it.
If there is a deeper page, link to it.
For example:
Do I need to provide all my website content?
can give a direct answer and then link to the deeper guide about getting a website built when you have no content.
That gives the reader both speed and depth.
Avoid fake questions designed to praise the company
This is one of my least favourite FAQ habits.
Why is ABC Ltd the best choice for your business?
That is not a frequently asked question.
It is a sales paragraph wearing a fake moustache.
If you want to explain why the business is different, do it directly.
The FAQ format works because it feels practical.
Do not undermine that trust by turning every answer into an advert.
What about accordion layouts?
They can work well when the section is long because they keep the page compact.
But hiding every answer behind an interaction is not automatically better.
For a small set of important questions, visible answers can be easier to scan.
The design should fit the amount of content and the page.
The content matters more than whether the question has a little plus icon.
FAQs are especially useful on service pages
Service businesses often have repeated practical questions.
How long does it take?
What do I need to provide?
Where do you work?
Is there a minimum project size?
What happens after launch?
Those questions sit close to the buying decision.
That is where FAQ content can genuinely earn its place.
Gavin’s perspective
Built by Gavin's approach
I would rather collect real questions from client conversations and turn those into useful content over time.
That gives the site a stronger voice because the questions come from real small-business concerns.
It also creates natural opportunities for deeper Guides.
A short FAQ can answer:
Do I need WordPress?
Then the full WordPress guide can explain the decision properly.
That is a much healthier content system than manufacturing fifty questions because somebody thinks Google likes FAQs.
The bottom line
Use FAQs when they answer real questions.
Put answers close to the relevant part of the journey.
Keep them direct.
Use them to reduce uncertainty and qualify customers.
Do not create them merely to make a page longer or chase an SEO feature.
The best FAQ section feels like someone listened to customers.
Because they did.
Have questions customers keep asking?
That is useful website material.
If your current site leaves people confused, send it to me or see how I structure small-business websites.
Often the best content improvements come from the questions already arriving in your inbox.
---