Check HTTPS Redirects and Canonical URLs Together
Website intelligenceCheck HTTPS Redirects and Canonical URLs Together
A website may redirect visitors to HTTPS while its HTML still publishes a canonical using an old HTTP address. Checking only the browser lock icon can miss that mismatch.
Confirm the public URL version
Open the HTTP version and note whether it redirects to the intended HTTPS page. Confirm the hostname and path remain correct and that important query or page details are not lost.
Do not assume every redirect is useful. The final destination should be the version the business intends to maintain, not a chain through several historical hostnames.
Compare the final URL and canonical in SiteBoost
Run SiteBoost against the public HTTPS page and compare the final URL with the canonical value reported in the scan. Both should support the same preferred page version where a self-canonical is appropriate.
If the canonical still uses HTTP, inspect the template or global URL configuration. Review internal links and sitemap entries as part of the same correction.
- Test HTTP to HTTPS behavior.
- Check the final HTTPS URL.
- Review the reported canonical.
- Update internal links and sitemap entries where needed.
Retest after domain configuration changes
After changing redirect or canonical settings, scan the same page again and confirm that the published values now align.
Use a broader URL sample to catch pages that use a different template or old domain configuration.
