How to organise a website redesign from brief to launch

A redesign needs a sequence of decisions, not just a launch date. Use this guide as the project overview, with separate checklists for the detailed work. For each stage, identify an owner and the evidence needed to proceed.

Agree what success looks like

Begin with the customer task and the problems in the current site. Record the pages, features and integrations to keep. Confirm the scope, content responsibilities, price and schedule assumptions before work starts. If a required feature is unclear, settle it before approving a layout built around it.

Prepare the material

Create a content inventory and identify missing text or assets. Check image permissions and public business details. Record important existing URLs so they are not lost when the page map changes. Keep project files organised and separate publishing material from credentials or private customer information.

Review a working preview

Approve content and functionality as well as visual design. Follow the customer's journey on a phone and desktop. Consolidate feedback through one decision-maker, using page addresses and specific changes. Keep new requests separate from corrections against the agreed scope.

Prepare the switch

Confirm the destination host, domain setup and fallback version. If URLs change, prepare and test the redirect map. Google's migration guidance recommends relevant permanent redirects and updated internal links. Do not let a launch deadline replace those checks.

Launch and hand over

Verify the public domain, core pages and enquiry route. Check the source files or platform export, deployment notes, account ownership and recurring costs. Name the person who watches the site after launch and handles agreed defects.

Use a status sheet with stage, owner, blocker, evidence and approval date. A useful row might say “Contact delivery: waiting for authorised inbox test,” rather than “Website 95% complete.” That keeps the unresolved risk visible.

After launch, separate technical acceptance from marketing results. Publishing is not proof of indexing, and indexing is not proof of enquiries. Review those outcomes as evidence becomes available instead of promising that the redesign will preserve every ranking or produce a fixed number of leads.

Practical guidance with illustrative examples. Read our editorial standards or send a correction.