TL;DR: A good FAQ does three things: absorbs objections before the buyer asks, pre-qualifies fits so wrong-fit visitors self-disqualify, and works as AEO infrastructure (question-shaped H3s with concise answers are exactly what Perplexity and Claude quote). Patterns that work: real buyer questions in the buyer's words, short answers (40–120 words) that lead with the direct answer, no marketing softening, 6–10 questions max, accordion or visible by default depending on length. Patterns that fail: questions the rest of the site already answered, vague reassurance, and 30+ questions that signal the page is for SEO not buyers.
The FAQ section is the most-skimmed and least-redesigned part of most websites. It exists because someone said "we should have an FAQ" three years ago. Nobody checks whether it's earning its space. Almost always, it isn't.
Done well, an FAQ is a conversion machine. It absorbs the doubt that would otherwise stall the lead, and it does so without forcing the buyer to ask a person. Done poorly, it's filler.
Here is the difference.
What an FAQ actually does
A good FAQ does three things:
- Absorbs objections. Before the buyer needs to ask "but what about X," the answer is on the page.
- Pre-qualifies fits. Buyers who see an answer that doesn't match their case self-disqualify quietly, saving everyone time.
- Functions as AEO infrastructure. Each FAQ answer is a directly-citable chunk for AI search. Question-shaped H3s with concise answers are exactly what Perplexity and Claude quote.
A bad FAQ does none of these. It tells the buyer things they could have inferred from the rest of the site, in vague language that doesn't move the decision forward.
The questions to actually answer
Most FAQs answer the wrong questions. They answer easy ones the team feels comfortable with. The right questions are the ones the buyer is already wondering and not asking.
Three categories:
1. Process questions.
- "What happens after I submit the form?"
- "How long until we kick off?"
- "Who am I working with?"
- "What does the first call cover?"
2. Money questions.
- "How much does this cost?"
- "What's included at $X?"
- "What if scope changes?"
- "Do you offer payment plans?"
3. Risk questions.
- "What happens if I don't like the first direction?"
- "What if the project takes longer than estimated?"
- "Who owns the work when it's done?"
- "What happens after launch?"
Most FAQs cover process. Few cover money. Almost none cover risk. The risk questions are the ones that decide deals.
What makes an FAQ answer work
Five rules.
1. Answer the actual question in the first sentence. Don't lead with "Great question!" Don't restate the question. Answer.
2. Give a number when possible. "How long does it take?" → "1 to 3 weeks." "How much?" → "$1,000 to $10,000." Specific numbers earn trust faster than ranges, which earn trust faster than "depends."
3. Be willing to disqualify. "Can you build a marketplace?" → "Probably not. We build websites and AI automations. A real marketplace is a different kind of project." Visitors trust businesses that say no.
4. Use real words. "Custom solution," "tailored approach," "dedicated team" are AI-slop fillers. "We build you a Next.js site," "we design from scratch," "you work with the same two people" are real words that say something.
5. Keep answers short. 2–4 sentences. If the answer is longer, it's a blog post, not an FAQ. Link out and keep the FAQ chunk citable.
Where to put the FAQ
Three patterns work.
1. End of the homepage. Catches the visitor who scrolled all the way down without converting. Often the highest-converting placement because the visitor is fully read-in.
2. Inline on services / pricing pages. Service-specific FAQs ("how long does a website take") live on the services page. Pricing-specific FAQs live on pricing.
3. A dedicated FAQ page. Useful for high-volume sites with many questions. Less useful for a small service business with 6–10 real questions.
The pattern that doesn't work: a hidden FAQ link in the footer. Nobody finds it. Nobody clicks. The questions stay unanswered.
What we ship
A typical Webdimonia client site has:
- 6 questions on the homepage at the bottom, grouped under a "Questions" or "Common questions" heading.
- 5 questions on the services page specific to the service.
- Schema markup (
FAQPage) on the page where the FAQ lives. - Each question phrased as the buyer would ask it, not how the company would frame it.
- Each answer 2–4 sentences, with a number or specific where possible.
This is enough. We've seen sites with 40-question FAQ pages and conversion didn't lift. The questions that matter are the 6 risky ones the buyer is going to think about anyway.
What our own FAQ looks like
From our services page, the questions are:
- What counts as an "AI automation"?
- What do you need from me to start?
- What if I don't love the first direction?
- Who owns the work when it's done?
- Who runs the automation after launch?
- What happens when an API or model changes later?
Three of those are risk questions ("what if I don't love it," "who owns it," "what when it changes"). Those are the ones that earn the click and decide briefs.
Three questions to fix your FAQ this week
- Is the FAQ on the page where the buyer is making the decision, not on a separate hidden page? If hidden, move it to the homepage or services page.
- Do at least 3 of your questions address risk? If they all address process, rewrite three to address what could go wrong.
- Does each answer start by answering the question, not by restating it? Audit. Rewrite the ones that don't.
If you want a 10-minute review of your current FAQ (placement, questions covered, answer quality, schema), send us the page URL. We send these back same-day.