Answer the questions that stop the next step

Collect uncertainty in the customer’s words

Nielsen Norman Group lists made-up questions among the common objections to FAQs and answers it directly: if you are listening to your users, you already know their questions, and sometimes you only need to rewrite them to be general enough to help most people who need that answer.^[1] The sources are close at hand: pre-sale calls, quote requests, the first five minutes of a kickoff meeting, support tickets, reviews and the questions people ask just before they go quiet.

Group what you collect by what the doubt was blocking. Ask what stopped the next step, not what was asked most often. A trivial question that comes up daily matters less than one that makes a third of prospects hesitate. Nielsen Norman Group notes that people reading FAQs are often judging the company, not just looking for an answer, and that good FAQs address tacit questions such as how credible the information is, whether the answers sound factual and frank and whether the page openly acknowledges known limitations.^[1]

Place the answer where the doubt arises

A single FAQ page at the bottom of the site is the weakest place for most answers, because the doubt appears earlier, on the page where someone is deciding. Put the answer there: next to the price, inside the process section, beside the form. A longer FAQ page is still useful for people who arrive with a question and for broad topics, and it should link to the deeper page for each answer.

Write an answer that closes the gap

An FAQ answer has one job: to let the reader stop worrying and take the next step. State the answer first, then the boundary, then what to do. Avoid restating the article above it, and avoid answers that send people to “contact us” for the thing they asked. If the honest answer includes a limit, say so. That is the quickest way to make the rest believable.

Choose an accessible presentation

Collapsing answers saves space, but it hides content that people need. Keep the three or four most decisive answers visible by default. For the rest, use the native <details> element, which MDN describes as a disclosure widget with a <summary> label, so the control and its state come with the browser, including for keyboards and assistive technology.^[2] Write the whole answer into the HTML. If answers are fetched when someone clicks, a crawler that does not click may never see them, as the JavaScript chapter explains.

<h2 id="faq">Questions before you book</h2>
<details>
  <summary>What happens if the project runs late?</summary>
  <p>Delays are usually caused by late copy or images. We agree dates for
  those at the start, and if a delay is on our side we extend your
  support period by the same number of days.</p>
</details>

Group questions under headings by topic. Nielsen Norman Group advises chunking large FAQs by topic and designing them to be scanned, so that people can rule out most topics quickly and read only the part that relates to their question.^[1]

Treat markup as a separate decision

The FAQ content itself is still worth writing, because people still need the answers. Google’s own guidance for generative AI search says structured data is not required to appear in those features.^[5] If you keep FAQPage markup that is already on a page, keep it truthful: Google’s structured data policies treat markup that does not represent the main content, or that describes content hidden from users, as a violation that can lead to a manual action.^[6] The simplest policy is to leave it out unless you can name a concrete benefit. Time is better spent on the answers.

Review the FAQ as a living document

An FAQ goes stale faster than most pages, because questions come from a moving market. Review it every quarter against fresh sources: the last quarter’s enquiries, objections raised in calls and the queries from site search. Move answers that keep surfacing into the page where the doubt arises. Retire questions nobody asks. Rewrite marketing-flavored questions, such as “Why are we the best?”, into the plain questions customers actually use. Track whether the number of repeated pre-sale questions falls; that is the plainest sign the FAQ is working.

Apply it to your website

• Questions come from real conversations, enquiries and tickets, in customers’ own words.
• Each question is tagged with the step it blocks, and answers sit where the doubt arises.
• Answers state the answer first, then the boundary, then the action, and admit limits honestly.
• The most decisive answers are visible by default, and the rest use native details and summary elements.
• Answers are present in the HTML and do not depend on a click to load.
• You have not added FAQ markup for a rich result, and any existing markup matches visible content.
• The FAQ is reviewed every quarter, and the number of repeated pre-sale questions is tracked.