Skip to content

www vs non-www: Canonicalisation Benchmark 2026

Key idea:

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.

Check your site →

Key Findings

MetricPass / ValueMedianp75
non-www canonical63%
www canonical34%
Both versions live without redirect (SEO issue)3%
Runet non-www58%
Runet www38%
Sites younger than 2020 on non-www80%
Sites older than 2015 on www55%
301 permanent redirect used91%

Breakdown by Platform

PlatformShareDetail
Next.js/Vercel9%non-www: 94%
WordPress22%non-www: 61% / www: 38%
1С-Bitrix14%non-www: 48% / www: 50%
Shopify4%non-www: 82%
Tilda/Wix/no-code8%non-www: 71%
Custom PHP/Django/Rails31%non-www: 65%

Why It Matters

  • No SEO difference between www and non-www — Google ranks equally. Choice is stylistic
  • A small percentage of sites have both versions live without a redirect, which can lead to duplicate content issues. Google typically selects the canonical version automatically, but this can result in some loss of equity.
  • A significant majority of sites utilize a 301 permanent redirect, which is crucial for transferring link equity effectively. In fact, 91% of the sites surveyed employ this method, highlighting its importance in SEO practices.
  • Legacy www sites don't need mass migration — keep them. But new project — non-www default
  • Choice affects cookie sharing: www + foo.example.com = cookies don't cross (if not .example.com)

Methodology

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.

TL;DR: www vs non-www Canonical 2026 Overview

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.

Understanding the Canonicalization Process

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:

  • Redirects: Implement 301 redirects to ensure that users and search engines are directed to the preferred version.
  • Canonical Tags: Use the <link rel="canonical" href="https://www.example.com/"> tag in the header of your HTML to specify the preferred version.
  • Consistency: Ensure that all internal links point to the chosen canonical 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.

Impact of www vs non-www on 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:

  • Cookie Management: Using the www subdomain allows for better cookie management across subdomains, which is beneficial for user tracking and analytics.
  • Content Delivery Networks (CDNs): Many CDNs operate optimally with www subdomains, improving load times and performance metrics.
  • Perceived Trust: Users often perceive www as more trustworthy, which can influence click-through rates.

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:

  1. Regular Monitoring: Keep track of which version is being indexed by search engines.
  2. Use Analytics Tools: Analyze traffic patterns and user behavior to determine if a shift in canonical preference could benefit performance.
  3. Stay Informed: SEO guidelines and best practices evolve, making it essential to stay updated on industry changes.

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.

Redirect ChainsEach extra redirect adds 100-300ms latency and reduces PageRank along the chain.
HTTP to HTTPSVerify the redirect is performed correctly without intermediate unencrypted hops.
Redirect LoopsCircular redirects cause ERR_TOO_MANY_REDIRECTS error and complete page unavailability.
301 vs 302 Codes301 permanently passes PageRank, 302 is a temporary redirect without passing SEO weight.

Why teams trust us

10+
redirect hops
HTTPS
redirect check
<2s
result
301/302
redirect codes

How it works

1

Enter URL

2

Redirect chain followed

3

Codes & final URL shown

Redirect checker: optimize redirect chains

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.

Full hop chain

Shows each redirect step: URL → code → URL → code, through to the final destination.

Time per hop

Measures latency at each redirect step for precise identification of performance bottlenecks.

Redirect type

Distinguishes 301, 302, 303, 307, 308 — each has different behavior for SEO and browsers.

Loop detection

Automatically detects circular redirects and warns before the browser throws an error.

Who uses this

SEO

redirect chain audit

Developers

301/302 debugging

DevOps

HTTPS redirect check

Marketers

UTM link tracking

Common Mistakes

Chains of 3+ redirectsHTTP → HTTPS → non-www → www — that's three redirects instead of one. Merge them into a single direct redirect.
Using 302 instead of 301302 for permanently moved pages means losing PageRank. Use 301 for final migrations.
Redirecting HTTP to HTTP before HTTPSAn intermediate unencrypted hop creates an MITM vulnerability and adds an extra request.
Not updating internal linksRedirects are not a substitute for updated links. Links to original URLs should be updated directly.

Best Practices

Use one redirect: HTTP+www → HTTPS+non-wwwConfigure a single nginx/Apache rule combining both conditions into one 301 redirect.
Check redirects after migrationsDomain change, HTTPS migration, URL structure redesign — all create new redirect chains.
Remove stale redirectsRedirects accumulated over years create hidden chains. Audit .htaccess and configs quarterly.
Control redirects in sitemapSitemap should only contain final URLs without redirects — otherwise crawlers waste crawl budget.

Get more with a free account

Redirect check history and API for automated chain auditing.

Sign up free

Learn more

Frequently Asked Questions

www or non-www — better for SEO?

No difference since 2014. Google treats them equally. What matters is consistency + 301 redirect of one to the other.

What to pick for a new site?

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.).

What's wrong with both versions live?

Duplicate content, split backlinks, PageRank loss. Google picks canonical itself but you lose control.

How to verify my canonicalisation?

<a href="/en/redirects">Enterno Redirects Checker</a> — enter the domain, see chain + canonical target.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.