Planning a Website Redesign? Protect the Local SEO You Already Have

Protect local SEO during a website redesign by inventorying useful pages, retaining suitable URLs, mapping necessary redirects and checking the public site after launch. Agree on content and account handover before the new design is approved. The search work is part of the project scope, not a final cosmetic check.

I would put that work into the project brief from the beginning. It is much easier to plan a URL handover before development than to reconstruct the old site after its pages have disappeared.

Make a page inventory before approving the new structure

List the current page addresses, their purpose, and what should happen to them. Include service pages, useful articles, contact details, downloadable guides, and campaign destinations. Use the existing sitemap and available Search Console and Analytics reports to identify pages that receive attention.

Do not limit the list to the pages in the main menu. An older guide or a page linked from a business directory may still be an important entrance. Ask the team which links appear in quotes, email signatures, printed material, or customer messages.

Give each address a decision: keep, improve, merge into a genuinely relevant page, or retire. Keep useful URLs when there is no reason to change them. For necessary changes, plan the destination before launch.

In a hypothetical electrical business, a useful lighting-installation page might keep its address while receiving a clearer layout. Two thin pages about the same maintenance service might be combined. An unrelated expired promotion may need a different retirement decision. Sending all three to the homepage would ignore what each visitor expected.

Save the agreed inventory with the project documents. It should be understandable to the business owner as well as the developer.

Build the handover into the redesign scope

If URLs change, Google recommends mapping old addresses to their appropriate replacements and using permanent redirects where suitable. The aim is a direct, relevant route rather than a chain of stops. Google’s site-move documentation also explains that search visibility can fluctuate while changes are processed.

Assign a person to the redirect map, another to the service information, and an owner for the launch decision. In a small project, one person may hold several roles. The responsibility still needs to be explicit.

Carry over the useful substance of the old pages. Confirm service coverage, phone numbers, pricing explanations, permissions for photographs, and the details needed for enquiries. A cleaner design should not accidentally remove the answer that made a page useful.

Use the service-page content brief to collect missing facts. Keep a list of decisions that require the owner’s input, such as whether a discontinued service should still appear anywhere.

Test the new site on real customer tasks: finding a service, reading the conditions, calling the business, and completing a form. Check what happens after submission and where the notification arrives. A success message alone does not prove that the team received the enquiry.

Check the launch and leave time for follow-up

Before launch, agree on a recovery plan and who can use it. Keep a backup of the previous site and the approved page map. Choose a launch time when the people responsible for the website and enquiries are available.

Use a short launch checklist:

• Test representative old links and their intended destinations.
• Check that live pages are accessible and any staging noindex restriction has been removed where appropriate.
• Confirm canonical addresses, internal links, and the sitemap reflect the live site.
• Test the phone link, contact form, notification delivery, and confirmation message.
• Confirm analytics still records the agreed customer actions.

Our XML sitemap checklist explains the sitemap part in more detail. An updated sitemap helps discovery; it does not promise indexing or a particular ranking.

After launch, inspect important URLs in Search Console and review errors, traffic, and enquiries against the saved baseline. Investigate specific missing pages or broken journeys before drawing conclusions from one quiet day. Keep the old-to-new map available for fixes discovered later.

If a redesign is on your calendar, explore RenForge Studio’s website services and include the existing site’s search and enquiry needs in the brief. A successful launch should give people a better route to the business while accounting for the routes they already use.

For a related application, explore the Tampa roofing website redesign study. These planning examples explain proposed decisions and do not report completed client results.

Confirm that a rebuild is the right scope

Before replacing the platform, separate faults that need a repair from constraints that justify a rebuild. A wrong form recipient, missing service explanation and inaccessible account are different problems. Ask the provider which content and working URLs it will retain.

The contractor website redesign-or-repair guide helps frame those options. Keep this local SEO checklist for the migration and launch work once the replacement scope is agreed.

Sources and photo credits

• Google Search Central: site moves and migrations
• Google Search Central: request a recrawl
• Further reading: Google on hiring SEO help during a redesign

Photos, in order of featured image followed by section images: sarah b; Compagnons; Hal Gatewood; Amy Hirschi. Used under the Unsplash License. These are illustrative stock photographs, not RenForge client projects or business premises.