Back to blog

Blog article

Website Audit Before a Redesign: What Agencies Should Check First

The Automate Team November 5, 2026

Before you redesign a client's site, audit it first. What to check, what to keep, and how to avoid losing rankings, traffic, and enquiries in the rebuild.

Why Audit Before You Redesign

A redesign that starts from taste instead of evidence usually repeats the old site's mistakes in a newer layout. The pages that brought in enquiries get rebuilt without anyone noticing, the URLs that ranked disappear, and the client judges the result on how it looks — until the traffic and the enquiries drop.

An audit before a redesign gives you the evidence to avoid that. It tells you what is already working, what is actually broken, and what the new site has to protect. For an agency, it also turns a vague "we need a new website" brief into a scoped job with a defensible price. The audit is the part of the redesign that makes the rest of it safe to sell.

Three Things the Audit Is For

Before you touch a layout, the audit should answer three questions.

  • What is already working? The pages that rank, the pages that bring in enquiries, and the content visitors actually read. These are the parts of the site the redesign must protect, not replace.
  • What is actually broken? The problems visitors and search engines hit today — slow pages, dead links, pages that never rank, forms that never get completed. These are the reasons a redesign is justified.
  • What should the redesign change — and what should it leave alone? Most sites need a focused set of changes, not a rebuild of everything. The audit is what separates the two.

What to Cover in a Pre-Redesign Audit

A pre-redesign audit is broader than a design review. It covers the parts of the site a new layout can easily damage: search visibility, content, and the paths visitors take to enquire.

AreaWhat to checkWhy it matters for the redesign
Search visibilityWhich pages rank, for which queries, and how much traffic they bring inRanking pages must keep their URLs and their substance, or the redesign costs the client traffic
ContentWhich pages earn visits and which pages nobody readsThin or unread pages can be merged or removed; strong pages should be kept and improved, not rewritten from scratch
Design and usabilityWhether visitors understand the offer, find the next step, and trust the siteThese are the findings the new design has to fix — a clear headline, a visible action, a page that reads well on a phone
Technical healthSpeed, mobile behaviour, broken links, and pages search engines cannot reachTechnical problems should be fixed in the rebuild, not carried into the new site unchanged
Enquiries and conversionsWhere visitors enquire, where they drop off, and which pages never lead anywhereA redesign that looks better but converts worse has failed, whatever the client thinks of the layout

Record a Baseline Before Anything Changes

Write down the numbers before the redesign starts, or you will have no honest way to judge it afterwards. Record, at minimum: the pages that bring in the most search traffic, the queries they rank for, the site's overall search traffic, and the number of enquiries or calls the site produces in a typical month. Keep the list short and keep it in the audit document, so the client can see the before-and-after in the same place.

A baseline also protects you. If traffic dips after launch, you can show whether the dip is a redesign problem or a seasonal one — and which pages changed. Without it, every drop after launch becomes the redesign's fault, whether it is or not.

Decide What to Keep, Fix, or Drop

Use the audit to sort every important page into one of three groups before anyone designs anything.

  • Keep. Pages that rank, bring in traffic, or convert. The redesign should preserve their URLs, their main content, and their internal links. If a URL has to change, plan the redirect before launch, not after.
  • Fix. Pages with a real problem the redesign can solve — a confusing layout, a missing call to action, slow loading. These are the pages the redesign is for, and the brief should name them.
  • Drop or merge. Pages nobody visits, pages that say the same thing twice, and pages that exist only because someone once asked for them. Removing them makes the new site smaller, clearer, and easier to maintain.

This sorting is also the honest way to scope the job. A redesign that keeps ten strong pages, fixes five broken ones, and drops the rest is a very different project from a redesign of everything — and the client deserves to know which one they are buying.

Protect Rankings During the Rebuild

Most of the ranking damage from a redesign happens in the handover, not in the design. The common failures are simple: URLs change without redirects, page titles and headings are rewritten without checking what ranked, and internal links point at pages that no longer exist.

Plan the handover before launch. List every URL that changes and where it should redirect. Check that the new pages keep the titles and headings that earned their rankings. And check the new site's internal links against the old ones, so pages that used to pass authority to each other still do. A short launch checklist, written from the audit, catches most of this in an afternoon.

Present the Audit as the Redesign Brief

When you show the audit to the client, keep it short and concrete: what is working, what is broken, what the redesign will change, and what it will deliberately keep. Name the baseline numbers, so the client knows how the redesign will be judged. And be honest about what a redesign will not fix — a new layout will not rescue content nobody wants, or traffic that was never there.

That honesty is what makes the audit worth paying for. A client who understands why the redesign is scoped the way it is will defend it internally, and will come back when the next site needs the same treatment.

Start With an Audit, Not a Mockup

The fastest way to build a pre-redesign audit process is to run one on a site you already know. Start with a free audit to surface the structural and search issues, then work through the checks above — search visibility, content, design, technical health, and enquiries — and sort the pages into keep, fix, or drop. If the audit gives you a clear brief and a baseline you can defend, you have a process you can offer to every client who asks for a redesign.

Turn the findings into a structured document with the report generator, or start at AuditPitch and judge the output on the findings themselves.