Nov
12

How to Compare Two Versions of a Page After a Redesign

11/12/2026 05:00 PM bởi Seovaro Team trong


How to Compare Two Versions of a Page After a Redesign

A redesign can make a page look better and perform worse at the same time, which is why comparing the old and new versions carefully matters so much. What should you compare? Everything a visitor or crawler experiences: headings, text, links, speed, layout, and how deep important content sits. Who should do it? The site owner, marketer, or developer responsible for results after launch, not just the person who approved the new design.

When is the right moment? Twice, ideally: once on a staging copy before launch, and again in the first weeks after launch when real data arrives. Where do differences hide? Often below the surface, in a dropped heading, a moved call to action, or a link that quietly vanished from a template. Why bother? Because traffic drops after redesigns are usually caused by small, fixable losses that nobody noticed, not by the new look itself.

How do you compare two versions without drowning in detail? You work through one layer at a time, content first, then structure, then technical signals, and you write down every difference before deciding what to restore. This guide gives you that order, plus the checks that catch the problems teams most often miss.

How to Compare Two Versions of a Page After a Redesign Systematically

Start by getting both versions in front of you. Use a saved copy, a staging URL, or a web archive snapshot for the old page, and open the new page beside it. Resist judging by appearance for the first pass. Your opening question is not which looks nicer, but whether the new version still says the same things to the same audience.

Read the old page top to bottom and note its promise: the main heading, the first paragraph, and the primary action you wanted visitors to take. Then read the new page the same way. Redesigns often soften strong copy into vague design-friendly text, and that single change can explain a fall in enquiries even when rankings hold steady.

The content layer checklist

  • The main heading still targets the same topic and search intent.
  • Key paragraphs, proof points, and answers survived the move intact.
  • The primary call to action appears in the same places, or better ones.
  • Important images carry the same subjects, captions, and alt text.
  • No sections were dropped silently to make the layout cleaner.

Comparing Structure, Depth, and Internal Links

Next, compare how each version is built. Check the heading order, because a redesign that turns the main heading into a decorative banner or stacks multiple top-level headings confuses both readers and crawlers. Then trace how far key content sits from the homepage and how many internal links point to the page in each version.

A tool such as the Page Depth Analyzer makes the depth side of this comparison quick, showing how many clicks separate a page from the homepage. If the redesign buried a money page one level deeper and stripped its links from the navigation, you have found a concrete problem to fix rather than a mystery to worry about.

Structural differences that change results

  1. Heading hierarchy changed, skipped levels, or lost the main keyword focus.
  2. Internal links to or from the page were removed during the rebuild.
  3. Content moved far below long banners, sliders, or decorative sections.
  4. Navigation labels changed, breaking familiar paths for returning visitors.
  5. Forms, buttons, or phone numbers became harder to reach on mobile.

Technical signals belong in this pass too. Compare the title tag, meta description, canonical, and status code of both versions. Google's troubleshooting guidance on HTTP and network errors is worth keeping nearby, because a page that intermittently errors after a server move can lose ground in ways that look like a content problem.

Comparing Speed and the Mobile Experience

Redesigns love heavy visuals, and heavy visuals love slowing pages down. Load both versions on a phone over a normal connection and time how long each takes to become usable. A new hero video or uncompressed image set can double load time while the desktop preview in a meeting room still feels instant.

We keep more redesign and audit walk-throughs on the Seovaro blog if you are planning a bigger relaunch. The recurring lesson is that every beautiful change still has to survive contact with a small screen, a slow connection, and a distracted visitor.

What the numbers should tell you afterwards

After launch, compare like with like. Match the same weekdays before and after, and separate brand searches from generic ones where you can. Look at clicks, average position, enquiries, and how far visitors scroll or move through the site. One bad week proves little; a consistent gap across several weeks, tied to a difference you found in your comparison, is a finding worth acting on.

Deciding What to Restore and What to Let Go

Not every difference deserves a rollback. Some old elements were genuinely weak, and the new version should keep its improvements even if early numbers wobble. Restore the things that served search intent and visitors clearly: lost content, lost links, lost clarity. Let go of clutter the redesign rightly removed, even if you feel nostalgic about it.

The goal of comparison is not to rebuild the old page inside the new design. It is to make sure progress did not quietly delete the ingredients that made the page work. When you can name exactly what changed, you can fix a redesign with a scalpel instead of a panic-driven rebuild.

Starting your own comparison this week? Try the Page Depth Analyzer on your redesigned pages, check whether anything important drifted deeper, and work through the layers above with the results in hand.

Frequently Asked Questions

How soon after a redesign should I compare performance?

Do a structural comparison before or at launch, then compare traffic and conversion data after a few weeks of stable running. Avoid judging on the first chaotic days, when crawling and caching are still settling.

What if I no longer have a copy of the old page?

Check web archives, staging environments, backups, and cached copies from your tools. Even a partial record of the old headings, text, and links is enough to spot the biggest losses.

Can a redesign hurt rankings even if the content stays the same?

Yes. Changes to internal links, page depth, speed, headings, or status codes can all affect performance without a single word changing. That is why a full comparison covers structure and technical signals, not just copy.

Should I roll back a redesign if traffic drops?

Rarely as a first move. Identify the specific differences first and restore the lost elements inside the new design. A full rollback is a last resort when the new version is fundamentally broken.