FAQ sections that answer real questions, rank and convert
Most FAQ pages are written in an afternoon from questions nobody asked: what makes you different, why choose us, do you offer quality service. A good FAQ does the opposite. It answers the specific doubts that stop people from getting in touch, in the place where those doubts appear. Done well, it reduces support emails, lifts enquiries and gives search engines and AI assistants clear answers to quote.
Where the real questions come from
The questions worth answering are already arriving in your inbox, on the phone and in sales calls. The work is collecting them instead of inventing new ones.
- Go through the last three months of emails and enquiry forms and write down every question a prospect asked before buying.
- Ask whoever answers the phone which five questions they hear every week.
- Note the objections that come up in quotes and sales conversations: price, timing, what happens if something goes wrong.
- Check Google's People also ask box and autocomplete for your main service, which shows how strangers phrase the same doubts.
- Look at Search Console for question queries such as how much, how long or can I, where your site already gets impressions.
Keep the customer's wording. If people ask do you work on weekends, the question should say that, not regarding our service availability.
Which questions deserve an answer
Not every question belongs on the site. Prioritise the ones that block a decision.
Price questions come first. How much does it cost, what affects the price, is there a minimum order, are there hidden fees. If you cannot give an exact number, give a range and explain what moves it.
Next come process and risk: how long it takes, what the customer needs to prepare, what happens if they are not happy, how cancellation or returns work.
Then fit: do you work with small companies, do you serve my area, do you speak my language, can you work with my existing system.
Skip marketing questions dressed up as FAQs. Why are we the best is not a question anyone asks, and every reader recognises it as a sales pitch in disguise.
Remove questions that nobody asks anymore. An FAQ with thirty entries, half of them outdated, is harder to use than one with ten sharp answers.
Put answers where the doubt appears
A single FAQ page in the footer is the least effective place for answers, because few people go looking for it at the moment they hesitate.
Place three to six relevant questions directly on each service or product page, below the main description and near the call to action. The questions about installation belong on the installation page, not on a general list.
Put price questions next to prices, shipping questions in the cart and checkout, and data questions next to the contact form.
A central FAQ page can still exist as a reference, especially for support and existing customers. Just do not rely on it to remove doubts during a sale.
Use an expandable accordion only when the list is long. Five short questions fully visible are read more often than five hidden behind clicks, and accordions that hide content make it easy to miss the answer that matters.
Make sure expandable answers are present in the page HTML, not loaded only on click, so search engines can read them.
How to write the answers
Start with the direct answer in the first sentence, then add the detail. Yes, we work on Saturdays by appointment is better than a paragraph about flexibility before getting to the point.
Be specific. Delivery in Estonia takes one to three working days, Latvia and Lithuania three to five is useful. Delivery times vary depending on location is not.
Write two to five sentences for most answers. Long enough to settle the doubt, short enough to scan. If an answer needs a full page, write that page and link to it.
Link to the next step. An answer about pricing can end with a link to the calculator, an answer about the process with a link to the booking form.
Answers written this way also work well for AI assistants and AI Overviews, which prefer short, self contained passages that answer one question clearly.
Review the answers when things change. An FAQ that promises a delivery time or a price you no longer offer creates exactly the kind of disappointment it was supposed to prevent.
FAQ schema and measuring the effect
FAQPage structured data used to produce expandable answers directly in Google results for many sites. Since 2023, Google shows these rich results only for a small group of authoritative government and health websites.
That does not make the markup useless. It still describes the content clearly for search engines and other systems that read structured data, but do not add it expecting extra space in the results.
The main value of an FAQ is on the page itself, so measure it there. Compare the conversion rate of service pages before and after adding questions.
Track clicks on the accordion items if you use one. The questions opened most often tell you which doubts matter most and which ones should move into the main page text.
Watch your inbox too. If the same question keeps arriving by email after it is answered on the site, the answer is either hard to find or not clear enough.
Treat the FAQ as a living part of the site. Every new recurring question from a customer is a candidate for the next update.
FAQ
Should I have a separate FAQ page or questions on each page?+
Both can exist, but questions placed directly on the relevant service and product pages do far more for enquiries. People hesitate while reading about a specific service, and very few leave that page to look for a general FAQ in the footer, so an answer about installation time or pricing needs to be right there near the call to action. A central FAQ page is still useful as a reference for existing customers and support topics. A practical setup is three to six targeted questions on each key page, and a broader FAQ page that collects general questions about ordering, payment, delivery and data handling.
Does FAQ schema still help SEO?+
It helps much less than it used to. Since 2023 Google shows FAQ rich results, the expandable questions directly in search results, only for a limited set of well known government and health websites, so most businesses will not get that extra visibility from adding the markup. The structured data is still valid and describes the content clearly for systems that read it, and it does no harm when the questions are genuinely visible on the page. The real SEO value of an FAQ now comes from the content itself: clear, direct answers to questions people search for, which can rank for long question queries and are easy for AI assistants to quote.
How many questions should an FAQ section have?+
On a service or product page, three to six questions is usually the right amount, enough to cover the main doubts about price, process, timing and fit without turning the page into a wall of text. A central FAQ page can hold more, but beyond twenty or so entries it helps to group questions into clear categories. The number matters less than the source: every question should come from real customer emails, calls or search data, not from what the business would like to say about itself. Review the list regularly, remove questions nobody asks anymore and update any answer that mentions prices, delivery times or policies that have changed.