Skip to main content
Start for free

Redesign & migration

Measure the site before and after a redesign.

Compare both versions in the same scope.

Save a pre-change result How it works

Result comparison from the Growth plan

company.comExample

Before · WordPressAfter · Next.js

Performance4988+39

SEO8672-14

Accessibility6489+25

New after the migration

  • noindex on /blog after launch
  • canonical points to the old domain
  • 9 pages without a meta description

The situation

The old site is hard to reconstruct after a migration.

A new version can look better while introducing technical problems. A saved result lets you compare both states against shared thresholds instead of relying on memory.

Today

  • No reference point from before launch.
  • Unclear which regressions are new versus pre-existing.
  • Before and after reports come from different tools.

With Insight

  • A dated result from before the change
  • A module comparison in the same scope
  • A list of new issues after the migration

Project stages

One measurement from quote to ongoing care.

This scenario is one of five stages. The same audit runs at each one, so results compare.

  1. Before the project
    New client Specific site issues before you quote.
  2. During the project
    Redesign & migration Old and new version side by side. You are here Project handover A dated report for sign-off.
  3. After launch
    Release quality Drops after a release, before the client sees them. Ongoing care A monthly before-and-after of your fixes.

How it works

Three steps, one result.

You end up answeringWhat improved after the change, and which differences need review?

  1. Measure the current version

    Before the change, check the key URLs or crawl the whole site.

  2. Measure the new version

    After launch, run an audit in the same scope.

  3. Compare the results

    See which modules gained and where new issues appeared, such as a canonical or noindex.

What you get

A before-and-after comparison of the site

One document with a date, scope and sources. Share it with a link; the recipient needs no Insight account.

See a sample before/after comparison
Have ready
  • An audit made before the change
  • A list of key URLs
  • The same audit scope after launch

Result comparison from the Growth plan

Limits

What Insight will not do here.

An automated audit is a starting point. What it cannot see stays with you.

Outside the audit
  • It does not guarantee you keep traffic or rankings.
  • It does not build a redirect map.
  • It does not replace full UX testing of the new version.
Methodology and analysis scope

What you use

Modules and industries for this scenario.

The Insight areas this scenario uses most, and the industries where it comes up most.

Save a reference point before the change.

The Free plan needs no card. Comparisons and result history are on paid plans.

Save a pre-change result All use cases
  1. 1 Measure the current versionBefore the change, check the key URLs or crawl the whole site.
  2. 2 Measure the new versionAfter launch, run an audit in the same scope.
  3. 3 Compare the resultsSee which modules gained and where new issues appeared, such as a canonical or noindex.