Website redesign that protects useful URLs

Prepared by Joe Design Group · Updated October 8, 2026

Decide how much change is needed

Joe Design Group offers website redesign for Indiana businesses and remote clients. A slow site, unclear offer, outdated platform, and broken inquiry path are different problems. Begin with the cause and scope a repair that addresses it.

A refresh can improve hierarchy, typography, images, and navigation while keeping the platform. A rebuild may be justified when editing, structure, or integrations no longer support the business. Neither should erase useful content merely because the new template has fewer sections.

Protect existing search paths

Inventory URLs from the site, sitemap, Search Console, campaigns, and analytics where available. Record which addresses stay and which need a permanent redirect. Preserve a valuable URL when there is no reason to change it.

If pages overlap, combine their useful content into a relevant destination. Do not send every retired guide to the homepage. Google’s site move documentation explains the preparation needed when addresses change.

Define content and asset responsibilities

Gather current service information, business contacts, approved images, and copy that needs updating. Label illustrative visuals. Keep genuine customer evidence and its permission record separate from concept images.

Agree on who writes, approves, and maintains the pages. Also confirm domain, hosting, CMS, and asset ownership. A polished release is difficult to maintain if no one knows which account controls the site.

Build a release checklist

• Compare old and new page purposes and contact paths.
• Test redirect destinations and remove redirect chains.
• Parse the sitemap and JSON-LD, then verify canonicals.
• Inspect mobile and desktop layouts and keyboard access.
• Test validation, storage, notification, and fallback routes.
• Back up files and server rules before deployment.

Measure the result honestly

Save an equivalent-period baseline before the rebuild. Compare retained URLs after release; group retired URLs as redirects rather than interpreting them as missing indexable pages. Include qualified inquiries and response handling alongside visibility.

Local checks establish whether the package renders and functions under test. Live hosting checks and actual Google index decisions must be recorded separately. A redesign cannot promise that every URL will be indexed or that positions will improve immediately.

Prepare for the audit

Send the current domain, the editing problem, and any must-preserve pages or integrations. Include Search Console exports if you have them. Avoid sending passwords or private customer records through a general inquiry.

Use the redesign decision guide to compare repair options. Before a platform or URL change, work through the migration checklist. If the current site earns visits but few useful contacts, consider a conversion review before commissioning a full rebuild.

Page imagery is illustrative. It is not a customer project or a performance result.