Skip to content

Why does my website show a security warning when I add "www"?

If your website works without "www" but shows a security warning with it, customers, search engines and AI assistants may see it too. A 10-second check.

By Ash Harris4 min readWebsite Care
A dark green card with the nimblefish mark and the label Who holds the keys, above the title Why does my website show a security warning when I add "www"? An engraved pufferfish, spines out, fills the rest of the card.

Because your website is only set up to answer at one of its two addresses. Most domains have two: yourbusiness.com and www.yourbusiness.com. If only one was set up properly, the other can show a security warning, a blank page, or nothing at all. The fix is usually one setting.

Try it now

This takes ten seconds. Open your browser and type your web address without the "www." Then type it again with the "www." in front. Do it on your phone, too.

Both should land on your website, ideally the same one, with no warning. If one of them shows "Your connection is not private," "This site can't be reached," or anything else that isn't your home page, that's the problem.

Why you've probably never noticed

You visit your own site the same way every time, usually from a bookmark or by typing it the way you always do. Your customers don't all do that. Some type "www" out of habit. Some click an old link, a business card, an email signature or a directory listing that has it. Those people get the warning, and most of them don't call to tell you. They just leave, and a security warning is a hard first impression to recover from.

What's actually going on

Your domain is a set of settings that tell the internet where things live: your website, your email, and so on. "www" is its own entry in those settings. When a site is set up, someone has to point both versions at the website and make sure each one has a security certificate (the thing behind the padlock in your browser). If one version gets skipped, it either points nowhere or points somewhere without a certificate.

It's an easy step to miss. A site can be built, launched and look perfect while one of its two front doors was never opened.

Where the "www" version still turns up

Even if you've never typed it, the "www" version of your address is probably out in the world already. Look for it in:

  • Printed things: business cards, truck lettering, yard signs, brochures and the QR codes on them. Print lasts for years, and a lot of it was designed with "www" in front because that was the habit.
  • Listings: your Google Business Profile, Yelp, the chamber of commerce directory, industry associations. Each one holds whatever address someone typed into it, sometimes years ago.
  • Other people's websites: a supplier's "where to buy" page, a local news story, a partner's referral list. You can't edit those, so your address has to work however they wrote it.
  • Email signatures, yours and your staff's, which travel with every message you send.

Every one of those is a door a customer might walk through. Fixing the address once fixes all of them.

What it means for search and AI

Customers aren't the only visitors who follow links. Search engines and AI assistants read the web by following links too, and they find you through the same business cards, listings and articles your customers do.

When the "www" version shows a warning, those tools hit the same wall. A link to your site that leads to a warning doesn't help them find you or understand who you are. And when both versions work but don't forward to one main address, they can treat them as two copies of the same site, which splits the signals that tell them which one is yours.

One main address, with the other forwarding to it, gives search engines and AI assistants one clear place to read about your business. That's the setting we want on every site, and it's one of the first things we look at in AI search optimization.

How it gets fixed

Usually with one setting, made by whoever manages your domain or your website hosting:

  1. Point the missing version (with or without "www") at your website.
  2. Make sure it has a security certificate.
  3. Have it forward to your main address, so everyone ends up in the same place.

If you manage your own domain, your registrar or host usually has a setting for this. If someone else does, send them a two-line note: "My site works at one address but shows a warning at the other. Can you make both work and forward to the main one?"

And if you're not sure who manages your domain, that's worth finding out this week, whatever the www check shows. If you'd rather not keep track of settings like this at all, that's what website care is for.

Share

common questions

A few questions we hear often.

Should my website use "www" or not?

Either is fine. What matters is that both versions work and one forwards to the other, so every visitor lands on the same address.

Does this affect how my site shows up on Google?

It can. A version that shows a warning is a dead end for anyone following a link to it, search engines included. Two versions that both work but don't forward to one main address can split your site's signals between them. Making both work and forwarding one to the other gives Google one clear address to show.

Is a "connection is not private" warning on my own site dangerous for my customers?

In this case it usually means a missing certificate, not an attack, but your customers can't tell the difference. Most will leave rather than click through, so it's worth fixing quickly. Our website security page covers certificates and the rest of the basics.

Who fixes it?

Whoever manages your domain settings or your website hosting. It's typically a small change.

Will fixing it change anything else on my site?

No. Forwarding one address to the other leaves your pages, your content and your email as they are. It only decides which address visitors end up on.

Why do some websites not work without "www"?

It's the same gap from the other side. The address without the "www" is missing its own setup, usually the record that points it to your site or the certificate that secures it. The fix is the same too: make both versions work and forward one to the other.

Keep reading

More from the blog

View all posts

Ready to talk about your site?

Reading is one thing. A conversation is where things actually start.

Let's talk