Practical troubleshooting guide · The business scenario is illustrative, not a client case study. Administrative changes require authorised access.

A professional-services business in Stoney Creek launches a redesign, then finds old proposal links and search results lead to missing pages. The new site can look finished while its old entry points are broken. Recover those journeys using a page-by-page map based on the previous content.

Collect the addresses people still use

Gather the old sitemap, important pages from available analytics, links in email signatures and URLs in printed or shared material. Include PDF downloads and campaign landing pages where relevant. Record the exact old path and its intended replacement. Do not assume the new navigation contains everything people have bookmarked; the useful inventory comes from outside the homepage too.

Map each old page to an appropriate destination

Use permanent server-side redirects for pages with genuine replacements. Send a retired service page to the corresponding current service when that is a meaningful match. Avoid redirecting every missing URL to the homepage. Where no equivalent content exists, a helpful missing-page response is more honest than a confusing detour. Review the map with someone who understands the original content.

Test status codes and final destinations

The read-only command below inspects an old address and follows redirects. Check for a permanent redirect to the intended final page, with no loops or unnecessary chains. Update internal links to the final URLs rather than relying on redirects forever. Align canonical URLs and the sitemap with the new structure. Confirm hosting-specific redirect syntax before releasing the map.

Watch the important entry points after launch

Test the links used in quotes, invoices and directory listings, then monitor reported missing pages. Keep redirects in place long enough for returning visitors and search systems; Google recommends at least a year for site moves. A technically correct redirect does not guarantee unchanged rankings. Prioritise the pages that explain services and let customers contact the business.

Technical check

Read-only redirect check — replace the example URL

curl.exe -I -L https://example.com/old-service

This command reads public information; it does not change configuration. Example domains are placeholders.

MAKE IT ACTIONABLE

Your next steps

  • Map old URLs to real replacements.
  • Check status, destination and redirect chains.
  • Update internal links and the sitemap.

Official reference

Google: Site moves with URL changes

Technical guidance checked October 1, 2026. Product features and requirements can change. The business checklists above are practical suggestions from Cyber Bounds.

PUT THE NEXT STEP INTO PRACTICE

Help with web development.

Clear, thoughtful websites that help people understand your business and get in touch. Tell us about your situation and we’ll discuss a suitable scope and quote.

Explore Web Development