www vs non www: the short answer
Quick answer
Neither version ranks higher in Google. Pick one as the main address, redirect the other to it permanently, and read Search Console through a Domain property so both versions are counted. Four rules, taken in order, settle which one to pick. A site on a builder that fixes the version uses the builder's version: Wix keeps www, and Theo defaults to the bare domain. A site with links and history keeps the version Google already shows in a site: search. A large site with several subdomains or a content delivery network uses www. A new domain with nothing printed uses the bare domain. Whatever the choice, the other version must forward to it.
www vs non www is a choice about how the address looks, and Google neither rewards nor punishes it. The question comes up when a business registers its first domain, moves to a new host or builder, or sees almost no clicks in Search Console while visitors plainly keep coming. The rules above settle the first two. The third is often a report watching the wrong version, fixed in about ten minutes.
The part that matters is easy to miss because nothing on the site looks different. yourbusiness.com and www.yourbusiness.com are two separate addresses. They can point at the same site, at two copies of it, or at two different things, and Google treats them as two sites until one forwards to the other. Search Console watches one exact address unless told to watch the whole domain. Everything below follows from those two facts.
What www stands for, and why older sites have it
www stands for World Wide Web. In www.yourbusiness.com the domain is yourbusiness.com, and www is a label in front of it, the same kind of label as shop in shop.yourbusiness.com. Early websites used it because one domain also ran email and file servers, and the label told a visitor's computer which machine to ask for. That need is long gone. Today the label is a habit some sites keep and others drop, and plenty of well-run sites use each.
Search Console once had a preferred domain setting for this choice. Google removed it, and today the site itself tells Google which version is the main one, through the redirect and the canonical tag on each page. That is why the rest of this post is about settings at the host, not at Google.
The three technical differences, and the pros and cons of each version
The two versions differ in three technical ways, and the table doubles as the pros-and-cons list. The www side holds the technical advantages, but only a large site with subdomains or its own servers feels them. The bare domain wins on looks, the only difference a customer can see. The last two rows are the ones people expect to differ and do not.
| Difference | www version | Bare domain | Who it matters to |
|---|---|---|---|
Cookies | A cookie set on www stays on www unless the site widens it, so a separate app or shop subdomain does not share logins | A cookie set on the bare domain reaches every subdomain: shop, mail, app | Sites with subdomains that must not share logins or tracking (a one-domain site never notices) |
Pointing at a host or a CDN | Can point at a name, so a content delivery network is attached and the host can move its machines without the owner touching anything | By the rules of DNS the root points at a fixed address, unless the DNS provider offers a workaround (Cloudflare and DNSimple do) | Sites running their own servers or a CDN (a managed host or builder handles it) |
Look and length | Reads as a web address in speech and on radio, but is four characters longer and one more record to point and test by hand | Shorter and cleaner on a truck, a sign, a card and in a spoken ad, and matches the way people say the business name | Every business |
HTTPS | Secure when the certificate covers www | Secure when the certificate covers the bare domain | Sites on their own servers, whose certificate must cover both versions (managed hosts and builders cover both; warnings explained) |
Ranking in Google | No advantage | No advantage | Nobody |
Does www or non-www rank better in Google
Neither. Google ranks pages, and a page is identified by its full address. Whether that address begins with www changes nothing about the words on the page, its speed, the sites linking to it or how well it answers a search. Those are the things that move rankings. Google has no stated preference, and its results mix both kinds.
What Google cares about is that the two versions are not competing. Without a redirect between them, Google treats them as two separate sites, and three things follow. Duplicate content: every page exists twice, and Google guesses which copy to keep. Wasted crawl budget: Google's visits are spent reading the same pages twice. Diluted link value: outside sites link to whichever version they found, so the links the site has earned are split between two addresses instead of adding up on one.
Google usually picks a version on its own, not always the one the owner expects. A permanent redirect settles it: Google follows it, keeps the main address, and carries each page's links and history over. The same logic applies to http and https: a site can answer at four addresses, and the healthy state is that three forward permanently to the fourth.
Which version to pick: a decision rule
What does not belong in the decision: which version looks more professional, which is more secure, and which Google prefers. The first is taste, the second is settled by HTTPS on either version, and the third has no answer. Four rules cover nearly every case. Take them in order, and the first one that applies wins.
- The builder fixes it: use the builder's version. Wix serves connected domains on www and forwards the bare domain to it, with no other direction on offer. Theo serves the bare domain by default and forwards www to it. Neither choice costs a ranking.
- Existing site with links and history: keep whatever Google already shows in a site: search. Switching later is safe with a permanent redirect, but it is a small move with weeks of settling and no ranking gain to pay for it. Printed material is not a reason to switch either, because the other version forwards and the trucks and signs keep working.
- Large site with several subdomains or a content delivery network: use www, for the cookie and pointing reasons in the table above.
- New domain, nothing printed, small site: use the bare domain. It is shorter, and www still works because it forwards.
How to check which version your website uses (one minute)
The check needs a browser and, for the last two steps, a Search Console login.
- Type the bare domain, yourbusiness.com, into a browser and let the page load. Click into the address bar to read the full address, since most browsers hide the https part, and some hide www, until the bar is clicked.
- Type the www version and do the same. If both land on the same address and show as secure, the setup is healthy: one version is the main address and the other forwards to it. The version left in the address bar is the one the site uses.
- If each version stays where you typed it and both show the site, nothing sends one to the other, and Google can keep two copies of every page. The redirect section below fixes it.
- If one version shows the site and the other a parked page, a security message or nothing, that version was never connected. Connect it at the host. On a Theo site, the domain panel says so when www is not yet pointing at the site.
- Run a site: search in Google, written as one word: site:yourbusiness.com. The addresses in the results are the version Google has kept. If they disagree with the browser test, the redirect is either new or missing.
- Open Search Console and read the property name at the top left. The bare domain with no https in front is a Domain property and covers everything. https://www.yourbusiness.com/ or https://yourbusiness.com/ is a URL-prefix property and covers only that exact version.
- Still in Search Console, paste the homepage address into the URL Inspection box at the top, spelled the way the property spells it. A URL-prefix property only inspects addresses under its own version, while a Domain property takes either. The line labeled Google-selected canonical shows which version Google keeps for that page. If it names the version the site does not serve, Google has not yet followed a redirect, or there is none.
How to redirect www to non-www, host by host
The redirect is a setting at the host or builder, not on the pages, and it takes about fifteen minutes. It should be the permanent kind, a 301, so Google moves each page's standing along with the visitor. A temporary 302 leaves the old version in the index. Set it once, confirm it with the one-minute check, then leave it alone, because every change of direction sends Google through another round of redirects. If it is not clear which builder or host runs a site, Theo's free what is this website built with check is made for that question. The list below shows where each platform keeps the setting.
- Cloudflare (DNS in front of any host): open the domain, click Rules, then Redirect Rules, then Create rule. From the list of templates, pick Redirect from WWW to Root, or the reverse one. The template fills in the match on the www hostname and a status code of 301. Save it. The rule only fires when the www record on the DNS tab is proxied, shown by the orange cloud. About five minutes.
- GoDaddy (domain only): set the redirect at the host and leave GoDaddy's Forwarding off, because a forward at the registrar replaces the connection to the site. The Forwarding section under the domain offers Permanent (301) or Temporary (302), but it forwards the whole domain. Forwarding is the right tool only when the domain itself should send visitors somewhere else. Two minutes to confirm Forwarding is off.
- Squarespace: Settings, then Domains, lists every connected domain with a Primary label on one and forwards the rest to it. In that domain's settings, switch the Use www prefix toggle on or off. Squarespace says the change takes 24 to 48 hours to apply, as of September 2026, so run the one-minute check two days later.
- Wix: Settings, then Domains, shows the connected domain with www in front. Wix serves every connected site on www and forwards the bare domain to it. As of September 2026 the direction cannot be changed, so the only job is to confirm the bare domain forwards. One minute.
- WordPress: Settings, then General, has two fields, WordPress Address (URL) and Site Address (URL). Put the chosen version in both, with https in front, and save. WordPress then forwards the other version to it. On an Apache host the same redirect can also be a rule in the .htaccess file, which most hosting control panels write from a redirect tool. Where both exist, the WordPress fields and the .htaccess rule must name the same version. Five minutes, typed carefully: a wrong address in those fields makes the dashboard unreachable until the host corrects it.
- Theo: nothing to set. The domain step connects both versions, makes the bare domain the main address by default and forwards www to it permanently. The panel shows Connected once both are in place.
Redirect or canonical tag: use both, and let the 301 lead
A canonical tag is a line in a page's code naming the address the page should be counted under. The builder writes it, and WordPress has added one to every single post and page on its own since version 2.9, though not to archive pages. The tag is not enough alone, for two reasons. It is a hint Google can decline when other signals disagree, while a 301 is an instruction Google follows. It also passes only the page's standing, while a redirect moves the visitor too, so nobody lands on a duplicate.
The healthy setup uses both, and they agree: the unused version redirects permanently to the main one, and every page on the main version carries a canonical tag naming its own address. When they disagree, say a redirect to the bare domain and a canonical tag naming www, Google gets two instructions and has to guess. That guess is what the redirect was meant to end. After any change of host, builder or version, view one page's source, search for the word canonical, and run the one-minute check. A copy that names the main address shows up in Search Console as Alternate page with proper canonical tag, which needs nothing. A page with no tag at all, reached at a second address, shows as Duplicate without user-selected canonical.
What to do after you choose: the checklist
Choosing a version is a one-time decision. Keeping it is a short checklist, most of it done once and re-checked after any change of host or builder.
| Item | When | Who does it |
|---|---|---|
One version is the main address, and the other redirects to it with a 301 | At launch, then again after any change of host or builder | The host or builder (on a Theo site, the domain step) |
Both versions load over HTTPS and show as secure | At launch, then again after a certificate or host change | The host (Theo serves every site over HTTPS) |
Every page's canonical tag names the main version | Once, then spot-check a page after any change of host, builder or version | The builder or WordPress writes it, and whoever does the search work reads it |
Search Console is a Domain property, or a URL-prefix property on the main version | Set up once, then read the report weekly | The owner, or whoever does the site's search work |
The sitemap lists only the main version and is submitted in Search Console | Once, then again after any address change | The builder or host (on every plan, Theo submits your sitemap when you connect Google) |
Internal links, the logo link and the navigation use the main version | Once, then again after a redesign | The builder on most sites (on WordPress, check after changing the Site Address) |
Every listing the business controls uses the main version: Google Business Profile, Facebook, Instagram, Yelp, ads, the email signature | Once, then re-check yearly | The owner |
Run the one-minute check | Quarterly, and whenever the Search Console graph drops to near zero in one step | The owner, or whoever does the site's search work |
Why www matters in Google Search Console
Search Console is Google's free report on a site, and it offers two kinds of property. A URL-prefix property watches one exact address, https or http, www or not. A Domain property watches every version at once: root, www, http, https and every subdomain.
The mismatch is common because a property is usually created once, on whatever version the site used then. Later the site moves to a builder that uses the other one. From then on the report watches the old address. Clicks and impressions fall to near zero in one step while the site is fine, because Google counts the visits under an address the report is not watching.
Theo's research report, The State of Small Business Websites 2026, shows how common a zero is. In Theo's audit of 10,470 small business websites, 47 percent of the 7,071 sites with search data got an estimated zero visitors a month from Google search. A zero can have bigger causes than www, and the guide to a website not showing up on Google covers them in order. But when the report says zero and customers keep arriving, the property version is the first thing to rule out, because it takes one minute to check and costs nothing to fix.
| What the report shows | What it usually means | What to do |
|---|---|---|
Clicks and impressions drop to near zero in one step and stay there | The property watches a version the site stopped using, often after a move or a new host | Add a Domain property and keep the old one for its history |
Clicks fall over weeks while the pages stay indexed | Not a www problem: a ranking change, a competitor, or the weeks after a move | Read the Pages and Queries reports, and if the site moved, read the post on rankings after a move linked below |
The Pages report lists Page with redirect for every address | The property watches the version that forwards | Add a Domain property, since the redirect is right and only the report is on the wrong side of it |
How to fix a Search Console property on the wrong version (ten minutes)
If step 6 shows a URL-prefix property whose version does not match steps 1 and 2, the report is watching the wrong door. The fix is a property that watches every door. It takes about ten minutes at the screen, plus time for the new report to fill.
- In Search Console, click the property name at the top left, choose Add property, and pick the Domain card on the left, not the URL prefix card on the right. Enter the bare domain with no www and no https and continue.
- Verify it through the domain registrar. Search Console shows a record to add and names where it goes. Copy it exactly, save it at the registrar, and click Verify. If Verify does not work, run the free record check in the google-site-verification guide before waiting, since a record that was never saved will not appear however long you wait.
- Keep the old property, whose history stays readable while the new Domain property starts empty and fills as Google's reports catch up. Judge the new property only once it holds a full week of data.
- Submit the sitemap again inside the new property. The post on getting Google to index a site covers the rest of the Search Console setup, including indexing requests and page statuses.
- If the old property fed Google Analytics or a rank tracker, point those at the new one. On a Theo site, the owner signs in with Google once the domain is active, and Theo sets up Search Console. The Google-selected canonical line in URL Inspection then shows which version Google kept.
Common www mistakes and how to fix each
Most www trouble comes from one of six settings, each listed with what the owner sees and the fix.
| Mistake | What you see | The fix |
|---|---|---|
Both versions live with no redirect | Each version stays in the address bar when typed, and the site: search mixes www and bare addresses. | Set the main version at the host or builder so the other forwards permanently. |
Search Console on the version the site does not use | Clicks and impressions fall to near zero in one step while customers keep arriving. | Add a Domain property and keep the old one for its history. |
Only one version connected at the registrar | One version shows the site, the other a parked page, an old site or a privacy warning. | Point both versions at the site. On a Theo site, the domain panel says when www is not pointing at it. |
Domain forwarding used instead of a connection | The address bar changes to the builder's own address after the page loads. | Turn off forwarding and parking at the registrar and point the domain at the site. A forward hands the search credit to the address it forwards to. |
The sitemap lists the other version | The Pages report shows Page with redirect for every address in the sitemap. | Regenerate the sitemap from the main version and resubmit it, since the old one pointed at the wrong side of a correct redirect. |
The version switched with no redirect | The site: results still return the previous version, and those addresses now show a security message or nothing. | Add the permanent redirect from the old version to the new one, resubmit the sitemap, and give Google time. |
What Theo does with www when a domain goes live
A Theo site begins as a preview the owner refines in chat, then publishes. When the owner connects a domain they already have, the domain step walks them through pointing both the bare domain and www at the site. A domain bought inside Theo connects both versions on its own. By default the bare domain becomes the main address, and www forwards to it with a permanent redirect, so Google sees a single site. The walkthrough also covers turning off forwarding and parking at the registrar and leaving the email records alone. Until the registrar's records update, usually within a few hours, visitors still reach the old site. The domains page explains the connection step by step.
Theo's own site works the same way: www.theo.site forwards permanently to theo.site, and so does the http version. Buy My Lunch, a customer site on Theo, answers at www.buymylunch.com and forwards it to buymylunch.com, its main address. Theo serves every site as static pages over HTTPS, so both versions show as secure. If www is not pointing at the site yet, the domain panel says so.
Once the domain is active, the owner clicks Connect Google and signs in, and Theo sets up both Analytics and Search Console. Theo also submits the sitemap on every plan, so Google finds every new page, and the ongoing growth work on Starter and Pro switches on after the domain and both Google connections are in place. If Google indexed the old site under www, the switch to the bare domain is an ordinary permanent redirect. The post on what happens to rankings when a website moves covers the weeks after any move, this small one included.

Frequently asked questions
Does it cost anything to switch a website to www or away from it?
No. The redirect is a setting at the host and Search Console is free. On Theo, a site plus hosting starts at $29.99 a month on Basic. The ongoing SEO work that catches a stray second version later is Starter at $69.99 a month, free for the first 30 days, or Pro at $129.99 a month.
How long does it take Google to notice a www redirect?
Google notices the redirect the next time it crawls each page, at its own pace. Expect the site: results to switch gradually and the Search Console report to follow, since the report runs behind the crawl. Resubmitting the sitemap in Search Console nudges the crawl. Beyond that, leave the redirect alone, because every change of direction starts the process over.
Who owns the domain and the site if Theo connects it, and what happens on cancellation?
You own the site's pages, words and photos, and the domain is yours wherever it is registered. One you registered elsewhere stays registered there, and one bought inside Theo is registered in your name. Theo hosts the site. When you cancel, the confirmation shows the day the subscription ends, and the site stays live until then. Before that day you can save your text and images and point the domain, both versions, anywhere else. Pro also includes read-only access to the site's code on GitHub, which you can copy.
Is it better to have www or not?
Neither is better for ranking, security or speed. The bare domain is shorter, the www version is familiar, and both work over HTTPS. The technical points in favor of www matter only to large sites with subdomains or their own servers.
Can www be redirected to non-www with DNS alone, or does it need .htaccess?
No, DNS alone cannot redirect. DNS only says which machine answers for a name, and a redirect is an answer that machine gives. So the www version has to point at something that answers with a permanent redirect. That can be the host itself, as with WordPress, Squarespace, Wix and Theo, or a Cloudflare redirect rule in front of the host. A registrar's forwarding tool can redirect too, but it is the wrong tool once the site lives at a host. A rule in .htaccess is one way to make an Apache host give that answer, and a site on a builder does not need one.
Should Search Console be on www or non-www?
Neither, if you have the choice: pick a Domain property, which covers root, www, http and https in one report. If only a URL-prefix property is possible, set it on the version that stays in the address bar after the page loads, because that is the version Google counts. A property on the other version reports near zero while the site is fine.
Can a site switch from www to non-www later without losing rankings?
Yes, with a permanent redirect from the old version to the new one and canonical tags naming the new one. Google follows the redirect and moves each page's standing with it. Treat it as a small move: redirect, update the listings the business controls, resubmit the sitemap, and watch Search Console over the following weeks.
Settling www vs non-www on a Theo site
The whole www vs non-www decision comes down to four steps: pick one version, redirect the other permanently, keep the canonical tags agreeing with the redirect, and read Search Console through a Domain property. Together they take an afternoon at most. On a Theo site the bare domain is the main address by default, www forwards to it, and both are connected as the owner's domain goes live. Basic covers the site and hosting at $29.99 a month. The ongoing technical SEO work that catches a stray second version later comes with Starter, at $69.99 a month and free for the first 30 days, or Pro, at $129.99 a month. For a site that is already live, the free audit reads its traffic, rankings and search health with no login. A business without a site yet can build one free and see it before the www question even comes up.
More like this in the guides and under getting found on Google. The audit numbers quoted across these posts are in Theo's research.



