WWW or Non-WWW: Which One Actually Helps Your SEO?
SearchBlueprint · · 7 min read · scored 98/100
Whether you pick www or non-www for your domain makes no real difference to your search rankings. Google treats both the same once you tell it which version is canonical, through a 301 redirect and a matching canonical tag. The decision that actually matters is picking one version and staying consistent everywhere else on your site.
What "www" and "non-www" Actually Mean
A www domain looks like https://www.example.com. A non-www domain, often called the root or apex domain, drops that label: https://example.com. Both point to the same website; the difference is just the hostname you type.
The "www." prefix dates back to the early web, when it wasn't unusual for a company to run separate physical servers for different services on one domain: mail.example.com for email, ftp.example.com for file transfers, and www.example.com for the actual website. The label told you which machine you were talking to. Most sites today run everything through one server or one platform, so www is no longer functionally necessary. It survives mostly as a convention people recognize, especially anyone who grew up assuming a web address starts with "www."
Does WWW vs Non-WWW Actually Affect Your SEO?
No. Google has said for years that it has no ranking preference between a www and a non-www domain, and nothing about how either version crawls or indexes changes that. A root domain isn't inherently "cleaner" to search engines, and a www subdomain isn't inherently more authoritative. Both are just URLs.
The Real Risk Isn't the Prefix. It's Running Both at Once
The problem shows up when a site answers to both versions without pointing one at the other. If https://www.example.com and https://example.com both load successfully with no redirect, search engines can index either one, sometimes both. That splits backlinks between two URLs instead of consolidating them on one, dilutes the ranking signals each page would otherwise carry, and creates duplicate content that forces Google to guess which version you actually want ranked. Google's own guidance on consolidating duplicate URLs addresses this exact scenario directly, and it's worth reading if you're auditing a site for the first time.
This is also the kind of issue that tends to hide in plain sight until a proper technical sweep catches it; our breakdown of the technical SEO fixes that actually move your rankings covers several more problems in the same category, like redirect chains and inconsistent internal links, that quietly cap how well an otherwise solid site performs.
The Real Differences Between WWW and Non-WWW
SEO aside, the two versions aren't perfectly identical under the hood. The gaps are small, but they're worth knowing before you pick one for a brand-new site.
| Aspect | WWW version | Non-WWW (root) version | Why it matters |
|---|---|---|---|
| Cookies | Can be scoped to just the www subdomain | Cookies set on the root apply to every subdomain by default | Matters mainly on sites running several subdomains that shouldn't share session data |
| CDN / DNS setup | Works cleanly with a standard CNAME record | Historically couldn't take a CNAME at the apex, needing ALIAS/ANAME or direct A records instead | Fewer setups hit this today since most CDNs now support apex-level routing, but older or stricter DNS providers can still require it |
| Typing & saying it aloud | Longer to type, rarely said out loud in ads or on the phone | Shorter, easier to say in a radio spot or over the phone | A branding and usability call, not a ranking one |
| First impression | Reads as the "standard" web address to less tech-savvy visitors | Reads as cleaner and more modern to most users today | Depends heavily on your audience |
Neither column is the "correct" choice. A SaaS product optimizing for a short, sayable brand name usually drops the www. A site with heavy subdomain use, or one built on older infrastructure with DNS constraints, sometimes keeps it for the technical convenience.
How to Set Your Preferred Version Without Losing Rankings
Once you've picked a version, the setup is mechanical, but getting it wrong is what actually costs you rankings.
- Redirect the version you're not using to the one you are, with a 301. A 301 tells browsers and search engines the move is permanent, which is what consolidates backlinks and ranking signals onto the surviving URL. A 302 signals "temporary," so search engines may keep crawling and indexing the old version anyway, which defeats the point.
- Add a matching canonical tag. The canonical tag on every page should point to your chosen version. If your redirect says one thing and your canonical tag says another, you're sending Google contradictory signals.
- Make your sitemap and internal links agree. A sitemap full of www URLs while your redirect sends everything to non-www just adds noise Google has to resolve on its own.
- Forget the old "preferred domain" setting. Older Search Console had a manual www/non-www preference toggle. That setting is gone. Today's Search Console reads your redirects, canonical tags, and sitemap to work out your preferred version on its own, so the redirect and canonical tag are doing all the real work now, not a dropdown menu.
| Signal | What it tells search engines | Use it when |
|---|---|---|
| 301 redirect | This move is permanent; transfer ranking signals here | Always, for the version you're retiring |
| Canonical tag | This is the authoritative URL for this content | On every page, pointing to your chosen version |
| XML sitemap | These are the URLs worth crawling | Listing only your chosen version, never both |
If you want a clearer picture of what to fix first before touching any of this, seeing your SEO plan before you make changes is a faster way to prioritize than guessing at redirects one at a time.
WWW vs Non-WWW Best Practices Checklist
- Check which version is currently live at both addresses. Type both into a browser and see whether one redirects, both load separately, or one throws an error.
- Pick one version and commit. Base it on branding and ease of typing, not on any imagined SEO edge.
- Set the 301 redirect at the server or DNS level, not with a slower client-side JavaScript redirect.
- Update every internal link, sitemap URL, and canonical tag to match the chosen version.
- Watch Search Console for stray indexing of the old version for a few weeks after the switch; it should drop off as Google recrawls your redirects.
- Tell anyone who links to you which version you've standardized on, so new backlinks land on the right one from the start.
FAQs
Does www or non-www rank better in Google?
Neither. Google has confirmed repeatedly that it has no ranking preference between a www and non-www domain. Any ranking difference you see between two real sites comes from backlinks, content, or technical SEO, never from the prefix itself.
What happens if both www and non-www versions of my site are live with no redirect?
Search engines can index both, splitting backlinks and creating duplicate content. Fix it with a 301 redirect from the version you're not using to the one you are, plus a matching canonical tag on every page.
Should I use a 301 or 302 redirect when switching between www and non-www?
Use a 301. It tells search engines the change is permanent and consolidates your ranking signals onto the surviving URL. A 302 signals a temporary move, so the old version can keep showing up in search.
Do I need to set a preferred domain in Google Search Console?
No, that setting no longer exists. Current Search Console determines your preferred version from your 301 redirects, canonical tags, and sitemap, so get those three consistent and Search Console will follow.
Is dropping the www better for branding than keeping it?
Often, yes, for newer brands. A shorter, non-www address is easier to say in ads, over the phone, or on packaging. It's a branding and usability call rather than an SEO one, so weigh it against how your audience expects a web address to look.
See Which Version of Your Domain Google Has Actually Indexed
Run a quick check before you decide anything: search site:yourdomain.com and see whether www or non-www comes back, or look at the Pages report in Search Console for both. That single check tells you whether your current setup already has a working redirect or is quietly splitting signals between two URLs. If you'd rather have someone else confirm it for you, book a quick audit with the team and find out whether www or non www is quietly costing you anything before you touch a single redirect.
Sources
About the author
SearchBlueprint researched, wrote and scored this article with the content pipeline our customers run on their own sites. The score in the byline is what our content engine gave this page before it published. Nothing here is reviewed by hand, which is the point: it is the product's output, published where anyone can check it.