How do you write an FAQ page?

To write an FAQ page that people use, you collect the questions your readers or customers actually ask, write each one the way they would phrase it, and answer it plainly in the first line. Everything else, from layout to search, follows from that. This page is part of our guide to building an SEO content strategy, and it covers the writing. For the markup side, see our page on faq schema; we do not repeat it here.

What is an FAQ page for?

An FAQ (frequently asked questions) page collects the questions people keep asking and answers them in one place. Nielsen Norman Group’s Susan Farrell calls it “a mature information format that orginated in 1982” (her spelling) in FAQs Still Deliver Great Value, and the format is still familiar to almost everyone who uses the web.

A good FAQ page does a few jobs at once. It answers questions before someone has to email or call. It helps buyers decide: Farrell notes that when people read FAQs “they often look for more than just an answer. They may be judging your products, services, and company prior to purchasing.” And it shows what your customers worry about, which is useful to everyone who builds the product.

Should you have an FAQ page at all?

Not always. The UK’s Government Digital Service (GDS) advises against them. In FAQs: why we don’t have them, Sarah Richards wrote that FAQs “are convenient for writers” but “more work for readers,” because “questions take longer to scan and understand than simple headings.” Her other objection is duplication: “If a question is frequently asked, it means you need that content on your site,” and an FAQ that repeats it leaves you “fighting with your own content” in search.

Both views are right in their place. Our reading: an FAQ page works when the questions are small, varied and do not belong on any one page. It fails when it becomes a second copy of content that should live elsewhere.

What questions should an FAQ page include?

Only real ones. Farrell is direct about this: “Questions should echo the real concerns people contact you about.” Nielsen Norman Group has warned against made-up FAQ questions for years; it was number seven on their list of top web design mistakes in 2002.

Good places to find the real questions:

• Your support inbox and chat logs. Count which questions come up most and start there.
• Your sales team. Farrell notes that a good salesperson “can probably dictate the FAQs you need to publish.”
• Search Console. Google’s Performance report lets you “learn which queries are bringing traffic to your site.” Question-shaped queries are FAQ candidates.
• Google’s People Also Ask box. Search your product type or service and see which questions Google lists, then open a few to reveal more. PAA Box, our free Chrome extension, opens that box up to four levels deep and exports the questions to CSV if you want more than the first few.
• Your own site search. Searches that return nothing are questions you have not answered.

Our guide to question keywords covers more ways to find what people ask.

How to write FAQ questions and answers

Write the question in your reader’s words

Farrell says the questions “should reflect the vocabulary and phrasing of your visitors.” If customers ask “Can I get my money back?”, do not write “What is our refund policy framework?”. She adds that you will sometimes need to rewrite a question “to make them general enough to apply to most people who need that answer.”

Answer in the first sentence

Put the answer first, then the detail. GDS calls this frontloading: putting “the term most people are looking for at the beginning of the sentence or paragraph.” A reader scanning the page should get the answer from the opening words of each reply.

Here is the difference, using a made-up example:

• Weak: “We understand that plans change, and we always aim to be flexible with our customers. Depending on a number of factors, refunds may be possible.”
• Better: “Yes. You can get a full refund within 30 days of buying. Email us with your order number and we will refund the card you paid with.”

Keep answers short, and link for depth

Most FAQ answers should be a few sentences. When an answer needs more, write a short version and link to the page that covers it fully. Farrell points out that linking to fuller resources “can often save everyone time and money, and it makes your organization seem more helpful and credible.”

Be honest about limits

Readers notice spin. Among the questions Farrell says a good FAQ quietly answers: “Do the answers seem factual and frank or more like marketing hype?” and “Does the FAQ openly acknowledge the problems or limitations that everyone knows about?” If your product does not do something, say so.

How should you structure an FAQ page?

Group questions by topic, put the most asked ones first, and make the questions easy to scan. Farrell writes that “good, large FAQs are chunked by topic and designed to be visually scanned,” so people can “rule out most of the topics quickly.”

The right layout depends on size:

Use topic headings above each group (“Orders”, “Returns”, “Accounts”) so the page can be scanned by section first.

FAQ page or FAQ section?

You do not have to choose one. Many sites have a main FAQ page for general questions and short FAQ sections on product or service pages for questions about that one thing. The rule we use is simple: put each question where someone would be when they ask it.

• Use the main FAQ page for questions that cut across the whole business: delivery, payment, accounts, contact.
• Use an FAQ section on a page for questions about that page’s subject. A question about one product’s sizing belongs on that product’s page, where the buyer already is.
• Do not put the same question in both. Pick one home and link to it from the other. Two copies drift apart the first time someone updates only one of them.

A small business with a handful of questions may only need sections on its key pages. A large one usually needs both, plus a help center once the questions run into the hundreds.

How to write an FAQ page, step by step

1. Collect questions from support, sales, Search Console, People Also Ask and site search.
2. Count and cut. Keep the questions that come up often. Drop the ones nobody asks.
3. Merge rewordings. “Can I return this?” and “What is your returns policy?” are one question.
4. Move big questions out. If an answer needs more than a few paragraphs, give it its own page and link to it. For a site plan built this way, see topic clusters.
5. Write each answer with the answer in the first sentence, in plain words.
6. Group by topic and order the groups by how often people ask.
7. Link the page from your footer, help area and the pages its answers relate to.
8. Review it on a schedule. Every time a price, policy or feature changes, check the FAQ. Farrell lists “How fresh is the latest information?” among the things visitors judge.

Do FAQ pages help SEO?

They can, if they answer questions people search for. Farrell notes that “people often type questions into web-search engines,” so questions written in your visitors’ words can match those searches. Use the same vocabulary as your searchers and each answer has a chance of being the result for that question.

Three cautions:

• Do not duplicate your own pages. GDS’s warning about duplicate results “competing for attention” applies to any site. If a question already has a full answer page, the FAQ should link to it, not repeat it.
• Do not stuff it. Google’s people-first content guidance asks whether content is “primarily made to attract visits from search engines.” An FAQ padded with keyword-shaped questions nobody asks reads that way.
• Do not write it for AI. Google’s guide to generative AI features says “You don’t need to write in a specific way just for generative AI search.” A clear FAQ helps because it is clear, not because of its format.

Whether FAQ markup still earns anything in Google’s results is a separate question, answered on our faq schema page linked above.

Common mistakes

• Made-up questions. “Why is your product so great?” is not a question anyone asks.
• Answers that dodge. If the first sentence does not answer the question, rewrite it.
• A dumping ground. Anything that does not fit elsewhere ends up in the FAQ. If a topic keeps growing, it needs its own page.
• Out-of-date answers. An FAQ with an old price or policy does more harm than no FAQ.
• Burying contact details. Some questions will not be on the page. Make it easy to ask.