Hreflang URL protocol mismatch — the fix
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.
Where this fits: indexability in SEO
Indexability is whether a crawled page is allowed into the search index at all. A page can be perfectly reachable and still tell Google to ignore it — through a noindex directive, a conflicting canonical, or an X-Robots-Tag header set by the server. These directives are absolute: one stray meta tag removes a page from search entirely. Indexability issues are the most binary in SEO — the page either can rank or it cannot — which is why they sit at the top of every serious audit.
Why hreflang url protocol mismatch hurts your rankings
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.
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.
How to fix it
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.
Indexability best practices
- Audit noindex directives after every deploy — one templating mistake can deindex a section overnight.
- Give every indexable page exactly one self-referencing canonical URL.
- Never mix signals: a page should not be canonicalised away AND noindexed AND in the sitemap.
- Use hreflang pairs that reciprocate; a one-way hreflang is ignored.
- Check the HTTP layer too — X-Robots-Tag headers override what you see in the HTML.
The full library: SEO best practices, by category.
Frequently asked questions
What does "Hreflang URL protocol mismatch" mean?
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.
Why does hreflang url protocol mismatch matter for SEO?
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.
How do I fix hreflang url protocol mismatch?
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.
How serious is this issue?
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.
How do I find every page affected by this on my site?
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.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by hreflang url protocol mismatch, and hands you a ready-made fix task.
Check my site free