How to Audit Website Content Before a Redesign

A redesign without a content audit usually discovers its real scope late. Empty templates wait for copy. Old pages are deleted because no one recognized them. Several owners rewrite the same claim differently. A high-traffic article survives even though it attracts the wrong audience, while a low-traffic page used in every major sale disappears. The audit moves those decisions ahead of design and development, when there is still time to ask why.

Digital.gov describes a content audit as listing and analyzing the content on a website or app, including more than pages: files, video, audio, and other data may be in scope. That breadth matters. A downloadable guide, calculator, embedded video transcript, policy document, form confirmation, or location record can be central to a customer journey even if it never appears in the main navigation.

Define the audit question before collecting rows

• Which domains, subdomains, languages, applications, files, media, forms, and campaign pages are included?
• What redesign decisions will the audit unlock: sitemap, templates, messaging, migration, records handling, staffing, or all of them?
• Which period of search, analytics, sales, support, and campaign evidence is representative, including seasonal content?
• Who can approve facts, brand claims, legal or policy content, customer instructions, and retirement decisions?
• What evidence is unavailable or unreliable, and how will that uncertainty be recorded?
• What is the content freeze or handoff date, and how will changes made during the audit be captured?

Create a complete working inventory

A crawl is a starting point, not the whole audit. Digital.gov's discussion of content audits similarly describes starting with an automated tool and using its spreadsheet as the basis for review. Pages hidden behind forms, scripts, account access, disconnected collections, or old links need other sources. Record access limits instead of quietly calling the inventory complete.

Use fields that support content and migration decisions

Evaluate each page through eight lenses

Assign a treatment that production can execute

“Merge” deserves scrutiny. If three service pages attracted different audiences and contained different proof, one short overview is not an equivalent destination. Create a content crosswalk: old section, evidence, query or customer need, new section, and responsible reviewer. Only then can the redirect decision be defended. Connect approved moves and retirements to the SEO-safe redesign guide so content choices, URLs, canonicals, links, and sitemaps agree.

Turn the audit into the new content system

Patterns across audit rows should shape the redesign. Repeated services suggest a service content type with required fields. Proof that needs to appear by service and industry may deserve structured case-study relationships rather than copied quotes. Staff information may belong in profiles with one source of truth. Recurring expiry dates suggest review reminders. Consistent related questions may become a deliberate internal-link and FAQ practice. This is where website design planning becomes an operating system instead of a set of page mockups.

• Define every content type, its purpose, required and optional fields, relationships, and allowed editors.
• Separate reusable facts from page-specific persuasion so one update can correct the right places without flattening context.
• Create templates around real content ranges, including long names, missing media, multiple locations, dated proof, and empty optional fields.
• Assign a subject owner, editorial owner, review interval, and expiry behavior to high-risk content.
• Document source and evidence requirements for claims, statistics, credentials, pricing, policies, and regulated information.
• Plan accessible alternatives and transcripts as part of the asset—not as a post-launch cleanup task.
• Tie each approved row to a production ticket or workflow state so the spreadsheet does not become a disconnected archive.

Sequence writing so design is tested with real meaning

Govern the audit like a decision register

Spreadsheets become unreliable when anyone can change a decision without a date, owner, or downstream notification. Lock identity and evidence fields after collection, define controlled values for treatment and status, keep comments separate from approved decisions, and record revisions. A small team can do this in a well-managed sheet; a large estate may need a database or project system. The tool matters less than traceability.

Definition of done for a pre-redesign content audit

• The scope and known exclusions are written, and the inventory combines crawl, platform, search, analytics, business, file, and legacy sources.
• Every in-scope item has an audience, purpose, business role, owner, quality assessment, evidence notes, and approved treatment—or a named escalation.
• Low-traffic, seasonal, support, sales, legal, records, accessibility, and offline use cases were not discarded by an automatic threshold.
• Merge decisions include a content crosswalk; retirement decisions include approval and records handling; moves include final production destinations.
• New content gaps have briefs, owners, source material, architecture positions, template needs, and production deadlines.
• The content model, page templates, redirect map, internal-link plan, migration tickets, and QA criteria reference the audit decisions.
• A change-control process covers new or edited content between audit completion and launch, and ongoing governance begins after release.

A good audit may recommend less content, more content, or a different form of content. Its success is not the number of pages deleted or preserved. Success is that each item on the new site has a defensible customer and business purpose, accurate evidence, an intentional location, a capable owner, and a tested path from its old address.