FAQ content: when it works, when it is padding, and how to write it

Where should questions come from?

1. 1Support tickets — the questions people ask after they have already read the page.
2. 2Sales calls — the objections and clarifications that come up before buying.
3. 3Search Console queries — the long-tail questions bringing people to the page.
4. 4People Also Ask boxes for your target queries.
5. 5Community forums and social threads where your topic is discussed.
6. 6Your own team's recurring internal questions, which usually mirror customers'.

How should answers be written?

<!-- Poor: vague, unhelpful, self-referential -->
**How much does a website cost?**
Costs vary depending on your requirements. Contact us for a quote.

<!-- Good: specific, self-contained, honest -->
**How much does a business website cost?**
A professional business website typically costs between ₹60,000 and ₹3,00,000
depending on page count, custom design and integrations. A five-page marketing
site sits at the lower end; a platform with a CMS, payments and a dashboard
sits at the upper end. We publish indicative ranges on our pricing page.

• Two to four sentences — complete but quotable.
• Answer directly in the first sentence; qualify afterwards.
• Include specifics: numbers, ranges, timeframes, named conditions.
• Write so the answer makes sense with no other context.
• Do not repeat the question back before answering it.
• Link onward where a full answer needs more room.

How should FAQs be implemented technically?

<!-- Native details: the answer is in the HTML whether open or closed -->
<details>
  <summary><h3>How long does a website take to build?</h3></summary>
  <p>A typical business website takes 4–8 weeks from kickoff to launch…</p>
</details>

1. 1Keep answers in the server-rendered HTML — crawlers should not need to click.
2. 2Use real heading elements for questions so they appear in the document outline.
3. 3Give each question a stable id so it can be linked directly.
4. 4Add FAQPage structured data when the content genuinely is a question-and-answer set.
5. 5Do not hide answers behind a JavaScript fetch triggered by expanding the item.

Is FAQPage schema still worth adding?

Google restricted FAQ rich results to a limited set of authoritative sites, so most sites will not see the visual result any more. The markup is still worth including where it accurately describes the content: it makes the question-and-answer relationship explicit for any system parsing the page, including AI answer engines.

What is not worth doing is adding an FAQ section purely to obtain markup. That was always a weak tactic and now has no visible payoff at all.

When does an FAQ not belong?

• When it restates content already covered on the same page.
• When the questions were invented to hit a word count.
• When a dedicated page would serve the question better — a complex topic deserves its own article.
• When it pushes the actual conversion path far down the page.
• When it has not been reviewed in two years and now contains outdated pricing or policies.