THE JADU BLOG

Here's where you'll find lots of useful information about our customers' successes, product and partner news... and lots more!

All Posts

4 ways CMS reports will help your content audit

As every good web manager will tell you, it’s essential to audit your content regularly if you want your site content to remain relevant and engaging.

 

The new Reports utility in Continuum CMS, has just made this a whole lot easier.

When auditing your content, you’re going to want to find all the content on your website and then take a look at some key metrics for those pages. Here’s our take on 4 ways that Reports can help you do that.

  1. Create a full inventory of your content.
    Before you can start your audit, you need an inventory of the content in your CMS. Ideally, you’re going to want to track some key pieces of information such as what type of page it is, the title of the page and a link to that content.

    Key reports: Content by live status, Content by visible status
     
  2. Double check any pages that aren’t visible on your website.
    There are lots of reasons why you might have some archived content on your website - but during your audit is the perfect time to review whether that those pages should actually be live.

    Key reports: Content by live status, Content by visible status
     
  3. Make sure every page has an active owner.
    It's crucial that every page has an engaged and active owner. Pages with an owner who has left the organisation or stopped logging into the content management system are never going to be updated and maintained.

    Key reports: Orphaned content, dormant users, Content owned by user, Locked owner
     
  4. Identify content that’s not been edited in a long time.
    Some pages don’t need to change often, but pages that haven’t been updated for a while should be reviewed during your content audit. It can be a sign that the original author has abandoned that page, in which case there’s a chance the content of the page won’t be as relevant as it could be.

    Key reports: Content not modified in period
Sarah Backhouse
Sarah Backhouse
Sarah graduated from the University of Cambridge, before joining Jadu in 2005. Initially working within the professional services team, Sarah has been involved in implementation projects for DirectGov, Manchester City Council and IMI plc. She has since transitioned into the product management team within Jadu, leading the development of Jadu CMS and is now Head of Product.

Related Posts

Q&A with new(ish) PM All-Star, Sylwia Checinska!

What better way to give Technical Project Manager applicants an idea of what to expect here at Jadu than chatting with new(ish) PM All-Star, Sylwia Checinska?

The New Emergency Communications Module (for Jadu CMS)

Be it a natural disaster, accident, civil disturbance or terrorist attack - or any form of tragic or sombre event - the need for urgent, clear communication has been proven time and again to be of the utmost importance.

Sending Webhooks using rules in Jadu CXM

We are pleased to announce the release of an exciting enhancement to our webhooks feature within Jadu CXM, which opens more possibilities for you to use your data, and makes webhooks easier to work with. If you want to know more about webhooks then you might find it useful to read our previous post - ‘What are webhooks?’