WordPress

Audit your WordPress content before a redesign

A practical content audit for a WordPress redesign: inventory URLs, identify missing information, assign decisions and protect useful existing pages.

A redesign is a good time to question a site’s structure. It is also an easy time to lose useful information. If a service page has an old phone number and an unclear call to action, putting it into a new template only gives those problems a fresh appearance.

Start with a content inventory before approving the new page designs. The aim is to give every important URL a clear owner and a decision.

Build an inventory that supports decisions

Create a spreadsheet with one row per public page. Record the URL, page title, content type, purpose, owner, review date and proposed action. Include landing pages and custom post types, not just the pages visible in the main navigation.

Then add evidence. Where available, use analytics to understand visits and enquiries, and Search Console to understand search visibility. A quiet page might still answer an important support question; traffic alone is not a reason to remove it.

Use four actions: keep, improve, combine or retire. Avoid a vague “needs work” label. A useful decision describes the next step: “Improve: replace the retired support email and add the current enquiry process.”

Check facts separately from presentation

Review the information customers act on first:

  • Contact details, opening hours and service areas.
  • Prices, availability and claims about what is included.
  • Forms, downloads and links to external booking systems.
  • Author or team details that establish who is responsible for the content.

For each issue, record the source of the correct information. An editor should not have to guess which of two phone numbers is current. The contact details review tutorial shows a workflow for locating potentially outdated values before editing them.

Define completeness for each content type

A course page and a service page need different information. For a course, you may require a duration, delivery format and registration link. For a service, you may require a scope statement and an enquiry route.

Separate stored values from visible output. A custom field may be filled in but absent from the template. Conversely, a template may display fallback content even when the stored field is empty. Review both the editor and the public page. The missing content fields tutorial can help with the stored-value part of that review.

Plan URL changes before building templates

Prefer keeping an existing URL when its purpose remains the same. When combining pages, record the old URLs and the most relevant destination for each. A redirect should send a visitor to information that addresses their original intent.

Do not redirect every retired page to the homepage by default. If a page has no suitable replacement, decide explicitly how it should be retired. Keep the URL decision sheet so that development and content teams use the same map.

Turn the audit into a release checklist

Before launch, check a sample from every template and content type. Open the public URL, follow its primary action, inspect the page title and confirm that the approved text appears. Test redirects from the old URLs rather than assuming a redirect configuration worked.

An audit is finished when decisions have been implemented and verified, not when the spreadsheet is complete. Keep the owner and review date fields after launch so the next audit starts with accountability rather than archaeology.

For the next stage, read how to review WordPress changes on staging, or explore the WordPress tools used in the linked tutorials.