how do i add an faq section that answers real questions

web · 2026-10-10 · 3 min

an faq section is a list of real questions written as headings, each followed by a short answer. the widget is the easy part: an accordion, a few details tags, a block in your page builder. the work is choosing the questions, and the honest source for them is your inbox and your phone calls.

where the questions come from

open your last thirty emails and note what people ask before they buy: delivery times, what is included, whether you work outside the city, whether the price is final. those are the questions. not the ones you wish they asked. if something appears three times, it belongs on the page, and the answer should be the one you give on the phone, including the part where you say no.

build it so it works without javascript

the native way is a details element with a summary inside: the browser opens and closes it, the text is in the page for google, and it works if a script fails. page builders give you an accordion block with the same behaviour, but check that the answer text is in the html and not fetched when someone clicks. an accordion that loads its content on click is invisible to a search engine and to anyone on a slow connection.

what not to put in an faq

do not hide the price, the delivery time, or the fact that you do not do something. an faq is not a place to bury the inconvenient answer, because people read it precisely when they are deciding. put the three questions that decide a sale at the top, in the order a customer asks them, and keep the rest short.

faq

does an faq section help with google?

a little, and indirectly. it can win a featured snippet if the question matches a real search and the answer is two sentences long. mostly it helps because it removes objections before the contact form, which is the part you can measure.

how many questions should i have?

between five and ten. fewer looks like you avoided the awkward ones, more becomes a manual nobody reads. start with the five that appear most often and add one when a new question repeats.

should the answers be hidden behind a click?

only if the list is long. on a phone, ten open answers are a wall of text. three or four visible and the rest collapsible is a reasonable compromise, as long as the text is in the page from the start.