One Host URL: www, HTTPS, and the Trailing Slash

www vs non-www, HTTPS, and the trailing slash are one decision: which string is the only live host URL. Four 200s of the same post is not “flexibility.” It is four votes.

This page is Pick-Then-Redirect. It is not mixed content cleanup (http files on an https page). It is not moving a blog to a new domain (new brand, new registrable name). It is not redirect chains (extra hops after you already picked). It is not canonical vs 301 (hint versus move on a leftover path). This is host-level consistency.

Pick one live pattern—HTTPS plus either www or the apex, plus the slash style your CMS already uses—and 301 every other combination to that keeper. Google prefers HTTPS over HTTP. Google does not say www beats apex, or slash beats no-slash.

Official: Consolidate duplicate URLs, Redirects and Google Search, URL structure.

Table of contents

1. Pick-Then-Redirect
2. HTTPS is the only preference Google states here
3. www or apex: flip the coin once
4. Trailing slash: inspect the CMS, do not invent a rule
5. Align sitemap, links, and Search Console
6. Mix-ups this page is not
7. FAQ

Pick-Then-Redirect

Write the keeper on a sticky note. Then make every other spelling a 301, not a second homepage.

        PICK-THEN-REDIRECT
  1. PICK     → https://www.example.com  OR  https://example.com
  2. SLASH    → copy the final path your CMS already 200s
  3. REDIRECT → http, other host, other slash → keeper in ONE hop
  4. ALIGN    → sitemap + internal links + Search Console property
  5. INSPECT  → Google-selected should match the sticky note

If both hosts still return 200, a self-canonical will not reliably replace the redirect. Host aliases are a move, not a hint.

HTTPS is the only preference Google states here

Consolidate duplicate URLs says Google prefers HTTPS over HTTP when it picks a canonical among duplicates. Sitemap-listed URLs are suggested canonicals. rel=canonical remains a hint.

That is the entire official “which protocol” answer. No invented ranking percentage. No “HTTPS is 70% of the cluster.”

So the keeper starts with https://. HTTP versions 301 to that keeper. If images still load on http://, that is mixed content—the padlock sweep—not this host map.

A certificate on the apex only, or on www only, can force the host choice. Do not pick www in a blog post and then serve a cert that only matches the bare domain. The browser error will educate you faster than Search Console.

www or apex: flip the coin once

People ask which is “better for SEO.” Google does not publish a winner. Cookies, CDN CNAME habits, and “it looks shorter” are product reasons, not ranking law.

Practical tie-breakers I actually use:

• If the site has been live on one host for years, keep that host and redirect the other. You are not late to a secret www bonus.
• If email and the CDN already assume www, stay on www. Fighting DNS for a shorter address is a weekend you will not get back.
• If you are launching this week and nothing is indexed, pick the host your registrar’s HTTPS docs already complete in one click.

Then 301 the loser. http://www and http://apex should not hop through each other. Each alias goes straight to https:// + chosen host + chosen slash.

URL structure is about readable, consistent paths. It is not a bake-off between www and the apex.

Trailing slash: inspect the CMS, do not invent a rule

Open a post in a private window. Copy the address bar after the spinner stops. That string is the slash policy.

WordPress pretty permalinks often keep a trailing slash on posts. Some static hosts and Next-style apps omit it. Both can be fine. The bug is serving both as 200.

Do not write a blog comment that “Google prefers the slash.” They do not say that. Do not flip the CMS default to match a forum screenshot.

If /blog/slug 301s to /blog/slug/, inspect the slashed URL. If you inspect the unsashed string, Google-selected canonical may already show the slashed keeper. That is alignment, not a bug.

Pagination and archives have their own slash-and-page rules on pagination SEO. Do not “fix” page 2 by stripping slashes.

Align sitemap, links, and Search Console

A redirect without a sitemap update leaves Google a suggested canonical that still names the alias. List only the keeper in the XML sitemap.

Change the home-page menu, the logo href, and the leftover http links in old posts. One leftover http://www in the footer is a small vote, but it is a sloppy one.

Verify the Search Console property that matches the keeper. If you only verified http://example.com, add the HTTPS + chosen-host property. Inspection lives there.

After the 301s settle, inspect the keeper. User-declared and Google-selected should name that same HTTPS URL. The click-path is URL Inspection. If they still disagree, align—do not request the HTTP leftover.

Syndication on another company’s domain is not a host-pattern job. That is cross-domain canonicals.

If pages never enter the index at all, start with why Google isn’t indexing your pages. A www mix can contribute; it is rarely the only block.

Mix-ups this page is not

Broken padlock. HTTPS page, http:// image. Different owner.

New .com. oldname.com → newname.com is a migration. You need a URL map, not only an apex redirect.

A→B→C hops. You already picked the keeper, then stacked hosting redirects. Collapse to one hop on the chains post.

Two articles, one query. Host cleanup will not merge intents. That is cannibalization, not www.

robots.txt Disallow on the keeper. The file cannot “prefer” www. If you blocked the HTTPS host by mistake, open robots.txt for small blogs.

FAQ

Should I use www or the apex (non-www) domain?

Pick one. Redirect the other. There is no official “www ranks more” note to chase.

Does Google prefer a trailing slash or no trailing slash?

No published winner. Use the final URL your CMS already serves. Redirect the other shape.

Why pick one host URL?

So http/https, www/apex, and slash variants are not four live copies. Google prefers HTTPS when it consolidates. You still have to pick the host and the slash.

Is this mixed-content cleanup?

No. Mixed content is insecure files on a secure page. This page is which hostname is the keeper.

Is this a domain move to a new brand?

No. New registrable domain = migration owner. www vs apex on the same name stays here.

How do I handle http and https together?

301 HTTP to the HTTPS keeper in one hop, then fold www and slash onto that same keeper.

What if I create a redirect chain?

Point every alias at the final URL. Do not daisy-chain http→www→https→slash. The chains post is the collapse walkthrough.

Where is official help?

Consolidate duplicate URLs, Redirects, URL structure.

Write the keeper URL at the top of your host panel this week. 301 the rest in one hop. Inspect the keeper once. Then stop debating www as if it were a ranking feature.