Skip to content

WWW Redirect Checker

This www redirect checker requests the four addresses your site can be reached at, http:// and https://, with and without www., follows each redirect chain hop by hop and tells you whether they all arrive at the same final URL in one permanent redirect.

Following up to six redirect chains, one hop at a time. This takes a few seconds.

Note

We request http:// and https://, with and without www., on the path you enter (the homepage for a bare domain), as a desktop browser, from our server. Redirects are followed one hop at a time with automatic following switched off, up to ten hops, and every hop's host is checked before it is requested. The final URL is the one most versions reach. For the trailing slash test we take the first plain internal link on the final page, or the page you entered, and request its other form; if that answers 200 we also request the linked form, so a check makes at most six chains of requests. The canonical and HSTS header are read from the final response. Nothing is stored beyond a ten-minute cache of the result.

It flags a version that serves the page itself instead of redirecting (the whole site served twice), plain http:// that never moves to https://, chains of two or more hops, temporary 302 and 307 redirects, versions that end on different URLs and names with no DNS record or the wrong certificate. It also tries one inner page with and without its trailing slash, compares the final page’s canonical tag with the final URL, reads the HSTS header, and writes the one-hop rule for Apache and Nginx with your domain filled in. No sign-up and no email.

Use this tool often? Bookmark this page, so it is one click away next time.

Email me this result

Want a copy for your records or a client? Leave your email and we'll send you this result. It is written by a real person at Crawl Cove, not an automated blast, so it may take a little while to arrive. We'll only use your address to send it, unless you also tick the box below. Privacy policy.

That email address doesn't look right. Please check it and try again.

Something went wrong saving your address. Your result above is unaffected; please try again.

Got it. We'll email your result to you. Nothing else lands in your inbox unless you ticked the tips box.

How to check your www and https redirects

  1. Enter your domain

    Type example.com or paste any page address. A bare domain tests the homepage; a page address tests that page on all four versions and uses it for the trailing slash test.

  2. Read the verdict

    Green means every version reaches the same final URL in one permanent redirect or less. Otherwise the findings list what is wrong, worst first, with the versions each one affects.

  3. Open each chain

    Every version shows its hops with the status code of each, so you can see which rule fires first and where a second hop or a 302 comes from.

  4. Fix it and check again

    Copy the Apache or Nginx rule for your domain, or set the same redirect at your host or CDN, then run the check again. Results are cached for ten minutes.

What this www redirect checker tests

Four addresses: http://example.com, http://www.example.com, https://example.com and https://www.example.com, each followed hop by hop with redirect following switched off, so the status code of every hop is visible. The final URL most of them agree on is taken as the address the site means, and each version is graded against it: pass when it is that address or reaches it in one 301 or 308, a warning for an extra hop or a temporary redirect, and a failure when it serves the page itself, lands somewhere else, ends on an error or cannot be reached at all. A subdomain such as shop.example.com is tested on http:// and https:// only, since a www. version of a subdomain is not expected to exist.

trace any single URL hop by hop

www or non-www: pick one, redirect the other

Search engines treat www.example.com and example.com as two different hosts. If both answer with the page, every URL on the site exists twice, links from other sites are split between the two copies, and Google has to choose which to show. Neither choice ranks better than the other. What matters is that one of them is the real address and the other sends every request to it, path and query string kept, with a permanent redirect. Pick the one your links, sitemap and Search Console already use, so the redirect confirms what search engines already see rather than asking them to change.

HTTP to HTTPS: one permanent redirect, not two

Plain http:// should never answer with the page; it should send visitors to https:// straight away. The commonest fault this check finds is a chain built from two rules that each fix half the address: http://example.com goes to https://example.com, which then goes to https://www.example.com. Both hops are 301s and the site works, but every visitor and crawler starting from the bare http:// address pays for two requests, and a third rule added later makes it worse. Google follows up to ten hops, so this does not stop indexing, but one hop is the standard to aim for. The fix is one rule that checks the scheme and the host together and redirects anything that is not exactly the final address. The one exception is HSTS preload: the preload list asks for http:// to go to https:// on the same name first, so on a site that asks for preload two hops from the bare http:// address are correct, and the result says so.

Redirect normalisation: is it a problem?

301, 302, 307 or 308 for a domain redirect

Moving every visitor from http:// to https://, or from one host to the other, is as permanent as a move gets, so it should use a 301 or a 308. A 302 or 307 says the move is temporary: search engines keep re-checking the old address and are slower to pass its signals to the new one. Temporary codes turn up more often than you would expect, because a redirect written in code usually defaults to 302: PHP’s Location header, Laravel’s redirect() and Express’s res.redirect() all do. The checker lists the code on every hop and flags any 302, 303 or 307 in a chain that ends on the final URL.

Trailing slashes, the canonical tag and HSTS

The same duplicate problem happens one level down: /about and /about/ are two URLs, and a site that answers both with the page has every inner page twice. The checker takes the first internal link on your homepage (or the page you entered), requests the other form and checks that it redirects in one hop or answers 404. Then it reads the canonical tag on the final page: it should name the final URL exactly, because a canonical pointing at the http:// or the other host version contradicts the redirects. Last, it reads the Strict-Transport-Security header on the final https:// response, with its max-age and whether includeSubDomains and preload are set. HSTS makes browsers go to https:// directly on later visits, so the http:// redirect only has to work the first time.

URL consistency: uppercase, slashes and tracking parameters · Canonical pointing to the insecure http version · Missing security headers: HSTS and CSP

How to fix www and https redirects

On Apache, one rewrite rule in .htaccess that redirects when the request is not https or the host is not the final one; the result gives you that rule with your host filled in, and the .htaccess redirect generator writes it alongside page-level redirects. On Nginx, a server block on port 80 for both names and one on port 443 for the other name, each returning 301 to the final address. On a CDN or a managed host, use its redirect or "always use HTTPS" setting, and check that it does not add a hop in front of a rule on the server. Behind Cloudflare or a load balancer, the server can see every request as http://, so a rule that tests the HTTPS variable loops; test the X-Forwarded-Proto header instead. Make sure the certificate covers both names, or the https:// version of the other name fails before it can redirect.

generate the .htaccess or Nginx rules · check the response headers on each hop

Frequently asked questions

Is this www redirect checker free?
Yes. It is free, needs no sign-up and no email. A rate limit stops one visitor sending hundreds of checks a minute, and results are cached for ten minutes.
Should I use www or non-www?
Either is fine for search; neither ranks better. Use the one your links, sitemap and Search Console property already use, and redirect the other to it with a 301. Some prefer www because a www. name can point at a CDN with a CNAME record, which DNS does not allow on a bare domain without a provider workaround.
Do www and non-www count as different sites to Google?
They are different hosts, so each URL on one is a different URL from its twin on the other. Google usually works out that they are duplicates and picks one, but a redirect makes that choice for it and moves the links to the address you chose.
Should http to https be a 301 or a 302?
A 301, or a 308. The move to https is permanent, and a temporary 302 or 307 tells search engines to keep checking the old address.
How many redirects is too many?
Any version that needs more than one hop to reach the final URL is worth fixing, because each hop is another request before the page starts loading. Google follows up to ten, so a two-hop chain still gets indexed, but one hop is the standard.
Why does my site say "too many redirects"?
Two rules are sending the request back and forth. The usual cause is a CDN that talks to the server over http:// while the server redirects every http:// request to https://. Test the X-Forwarded-Proto header in the server rule, or turn on the CDN’s full SSL mode so it connects over https://.
Does the certificate need to cover www?
Yes, if anyone ever types or links the www. version. Without it, https://www.example.com fails with a security warning before the redirect can run. Most hosts and certificate authorities issue one certificate that covers both names.
What is HSTS and do I need it?
Strict-Transport-Security is a response header that tells browsers to use https:// for your site for a set time without asking. It is not required for SEO, but it protects visitors who type the http:// address. Start with a short max-age, raise it to a year once you are sure every subdomain works over https, and only add preload once you are certain.
Does a trailing slash matter?
Only when both forms answer with the page. /about and /about/ are two URLs, so serving both splits links and makes search engines choose. Pick one form, link to it and 301 the other to it, or let the other answer 404.
Can I check every page on my site this way?
Not here: this tests the front door of one site. Crawl Cove checks http:// against https:// at the end of each crawl and follows every redirect on every page it crawls, so chains, 302s and redirects to errors anywhere in the site show up in one report. It has a permanent Free plan.

From one page to your whole site

This checks the front door of one site. Crawl Cove checks http:// against https:// at the end of every crawl and follows every redirect it meets on every page, so a chain or a 302 deep in the site is found as well as the one on the homepage. See trace a single URL with the redirect checker or check every redirect on your site.

Download free