Website Redesign & Conversions

Create a Content Inventory Before Rebuilding Your Website

Inventory pages, downloads and important content before a redesign. Decide what to keep, improve, merge or retire with a clear owner.

White work table with notes, smartphone and laptop
Illustrative photograph, not a client or team claim. Photo: JESHOOTS.COM jeshoots via Wikimedia Commons · CC0. Resized and cropped.
In this guide
  1. Record what exists
  2. Give every important item a decision
  3. Look beyond the menu
  4. Use the inventory at launch

A redesign can accidentally remove the page that answers an important customer question. A content inventory gives the project a memory before layouts and menus start changing.

Record what exists

List important URLs, their purpose, content owner and relevant assets. Include PDFs, forms and landing pages that may not appear in the main navigation. Where authorised data is available, add search and enquiry context without treating low traffic as automatic permission to delete useful information.

Give every important item a decision

Keep, improve, merge and retire are different actions. A merged page needs a useful destination and a URL plan. A page awaiting updated facts needs an owner, not simply a “rewrite later” label.

  • Identify outdated services and contact details.
  • Mark unique proof, customer permissions and licences.
  • Review important downloads and embedded tools.
  • Keep the original content available during development.
  • Confirm who approves removals and new wording.

Look beyond the menu

For example, a campaign page may still receive visits even though it is not linked from the header. Its role should be reviewed before it is replaced or removed. The correct decision may be to keep it, update it or redirect it to a genuinely relevant destination.

Use the inventory at launch

Compare the final site with the agreed decisions. Check missing pages, images, documents and links. The inventory is not paperwork to abandon after design approval; it is a practical way to verify that the rebuild retained what the business intended to keep.

Need help putting this into practice?

Tell Nithu what your website needs and which systems are involved. The next step is a review of the requirements and an agreed scope, with any paid tools or ongoing costs explained before work.

Request a website project review

Further reading from the official documentation