How to organise a website redesign from brief to launch
Coordinate a redesign through brief, content, preview, switch and handover. Keep owners, blockers and verification evidence visible at each stage.
10 PRACTICAL GUIDES
Redesign and launch
Keep useful pages, give clear feedback and check the public website.
Use the redesign overview to coordinate the work, then follow the detailed checks for redirects, hosting, testing and handover. A preview and a public deployment need separate checks. Keep failed or unperformed checks visible in the launch decision.
↗
How to map old website URLs before a redesign
Prepare an old-to-new URL map and test relevant permanent redirects. Keep removed content, final destinations and updated internal links explicit.
How to change website hosting without overlooking email
Move hosting while preserving related domain services. Prepare a working copy, agree a fallback and verify the public site and relevant email routes.
How to find and fix broken links on a business website
Find broken destinations in menus, content and downloads. Choose a correction that preserves the customer journey and retest from the source page.
How to review a website preview before it goes public
Review preview access, test integrations and production differences. Consolidate feedback against a named version before approving the public launch.
How to give website feedback a developer can act on
Write feedback with a page, observed problem and desired outcome. Resolve conflicting requests and distinguish corrections from additional scope.
How to test a business website before acceptance
Create an acceptance test plan around customer journeys. Record content, interface and feature checks with honest coverage and clear defect reports.
How to check a business website on launch day
Check the actual public domain, content and enquiry route on launch day. Record pass, fail and unperformed checks with ownership and recovery details.
How to check a website handover before closing the project
Verify source files, setup notes, accounts and licensed assets against the quote. Demonstrate a safe update before closing the handover.
How to write a maintenance plan for a small website
Set owners and review tasks for content, renewals, software and recovery. Define the maintenance scope and keep a practical change log.
Move to the next stage
Explore the five guide topics or review the website package scope.