Website development

Website redesign checklist for businesses

Plan a business website redesign around existing leads, useful content and a launch you can verify.

Illustration for Website redesign checklist for businesses

Checklist

  1. Create an inventory of pages and conversions
  2. Preserve URLs and redirect changed addresses
  3. Prototype high-value navigation paths
  4. Rehearse editor and launch handover

Example

A service firm receives enquiries from two older resource pages even though those URLs are missing from the new sitemap. An inventory that joins URLs, search data and forms catches that gap before launch.

What to bring to your review

Search Console exports, form sources, URL inventory, editors, landing pages.

Worked example: preserve an enquiry page through a redesign

Export the last 90 days of relevant landing pages from your own analytics and Search Console. Create columns for the URL, current user task, desired destination, form or call action, content owner and proposed redirect. A resource page that sends visitors to a specific service deserves a destination that keeps that relationship visible.

Run the old and new pages against the same customer brief. The reviewer should be able to discover the correct service, see its questions and submit an enquiry on mobile. In staging, record which address accepts the submission and whether the internal report retains the source page.

At launch, request a shortlist of old URLs without relying on the site menu. Check the HTTP status and final destination, then check internal navigation for updated links. If you change the homepage layout, also confirm the existing high-value paths from search and shared links.

How to put the checklist into practice

Build a page inventory

Collect landing pages from analytics, sitemap exports and the current navigation. Add entry pages from search reports and known inbound links. Record each page's owner, preferred URL, current purpose and required next action. Prioritize pages that are used heavily by sales or customers.

Review the new templates

Check a service detail, catalogue item, article, enquiry page and any translated template. Use real content because long titles, empty sections and regional contact information can change what the layout needs. Verify that mobile users can reach the primary action and that keyboard navigation follows the page order.

Map changes before launch

Mark each URL as retained, replaced or retired and record the destination for redirects. Check that it delivers a matching intent. Review canonical tags, redirects and indexing in a production-like environment. Export the approved mappings so the launch team can test against them.

Separate technical release from content sign-off

Agree what must be true before traffic changes. Check a successful enquiry, a mobile form error, an old backlink destination and visits from search. Identify who can roll back a release and when. Keep notes on what was checked before and after the switch.

Website redesign gate

  1. Confirm important old URLs reach their corresponding pages
  2. Test form submission against the destination system
  3. Review production robots and sitemap
  4. Compare early landing-page changes to the prior baseline

Need help putting this into practice?

Share what you are working on and where you need input.

Discuss this project