Write FAQs

Work with your team to compile a list of the most commonly asked questions about your product or service. Don’t worry if it’s super long - you don’t have to answer them all right away. At this point you can try and loosely categorise them (e.g. how it works, pricing, about us).

Next up, rank them based on how important they are to your users. Are there questions which always come up in sales calls or during onboarding? Clearly they’re top of mind, so let’s bump them up the list.

Take the top 10 or 20 questions to start with as a starting point, and draft an answer to them.

With a shortlist of questions and answers drafted, it’s time to add them to your site. Consider using an accordion (show/hide) element to avoid having too much text displayed on the screen, particularly on mobile devices.

You can add the FAQs to a dedicated /faq page on your website and/or pepper them throughout the site where relevant - for example, you could show the pricing-related FAQs on your pricing page.

FAQs allow users to quickly get answers to their questions, reducing uncertainty, building a clearer picture of your solution and the problems it solves. When built correctly with structured data, they may also get picked up by search engine results pages - helping to establish your domain authority and lead more visitors to your site.

Consider adding structured data your FAQs so that they are prioritised in search engine results. Regularly review and update FAQs to ensure that they’re relevant to what users are searching for.When writing FAQs, refer to recent conversations you’ve had with customers before, during and after the purchase of your product. Trying to rank for specific keywords in organic search? Why not create FAQs based around those, or include those keywords in your FAQ list organically. If you’re using an accordion (show/hide list) or FAQs, it’s best practice to open the first question by default when the user lands on the page, to indicate that questions can be opened and closed.If your website is built using Webflow or another CMS, it usually makes sense to store them there, rather than in plain text on a static page. That way, you can refer to the same FAQs throughout the site.