How to write FAQs that add information instead of repeating the page
The best FAQ questions are the ones a reader could reasonably still have after reading the page.
4 min read
A lot of FAQ sections simply turn information from the page into questions.
If the page already explains shipping, adding “How does shipping work?” at the bottom does not make the page more useful. It just repeats the answer.
A useful FAQ does something different: it answers legitimate follow-up questions that belong on the page but do not need their own full section.
The easiest test is simple: could someone read the whole page and still reasonably ask this question?
How do you decide whether a question belongs in an FAQ?
Read the question and ask:
Could someone read the entire page and still reasonably need this answer?
If no, the FAQ is probably repeating the page.
If yes, ask one more question: is the answer important enough to deserve its own section?
Already answered on the page → do not add it
Important enough for a full section → put it in the main content
Useful follow-up with a short answer → good FAQ candidate
Only loosely related to the page → leave it out or answer it somewhere else
That eliminates most unnecessary FAQ questions before you write anything.
Where should FAQ questions come from?
Start with evidence that people are actually asking the question.
Useful sources include:
Search Console: Look for queries the page already receives impressions for but does not directly answer.
People Also Ask and related searches: Look for relevant follow-up questions around the main search.
Reddit, forums, and communities: Look for questions people ask after they already understand the basics.
Customer support: Questions that repeatedly reach support often belong somewhere on the site.
Sales calls, reviews, and customer feedback: These can reveal objections and details people need before making a decision.
Your own site search: If available, look at what people search for after landing on the site.
Then apply the FAQ test. A real question does not automatically belong on this particular page.
What does a useful FAQ section look like?
Say you have a page explaining how to choose a project management tool.
The main page already covers features, pricing, team size, integrations, and how to compare platforms.
These would be weak FAQs:
What is project management software?
What features should I look for?
How much does project management software cost?
The page already answers them.
But your Search Console data, customer conversations, and community research reveal questions like:
Can I switch project management tools without losing my existing projects?
How long does it usually take a team to switch tools?
Do contractors need paid accounts too?
What happens if a client uses a different project management platform?
Those are useful follow-ups. They are relevant to choosing a tool, but each can probably be answered without adding another major section to the article.
That is what the FAQ is for: questions that belong with the page but do not belong in the main structure.
Want to check yours?
Run the FAQ writer →
How should you write FAQ answers?
Answer the question immediately.
For a simple question, one or two sentences may be enough. For a conditional answer, state the condition first and then explain what changes.
Avoid openings like:
There are several factors to consider when deciding whether...
when the useful answer is:
Yes, but only if...
Include enough context to make the answer useful on its own, but do not turn every FAQ into another article.
If an answer needs several paragraphs, examples, or substantial explanation, that is a sign the question may deserve a section in the main page instead.
What should you leave out of an FAQ section?
Leave out:
Questions the page already answers. Rephrasing an H2 as a question adds nothing.
Questions that deserve their own section. Important information should not be buried at the bottom of the page.
Questions added only for keywords. If nobody reasonably needs the answer, do not invent the question.
Questions that belong on another page. Shipping, returns, account policies, or support questions may have a better home.
Questions with no useful answer. An FAQ does not need to exist simply because the template has space for one.
There is no ideal number of FAQs. Zero is better than five questions nobody needs.
Should FAQs use FAQ structured data?
FAQ sections should use FAQPage structured data when the questions and answers are visible on the page and the markup accurately reflects that content.
The structured data helps search engines understand that the page contains a set of questions and answers. It should match the visible FAQ exactly and stay updated when the FAQ content changes.
Use FAQ structured data when:
the questions and answers are visible on the page
each question has a clear answer
the markup matches the page content
the FAQ section is genuinely useful, not added only for markup
Do not use FAQ schema for hidden content, promotional copy disguised as questions, or answers that do not match what is rendered on the page.
If you have a real FAQ section, mark it up correctly.
Where should FAQs appear on a page?
They do not automatically belong at the bottom.
If a question is important at a particular point in the reader’s journey, answer it there. Important information should not be pushed into an FAQ simply because the site has an FAQ component.
A dedicated FAQ section works well for genuine follow-up questions that remain after the main content has done its job.
Main questions belong in the main content. Follow-up questions belong in the FAQ.
How often should you review existing FAQs?
Review FAQs when you refresh the page.
Questions change. A question that once belonged in the FAQ may now be answered in the main content, become outdated, or no longer matter.
During each refresh, ask:
Is this still a real question?
Is it now answered somewhere else on the page?
Is the answer still accurate?
Does the question still belong on this page?
Have new recurring questions appeared?
FAQs should change with the page rather than accumulating forever.
How do you audit an existing FAQ section?
Read each question and try to answer it from the main page without looking at the FAQ.
If you can, the FAQ is probably duplicating the page.
For everything that remains, ask whether the question deserves a full section, belongs on another page, or works as a short follow-up.
What survives that process is the FAQ section worth keeping.
How do you build a better FAQ section?
Start with questions, not an FAQ template.
Find the questions people actually ask. Remove anything the page already answers. Move important questions into the main content. Remove questions that do not belong. Then write direct answers for the useful follow-ups that remain.
The FAQ Writer can help find candidate questions from the page and its search context, but the same rule applies to generated questions: a question only belongs if it adds something the page still needs.
If you are deciding what belongs in the main page before you get to FAQs, start with how to structure an article from the SERP.
A good FAQ section fills the questions the page leaves behind. It does not rewrite the page as questions.
Keep reading
