VDNX
ESLet’s talk

Web design & development·5 min read

Changing your website without breaking links: what to check before migration

A redesign should not erase addresses still used by customers, campaigns and search engines. This example turns five old URLs into testable decisions.

Every useful old address needs a decision before launch

Before replacing your business website, ask for a table that gives every relevant current URL one outcome: keep it, redirect it to an equivalent page, or retire it with a stated reason. A supplier who has shown the new navigation and page designs has not yet covered the whole migration. Customers, advertising, emails, directories and printed material may continue sending people to old addresses after launch.

Use a simple rule. Keep the address when the page and its purpose continue. Redirect it when there is a genuinely equivalent replacement. Retire it only when the content is gone and no other page answers the same need. The homepage is not an automatic destination for every discontinued service.

Worked example: five URLs for an equipment hire company

Consider a fictional company that hires access equipment and is commissioning a new website. The design groups its services more clearly, but also changes names and folders. Before development, client and supplier agree this small map. A live project would extend it to every address with commercial use, external links or content worth preserving.

  • `/platform-hire` → `/equipment/access-platforms/`: permanent redirect. The same service continues and the replacement has a more precise name.
  • `/forklift-hire` → `/equipment/forklifts/`: permanent redirect. The visitor reaches the specific category rather than the top of the catalogue.
  • `/machinery-repairs` → `/maintenance-and-repairs/`: redirect only if the new page still offers repairs. If it covers contract maintenance alone, it is not equivalent; the repair information must be retained or recreated.
  • `/contact` → `/contact/`: keep the address. A visual redesign does not require a route that still serves the same purpose to change.
  • `/campaign/winter-inspection` → `/winter-safety-inspection/`: keep or redirect while adverts, QR codes or emails remain active. Update those materials too, so they do not depend on a redirect forever.

The map protects customer journeys, not just search visibility

A customer may bookmark a forklift page, follow a link from a sales email or scan a QR code months later. If that path disappears, the customer sees an error even though the new website works from its own menu. Add the known origin of each address to the map: navigation, advertising, email, document, external profile or an uncontrolled bookmark.

Google advises site owners to map current URLs to new ones, configure redirects, update internal links and monitor both old and new addresses. It also notes that rankings may fluctuate while a moved site is recrawled and reindexed. A sound redirect plan prevents avoidable failures, but it cannot support a promise that search visibility will be unchanged from day one.

Equivalence is about meaning. The former repair page can point to the new one only if the new page still describes that offer. Sending every address to the homepage hides missing content and makes visitors start again. Where no replacement exists, a clear retired-content response can be more honest than a misleading redirect.

Compare keeping, redirecting and retiring before development

Keeping a route minimises change and is usually clearest when the purpose remains. Redirecting supports a better name or architecture, but introduces a dependency that must be maintained and tested. Retiring prevents obsolete material lingering, while requiring navigation, campaigns and documents to be reviewed and the experience of an old-link visitor to be decided.

For a permanent move, Google recommends server-side permanent redirects and identifies 301 and 308 responses. A business owner need not prescribe the server configuration. The brief should, however, state whether each move is permanent, require the final destination to be checked and avoid unnecessary chains through several addresses.

Do not treat this as part of visual sign-off. You can approve colours, type and components while the URL map remains incomplete, but public replacement should wait. Discovering the old addresses after launch turns planning into incident response.

Make launch a business acceptance test

Request the final map and a result for every row on the published site. Kept addresses must show the intended page. Redirected addresses must finish at one correct destination without loops or a generic fallback. Retired content must be recorded. Then test the navigation, links inside copy and each form, telephone link, download, booking or purchase that belongs to the journey.

Include external sources you control: adverts, profiles, email signatures, downloadable documents and QR codes. Update them even when a redirect exists. Redirects remain the safety net for links you cannot change. Keep a list of live campaigns as well, so a destination failure is not mistaken for an advertising problem.

The new sitemap should contain the complete canonical addresses you want presented, not obsolete routes that now redirect. Google describes sitemap submission as a hint rather than a guarantee of crawling or indexing. Acceptance must therefore include opening the pages and completing the agreed actions; a valid XML file is not sufficient evidence on its own.

When to coordinate it yourself and when to bring in help

A small site can be coordinated internally if you can obtain its URL list, know which services remain current and control campaigns, profiles and documents. Even then, give the map to the supplier before launch and agree who owns the redirects and how long errors will be reviewed.

Professional help is worthwhile when the domain, content system and structure change together; the site has many pages; different agencies run campaigns; booking, commerce or a private area is involved; or nobody knows where some incoming links originate. An independent review is also reasonable when a redesign quote says nothing about inventory, mappings, redirects or post-launch tests.

The handover should contain more than the new website. Keep the source inventory, approved map, implemented rules, launch date and test results. That evidence lets you accept the work, investigate a broken destination and change supplier without reconstructing every decision.

Sources and documentation

Content created with AI assistance. Check the sources, date and scope of each guide.

Let’s define the next step for your website.

Tell us what your business needs and where your current website falls short. We can help you define the scope.

Let’s talk about your idea