What to measure before a website redesign

A redesign is useful when we know what it should improve. Before the first layout, we review data, user flows, and sales context.

Context before the solution

A redesign without measurement can become a change in taste. Data should not replace strategy, but it should show where users stop, which pages have potential, and what the new design needs to improve.

What we check first

• Top entry pages and how often visitors continue.
• Flows toward inquiries, calls, or purchases.
• Search queries that bring relevant visits.
• Places where users stop because the next step is unclear.

Turning it into a plan

Before design, we write the hypotheses. Every major change should have a reason: clearer messaging, less friction, stronger proof, or faster loading.

The signal that it works

A strong redesign can explain which metrics it expects to change and why.

A redesign becomes an investment when we know which problem it solves.

Common pitfalls we keep seeing

Most redesigns start from a feeling: "the site looks outdated." The feeling is not wrong, but without data the redesign easily becomes an aesthetic change that does not move the business.

• There is no baseline snapshot of key metrics before the project starts.
• Top-performing pages get changed even though they currently bring the most useful visits.
• Flows to inquiries or purchases are not mapped, so the new design can quietly make them worse.
• Search Console queries are not analyzed, so existing signals of interest are lost.
• The redesign goal is described as "a more modern look" rather than as a concrete change in user behavior.

Without measurement, after launch nobody can say what improved and what regressed. The team feels relief because the site is new, but the business result may quietly drop with no visible cause.

What to apply this week

Before design starts, it is worth dedicating a week to measurement. It is an investment that protects far more hours later.

1. Capture the baseline: visits, sources, continuation rates, and conversions for key pages.
2. Identify 5 to 10 important flows and document where users typically drop off.
3. Review Search Console queries and isolate topics already bringing relevant traffic.
4. Turn assumptions into hypotheses: "if we change X, we expect Y."
5. Save this snapshot as the comparison line for 30, 60, and 90 days after launch.

A redesign with hypotheses and a baseline is a project with an end. Without them, the site may look better while nobody can say whether it works better.

Next step

Collect the baseline before the first layout because after launch the old comparison point is gone. If you want us to review your website foundation, send us a short note with the goal you are working toward.