Insights / BeyondPHP

Content audit before a website redesign

Give the new design a better set of material to work with.

The short answer

A content audit records what exists, who it serves, whether it is accurate and what should happen to it. Its value is the set of decisions and owners it produces, not the size of the spreadsheet.

Published · Reviewed · BeyondPHP editorial review

Illustrative visual for content audit before a website redesign
Illustrative visual · Not a client case study

Inventory the material visitors actually encounter

List pages, downloads, images and recurring content types. Include search landing pages and older resources outside the main menu when the available evidence identifies them. Record purpose, audience and ownership. Flag missing information instead of guessing how a document is used. This gives the redesign a factual starting point.

Give each item a concrete treatment

Retain accurate material that supports a clear task. Revise useful pages with outdated claims or weak explanations. Combine pages that answer the same question, preserving the meaningful distinctions. Retire obsolete material with an explicit URL decision. These choices should be made by someone who understands the business, with specialist review for regulated or sensitive claims.

Turn the audit into an editorial workload

For every revision, state what is missing, who supplies it and when it can be approved. Group related work so the same expert is not asked the same question repeatedly. Prioritise content that changes navigation and page structure before polishing smaller details. A design schedule should acknowledge this workload rather than assuming final copy will arrive automatically.

A practical next step

What to prepare.

  1. Purpose field

    Write the visitor question each important page is meant to answer.

  2. Decision owner

    Assign an approver for claims, imagery and retirement choices.

  3. Content backlog

    Convert vague rewrite notes into specific missing information and deadlines.

Questions worth asking.

Should we keep pages just because they get traffic?

Traffic is useful context, but relevance and accuracy still matter. Review the purpose before deciding the treatment.

Can similar pages be combined?

Yes, when the resulting page answers the shared task without losing useful distinctions.

Does the audit replace copywriting?

No. It defines the work and decisions that the writing phase must complete.

This website uses no analytics, advertising cookies or third-party embeds. There are no optional tracking services to enable.

We remember only that you have seen this notice, in this browser. This is an acknowledgement, not permission for a future service. Your project enquiry draft is not saved in site storage.

Read the cookie notice · Privacy notice