The measured data reveals the following key findings: the non-www canonical has a pass rate of 63%, while the www canonical has a pass rate of 34%. Both versions are live without a redirect, which is an SEO issue, and this has a pass rate of 3%. For Runet, the non-www version has a pass rate of 58%, and the www version has a pass rate of 38%. Full tables are provided below on this page.
Below: key findings, platform breakdown, implications, methodology, FAQ.
Free online tool — redirect checker: instant results, no signup.
| Metric | Pass / Value | Median | p75 |
|---|---|---|---|
| non-www canonical | 63% | — | — |
| www canonical | 34% | — | — |
| Both versions live without redirect (SEO issue) | 3% | — | — |
| Runet non-www | 58% | — | — |
| Runet www | 38% | — | — |
| Sites younger than 2020 on non-www | 80% | — | — |
| Sites older than 2015 on www | 55% | — | — |
| 301 permanent redirect used | 91% | — | — |
| Platform | Share | Detail | — |
|---|---|---|---|
| Next.js/Vercel | 9% | non-www: 94% | — |
| WordPress | 22% | non-www: 61% / www: 38% | — |
| 1С-Bitrix | 14% | non-www: 48% / www: 50% | — |
| Shopify | 4% | non-www: 82% | — |
| Tilda/Wix/no-code | 8% | non-www: 71% | — |
| Custom PHP/Django/Rails | 31% | non-www: 65% | — |
Top-1M Tranco + top-5k .ru by SimilarWeb (March 2026). For each domain: curl -I http://example.com + http://www.example.com + https://example.com + https://www.example.com. Canonical = final URL after all 301s. Both-version detection: both responses 200 without Location.
The analysis of the Top-1M websites indicates that 34% of domains prefer the www version, while 63% utilize the non-www version as their canonical URL. This trend reflects ongoing SEO strategies that prioritize user experience and site performance. Implementing proper redirects, as seen with 91% of sites using 301 permanent redirects, and ensuring consistent canonicalization is crucial for maintaining search engine rankings and avoiding duplicate content issues.
Canonicalization is the process of selecting a preferred URL when multiple URLs point to the same content. This is essential for SEO as it helps search engines understand which version of a webpage to index. In 2026, the distribution of www vs non-www domains in the Top-1M websites reveals significant implications for webmasters and SEO professionals.
When analyzing the distribution, it's important to note that both versions can rank equally well in search results if properly configured. However, choosing one version over the other can help prevent potential duplicate content issues. Here are some key considerations:
<link rel="canonical" href="https://www.example.com/"> tag in the header of your HTML to specify the preferred version.For example, if your preferred version is www, you would set up a 301 redirect from http://example.com to http://www.example.com using a server configuration like this for Apache:
RewriteEngine On
RewriteCond %{HTTP_HOST} ^example.com [NC]
RewriteRule ^(.*)$ http://www.example.com/$1 [L,R=301]This simple configuration ensures that all traffic is directed to the www version, helping to consolidate link equity and improve SEO performance.
The choice between www and non-www can have a tangible impact on SEO performance. As of 2026, data shows that a majority of the top-ranking websites prefer the www format, which can provide several advantages:
To illustrate, consider two similar domains: www.example.com and example.com. If both domains host identical content, the one with the better canonical strategy (e.g., consistent use of 301 redirects and canonical tags) will likely perform better in search engine rankings.
In practice, webmasters should regularly audit their domain configurations to ensure that they are not inadvertently creating duplicate content. Tools like Google Search Console can help identify indexing issues related to canonicalization. Additionally, consider the following best practices:
Ultimately, the decision to use www or non-www should be guided by technical considerations, user experience, and SEO best practices, aligning with the broader goals of site performance and visibility.
Incorrect or long redirect chains slow down the site, lose PageRank and confuse search crawlers. The tool visualizes the full redirect chain with response codes and timing for each hop.
Shows each redirect step: URL → code → URL → code, through to the final destination.
Measures latency at each redirect step for precise identification of performance bottlenecks.
Distinguishes 301, 302, 303, 307, 308 — each has different behavior for SEO and browsers.
Automatically detects circular redirects and warns before the browser throws an error.
redirect chain audit
301/302 debugging
HTTPS redirect check
UTM link tracking
Redirect check history and API for automated chain auditing.
Sign up freeNo difference since 2014. Google treats them equally. What matters is consistency + 301 redirect of one to the other.
2026 default: non-www (shorter, modern). Exception: if you have many subdomains and cookies across the tree — use www (cookies on .example.com work for every subdomain except www.).
Duplicate content, split backlinks, PageRank loss. Google picks canonical itself but you lose control.
<a href="/en/redirects">Enterno Redirects Checker</a> — enter the domain, see chain + canonical target.
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.