← All insights
PRODUCT DESIGN4 MIN READ

A website redesign should make the next decision easier for a visitor and the site easier to operate. Before changing the visual direction, understand what already works, what blocks enquiries and what must survive the launch.

The short answer

Start with goals and a content inventory. Check the mobile journey, performance and accessibility. Preserve valuable URLs, validate measurement and prepare a controlled launch with clear ownership.

01 / Agree the visitor and business goal

Write one sentence about the main visitor: what brings them to the site, what they need to understand and what a useful next action looks like. A portfolio, a software product and a professional service need different paths. “More modern” is a visual direction; it does not define a successful enquiry or a qualified trial.

Review the existing path from entry page to contact, purchase or registration. Check which pages attract relevant visitors and which questions appear repeatedly in sales conversations. Define the primary conversion and the smaller steps worth observing without turning every scroll into a business result.

02 / Inventory the pages before drawing new ones

List current URLs, page purpose, content owner, important incoming links and any known search performance. Mark each page to keep, improve, combine or retire. This prevents the attractive new sitemap from silently removing useful material or leaving the team to write essential copy just before launch.

Make responsibilities concrete. Who approves service descriptions, case permissions, product screenshots and contact details? Confirm which proof is current and explain time-specific results appropriately. Build the design around actual content length, including long titles and incomplete records.

  • Current URL and intended replacement
  • Audience, purpose and primary next action
  • Keep, improve, combine or retire
  • Copy, image and approval owner
  • Known traffic, links and conversion role
The launch should change the experience deliberately, not lose the parts of the website that already work.

03 / Walk the journey on a phone

Try the important task on a narrow screen with a real keyboard open. Can someone understand the offer, inspect relevant evidence and complete the form without fighting the navigation? Check labels, validation, tappable controls and the ability to recover after an error. A desktop layout compressed into a column is not a complete mobile experience.

Also review keyboard navigation, visible focus, contrast, headings and motion preferences. Test menus and dialogs rather than evaluating static screenshots alone. Include states such as a slow image, an unavailable video, an empty result and a failed submission.

04 / Check technical foundations and media

Run a technical check before redesigning so you can distinguish existing problems from new ones. Our Website Health Check offers a public URL check through Google PageSpeed Insights and a separate local HTML inspection. A lab report is a diagnostic input, not a complete accessibility audit or a guarantee of rankings.

Review image dimensions, formats and loading behaviour. Use video posters and avoid making an initial visit download every video in full. Test your interactive design on a less powerful device. Animation should support the page without delaying a visitor who is ready to act.

When should media load?

On arrival
  • Responsive imageServe the size that fits the screen.
  • Video posterShow a still and reserve space for the player.
On interaction
  • Video requestRequest the video when someone presses play.
Load the image size a visitor needs, show video posters first and request video on interaction.

05 / Plan URL changes and search continuity

Keep useful URLs where practical. If a URL changes, map the old page to the closest relevant replacement and implement a permanent server-side redirect. Do not redirect every retired article to the homepage. Update internal links, canonical references and the sitemap so the new structure tells a consistent story.

Google’s site-move guidance recommends preparing URL mappings, configuring redirects and monitoring the move. Follow the applicable steps for your hosting and URL changes. Check that a staging noindex directive is removed only for the production version intended to appear in search, while private previews remain protected.

06 / Define the launch and follow-up checklist

Test real form delivery, confirmation messages, external links, redirects, metadata and key mobile interactions. Confirm account access, backups, deployment ownership and the person who can resolve an incident. Check the production configuration rather than assuming a successful preview proves the live service works.

After launch, monitor meaningful events, errors, indexing and enquiries. Compare with an appropriate baseline, allowing for seasonality and traffic changes. Keep a prioritised correction list and schedule an initial review; the first release should make the next improvement easier to identify.

  • Forms deliver to the intended destination
  • Important old URLs reach relevant pages
  • Titles, descriptions and canonicals are correct
  • Analytics events represent real completed actions
  • Mobile, keyboard and reduced-motion checks pass
  • Launch owner and post-launch review are agreed

What to take away

A stronger website starts with a clear visitor journey and a controlled migration. Make content, technical checks and operating responsibilities part of the redesign scope from the beginning.

Your next step

Find the first thing to improve.

Run a website check, keep the report and use it to frame a focused redesign conversation.

Check your website

Start a project ↗