Anyone who\u2019s been anywhere on the internet ever has seen an FAQs page. A list of questions that range from the broad and timeless:<\/p>\n
\u201cHow do I log in to my account?\u201d<\/p>\n
All the way down to the horrifyingly niche:<\/p>\n
\u201cHow do I log in to my account if I forgot my password in 2003 and the piece of paper I wrote it on was still in the pocket of my baggy low-rise jeans when they went through the wash and the operator on your phone helpline told me to stop calling (\u201cdon\u2019t you know no one uses the phone anymore?\u201d) and instead to check this page to find out what to do?\u201d<\/p>\n
Most people have learnt to adapt to the difficulties of navigating an FAQs page and the format is still very popular for presenting large amounts of information.<\/p>\n
But we want our users to find what they need easily, and trawling through FAQs is not the best way to do that. Here\u2019s why.<\/p>\n
Simple, carefully worded headings take far less time to read than long questions while providing the same information. For example, \u201cBorrowing books\u201d can be read much more quickly than, \u201cHow many books can I borrow and for how long?\u201d<\/p>\n
In fact, you can skim-read all of the headings in this blog post in about ten seconds and know exactly why we don\u2019t like FAQS.<\/p>\n
Don\u2019t forget, our content needs to be accessible to all of our users. Try using a screen reader<\/a> to find a specific piece of information on an FAQs page and see how long it takes.<\/p>\n If everyone who needed to put information on the University website used an FAQs page, we\u2019d have no idea who was responsible for providing what answer to which questions. Plus, the infor<\/span>mation a user is looking for could appear in the answer to more than one question, m<\/span>aking it harder for them to find what they really need.<\/span><\/p>\n It also takes much longer to assess what content we have on our pages in order to update it when we have to trawl through a whole list of questions. If we can\u2019t find it, we or another team might make another page about exactly the same thing.<\/p>\n Duplicated content increases the chances of contradictory content. If a user finds two versions of one piece of information, they\u2019ll need to get in touch to find out which one is correct.<\/p>\n And adding \u201cWhat do I do if my FAQ is answered differently by two different FAQs pages?\u201d to your FAQs page is definitely not going to work.<\/p>\n Gone are the days when people had the reams of free time required to type, \u201cWhat is the weather in Bath tomorrow?\u201d into a Google search bar. \u201cWeather Bath\u201d now brings up the full week\u2019s forecast in five fewer keywords, leaving you more time to dig out your raincoat or cancel your plans to stay in and read blogs.<\/p>\n The closer our section headings match the keywords our audience is using, the more likely they are to find our pages.<\/p>\n Unless we collect a database of every question that our team\u2019s been asked in the past year or so, count up the number of times each question has been asked, and only add the most frequent ones to our FAQs page, they are not actually frequently asked questions.<\/p>\n We can\u2019t possibly list every question a person could ask us, and it\u2019s very likely that our audience will go to the FAQs page with a very valid question just to find it doesn\u2019t appear in the list and have to contact us anyway.<\/p>\n If our content is structured logically under simple headings, they\u2019ll find it where they\u2019re expecting to see it. Reliable content is trustworthy content.<\/p>\n Typecase has been designed with structured content in mind. Structured content is information on a website that's organised into appropriate components and fields, making it easier for users to find what they need and for us content creators to manage our content.<\/p>\n Structured content means:<\/p>\n FAQs pages are:<\/p>\n Luckily, it\u2019s super easy to create a page that doesn\u2019t use an FAQs format. The best place to start is by reading our guide to creating structured content.<\/a><\/p>\n Then take a look at our guide to writing good headings.<\/a><\/p>\n And if you have content you need to add to the website but don\u2019t know how to structure it, you can always contact us for help.<\/p>\nThey cause duplication<\/h2>\n
They\u2019re inefficient<\/h2>\n
They lie<\/h2>\n
They don\u2019t meet our structured content standards<\/h2>\n
\n
\n
The solution<\/h2>\n