HTTPS Redirect Checker

An HTTPS redirect checker tests the four common variants of a site address (http, https, www and non-www) and shows where each one ends up. They should all resolve to a single secure version with one redirect.

This tool fetches the address you enter once, from our server, and reports what a crawler would receive. The URL is not stored; only a short-lived rate-limit counter is kept. Results show the page at the moment of the check and can differ from what a logged-in browser or a bot with different headers sees.

How to read the result and act on it

Check all four variants: http, https, www and non-www. Ideally three of them redirect with a single 301 to the one preferred version, and that version returns 200. If any variant answers 200 on its own, search engines may see duplicate sites, so add a redirect. If a variant takes two or more hops, such as http non-www to http www to https www, combine the rules so it goes directly to the final address. Make sure the canonical tag, internal links, sitemap and structured data all use the same preferred version. After fixing, retest and also confirm the SSL certificate covers both the www and non-www hostnames.

Common mistakes to avoid

A frequent mistake is redirecting HTTP to HTTPS but leaving the www and non-www versions both reachable, which splits signals and complicates reporting. Another is a redirect loop caused by a CDN or load balancer that terminates HTTPS and passes plain HTTP to the origin, which then redirects again. Mixed content, where an HTTPS page loads HTTP images or scripts, can still show warnings after a redirect is in place. Forgetting to update the site URL in the CMS settings leaves old links in the markup. Using 302 for a permanent change is also common. Cover subdomains and the certificate renewal, since an expired certificate breaks the secure version.

Should I redirect HTTP to HTTPS?

Yes, with a 301, so users and search engines always land on the secure version.

Does www vs non-www matter?

Pick one and redirect the other to it so signals are not split.

How do I redirect HTTP to HTTPS?

Install a valid SSL certificate, then add a site-wide 301 redirect from http to https at the server, CDN or hosting level. Update the CMS site address, internal links and canonicals, then test every variant of the domain.

Should I choose www or non-www for SEO?

Either works. Pick one, redirect the other to it with a 301 and keep it consistent in links, canonicals and sitemaps. Changing later is possible but needs careful redirects, so choose based on your setup and stick with it.

• Redirect Checker: Trace every redirect hop from a URL to its final destination, with status codes.
• Security Headers Checker: Check for HSTS, Content-Security-Policy, X-Content-Type-Options, frame and referrer headers.
• .htaccess Redirect Generator: Generate Apache 301 and 302 redirect rules, including HTTPS and www forcing.

Browse all 41 free technical seo tools, or see the full free SEO toolbox. If you would rather have this handled for you, take a look at our technical SEO services and the results from real projects.