HTTPS Redirect Check
The HTTPS redirect check validates whether your website properly redirects all HTTP traffic to the secure HTTPS version, ensuring all connections are encrypted.
What this check validates
- ✅ HTTP redirects to HTTPS - All insecure traffic is redirected
- ✅ Proper redirect status - Uses 301 (permanent) redirects
- ✅ All pages covered - Redirects work for all website URLs
- ✅ No redirect loops - Avoids infinite redirect chains
- ✅ WWW consistency - Handles www and non-www variants correctly
Why HTTPS Redirects matter
- Security: Ensures all data transmission is encrypted
- User Trust: Prevents browser "Not Secure" warnings
- SEO Benefits: Google considers HTTPS a ranking factor
- Data Protection: Required for GDPR compliance and payment processing
How HTTPS redirects work
When a user visits http://yoursite.com, they should be automatically redirected to https://yoursite.com:
Request: http://example.com/page
Response: 301 Redirect to https://example.com/page
Common Redirect Patterns
# Basic HTTP to HTTPS redirect
http://example.com → https://example.com
# With www subdomain
http://www.example.com → https://www.example.com
http://example.com → https://example.com
# Canonical redirect (removing www)
http://www.example.com → https://example.com
https://www.example.com → https://example.com
Common issues
- No Redirect: HTTP version loads without redirecting to HTTPS
- Wrong Status Code: Using 302 (temporary) instead of 301 (permanent)
- Partial Coverage: Some pages redirect while others don't
- Redirect Chains: Multiple redirects before reaching final HTTPS URL
- Mixed Redirects: Inconsistent handling of www/non-www variants