A redesign rarely fails because of the new design. It fails because the team starts building on top of problems they never measured. A pre-redesign website audit is the step that turns a redesign from a guess into a plan. It tells you what is broken, what is worth keeping, what is costing you enquiries, and what the new build actually has to solve.
For a UK small business, this matters even more. A redesign is a real cost in time and money, and the new site usually replaces something that already affects your search visibility, your enquiry flow, and your day-to-day operations. A practical audit protects that investment.
What a pre-redesign website audit is supposed to find
A good audit is not a checklist of generic SEO tips. It is a structured review of the current site across four layers:
- Business layer: Is the site doing the job the business needs it to do, such as generating enquiries, taking bookings, or supporting existing customers?
- User layer: Can real visitors find what they need, understand the offer, and complete the main actions without friction?
- Technical layer: Is the platform, hosting, code, and infrastructure healthy enough to build on, or are there problems the redesign will inherit?
- Content and SEO layer: Which pages earn traffic, which ones are thin or duplicated, and what search visibility would be lost or improved by the new build?
The goal is to leave the audit with a clear list of what to keep, what to fix during the redesign, what to drop, and what new functionality the new site needs.
Why small businesses often skip the audit and pay for it later
Most small business redesigns start with a visual brief. A team picks a fresh look, a new layout, or a new template, then tries to retrofit the existing content into it. Within a few weeks, three problems appear:
- Traffic drops because old URLs, titles, or content patterns were lost in the move.
- Enquiries drop because the new information architecture buries the contact details, service pages, or booking flow.
- Technical debt carries over because the underlying CMS, hosting, or plugin stack was never reviewed.
An audit does not have to take weeks. For a typical small business site, a focused audit can be completed in a few working days and produces a document the developer or designer can build against directly.
The practical process for auditing a business website before a redesign
1. Define the business goals of the new site
Before touching the current website, write down what the redesign is meant to achieve. Without this, every later judgement call becomes a debate.
Useful prompts include:
- What are the top three actions a visitor should take on the new site?
- What does a successful enquiry, booking, or sale look like?
- Which pages currently bring in enquiries, and which do not?
- What has changed in the business since the current site was built?
This step also pairs well with the early discovery work covered in key discovery questions before starting a business website project, because the answers shape what the audit needs to measure.
2. Map the current site structure and content inventory
Create a spreadsheet of every important page on the current site. For each page, record:
- URL and page title
- Main purpose, such as service page, contact, blog post, landing page, or product page
- Word count and last updated date
- Calls to action present on the page
- Internal links pointing to it
- Whether it is indexed in search engines
This inventory quickly shows where content is duplicated, where pages are thin, and which pages carry real weight. It also forms the baseline for redirect planning later.
3. Review analytics and search performance
Analytics data answers the question of what the current site is actually doing, separate from what people assume it is doing.
Pull the last twelve months where possible and look at:
- Top landing pages by traffic
- Top exit pages
- Conversion events or enquiry form completions
- Bounce rate and time on page for the main service pages
- Mobile versus desktop split
- Search queries that already bring visitors, including branded and non-branded terms
If you use Google Analytics, Google Search Console, or a similar stack, this data should be exported before any redesign work starts, so the new site can be measured against the same baseline.
4. Audit the technical foundation
The technical audit is where many hidden costs live. For a small business site, the most useful areas to check are:
- Hosting and server: Is the current hosting plan appropriate, or is it the reason the site feels slow? Check server response time, resource limits, and PHP version.
- CMS and stack: What platform is the site on, what version is it running, and how many plugins or extensions are active? An outdated WordPress install with 40 plugins is a common cause of slow loading and security risk.
- SSL, DNS, and email: Is the certificate valid, do DNS records resolve cleanly, and is the domain email set up properly for deliverability?
- Backups and recovery: Are backups running, are they tested, and where are they stored?
- Performance: Check page weight, time to first byte, and largest contentful paint on a sample of key pages using a tool such as Lighthouse or WebPageTest.
- Accessibility basics: Check colour contrast, form labels, image alt text, and keyboard navigation on the main pages.
A simple health check often surfaces the real reasons a redesign is being considered in the first place.
5. Review content quality and SEO
Content is usually the largest part of a redesign, so it needs its own pass.
- Service pages: Do they clearly state the offer, who it is for, where the business operates, and how to take the next step?
- Duplicate or thin content: Are several pages competing for the same search terms with overlapping text?
- On-page SEO: Are titles, meta descriptions, headings, and internal links consistent and descriptive?
- Structured data: Is basic schema in place where it helps, such as LocalBusiness, FAQ, or Product?
- Images and media: Are images compressed, sized correctly, and using descriptive filenames and alt text?
6. Review the user journey
Walk through the site as if you were a new visitor arriving from search, a past customer returning, and a referrer following up. Try to complete the main actions:
- Find a specific service and request a quote
- Find pricing or a starting point
- Find contact details and get in touch
- Book a call, demo, or appointment
Note where the path is smooth and where it breaks. The redesign should remove the breaks rather than restyle them.
7. Capture everything in an audit report
The audit is only useful if it produces a document the design and development team can act on. A simple structure works well:
- Executive summary with the three to five most important findings
- Business and user findings
- Technical findings with severity levels
- Content and SEO findings
- Recommendations grouped by phase: keep, fix during redesign, drop, or build new
- A redirect map for any URLs that will change
This is the document that protects the project. It is also the right place to connect with how to scope a small business website project without surprises, since a clean scope is hard to write without audit evidence behind it.
Common audit mistakes that lead to weak redesigns
Even with the best intentions, a few mistakes reduce the value of the audit.
- Auditing the wrong things. Spending hours on minor visual details while ignoring slow hosting, broken forms, or weak service pages.
- No baseline data. Redesigning without recording current traffic, conversions, or search visibility means there is no way to know if the new site is doing better or worse.
- Assuming everything will change. Some pages and content patterns already work. Losing them in a redesign for the sake of a fresh look is a common and expensive mistake.
- Ignoring maintenance reality. A redesign that introduces a platform the business cannot maintain is a short-term win and a long-term cost. This is worth weighing against the wider small business website maintenance checklist for UK SMEs, since the new site will need ongoing care.
- Skipping redirects. Changing URLs without a redirect map will quietly remove search traffic that took years to build.
What an audit looks like in practice
A typical audit for a small business website with around fifty pages might produce findings like these:
- Three service pages account for most of the organic traffic, but the contact form on each sends users to a generic inbox that no longer routes enquiries correctly.
- The CMS is two major versions behind, and several plugins have not been updated in over a year.
- Mobile pages are noticeably slower than desktop, largely because hero images are not compressed and a slider script loads before content.
- The blog has 120 posts, but only 15 bring meaningful traffic, and another 20 are thin duplicates of service topics.
- SSL and DNS are fine, but the business email uses a default setting that affects deliverability for new enquiries.
None of these findings require a redesign on their own. Together, they explain why the current site is underperforming and give the new build a clear brief.
When to do the audit in-house and when to ask for help
Small business owners can do meaningful parts of an audit themselves, especially around goals, content inventory, user journey, and basic analytics review. Tools like Google Search Console, Google Analytics, and a simple crawl tool give most of the data needed.
The areas where external help usually pays for itself are:
- Server and hosting review, including DNS, mail records, and SSL configuration
- Code and CMS review, particularly for WordPress or custom PHP platforms
- Performance analysis using proper testing conditions
- Security review of admin access, backups, and update hygiene
- SEO audit at scale, including redirects and structured data
For many UK small businesses, hiring a freelance IT specialist or web developer to run a focused pre-redesign audit is faster and cheaper than absorbing the same problems after launch. The audit fee is usually small compared with the cost of a redesign built on hidden issues.
How the audit feeds into the redesign brief
The audit output is the raw material for a strong redesign brief. It should feed into:
- The information architecture of the new site, based on what currently works and what is missing
- The content plan, including which existing pages to refresh and which to retire
- The technical specification, including hosting, platform, security, and integrations
- The redirect map that protects search visibility through launch
- The post-launch measurement plan, using the baseline data captured during the audit
This is also where adjacent considerations matter, such as whether the new site should support progressive features, how it will fit into a wider IT setup, and what ongoing maintenance will look like. A practical overview of one option sits in turning your business website into a PWA, and longer-term thinking around infrastructure choices is covered in IT strategy for growth and scaling.
Closing thoughts
A pre-redesign website audit is the step that turns a redesign from a hopeful guess into a grounded plan. It protects existing search traffic, surfaces the real reasons the current site is underperforming, and gives the design and development team a clear brief to build against. For UK small businesses working with limited time and budget, it is usually the cheapest and highest-value part of the whole project.
If a redesign is on the horizon and the current site has accumulated a few unknowns, N. Cristea can carry out a focused audit, document the findings in a usable format, and support the next stage of planning, build, or handover. The goal is a redesign that starts from evidence and ends with a site the business can actually run.