The new homepage looks better in a desktop screenshot. But can a visitor still read a case on a phone, switch to its Chinese version, and contact the right team? A visual approval is useful, but it does not answer those questions.

Before publishing a redesign, agree on what must keep working and test those things on the preview.

Write three visitor tasks

Choose journeys that matter to the business. For example:

  • A visitor enters through an article and finds the related service.
  • A prospect opens a case, checks the project scope, and switches language.
  • Someone using a phone finds the contact route and can understand what to send.

Give a tester the goal, not the clicks to follow. Run the same tasks on the current site and the preview. Record where someone hesitates, loses their place, or ends up at the wrong page.

Compare pages that do not share the homepage layout

A redesign may change a shared heading, button, or navigation component. Check a long article title, a service page, a case with images, and the blog list on a narrow screen. Try longer translated labels and larger text. Confirm that controls remain usable without relying on a desktop hover state.

Use screenshots to document the difference, but also click links, open menus, and check the page with a keyboard. A screenshot cannot show whether a control works.

Verify the content and destinations

Check service names, deliverables, and the contact address. Where the scope is visual only, compare the old and new page text and links so intentional design changes do not become accidental content changes.

Open several existing URLs directly, including a page that was not changed. Check language switches and relevant destinations rather than only whether the link returns a page.

Decide what blocks release

Define blockers before the final review. A broken contact route or inaccessible navigation should block release. A minor spacing preference can go into a later iteration. Record who reviewed the preview, which version they approved, and the fallback if the live check fails.

After release, repeat the most important tasks on the real domain. A successful upload does not prove that visitors are seeing the approved result.

For URL changes, use our redesign SEO checklist alongside this review. To discuss a focused acceptance plan, email Storm Nova Labs.