What To Audit Before A Site Redesign

A redesign starts with ambition. The brand needs to feel sharper. The site needs to move faster. The CMS is frustrating. The homepage no longer tells the right story. Competitors look more current. Leadership wants the website to feel like the business has grown.

All of that may be true. Still, the first step should not be a moodboard, sitemap, or new component library. It should be an audit.

A website redesign audit protects the value the current site already has. Even a dated, messy, slow, or plugin-heavy site may be carrying organic rankings, referral links, conversion patterns, useful content, and editorial habits that should not be discarded blindly.

The point is not to defend the old site. The point is to understand it before replacing it.

Audit The Business Role Of The Site

Start with the job the site performs for the business. A redesign should not be judged only by visual improvement. It should be judged by whether the new site supports the next stage of growth.

Ask practical questions:

• What does the site need to help the business do in the next 12 to 24 months?
• Which audiences matter most?
• Which services, products, or offers need clearer positioning?
• Which pages influence sales conversations?
• Which pages support hiring, partnerships, investors, or existing clients?
• Which campaigns depend on the site?
• Which conversion paths are business-critical?

This step keeps the audit grounded. A site that supports enterprise sales needs different evidence than a site built around local search, ecommerce, recruiting, or product-led growth.

It also helps identify constraints. Maybe marketing needs more flexible landing pages. Maybe sales needs stronger proof pages. Maybe leadership needs a premium brand signal. Maybe operations needs cleaner tracking and CRM handoffs.

Without this business layer, a redesign can become taste-driven. Taste matters, but business fit matters more.

Inventory Search And Content Value

The current site may look tired and still have pages that search engines and prospects trust.

Build an inventory from:

• A site crawl
• Search Console data
• Analytics landing pages
• Backlink reports
• Paid campaign URLs
• Sales-shared pages
• High-performing articles or resources
• PDFs and downloadable assets
• Location, service, or industry pages

Then categorize pages by role:

• Preserve because they already perform.
• Improve because the intent is valuable but the page is weak.
• Merge because several pages compete or repeat each other.
• Retire because the content is outdated, thin, or no longer relevant.
• Create because demand exists but the current site does not address it.

This is where SEO and content strategy meet. A redesign should make the site clearer, not smaller by accident. It should also avoid preserving every old page simply because it exists.

Google's Search Central documentation is broad, but one principle shows up repeatedly in technical SEO work: search engines need clear access to useful, crawlable, understandable content. A redesign audit should identify which current pages already provide that value.

Review Performance And Technical Debt

A redesign often inherits more than copy and URLs. It inherits scripts, plugins, embeds, tracking tags, image habits, hosting constraints, and CMS assumptions.

Performance review should include:

• Core Web Vitals and field data when available
• Largest templates by traffic and conversion value
• JavaScript weight and third-party scripts
• Image sizing, formats, and lazy loading
• Font loading behavior
• Caching and hosting constraints
• Mobile navigation and interaction delays
• Layout shift on key pages

Technical debt review should include:

• CMS version and maintenance status
• Plugin or package dependency health
• Security posture and access controls
• Theme or component architecture
• Redirect rules and URL handling
• Sitemap and robots behavior
• Form implementation
• CRM and marketing integrations
• Analytics and consent tooling

The goal is to decide what the redesign should fix at the foundation. Some issues are visual. Some are architectural. If the current stack cannot support reliable performance, clean tracking, or safe publishing, a cosmetic redesign will not solve the real problem.

That is often the moment when a redesign becomes website modernization. The question expands from "How should the site look?" to "What operating model should the site have?"

Check Conversion Paths And Measurement

A redesign can improve the brand and still hurt revenue if conversion paths are not understood.

Audit the actions that matter:

• Contact forms
• Booking flows
• Quote requests
• Newsletter signups
• Demo requests
• Downloads
• Phone clicks
• Chat tools
• Ecommerce checkout
• Account or portal entry points

For each path, record what happens after the user acts. Does the form submit to the CMS, CRM, email, or automation platform? Are required fields still appropriate? Is spam handled? Are hidden attribution fields captured? Are confirmation emails sent? Is the event tracked in analytics?

Then review performance by page type. Which pages convert? Which pages assist conversions? Which pages receive qualified traffic but underperform? Which paths are used by paid campaigns or sales outreach?

This prevents the redesign from overvaluing visible pages and undervaluing quiet infrastructure. A thank-you page, hidden field, CRM mapping, or tracking event may be more important than it looks.

Also decide which metrics need continuity. If leadership compares monthly lead volume, the new site should not reset the measurement model without explanation.

Evaluate Editorial Workflow

A premium site still fails if the team cannot use it.

Interview the people who update the site. Ask what is easy, what is fragile, and what they avoid doing. Watch how they create a landing page, update a service page, change metadata, add an article, swap a case study, or update navigation.

Common workflow issues include:

• Editors have too much layout freedom and create inconsistent pages.
• Editors have too little control and wait on developers for routine changes.
• Preview is unreliable.
• Reusable content is copied instead of referenced.
• Image handling is confusing.
• SEO fields are hidden or inconsistent.
• Publishing permissions do not match team responsibilities.
• Urgent updates depend on one person.

The redesign should define controlled flexibility. Editors should be able to publish confidently inside a system that protects design quality, performance, accessibility, and SEO.

Sometimes that means improving WordPress. Sometimes it means moving to a headless CMS. Sometimes it means keeping marketing content in code and giving editors a smaller, clearer surface. The audit should reveal which path matches the team.

Turn The Audit Into A Redesign Brief

The final audit deliverable should not be a long list of complaints. It should become a decision brief.

A useful brief includes:

• What the current site does well
• What must be preserved
• What should be improved
• What should be retired
• Which URLs and content carry search value
• Which conversion paths must not break
• Which technical risks need redesign scope
• Which editorial workflows need support
• Which metrics define success after launch
• Which decisions are still open

This creates a calmer redesign process. Designers know what the new experience must support. Developers know where technical risk lives. Content teams know which pages matter. Leadership can see why some work is essential and some is optional.

Redstone Foundry's modernization approach starts with that kind of clarity because a redesign should not erase hard-won value. It should preserve what works, remove what slows the business down, and give the next site a stronger operating foundation.

A good redesign audit is not a delay. It is how the team avoids rebuilding the wrong problem beautifully.