Updating canonical tags during site migration involves remapping every tag on your site to point to the corresponding destination URL on your new domain or platform. When you change domains or switch CMS environments, search engines must reconcile the link between the old legacy paths and the new live pages. By providing clear, consistent canonical signals, you prevent indexation errors and help Google transfer ranking authority from your historical site structure to the new one.
Why are canonical tags critical during a migration?
Canonical tags serve as a primary signal for search engines to determine which URL is the preferred version of a page. During a migration, this signal becomes even more vital because your site content exists in two places simultaneously: the staging or legacy environment and the new production site. If you fail to update these tags, you risk split indexing, where Googlebot incorrectly assigns authority to the wrong version or fails to index the new content entirely.
Consider a scenario where a retail site moves from a custom legacy platform to a modern CMS like Shopify or BigCommerce. If the canonical tags continue to reference the old file structure, Googlebot will see conflicting signals. The search engine must decide whether to trust the redirect or the canonical declaration, which often delays the indexing of the new content and can lead to ranking drops.
Maintaining search equity is a technical task. When you change domains, your canonical tags must point to the new, absolute URL structure. This ensures that the consolidation of signals—from old to new—happens efficiently without requiring the search engine to guess which version of the content you intend to show to the user.
How do you map canonical tags during a domain change?
The mapping process requires a complete inventory of your current URLs. You must verify that the canonical link tag on the new domain points to itself and not to the legacy URL. This prevents circular references that confuse the crawler. You should document these changes in a spreadsheet to ensure every page has a clear destination.
- Audit all existing canonical tags across the current site to ensure they are correct.
- Create a mapping document linking old URL paths to their new destination counterparts.
- Update the canonical tag dynamically on the new platform to reflect the destination domain.
- Verify that no canonical tags point to staging or development environments.
When migrating, verify that your absolute URLs include the correct protocol, such as HTTPS. If your new site uses HTTPS, every canonical tag should reflect this change immediately upon launch. Using relative URLs in canonical tags often leads to errors if the crawler interprets the base domain incorrectly.
For large sites with thousands of URLs, automate the generation of these tags based on your database mapping. Do not rely on manual updates, as the risk of human error is high. Use your site map and crawl data to build a reference table that the new CMS can use to inject the correct tag into the document head automatically.
How Alien Road applies this during migrations
At Alien Road, we approach migrations by treating canonical signals as part of a larger technical roadmap. For a typical client, we begin by auditing the existing site’s indexation to identify which pages are currently canonicalized. During the transition phase, we ensure that the new platform configuration automatically updates the canonical tag to the final production URL. This avoids the manual error of leaving old references in the metadata of the new pages.
In a typical engagement, our team audits the staging environment before the public launch. We verify that canonical tags point to the production URL, not the temporary staging URL. If a site is indexed with staging-domain canonicals, it can cause severe ranking issues once the site goes live. We also check for ‘noindex’ directives that might conflict with your canonical settings.
What common mistakes should you avoid?
Many teams struggle with inconsistent signals during the transition. A common error is keeping the old domain’s canonical tags active while the site is still being indexed on a temporary staging domain. This creates a conflict that forces Google to ignore your canonical tags entirely.
- Avoid relative paths in canonical tags; always use absolute URLs including the protocol.
- Ensure the canonical tag matches the 301 redirect target for every page.
- Remove any canonical tags that point to ‘noindex’ pages.
- Monitor Google Search Console for ‘Duplicate without user-selected canonical’ errors.
Another error involves pointing canonical tags to a URL that does not exist or that results in a 404 error. This essentially tells the search engine that the canonical version of your page is a dead link, which can lead to the page being dropped from the index. Always validate that your redirect targets match your canonical declarations.
Avoid using canonical tags to replace 301 redirects. A canonical tag is a hint for search engines, not a replacement for a proper HTTP status code. If you move a page, you must use a 301 redirect to send the user and the search engine to the new location. The canonical tag is only there to reinforce which URL is the master version.
How to verify your implementation
Verification requires checking both the HTTP header and the HTML source of your pages. You can use the URL Inspection Tool within Google Search Console to see exactly which page Googlebot considers the canonical version. This provides a direct look into how the system interprets your current settings.
We recommend checking a sample of pages across different site sections—such as product pages, category pages, and blog posts—to ensure the tagging logic is applied correctly site-wide. If your site uses a dynamic rendering process, inspect the source code as it appears to a search engine, rather than just the rendered page in a browser.
A structured approach is the most reliable way to maintain search visibility.
Google Search Central
Where to start this week
Begin by pulling a crawl report of your current site to identify all canonical tags. Export this list into a spreadsheet and prepare a matching set of new URLs for your target domain. By organizing this data before the migration code is pushed, you ensure that your technical SEO foundation remains solid from the first day of the move. If you have a large site, focus on your top 20 percent of traffic-driving pages first to minimize the risk to your revenue.
Set up a test environment where you can review these tags before deployment. Use a crawler tool to simulate a search engine visit to your staging site. Look for any instances where the canonical tag points back to the old domain. Fixing these issues in the staging phase is far easier than trying to correct them after your new site has been indexed by Google.