Illustration of two website layouts joined by a gold bridge, with planning cards on a desk.

A website redesign often begins with a visual problem: the pages look dated, the mobile menu is awkward, or the business has outgrown its original layout. But an existing site may also contain valuable information, working forms, and links customers still use.

Before approving a rebuild, identify what needs to change and what deserves to carry forward. A clear redesign brief helps your developer improve the experience while planning for the pages and business processes already in use. These seven steps give small-business owners a practical place to start.

1. Define the problem in customer terms

Replace “make it modern” with an observable problem. Perhaps visitors cannot find the right service, staff must update the same details in several places, or a phone user struggles to request an appointment. Choose a few priorities that the new site should address.

Write down what success would look like in everyday use. A customer can find coverage information from a service page. An employee can update a testimonial without editing a whole layout. A returning client can reach the portal from the main navigation.

These examples help distinguish essential work from optional visual preferences. They also give you something concrete to review when the new design is ready. A pleasing homepage is one part of the project; it should support the tasks people need to complete.

2. Inventory the pages and features you already have

List current page addresses, their purpose, and the person responsible for their content. Include articles, downloadable documents, booking pages, customer logins, and special landing pages. Some important destinations may not appear in the main menu.

Use available website reports and staff knowledge to identify pages that receive visits or generate useful inquiries. Ask which links appear in email signatures, advertisements, directory profiles, printed materials, or QR codes. Those links can remain in circulation long after a redesign.

Record working features as well as pages: form notifications, saved entries, payment handoffs, search, imports, and customer permissions. A screenshot captures appearance, but it does not explain the process behind a button. Give those processes a place in the project brief.

3. Decide what to keep, revise, combine, or retire

Assign a decision to each item in the inventory. Keep accurate information that still serves customers. Revise unclear or outdated material. Combine genuinely overlapping pages when a single destination will answer the questions better. Retire content only after considering who still uses it.

Separate content approval from design approval. Identify who can confirm service descriptions, prices, contact details, photographs, and customer quotations. If a page is waiting on an answer, record that dependency rather than letting placeholder text become part of the launch.

Avoid rewriting everything simply because the layout is changing. A focused content review can preserve useful explanations and reduce the amount that needs checking. Keep a copy of approved material so reviewers know which version belongs in the finished website.

4. Plan for every address that changes

Keeping a useful page at its existing address can simplify the transition when the content and purpose remain the same. When an address must change, record the old address and the most relevant new destination in a mapping document.

Google’s redirect guidance recommends permanent server-side redirects where possible for permanently moved pages, using status codes such as 301 or 308. Ask the developer how moved pages will be handled and tested, rather than assuming the new design automatically covers them.

Do not send every removed page to the homepage. Map a moved or consolidated page to its relevant replacement. If content has no suitable replacement, discuss the appropriate response with the developer. The goal is to give visitors an accurate destination, not merely avoid seeing an error.

5. Keep the launch manageable

If the redesign also includes a domain change, hosting change, or replacement business system, separate the decisions and dependencies. Google’s site-move guidance recommends changing one thing at a time where practical and preparing a URL mapping when addresses change.

Agree on who controls hosting, domain settings, email, backups, and the launch itself. Clarify whether moving the website affects any other service. A website project should not leave the team guessing which provider handles a contact mailbox or an existing customer portal.

Choose a launch window with support available and define how unexpected problems will be handled. Keep the current site backed up and agree on a recovery plan. For sites receiving orders or submissions, discuss how new records will be preserved during the transition.

6. Review real tasks on the test site

Test the redesign as a visitor would use it. Start at an important page, find the relevant service, complete a clearly labeled test inquiry, and confirm the message reaches the intended staff member. Check any saved record and acknowledgement as well.

Repeat the key tasks on a phone. Review navigation, readable text, contact links, downloads, and any login or checkout process. Use appropriate test accounts and payment testing arrangements so the review does not create unintended customer messages or live charges.

Have someone unfamiliar with the design try a few tasks without coaching. Note where they hesitate or take a wrong turn. Resolve important issues before launch and keep lower-priority improvements in a visible list with an owner.

7. Treat launch as the start of verification

After the site goes live, check the important old links, new pages, forms, and customer workflows again. Confirm the public site shows approved content and that any settings used to keep the test version out of search have been handled appropriately for launch.

Monitor inquiries and available search reports over time. Google notes that significant URL moves can involve temporary ranking fluctuations while pages are processed. No responsible redesign plan can guarantee unchanged search visibility; a documented transition makes issues easier to identify and investigate.

Pubvertise’s website services include redesigns, content reorganization, and custom WordPress functionality. If your website needs a rebuild, describe what customers struggle with and which existing features your business relies on. That gives the project a useful foundation before the first layout is drawn.

Before You Redesign Your Website: What to Keep, Change, and Test

Leave a Reply

Your email address will not be published. Required fields are marked *