Start with the visitor’s original need
A redirect sends someone from one address to another. It can help when a page moves, a useful service is renamed or two overlapping pages are combined. The destination should make sense to the person who followed the old link. Sending every old URL to the homepage can leave visitors searching again and obscure which content actually replaced it.
A redirect is not always the right answer. If a service has ended and there is no close replacement, discuss the appropriate response with the person maintaining the site rather than inventing an unrelated destination. Where the service continues, retain or improve the existing URL if changing it would add disruption without a clear benefit.
Inventory addresses before the change
Collect the old URLs from your site structure, sitemap, analytics or Search Console access where available, and ask colleagues about pages used in proposals, emails and printed material. Include important downloads and campaign links where practical. Record the business purpose of each page, not only its address.
Mark whether the content will stay, move, combine or retire. A page with few recorded visits may still be linked from a customer’s document or answer a valuable question. Use available evidence together with the team’s knowledge; no single data source contains every bookmark or external link.
Create an old-to-new mapping
For every changed address, record the exact old URL, the intended final destination, the reason for the change and the person responsible. Match a former service page to the closest relevant current page. Where no equivalent exists, document the decision and communicate clearly to visitors rather than hiding the gap with an unrelated redirect.
Consider important query parameters or documents if your site uses them, and confirm the correct domain, protocol and path. A map that uses the final address is easier to implement and review than a series of informal messages. Keep a copy of the approved list alongside the launch plan.
Redirect planning
- InventoryFind useful old addresses
- MapChoose relevant final pages
- ImplementUse the appropriate redirect
- TestCheck old and new journeys
Choose the appropriate redirect
For a permanent move, a server-side permanent redirect such as HTTP 301 or 308 is commonly appropriate when supported by the platform. Temporary changes may need a different response. Google documents how it treats different redirect types, but the correct implementation depends on the hosting stack and what actually happened to the content.
Ask the developer whether the host, server or content system controls the redirect and avoid overlapping rules in several places. Where server-level redirects are unavailable, discuss the limitations of alternatives. A redirect cannot preserve a page’s usefulness if the destination has unrelated or missing information.
Test the complete route
Before launch where possible, test a sample of mappings and all particularly important addresses. After the change, open each old URL and confirm it reaches the correct final page over the intended secure domain. Check that the destination responds successfully and that there are no loops or unnecessary chains through multiple intermediate addresses.
Update internal navigation, links in content and sitemap entries to use the final address directly. Redirects help people arriving from outside the site; direct links make your own site easier to maintain. Check forms, images and downloads on the destination, and ask the owner to confirm that the current offer is described correctly.
An illustrative mapping
Imagine a consultancy combines separate pages for two closely related advisory packages into a single current service page. It records both former URLs and maps each to the new page, which explains what is included and any important differences. The team updates navigation and checks each old address after launch.
An unrelated retired event page has no equivalent. Instead of automatically redirecting it to the service homepage, the team discusses a suitable response and whether a genuinely relevant event archive exists. This is an illustrative example, not a report of a real client or a guarantee about search performance.
Avoid redirect chains and loops
A chain occurs when an old address redirects to another address that redirects again. A loop returns a visitor to an earlier address and can prevent the page from loading. Map each old route to the final relevant destination where the host allows, and check protocol, domain and slash rules together so they do not conflict.
If a tool reports a chain, confirm the final destination before editing. Some platform-level rules may already handle the domain or secure connection. Document who controls each rule so a well-meant content-system change does not clash with server configuration.
Keep the mapping useful to the team
Add columns for the old address, new address, content decision, owner, implementation and test result. A clear reason such as “service renamed” or “two guides combined” helps future editors understand why the rule exists. Store the record with the website handover materials and avoid placing credentials in it.
Review reports and customer feedback after the change, especially for routes used in proposals or offline print. If a destination later changes again, update the mapping to the newest relevant page and retest the old route. Do not remove a redirect merely because the team no longer uses the old address internally.
When several old pages are combined, read the final destination from the perspective of a person arriving from each old link. The replacement should explain any meaningful change in scope and give a usable next step. If one old page discussed a service that has stopped, the destination must not imply it is still available. Keep the content owner involved so technical continuity does not hide a change that customers need to understand.
Monitor and maintain
After launch, check a sample of old URLs again, review available error reports and respond to customer reports of missing information. Keep redirects in place as long as they are useful and practical, particularly when the old address may be bookmarked or linked elsewhere. Agree who can change the rules and how those changes are recorded.
Before closing the task, verify that each destination serves the original reader’s purpose, each important old route works as intended and the new page is linked internally. Document exceptions and update the map after later changes. A redirect plan supports continuity; it cannot guarantee stable search positions after a move.
