Hreflang URL protocol mismatch: what it is, why it matters, and how to fix it

Hreflang annotations reference URLs using HTTP while the page is served over HTTPS, or vice versa. Protocol mismatches cause Google to treat the hreflang as pointing to a different page.

Google treats HTTP and HTTPS versions as different URLs. If your page is on HTTPS but hreflang tags point to HTTP versions, Google may not associate them correctly, breaking international targeting. This commonly happens when hreflang tags are generated before an HTTPS migration and not updated afterward.

Ensure all hreflang URLs use the same protocol (HTTPS) as the pages they are implemented on. Update any remaining HTTP references to HTTPS after migration.

This is a medium-severity issue: individually modest, but it compounds — dozens of medium issues across hundreds of pages add up to a real quality deficit in how search engines assess the site. It belongs to the indexability family of checks.

Run a free Dr Urls audit: it crawls your site, detects hreflang url protocol mismatch on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.