What Are URL Redirects and Why Are They Important?
A URL redirect sends a visitor or search engine from an old web address to a more appropriate destination.
Part of our guide: How to Replace an Existing Website: A Step-by-Step Guide
A URL redirect automatically sends a visitor or search engine from one web address to another. Redirects are important when pages move, merge or disappear because old addresses may still appear in search results, bookmarks, emails and links from other websites.
A good redirect leads to the closest relevant replacement. It preserves the visitor’s intent rather than sending every old page to the homepage.
What a redirect does
When a browser requests an old URL, the server returns a redirect response with the new location. The browser then requests that destination.
Search engines can follow the response and update their understanding over time. The status code communicates whether the move is intended to be permanent or temporary.
Redirects happen before the visitor sees page content. They are different from a link that requires somebody to choose the next page.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
Use the redirect map worksheet to record old URLs, relevant destinations and verification results before implementing rules.
Permanent redirects
A 301 or 308 response normally indicates a lasting move. Use one when a page has a permanent new address, two pages are consolidated or a canonical hostname changes.
The destination should match the old page’s purpose. A redirected product should lead to its successor or relevant category, not an unrelated promotion.
Keep important permanent redirects for the long term. Old links and bookmarks can continue producing visits years later.
Temporary redirects
A 302 or 307 response indicates a temporary change. It can suit planned maintenance, short-lived campaign routing or a destination expected to revert.
Do not use temporary redirects automatically because they are easier to configure. Match the response to the real intention.
When a temporary move becomes permanent, update the rule and internal links rather than leaving ambiguity indefinitely.
Why redirects matter to customers
Without a redirect, an old link reaches a not-found page. That can end an enquiry journey, hide important support information or undermine confidence.
A relevant redirect makes site changes almost invisible. The customer reaches the current information without needing to search again.
Still provide a useful 404 page for addresses that have no sensible replacement. Not every missing URL should be redirected.
Why redirects matter for SEO
Search engines have indexed URLs and discovered links pointing to them. A permanent redirect helps consolidate signals at the replacement address.
It does not guarantee unchanged rankings. Content, internal links, technical quality and competition may also change during a redesign.
Google documents redirects as one way to change page URLs. Use server-side redirects where possible.
Preserve URLs when they still work
The best redirect is often no redirect. If a page keeps the same subject and purpose, retain its established URL during the redesign.
Do not change addresses merely to make them shorter or match a new navigation. The visible site structure and URL structure do not need to be identical.
The guide to redesigning without losing Google rankings explains this risk-based approach.
Build a redirect map
Inventory old public URLs and assign each a final outcome: keep, redirect, return not found or intentionally remove. Include documents, common variants and campaign paths.
Record the old URL, destination, reason and owner. Review the mapping with content and service specialists, not only developers.
Create the map during content planning. Waiting until launch week leads to guesses and missing pages.
Choose the closest relevant destination
Match the user’s likely purpose. An old service page can redirect to the renamed equivalent. Two overlapping guides can point to the consolidated article.
Do not redirect a discontinued service to an unrelated offer. A clear explanation or honest 404 may be more useful.
Avoid mass redirects to the homepage. Search systems may treat irrelevant redirects like soft 404 responses, and users lose context.
Avoid chains and loops
A chain sends A to B and then B to C. Each extra step creates delay and another failure point. Update A to point directly to C.
A loop sends URLs back to one another and prevents the page loading. Automated tests should identify loops before launch.
Review legacy rules when destinations change. A clean redirect map should describe the final route, not project history.
Redirect hostname and protocol variants
Choose a preferred HTTPS hostname, such as the root domain or www, and redirect other valid variants consistently.
Avoid multiple hops from HTTP to www and then to HTTPS. Configure a direct route where the platform allows it.
Ensure certificates cover the hostnames that need to receive and redirect requests.
Handle query strings and fragments
Some campaign, filter or integration URLs include query parameters. Decide which values must be preserved and which can be discarded safely.
Fragments identify a location within the destination page and are handled by the browser. If heading IDs change, update important internal links.
Do not write one broad rule that accidentally forwards sensitive or meaningless parameters to every destination.
Test redirects properly
Check the response status and Location header, not only whether a browser eventually shows a page. Confirm one direct hop to a working canonical URL.
Test the full old URL list against the production build or launch environment. Include case, trailing slash and file-extension variants relevant to the old platform.
After launch, crawl the public domain and review server logs or Search Console for unexpected missing pages.
Include files and media in the inventory
Old websites often contain PDFs, price lists, forms and images that receive direct visits. They may not appear in the main navigation, but search results, emails and external websites can still link to them.
Decide whether each useful file will keep its address, move to an updated file or be replaced by an accessible web page. Redirect only when the destination genuinely serves the same need.
Do not redirect an outdated policy or unsafe instruction to a superficially similar document. Removal with a clear explanation may be more responsible.
Separate redirects from canonical links
A redirect changes where a browser goes. A canonical link is a hint in a page that identifies the preferred URL among duplicate or similar versions. They are related but not interchangeable.
If an old address should no longer be used, redirect it. Do not leave duplicate pages available and expect a canonical tag to provide the same customer experience.
Check that the destination page’s canonical points to itself or another deliberately selected public URL, not back to the old address.
Assign ownership for future changes
Redirect rules become part of the website’s infrastructure. Record where they are configured, who can edit them and how changes are tested and deployed.
When a destination later moves, update old rules to point straight to the newest page. This prevents chains accumulating through successive redesigns.
Retain the original migration map with dates and reasons. Future teams can then distinguish valuable historic routes from arbitrary automated requests.
Update internal links
Redirects are a safety net, not a substitute for maintenance. Change navigation, body links, canonicals and sitemaps to point directly to current URLs.
Direct links reduce unnecessary requests and make the site’s intended structure clear. Update external profiles and important campaigns where you control them.
Do not include redirected URLs in the new sitemap.
Platform considerations
Different hosts configure redirects through server rules, platform settings, edge functions or static configuration. The outcome should remain a real HTTP redirect.
JavaScript and meta refresh redirects are less robust and may create delays or accessibility problems. Use them only when a proper server response is unavailable and understand the limitations.
Keep rules under version control or documented in an export where possible.
Monitor after migration
Review 404 reports, redirect errors, search indexing and high-value landing pages. Add a redirect when a genuinely useful old URL was missed.
Do not automatically redirect every bot request. Many requests are malformed or have no historical value.
Retain the map as project documentation and update it when the site changes again.
Common redirect mistakes
The most common are missing valuable URLs, sending everything to the homepage, using temporary status for permanent moves and creating chains.
Other mistakes include redirecting to a page that itself returns an error, forgetting old PDFs and removing rules too soon.
Test with automation and manual review because a valid status code can still point to the wrong subject.
Frequently asked questions
What is a 301 redirect?
It is an HTTP response indicating that a resource has moved permanently to another URL.
How long should redirects remain?
Keep important permanent redirects for the long term, especially when old URLs have links, bookmarks or recurring traffic.
Do redirects preserve rankings?
They help search engines understand a move, but cannot guarantee positions. The replacement page and wider site still matter.
Should every 404 redirect to the homepage?
No. Redirect only when there is a genuinely relevant destination. Otherwise provide a useful not-found page.
Can redirects slow a website?
A direct redirect adds a request but is normally fast. Chains add avoidable delay and should be removed.
Give every old address a deliberate outcome
If a visitor never reaches a final page, use the too-many-redirects diagnosis to find conflicting rules instead of deleting the whole redirect map.
The Page with redirect guide explains why an excluded source address can be expected and how to check that its final destination is correct.
Redirects protect journeys that began before the new website launched. Preserve stable URLs where possible, map changed pages carefully and test every rule against a useful destination.
Afterworks includes URL inventories and redirect testing in website rebuilds so existing links continue helping customers after launch.
