Skip to content

Redirect old URLs sensibly during a website relaunch

Map old addresses to suitable new destinations and check redirects, content and accessibility using a concrete list.

Anna Neumann2 min read
Blue-accented browser window with a large 301 indicator and a bent redirect arrow.

Start with existing entry points

During a relaunch, people may still visit old addresses through saved links, search results or other websites. Identify them from existing page lists, internal links and available visit data. Record their purpose and content. A new design alone does not require new URLs; suitable addresses can remain.

A permanent address change needs a destination with a matching purpose. Google recommends mapping current URLs to their new counterparts. Decide what happens to the content before creating a general redirect rule.

A worked mapping example

This plan is entirely fictional. All paths belong to the example domain example.com. The new service page fully answers both previous questions about CRM-ERP integration. The campaign has ended and has no suitable replacement. The table describes expected behaviour, not test results.

Old address

New destination

Expected response

Content check

/crm-erp

/leistungen/systemintegration

301 to destination, then 200

Integration explanation remains available.

/erp-verbindung

/leistungen/systemintegration

301 to destination, then 200

Previous questions and useful examples have been retained.

/aktion-alt

—

410, no redirect

Removed campaign is explained clearly; no unsuitable replacement.

For permanently removed content without a replacement, 404 may also be appropriate. Permanent moves can use 308 as well as 301. Google explains the distinction from temporary redirects. Do not send every removed page to the home page indiscriminately. That does not answer the original question.

Check the entire journey

During implementation, request every recorded old address and check its response code, redirect destination and final content. A redirect to an error page is not a successful move. Avoid loops and unnecessary intermediate stops. Also check important variants, such as different capitalisation or relevant URL parameters, if they were previously used.

Update internal links, the sitemap and canonical references to the intended new addresses. Remove only test restrictions no longer needed for the public launch; look particularly for accidentally retained noindex. Private areas retain their access controls.

Add the actual result, check date, owner and outstanding correction to the list. Revisit important entry points and errors after launch. Correct redirects help the transition but do not guarantee unchanged visitor numbers or search positions.

Sources

Written by

  • Anna NeumannEditor for Content and Digital MarketingAnna Neumann plans and writes content on digital marketing at ASES. Her topics include search engine optimisation, content strategy and web analytics, with a focus on evaluating marketing activities and their results in a transparent way.

Follow ASES

Read more

All articles

Online Marketing with ASES

SEO, GEO, ads and analytics