Content Audits

1,244 views

Published on

This presentation explains what content audits are and shows 3 usecases of a content audit.

Published in: Design
  • Be the first to comment

Content Audits

  1. 1. Zurich Content Strategy Meetup Content Audits Memi Beltrame - @bratwurstkometLiip - Agile Web Developmentliip.ch
  2. 2. Content Audit An assessment of thestate and actionability of all available content.Liip - Agile Web Developmentliip.ch
  3. 3. Content Audit A view on content from inside by insiders. (*Not* You.)Liip - Agile Web Developmentliip.ch
  4. 4. Your role: Facilitation• Help customers decide which content needs attention.• Help them create the lists of content they have to audit.• Help them deﬁne criteria for the audit. Liip - Agile Web Development liip.ch
  5. 5. Steps in the Process• Deﬁne goals and criteria• List items• Analyse criteria• Deﬁne actionsLiip - Agile Web Developmentliip.ch
  6. 6. General Audit Goals• ROT analysis: Audit all content to spot „Redundant, Outdated, Trivial“ data.• SEO: Page-title, Description, (Canonical) URLs, Structure• Content Type (Continuity of format vs format mismatch)• Make hierarchy visible• Determine responsibility, allow prioritisation and planningLiip - Agile Web Developmentliip.ch
  7. 7. Tools and Helps• Crawler for Full Site Listing: Site Orbiter http://siteorbiter.com• Audit Spreadsheets http://www.kevinpnichols.com/enterprise_content_strategy/• Audit Questionnaires http://www.kevinpnichols.com/enterprise_content_strategy/• AnalyticsLiip - Agile Web Developmentliip.ch
  8. 8. Showcases• Classic List-All-Audit-All approach• CI Audit: Liip‘s CI challenge• Analytics based Content Audit.Liip - Agile Web Developmentliip.ch
  9. 9. List-All-Audit-AllLiip - Agile Web Developmentliip.ch
  10. 10. List-all-Audit-all• Analyse domain with Site Orbiter• Export Results to spread Sheet• Go through Spread Sheet and ‣ add missing objective data ‣ add analysis / suggestions / action Liip - Agile Web Development liip.ch
  11. 11. Site Orbiter Site Orbiter works like a page crawler, it indexes every linked page for as many levels you want.Liip - Agile Web Developmentliip.ch
  12. 12. Site OrbiterSite Orbiter gives you a list with all the pages on thesite, with useful info to start oﬀ you audit. Liip - Agile Web Development liip.ch
  13. 13. Spreadsheet (Using Google Spreadsheet to allow collaboration)Site Orbiter Columns imported into the spread sheet Liip - Agile Web Development liip.ch
  14. 14. SpreadsheetClient Audit Columns. These columns will be mainly the clients contribution, due tomanpower and knowledge about whether something is outdated or not.Columns: • Last modiﬁed in CMS • Out of Date • Visits • Superﬂuous • Caters for Main Target Groups • Revise • Main Target Group • Comments • Redundant Liip - Agile Web Development liip.ch
  15. 15. SpreadsheetAgency-Audit Columns: This is your work since you should have theexpertise on usability and what to do to improve it.Columns• Usability of Content • Findability• Appropriate page- • Comments title • Proposed Actions• Dead end?• Call To Action Liip - Agile Web Development liip.ch
  16. 16. Liip CI AuditListing all artefacts was a good starting point to evaluate what the design challenge would be. Liip - Agile Web Development liip.ch
  17. 17. Liip CI Audit ‣ Make visible the important dimensions ‣ Instances of use (inbound/outbound) ‣ Consistency ‣ Style ‣ ChannelsLiip - Agile Web Developmentliip.ch
  18. 18. Using AnalyticsLarge projects have often too muchinformation to handle via a classic audit.Selecting the relevant data is key. Liip - Agile Web Development liip.ch
  19. 19. What data is relevant?• Pages with a lot of traﬃc• Most used search terms• Pages with high traﬃc and high bounce rates.• Pages you communicateLiip - Agile Web Developmentliip.ch
  20. 20. Scenario 1Search Term and Bounce Rate• Look at the ﬁrst 100 most used search terms that bring you traﬃc• Select those that have a high bounce rate• List the pages they lead to• Figure out why users bounce Liip - Agile Web Development liip.ch
  21. 21. Search Terms that bring a lot of traﬃcbut have high bounce rates may pointout relevant pages that need attention. Liip - Agile Web Development liip.ch
  22. 22. Scenario 2Internal search • Look at the most used search terms in the internal search • look at the result pages. Do these match the expectations? • List the pages they lead to. Do a regular audit. Liip - Agile Web Development liip.ch
  23. 23. Scenario 3Landing Pages• Look up URLS like /something• list the pages they lead to• make the customer do a ROT They may not be aware these pages even exist! Liip - Agile Web Development liip.ch

×
https://www.slideshare.net/memibeltrame/content-audits
www.slideshare.net
crawl=CC-MAIN-2017-51
165670
application/http; msgtype=response
sha1:SUNBKTXSVBM5HXNWUD234DZ7FLS62WGE
<urn:uuid:0bd25512-7c52-4988-9079-00da8447d1e9>
2017-12-14T05:25:46Z
108.174.10.19
text/html
sha1:QIAIKPWEKSFKZF6YLE222LV64AJO5OBZ
<urn:uuid:00edc598-9ed9-43d7-a685-e93d42c7e364>
https://www.slideshare.net/memibeltrame/content-audits
length
response
<urn:uuid:cf182a65-f386-474d-9119-2d0723e39872>
robots: classic
hostname: ip-10-234-226-145.ec2.internal
software: Nutch 1.6 (CC)
isPartOf: CC-MAIN-2017-51
operator: Common Crawl Admin
description: Wide crawl of the web for December 2017
publisher: Common Crawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf