A redesign goes smoother when the business decisions are made before the homepage is being styled. You do not need a perfect brief, but you should know what must stay, what can change and who controls the important accounts.
1. Write down what the current site is supposed to do
Start with the business outcome, not the colours. Is the site supposed to generate quote requests, phone calls, appointments, applications, product enquiries or something else? A redesign should make that action clearer, not simply make the old pages prettier.
2. Keep access to the domain separate from the website
Your domain is the public address customers know. Before a redesign starts, confirm who controls the registrar account and DNS. The website can be rebuilt on a completely different hosting platform while the domain stays the same. Do not cancel the domain just because the old hosting is being replaced.
3. Decide what content is worth keeping
Old sites often contain useful service descriptions, FAQs, photos, testimonials and pages that already receive search traffic. Make a simple keep / rewrite / remove list. If a page already performs well in search, replacing its URL without a redirect can create an avoidable loss.
4. Review the customer journey on a phone
Open the current site on a phone and try to complete the main action yourself. Can you understand the service quickly? Is the phone number tappable? Is the form too long? Does important information sit behind tiny menus? Mobile friction is often a better redesign brief than a list of visual preferences.
5. List every form and integration
Quote forms, appointment requests, newsletter signups, maps, payment links, CRM connections and analytics all need to be accounted for. A form that looks good but sends nowhere is not finished. For each form, decide where the submission should go and what the customer should see after sending it.
6. Protect search visibility during the switch
Keep important page URLs when it makes sense. When URLs change, use redirects from the old addresses to the closest new pages. Carry over useful page titles and descriptions, update the sitemap and make sure the production site is indexable after launch.
7. Build the new version before changing DNS
A safer workflow is to build and test the redesign on a temporary deployment first. Check desktop, mobile, links, forms and analytics. Only after approval should the domain be pointed to the new site. That keeps the public site stable while the replacement is being built.
8. Keep a rollback copy of the old site
Before launch, save a copy or backup of the existing site. Most redesigns do not need it after launch, but having a rollback option makes the cutover less risky.
A simple redesign handoff
- Current website URL
- Domain registrar access
- Logo and brand files
- Services and priority offers
- Best existing photos and testimonials
- Forms or booking requirements
- Examples of sites you like — and what you like about them
Build the next version around the business — not a template.
Prairie Web Studio works remotely with businesses across Canada on new websites, redesigns, booking flows and web apps.
Start a project →