For a site migration, use 301 redirects for every URL that changes or is removed, and use canonical tags only as a supporting signal for near-duplicate content that remains accessible. Redirects tell search engines and users that a page has permanently moved, passing most of its ranking signals to the new URL, while canonicals merely indicate a preferred version among duplicates that all still exist. During a migration, if you rely on canonicals instead of redirects, old URLs stay crawlable, dilute signals, and risk being indexed instead of your new pages.
What a Site Migration Actually Changes
A site migration is any significant change to your website’s structure, URLs, domain, or platform. Common examples include:
- Moving from HTTP to HTTPS
- Changing domain names (e.g., example.com to example.net)
- Restructuring folders or file names (e.g., /products/item.php to /shop/product-name)
- Switching CMS or e-commerce platforms that alter URL patterns
- Merging multiple sites into one
Each of these changes creates a set of old URLs that no longer exist or have moved. The core question is how to tell search engines where the content now lives without losing the authority and traffic built up on the old URLs.
How 301 Redirects Work
A 301 redirect is an HTTP response status code that tells the browser and search engines that a requested resource has been permanently moved to a new location. When a crawler or user hits the old URL, the server responds with “301 Moved Permanently” and the new URL. Search engines then transfer most of the ranking signals—link equity, trust, and historical performance—from the old URL to the new one.
Key characteristics of 301s:
- They are the strongest signal that a page has moved.
- They consolidate signals from multiple old URLs into one new URL.
- They improve user experience by automatically taking visitors to the correct page.
- They remove the old URL from the index over time, replacing it with the new one.
For a migration, every old URL that has a meaningful equivalent on the new site should get a 301. Even if the new page is slightly different in content, redirecting to the closest match is better than returning a 404, because it preserves some value and guides users to relevant content.
How Canonical Tags Work
A canonical tag (rel=”canonical”) is an HTML element placed in the <head> of a page that tells search engines which URL is the preferred version when multiple URLs contain the same or very similar content. For example, if you have both example.com/page and example.com/page?utm_source=newsletter, the canonical on the parameter URL points to the clean version.
Canonicals are a hint, not a directive. Search engines may ignore them if they detect conflicting signals or if the duplicate pages are too different. They do not consolidate link equity the way redirects do; they simply help search engines choose which URL to index and rank.
Canonicals are useful for:
- Tracking parameters (UTM codes, session IDs)
- Printer-friendly versions of pages
- WWW vs non-WWW and HTTP vs HTTPS when both serve content
- Syndicated content that appears on other sites
But during a migration, canonicals are not a substitute for redirects because the old URLs still exist and can be crawled. If you put a canonical on the old URL pointing to the new one, search engines may eventually drop the old URL, but they will not transfer the full ranking power, and users hitting the old URL will still see the old page (or a 404 if it’s gone).
Why Redirects Are Essential in Migration
During a migration, the primary goal is to move your site’s search presence from the old URLs to the new ones without losing rankings. Redirects achieve this directly:
- They pass link equity: Backlinks pointing to old URLs are effectively transferred to the new URLs.
- They prevent 404 errors: Users and crawlers don’t hit dead ends.
- They update the index: Search engines replace old URLs with new ones in search results.
- They are permanent: Once in place, they require no ongoing maintenance.
If you only use canonicals, old URLs remain live and may compete with new URLs for ranking. Even if the canonical is respected, the old URL might still be indexed in some cases, causing duplicate content issues and splitting signals.
When Canonicals Can Play a Supporting Role
There are a few migration scenarios where canonicals are appropriate alongside redirects:
- If you have multiple URLs that serve the same content intentionally (e.g., a mobile version at m.example.com), you should redirect the mobile subdomain to the main domain or use canonical tags to point to the desktop version. In most cases, redirects are still preferred.
- If you have tracking parameters on internal links, you can use canonicals to consolidate them to the clean URL. This is not a migration issue per se, but it helps maintain consistency.
- If you are moving a subset of pages and leaving the rest, you might use canonicals on the moved pages to point to the new location, but only if the old pages are still accessible and you want to avoid 404s. However, this is risky because search engines may not pick up the change quickly, and users will still see old content.
In practice, the safest approach is to use 301s for all moved pages and reserve canonicals for non-migration duplicate management.
Common Problems and How to Avoid Them
Migrations often fail due to preventable mistakes. Here are the most common issues and how to handle them:
- Redirect chains: Ensure each old URL redirects directly to the final new URL, not through an intermediate redirect. Chains slow down crawling and can lose some equity.
- Redirect loops: Test all redirects to make sure they don’t point back to each other.
- Missing redirects: Create a complete map of old URLs to new URLs before going live. Any old URL that doesn’t have a redirect should return a 404, but that should be a deliberate choice, not an oversight.
- Mixed signals: Don’t combine a 301 redirect with a canonical tag on the same page. The redirect already tells search engines the final URL; adding a canonical is redundant and can confuse.
- Using 302 instead of 301: A 302 is temporary and does not pass link equity. Use 301 for permanent moves.
- Forgetting to update internal links: Even with redirects, you should update internal links to point directly to new URLs to reduce redirect chains and improve crawl efficiency.
How to Implement Redirects Correctly
Implementing redirects depends on your server or CMS. Here are the general steps:
- Create a spreadsheet of all old URLs and their corresponding new URLs. If a page has no direct equivalent, map it to the closest relevant page or decide to 404 it.
- Implement the redirects at the server level (e.g., .htaccess for Apache, nginx config) or via your CMS’s redirect plugin. For large sites, use regex patterns to handle groups of URLs.
- Test each redirect using a tool like Screaming Frog or a simple browser check. Verify that the old URL returns a 301 and lands on the correct new URL.
- Monitor search console for crawl errors and indexation issues after going live.
- Keep the redirects in place for at least a year, ideally indefinitely, because backlinks and bookmarks may still point to old URLs.
Frequently Asked Questions
Can I use canonical tags instead of redirects for a domain change?
No. A domain change requires 301 redirects from every old URL to the new domain. Canonicals are not sufficient because they don’t tell users or crawlers that the page has moved; they only suggest a preferred version among live duplicates. Without redirects, the old domain stays in the index and loses the chance to pass authority.
What happens if I forget to redirect some old URLs?
Those URLs will return 404 errors, which can hurt user experience and waste crawl budget. Over time, search engines will drop them from the index, but any backlinks pointing to them will lose value. It’s best to redirect as many as possible, even to a slightly less relevant page, to preserve some equity.
Should I use redirects or canonicals for HTTP to HTTPS migration?
Use 301 redirects from every HTTP URL to the HTTPS equivalent. Canonicals can be a secondary measure, but redirects are essential to ensure users and search engines are taken to the secure version. Many sites also use HSTS to enforce HTTPS, but redirects are the baseline.
How long should I keep 301 redirects after a migration?
Keep them indefinitely if possible. While search engines will eventually discover the new URLs, backlinks and external references may continue to point to old URLs for years. Removing redirects too soon can cause 404s and lose equity. There’s no downside to keeping them.
Can a canonical tag on the old URL help pass link equity?
No. Canonical tags do not pass link equity. They only indicate which URL should be indexed. If you want to consolidate signals from multiple URLs, you must use 301 redirects. Canonicals can help consolidate duplicate pages that you want to keep accessible, but they don’t transfer authority.
What about using JavaScript redirects or meta refresh?
These are not recommended for migrations. JavaScript redirects are slow and may not be executed by all crawlers. Meta refresh is deprecated and often treated as a soft 404. Always use server-side 301 redirects for reliability and speed.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Arctic Sea Ice Forecasts Disagree: What to Do
- MySQL Workbench to VPS: SSH Tunnel Setup
- Bluesky Beginners Guide: How to Get Started5.00 min/km
- LG V20 Won’t Turn On? Fixed
- Snagit vs Camtasia: Which One Do You Need?
- Scale a Small Business Without Losing Culture