{"id":531,"date":"2015-05-11T13:06:20","date_gmt":"2015-05-11T12:06:20","guid":{"rendered":"https:\/\/blogs.ncl.ac.uk\/web\/?p=531"},"modified":"2015-05-19T15:47:23","modified_gmt":"2015-05-19T14:47:23","slug":"faqs-and-why-we-hate-them","status":"publish","type":"post","link":"https:\/\/blogs.ncl.ac.uk\/web\/2015\/05\/11\/faqs-and-why-we-hate-them\/","title":{"rendered":"FAQs and why we hate them"},"content":{"rendered":"

We often get asked why we do not want FAQs<\/strong> (Frequently Asked Questions) on the University\u2019s websites.<\/p>\n

There are lots of reasons: all to do with making<\/strong> our<\/strong> websites<\/strong> work well<\/strong> for the people who use them.<\/p>\n

But, why do we reserve such hatred for such a simple page? Read on and I\u2019ll explain.<\/p>\n

Old school<\/h2>\n

Back in the day, you would always see FAQs on websites. They were used as a catch-all<\/strong> section for content that didn\u2019t quite fit<\/strong> elsewhere.<\/p>\n

Now websites have evolved, so has our understanding of how people use them.<\/a><\/p>\n

The good, the bad and the ugly<\/h1>\n

Good websites<\/strong> base their structures, sections and content<\/strong> on their audience\u2019s needs<\/strong>. They focus on what we call top tasks<\/strong>.<\/p>\n

Content should be in the most logical section. It should be labelled clearly so people can find it and complete their task with ease.<\/p>\n

FAQ<\/strong> pages are bad.<\/strong>\u00a0 They dump a jumble of content<\/strong> together in one page. They are often a long list of questions in a random order<\/strong>. Worse, they may not even answer the question<\/strong> that your reader has in mind.<\/p>\n

Another nail in the coffin for FAQs, is the very nature of them. Being a question<\/strong> they have useless, repetitive intros like \u201cHow do I?\u201d or \u201cWhere can I?\u201d<\/p>\n

This is ugly, lazy content!<\/strong> Hard to read, understand and scan.<\/p>\n

Why ask your audience questions, when they are visiting your website for answers?<\/p><\/blockquote>\n

They cause duplication<\/h1>\n

We\u2019ve had examples of sites that had perfectly good sections reflecting their top tasks.<\/p>\n

Instead of just adding content to these existing sections, a new FAQ page appears. It duplicates content<\/strong> in other sections.<\/p>\n

They are patronising<\/h1>\n

FAQs talk to you in a really irritating<\/strong> way.<\/p>\n

My personal favourite is the “How do I contact you?” FAQ when there is already a contact us section.<\/p>\n

They create more work (and mistakes)<\/h1>\n

When the contact us section is updated, will the Web Editor remember to track down and update the FAQ too? Often not.<\/p>\n

They cause confusion<\/h1>\n

Out of the two contact us sections, which one is correct? The phone number is different…<\/p>\n

Messing with Google<\/h1>\n

Duplicated content problems<\/strong> show up in Google search results.<\/strong><\/p>\n

FAQ content will fight your other content<\/strong> for attention. Google doesn’t know which contact us content is the right one. It might show both, it might show the out of date FAQ, either way, your user isn’t going to be happy.<\/p>\n

We’re not alone…<\/h1>\n

I hope you can start to see why we are not so keen on FAQs. And it\u2019s not just us\u2026<\/p>\n

Gov.uk<\/a> is stripping away all the FAQs it comes across for the same reasons I\u2019ve just highlighted.<\/p>\n

One of our favourite authors about all things web, Gerry McGovern<\/a> writes about FAQs<\/a> and really makes you question their worth.<\/p>\n

How to avoid using FAQs<\/h1>\n

If people are repeatedly asking you the same questions:<\/p>\n