One https address

Does every version of the address lead to one https site, quickly?

Access · 5 of 100 in Access · yours to do · host

What we look for

Your site can be typed several ways: with or without www, with http:// or https://. We score only what can cost a reader the page: https:// works and http:// reaches it; www and the bare domain end at the same host, with any redirect code; and every chain ends, within five redirects, the most crawlers follow.

All good scores 1. One problem scores 0.5, two or more 0.25. If the home page ends up on plain http://, the score is 0. If the other form of the address (www or bare) doesn’t exist at all, that’s fine; if it exists and fails, that’s a problem.

We ask over HTTP/2, as browsers and AI fetchers do. If your address refuses or challenges HTTP/2 and we get the page by asking once more over HTTP/1.1, the address fails for real clients, and that is a problem, said in plain words: “Browsers and AI fetchers are challenged at https://example.com/ (HTTP/2 answers 403); an older client gets through.” The scan goes on with the page the older client got.

A redirect that says the move is temporary (a 302, 303, or 307), and how many hops a chain takes, are said in the report, never scored: a temporary redirect to the right place loses no reader, and many hosts set one you can’t change. A 301 or 308 says the move is for good, if your host lets you set it.

When your home page redirects, the sentence says where it ends and in how many hops, and names a temporary code (a 302 or 307) on the way, which costs nothing: a 301 says the move is permanent.

Why it matters

Each version of an address that answers separately looks, to a crawler, like a different site. The links and attention your site earns get split between them, and an assistant may cite whichever one it found first.

Long redirect chains cost time and requests, and impatient fetchers give up partway. A site still on plain http looks neglected and is treated as less trustworthy.

How to pass

  1. Pick one address, for example https://example.com.
  2. Redirect every other form to it in a single hop, with a permanent (301) redirect: http://example.com, http://www.example.com, and https://www.example.com.
  3. On nginx, that looks like this:
    server {
        listen 80;
        listen 443 ssl;
        server_name www.example.com;
        return 301 https://example.com$request_uri;
    }
    
    server {
        listen 80;
        server_name example.com;
        return 301 https://example.com$request_uri;
    }
  4. On a hosted platform, set the primary domain in its domain settings and turn on “force https”.

Last changed .

The whole rubric