Non-Standard HTTPS Configurations and the Risks They Create
Key takeawayHTTPS problems fall into two groups: certificate issues (expiry, domain mismatch, incomplete chains) and mixed-content / redirect-chain issues. Search engines give no bonus just for using HTTPS, but a misconfigured HTTPS setup prevents normal crawling.
When this applies
- Sites that discover problems only after a certificate expires
- Sites where different subdomains have different certificate states
- Sites mixing http resources so browsers block content
- Sites with multi-hop redirects from http to https
| Issue type | Symptom | Severity | How to fix |
|---|---|---|---|
| Expired certificate | Full-site browser warnings | High | Auto-renewal plus expiry monitoring |
| Certificate domain mismatch | Errors on specific subdomains | High | Issue certificates covering all domains |
| Incomplete certificate chain | Errors on some devices | High | Deploy the fullchain |
| Mixed content | Resources blocked by the browser | Medium | Unify on https or protocol-relative paths |
| Multi-hop http→https redirects | Signals decay per hop | Medium | One-hop redirect |
| Some pages still on http | Duplicate content and split signals | Medium | Force site-wide redirects |
| Misconfigured HSTS | Hard to roll back | Medium | Confirm max-age before enabling |
Step-by-step diagnosis
- Test both http and https with curl, confirming the redirect behavior and the number of hops.
- Use openssl to inspect the actual certificate's CN, SAN list, and validity, confirming coverage of all public domains.
- Verify the certificate chain on multiple devices and regions (some older devices are sensitive to incomplete chains).
- Check page source and runtime requests for any remaining http:// resource references.
- Replace http→https redirects with a single server-side 301, avoiding intermediate pages or multiple hops.
- Configure auto-renewal for all public domains and add an alert ahead of certificate expiry.
- Confirm in GSC's HTTPS report that there are no "non-secure pages" records.
Common mistakes
- Assuming HTTPS automatically boosts rankings — it is a baseline requirement, not an advantage.
- Deploying certificates only on the main domain while ignoring other subdomains.
- Deploying a cert instead of the fullchain — some devices report an incomplete chain.
- Using meta refresh for http→https redirects.
- Fixing mixed content only for images in the page while ignoring http resources injected dynamically by JS.
- No certificate expiry monitoring — one expiry takes the entire site offline.
FAQ
Does HTTPS affect rankings?
Not as a direct bonus, but missing or misconfigured HTTPS causes crawl failures and reduced trust, indirectly affecting indexing and rankings.
Do subdomains need separate certificates?
Yes, unless you use a wildcard or SAN certificate covering all subdomains.
What are the symptoms of an incomplete certificate chain?
Some devices (older Android, embedded systems) report certificate errors while desktop browsers work fine — which is why multi-device verification is mandatory.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
Core Web Vitals: The LCP / CLS / INP Optimization ManualHow Overseas Hosting Latency and Packet Loss Really Affect IndexingWhen CDN Rules Block Crawlers: A Troubleshooting GuideUncompressed and Non-Lazy-Loaded Images: How They Hurt Indexing and PerformanceWhere Internal Link Equity Leaks Out: The Common PointsNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.