Redesign your website without abandoning useful URLs

Inventory the current site before approving a new menu

A redesign can look better while making an existing service harder to find. Begin with the website you have: pages, images, downloads, forms, and the URLs customers may have bookmarked. Include pages absent from the main navigation but still used in estimates, emails, or advertisements.

Our inventory columns are current URL, purpose, useful content, business importance, proposed destination, and action owner. Export available page information from the website platform and compare it with your service list and customer communications. Ask the team which links they send most often.

Separate design decisions from address changes

A new layout does not automatically require a new URL. Keep an address when the page still serves the same purpose and there is no practical reason to move it. If two services merge, write down what information survives and where the combined offer will live.

Google's site-move guidance recommends preparing a URL mapping, configuring redirects, and monitoring the move. It also cautions that significant changes can cause temporary search fluctuations. A careful migration reduces avoidable problems; it does not promise unchanged rankings.

Build the mapping before the launch date

For a fictional landscaper, /lawn-care might remain unchanged while /weekly-yard-service merges into /lawn-maintenance. The mapping should explain that relationship and identify the useful details transferred. An unrelated old article should not automatically redirect to the homepage just because no one reviewed it.

Give each old URL one deliberate treatment: retain, move to a relevant replacement, merge, or remove without a replacement. Ask a developer to implement the appropriate response. Do the same for important downloadable documents and images if their addresses change. These files may be linked from customer emails even when they are not prominent in the new design.

Use the correct redirect for a permanent move

Google recommends a permanent server-side redirect when a page's address changes permanently. HTTP 301 and 308 indicate permanent moves. Test the actual response and final destination, not merely whether clicking around the new site appears to work.

Run a customer-focused launch rehearsal

Open the old addresses from the inventory, including important deep links. Confirm each reaches the intended content without an unnecessary chain of intermediate pages. Check the new menus, inquiry form, phone link, booking tool, and confirmation messages on a phone.

Ask the developer to verify that staging restrictions are removed from the public site, preferred URL signals match the new structure, and the sitemap lists the intended destinations. Confirm who can roll back a faulty release and what evidence would trigger that decision. Keep a backup and a copy of the mapping.

Monitor the pages that matter

After launch, review the important old and new URLs and investigate customer reports promptly. Separate a broken form or failed redirect from a normal change in search activity. Record issues by affected page, business impact, responsible person, and fix status.

Do not declare the redesign complete solely because the homepage looks right. Completion means the intended content is available, established customer paths work, and the business has the access and documentation needed to maintain the new site.