Before you redesign your website, find the problem first

What should you check before a redesign?

A redesign often starts with a visual complaint.

The site feels old. The homepage feels busy. Competitors look sharper. The brand has changed. Somebody opens Figma and the project starts moving.

That sequence feels productive, but the first question belongs earlier.

What is the website failing to do?

A business might need more qualified enquiries. A SaaS team might need more demo requests. A service company might need clearer service pages. A founder might need a site that explains a new offer without a sales call doing all the work.

Those are different problems. They need different changes.

Before I redesign a website, I want to understand the goal, the audience, where traffic comes from, the main action, and what happens after that action. I also want to know what already works. A page that looks plain might still rank well, bring useful traffic, or support sales conversations.

That is why a redesign checklist should start with evidence.

Google's own redesign guidance and current industry checklists put the same risk near the top: understand existing performance before changing URLs, content, structure, or tracking. Search visibility, forms, analytics, and useful pages deserve protection before the visual layer moves.

The first pass does not need a giant audit deck.

Start with a short list.

• What is the primary business goal?
• Who is the main visitor?
• What action matters most?
• Which pages bring useful traffic?
• Which pages produce enquiries?
• Which pages support the sales process?
• Where do visitors leave?
• Which forms matter?
• Which URLs already rank?
• What content must survive the rebuild?
• What technical or CMS limits are causing problems?

If those answers are missing, the redesign brief is still incomplete.

What to protect

A redesign gives you permission to change a lot. It does not give you permission to erase useful work by accident.

I split the review into five areas.

First, protect demand.

Look at the pages people already find through search, paid campaigns, referrals, social, or direct visits. A redesign should make those journeys clearer. It should not break the entry points that already bring the right people.

Second, protect search equity.

List the current URLs. Check which pages receive impressions and clicks. Keep strong topics intact where they still fit the business. When a URL changes, map the old address to the most relevant new page. Do not send every removed page to the homepage.

Third, protect conversion paths.

A form, booking link, phone action, demo request, pricing step, or contact flow should be tested before and after launch. A new interface means little if the main action fails.

Fourth, protect proof.

Testimonials, case studies, client logos, product screenshots, numbers, certifications, and useful examples often sit too low or disappear during a redesign because the team is focused on the new visual system. Keep the proof that helps a buyer decide.

Fifth, protect measurement.

Google Analytics, Search Console, Microsoft Clarity, ad pixels, form events, and campaign tracking need a place in the launch plan. If tracking disappears during the rebuild, the new site starts with less information than the old one.

A redesign is easier to judge when the baseline is clear.

Save the current numbers before launch. Pick one to three KPIs tied to the business goal. For a lead generation website, that might be qualified form submissions, booked calls, and CTA click rate. For SaaS, demo requests, trial starts, or pricing page actions might matter more.

The point is not to build a huge dashboard.

The point is to know whether the redesign improved the part of the journey it was meant to improve.

Define the redesign decision

Once the current site is understood, then the redesign work gets simpler.

• Define the problem.
• Agree on the audience.
• Set the primary action.
• Map the pages.
• Protect the valuable URLs.
• Plan the content.
• Decide where proof belongs.
• Design the path.
• Build the site.
• Test it.
• Track it after launch.

That order sounds less dramatic than jumping straight into new screens, but it prevents expensive rework.

It also makes design decisions easier.

• A hero is no longer a style exercise. It has a job.
• A testimonial section is no longer decoration. It answers doubt.
• A service page is no longer a template. It matches a real search or buying intent.
• A form is no longer a box at the bottom. It starts the lead handoff.

A redesign works best when the site changes for a reason.

If the business problem is still unclear, I would spend more time diagnosing before replacing the interface.

That is often the fastest way to make the redesign worth doing.