How to Check Canonicals After a Domain Change
Website intelligenceHow to Check Canonicals After a Domain Change
A domain migration can leave old canonical values in a cached configuration or shared template. If the public page redirects to the new domain but its canonical still points to the old host, the site is sending mixed signals that need review.
Confirm the final destination first
Open the old and new URLs and record where each one ends. Check HTTPS, hostname, path and any trailing slash behavior so you know which address should represent the page.
The correct canonical should match the preferred public version after the move. Do not assume that a site-wide search-and-replace was complete without testing actual pages.
Read the canonical reported by SiteBoost
Run SiteBoost on representative new-domain pages and compare the reported canonical with the final URL. If the old hostname remains, inspect the page template, SEO plugin or cached configuration that produces it.
Check multiple page types because the homepage, articles and service pages may use different metadata logic.
- Compare old URL, final URL and canonical.
- Check the HTTPS and hostname versions.
- Inspect templates and global SEO settings.
- Test representative URLs after deployment.
Rescan after the migration fix
Publish the canonical update and run the same scans again. Confirm that internal links and sitemap entries also support the intended new domain.
Use a broader crawl and search-console review for site-wide migration validation; a few page scans cannot prove every redirect and indexed URL is correct.
