What and why are you auditing?
I understand the need for an organisation to want to know what it has now. However, a traditional content audit seems to stop at giving the organisation a snapshot of where it is now and a list of pages to work on. Traditional content audits don’t seem to tell you enough to make judgements on where the content should be or what the site should be doing.
By simply auditing what your site offers now, I think a number of people are missing a huge opportunity to turn their site from an organisation-focused site to a useful, accessible, user-centred site.
Content audit blog posts
I am seeing more and more posts supporting content audits - and they are saying the same thing. Which is perhaps great, the content community has a consensus!
But from the ‘pro-audit’ posts I’ve read this week:
- 50% don’t mention any sort of data or analytics
- 80% don’t mention the user
- 100% don’t mention in-page search terms or user feedback mechanisms
I find this a little odd. If you don’t know this information - how are you going to improve your content and who are you improving it for?
From what I have read, a lot of content audits follow this pattern:
- get a sitemap of your site
- build a spreadsheet
- work out what you need/don’t need (some suggest only basing this on number of visits)
I find two of those points challenging.
You may not experience this so let me explain: some people look at what they have and stay there. They improve what they have - which is wonderful. But if you are only looking at what you have, you may miss gaps or not be able to tie in a certain piece of content with certain user comments etc. It can be a very narrow view.
The blog posts I have read (and obviously it’s a small selection of posts out there) talk about the only metric being the number of visits. I don’t think that is enough. As Louise Stone, product content lead for GOV.UK said: “Just because people visit the page, it doesn’t mean they get what they want”. I agree wholeheartedly. A visit number is the start of the journey, not an end point, to improving content.
Work out what you need/don't need
You may have a low-performing page because the title is wrong and no-one can find it, not that the page is no good. You should find out what your organisation wants to convey, but put it in a user-centered way or it’s vanity publishing.
I fully support prioritising improvements - particularly if you are short on time or people - based on your top-performing pages or search terms. But if possible, I think you need to go further.
What I would want to see
- page title
- what user need it was fulfilling (see how to write for your audience for more on this)
- unique visits (time span to be specified by me - and would be alterable)
- time on page (criteria already set for success)
- how many user comments have been sent in about that page - negative and positive (with a way of seeing those comments)
- in-page search terms (highest number first)
- search terms related to that page/topic
- related content on the site
- traffic trends in the year (if applicable)
- content type - this is more for reporting purposes. If I had different types, of course. For example, it would be good to see if all my long-form copy pages had high instances of ‘it’s too long’ in the user comments section.
- URL - so I can get to that page easily
Audits are for life, not just for Christmas
Audits seem to be something some people do once a year. I’d want this information all the time.
Of course, it depends on how much you can automate this information or how much time you had but in any place I work, I’d want to make this part of my day job.
For example: get in, make a cup of tea, look at the top performing, lowest performing pages, trends for this time, search terms from the past 24 hours etc so that I could see what my users wanted *now*. Am I doing what they need now? Do I need to prioritise anything or be looking at trends? No? Fine. I’ll get on with the to-do list. But I’d like to see - every morning - what my users need.
I don’t think I would call it an audit. It would simply be a part of my job in creating and maintaining a user-centred site.
Huge thanks to Chris McCarthy who helped structure my thoughts on this one.