Looking at other companies' FAQ pages mostly teaches you about their design system. What transfers is the pattern underneath: how the questions were chosen, how they are ordered, and what happens when the answer is longer than a paragraph. Four of those patterns are worth copying and two of the common ones actively lose readers.
Works: questions in the order a decision is made
What is it, what does it cost, what happens if I stop, is my data safe. The order matches the sequence in the reader's head, which means the page reads as a conversation rather than a list, and the reader who stopped at question three got the three that mattered to them.
Works: the answer visible, not collapsed
Accordions look tidy and cost a click per question, and the click is paid by every reader who is scanning to see whether their question is here at all. Where there are few enough questions to show, show them. Collapse is a solution to having too many questions, which is a different problem with a different fix.
Works: a link to the full article under the short answer
Two sentences that answer it, then a link for the reader who needs the detail. This keeps the page scannable and stops the FAQ growing into a base, because the long material has somewhere else to be. The rule of thumb is that anything needing a second paragraph has outgrown the row it is sitting in.
Works: written in the words of the question actually asked
The best source for the questions is the support queue, verbatim, before anybody tidies them. A question rewritten into corporate phrasing stops matching what a searcher types and stops sounding like something a person wanted to know.
Avoid: the marketing question nobody asked
Why should I choose you, what makes you different. These are not questions, they are claims in question form, and their presence teaches a reader that the page is promotional and that the real answers are elsewhere. One of them is enough to cost you the rest of the page.
Avoid: forty questions under four headings
At that size the page has become a knowledge base with no search, no per-question link and no owner. The headings make it look organized and do not make it findable. Split it, and keep the six questions that genuinely belong to the page they were on.
Questions people ask about FAQ page examples
How many questions should a page have?
Few enough to scan without scrolling twice, which in practice is under a dozen. Past that the format stops doing the one thing it is good at.
Where do the questions come from?
The support queue and the sales calls, in the words they were asked. Questions invented in a meeting are the ones nobody searches for and the ones that make the page read as promotional.
Should we mark it up as structured data?
Where the page genuinely is a set of questions and answers, yes, because that is what the markup describes. Where it is an article with a question section, mark up the article and leave it at that.