www vs non-www: Which Is Better for WordPress SEO? A Comprehensive Guide

Table of Contents#

1. What Are www and non-www URLs?

   • 1.1 Historical Context: Why www Exists
   • 1.2 Technical Definition: Subdomain vs. Root Domain

2. The SEO Debate: Is One Better Than the Other?

   • 2.1 Google’s Stance: Consistency Over Preference
   • 2.2 Duplicate Content: The Hidden Danger of Mixed URLs
   • 2.3 Link Equity Dilution: Why Splitting Signals Hurts Rankings
   • 2.4 Crawl Budget Wastage: How Search Engines Treat Separate Versions

3. Technical Differences That Impact SEO

   • 3.1 DNS Configuration: A Records vs. CNAME Records
   • 3.2 Security: SSL Certificates and Wildcard Support
   • 3.3 Redirects: 301 vs. 302—Why Permanent Redirects Matter

4. WordPress-Specific Considerations

   • 4.1 WordPress URL Settings: The “Site Address” Trap
   • 4.2 Mixed Content Errors: When Switching Breaks Your Site
   • 4.3 Media and Internal Links: Updating URLs After a Switch

5. User Experience and Branding

   • 5.1 Memorability: Which Is Easier for Users to Recall?
   • 5.2 Brand Consistency: Aligning URLs with Marketing
   • 5.3 Social Sharing: How Links Appear to Audiences

6. Performance and Technical SEO

   • 6.1 CDN Compatibility: Why www Often Works Better
   • 6.2 Cookie Isolation: Boosting Load Times with www
   • 6.3 Caching: How Domain Choice Affects Server Responses

7. How to Choose Between www and non-www

   • 7.1 Key Factors to Consider
   • 7.2 Case Studies: www vs. non-www in the Real World

8. Step-by-Step Guide to Setting Up www or non-www on WordPress

   • 8.1 Step 1: Decide Your Preferred Version
   • 8.2 Step 2: Update WordPress General Settings
   • 8.3 Step 3: Configure Redirects (Apache/Nginx)
   • 8.4 Step 4: Set Canonical Tags
   • 8.5 Step 5: Update Google Search Console and Bing Webmaster Tools
   • 8.6 Step 6: Fix Mixed Content and Broken Links

9. Common Mistakes to Avoid

10. Conclusion

11. References

1. What Are www and non-www URLs?#

Before diving into SEO, let’s clarify what www and non-www actually are. At their core, they’re two different ways to structure a domain name, but their technical roles differ significantly.

1.1 Historical Context: Why www Exists#

The “www” prefix dates back to the early days of the internet (the 1990s), when websites were just one type of service hosted on a server. Back then, servers might host multiple services: email (mail.yoursite.com), file transfer (ftp.yoursite.com), and the World Wide Web (www.yoursite.com). The “www” was a subdomain used to explicitly identify the web server, distinguishing it from other services.

As the internet evolved, many sites dropped the “www” to simplify their URLs (e.g., google.com instead of www.google.com). However, www never disappeared—and for good technical reasons, as we’ll explore later.

1.2 Technical Definition: Subdomain vs. Root Domain#

• non-www URLs (e.g., yoursite.com) are considered “root domains.” They point directly to the main domain in DNS (Domain Name System) records.
• www URLs (e.g., www.yoursite.com) are subdomains. Think of them as “children” of the root domain. For example, www is just one subdomain—others might include blog.yoursite.com or shop.yoursite.com.

This distinction matters because search engines and servers treat root domains and subdomains as separate entities by default. Without explicit configuration, yoursite.com and www.yoursite.com could be seen as two distinct websites, leading to SEO problems.

2. The SEO Debate: Is One Better Than the Other?#

Let’s cut to the chase: Neither www nor non-www is inherently “better” for SEO. Google has repeatedly stated that it treats both versions equally, provided you’re consistent ([1]). However, inconsistency between the two can cripple your SEO efforts. Here’s why:

2.1 Google’s Stance: Consistency Over Preference#

Google’s John Mueller has clarified: “From an SEO perspective, we don’t care whether you use www or not. What matters is that you pick one and stick with it” [1]. The key is to avoid letting search engines index both versions, which leads to duplicate content, split link equity, and wasted crawl budget.

2.2 Duplicate Content: The Hidden Danger of Mixed URLs#

Duplicate content occurs when identical or very similar content appears on multiple URLs. If your site is accessible via both www and non-www without redirects, search engines will see two versions of every page (e.g., yoursite.com/blog and www.yoursite.com/blog).

Why is this bad? Search engines may:

• Struggle to determine which version to rank.
• Split ranking signals (e.g., backlinks) between the two URLs.
• Penalize your site for “thin” or duplicate content (though this is rare for accidental duplication, it’s still risky).

2.3 Link Equity Dilution: Why Splitting Signals Hurts Rankings#

Link equity (or “link juice”) is the value passed from one site to another via backlinks. If half your backlinks point to www.yoursite.com and half to yoursite.com, that equity is split between two URLs. Instead of consolidating all link value into one version, you’re diluting it—weakening your site’s authority and rankings.

2.4 Crawl Budget Wastage: How Search Engines Treat Separate Versions#

Search engines like Google have a “crawl budget”—the number of pages they’ll crawl on your site within a given time. If they crawl both www and non-www versions, they’re wasting budget on duplicate pages instead of indexing new or important content. For large sites (10k+ pages), this can significantly delay indexing of critical pages.

3. Technical Differences That Impact SEO#

While SEO parity exists between www and non-www, their technical underpinnings affect DNS, security, and redirects—all of which indirectly impact SEO.

3.1 DNS Configuration: A Records vs. CNAME Records#

DNS translates domain names into IP addresses. Here’s how www and non-www differ:

• non-www (root domain): Uses an A record to point directly to your server’s IP address (e.g., 192.168.1.1).
• www (subdomain): Typically uses a CNAME record to “alias” www.yoursite.com to your root domain (yoursite.com). Alternatively, it can use an A record, but CNAME is more flexible (e.g., if your server IP changes, you only update the root A record, and www automatically follows).

Why does this matter? CNAME records simplify DNS management, especially if you use a CDN (more on that later). Root domains (non-www) can’t use CNAME records in some DNS systems (due to RFC standards), limiting flexibility.

3.2 Security: SSL Certificates and Wildcard Support#

SSL certificates (HTTPS) are mandatory for SEO (Google uses HTTPS as a ranking signal [2]) and user trust. Here’s how www affects SSL:

• Wildcard SSL certificates (e.g., *.yoursite.com) secure all subdomains, including www. If you use non-www, a wildcard cert still works, but you might need to explicitly include the root domain (e.g., yoursite.com and *.yoursite.com).
• Single-domain SSL certificates only secure one domain (e.g., yoursite.com or www.yoursite.com). If you later want to use subdomains (e.g., blog.yoursite.com), you’ll need a new certificate.

For most WordPress sites, a wildcard SSL is ideal, and www subdomains play nicely with this setup.

3.3 Redirects: 301 vs. 302—Why Permanent Redirects Matter#

To enforce a single version (www or non-www), you need to redirect the “non-preferred” version to the preferred one. For SEO, 301 (permanent) redirects are critical: they pass ~90-99% of link equity to the target URL [3].

• Example: If you prefer www, redirect yoursite.com → www.yoursite.com with a 301.
• Avoid 302 (temporary) redirects—search engines may not transfer link equity, leaving duplicate content issues unresolved.

4. WordPress-Specific Considerations#

WordPress has unique quirks that make www/non-www setup trickier than on static sites. Misconfiguring URLs here can break your site or tank SEO.

4.1 WordPress URL Settings: The “Site Address” Trap#

In WordPress, navigate to Settings > General, and you’ll see two fields:

• WordPress Address (URL): The path to your WordPress core files (e.g., /wp-content).
• Site Address (URL): The public-facing URL users see (e.g., www.yoursite.com).

Critical: Both fields must use your preferred domain version (www or non-www). If they don’t match, or if they use the non-preferred version, WordPress will generate links (e.g., in menus, posts) pointing to the wrong URL, causing broken links or mixed content.

4.2 Mixed Content Errors: When Switching Breaks Your Site#

If you switch from non-www to www (or vice versa) after launching your site, you may encounter “mixed content” errors. These occur when your HTTPS site loads resources (images, scripts, stylesheets) from HTTP URLs (e.g., an image still pointing to http://yoursite.com/photo.jpg instead of https://www.yoursite.com/photo.jpg).

Mixed content errors:

• Break SSL security (browsers show “Not Secure” warnings).
• Harm user trust and SEO (Google flags insecure sites).

Fixes: Use plugins like Really Simple SSL or Better Search Replace to update old URLs in your database.

4.3 Media and Internal Links: Updating URLs After a Switch#

WordPress stores media URLs (e.g., images) in the database. If you switch domains, old media links will point to the non-preferred version. For example, if you move from non-www to www, an image inserted before the switch will still load from yoursite.com/wp-content/uploads/2023/01/photo.jpg instead of the www version.

To fix this:

• Use Better Search Replace to search for your old domain (e.g., yoursite.com) and replace it with the new one (e.g., www.yoursite.com) in the database.
• Regenerate thumbnails with plugins like Regenerate Thumbnails to ensure new images use the correct URL.

5. User Experience and Branding#

While SEO is critical, user experience (UX) and branding shouldn’t be ignored. Your URL is often the first thing users see—make it count.

5.1 Memorability: Which Is Easier for Users to Recall?#

Shorter URLs are easier to remember. non-www URLs (yoursite.com) are one character shorter than www.yoursite.com, which might help with recall. However, this is negligible for most users—especially if your brand name is long (e.g., www.thelongestbrandnameever.com vs. thelongestbrandnameever.com).

5.2 Brand Consistency: Aligning URLs with Marketing#

Your URL should match your brand identity. For example:

• Tech brands like GitHub (github.com) and Twitter (now X, x.com) use non-www for a modern, streamlined look.
• Traditional brands or sites with multiple subdomains (e.g., news sites with www.cnn.com, edition.cnn.com) use www to avoid confusion.

Consistency across marketing materials (business cards, ads, social media) is key. If you use non-www in ads but www on your site, users may struggle to find you.

5.3 Social Sharing: How Links Appear to Audiences#

When users share your content on social media, the URL is visible. non-www URLs look cleaner in tweets or Instagram bios (e.g., “Check out our blog: yoursite.com/blog” vs. “www.yoursite.com/blog”). However, link shorteners (e.g., Bitly) can mask this, so it’s a minor consideration.

6. Performance and Technical SEO#

Beyond SEO and UX, your domain choice impacts site speed—a top Google ranking factor [4]. Here’s how www and non-www stack up:

6.1 CDN Compatibility: Why www Often Works Better#

A CDN (Content Delivery Network) caches your site’s content on global servers, reducing load times. Many CDNs (e.g., Cloudflare, StackPath) recommend using www subdomains because:

• They simplify DNS setup (CNAME records are easier to point to CDN endpoints than root domains).
• Root domains (non-www) may have DNS restrictions (e.g., some registrars block CNAME records for root domains, limiting CDN integration).

For example, Cloudflare explicitly states: “We recommend using www for better compatibility with our CDN” [5].

6.2 Cookie Isolation: Boosting Load Times with www#

Cookies are small files stored on users’ browsers. If you use a root domain (non-www), all subdomains (e.g., blog.yoursite.com, shop.yoursite.com) will share cookies with the root. This increases cookie size, slowing down requests.

With www, you can isolate cookies to the www subdomain. For example, cookies set on www.yoursite.com won’t affect static.yoursite.com (a subdomain for images), reducing latency for static assets.

6.3 Caching: How Domain Choice Affects Server Responses#

Caching (storing frequently accessed data) improves load times. Some caching plugins (e.g., WP Rocket) work better with www subdomains, as they can more easily separate cache for the main site and subdomains. However, this is a minor advantage—most modern caching tools handle both versions well.

7. How to Choose Between www and non-www#

Now that you understand the tradeoffs, how do you pick? Consider these factors:

7.1 Key Factors to Consider#

7.2 Case Studies: www vs. non-www in the Real World#

• www Success Stories:

  • Wikipedia (www.wikipedia.org): Uses www to manage global subdomains (en.wikipedia.org, es.wikipedia.org).
  • Amazon (www.amazon.com): Relies on www for CDN and cookie isolation across regions.

• non-www Success Stories:

  • GitHub (github.com): Embraces non-www for a developer-friendly, minimalist brand.
  • Etsy (etsy.com): Uses non-www to keep URLs short and memorable for shoppers.

Takeaway: Both work—what matters is aligning with your technical stack (CDN, subdomains) and brand.

8. Step-by-Step Guide to Setting Up www or non-www on WordPress#

Ready to choose a version and configure it? Follow these steps to avoid SEO disasters.

8.1 Step 1: Decide Your Preferred Version#

Use the factors above to pick www or non-www. If you’re unsure, check your backlinks with tools like Ahrefs or SEMrush—choose the version with more existing links to preserve equity.

8.2 Step 2: Update WordPress General Settings#

1. Log into WordPress and go to Settings > General.
2. Set both WordPress Address (URL) and Site Address (URL) to your preferred version (e.g., https://www.yoursite.com).
3. Save changes. Warning: If you skip redirects (Step 3), this will break your site temporarily—proceed to Step 3 immediately.

8.3 Step 3: Configure Redirects (Apache/Nginx)#

To force all traffic to your preferred version, set up 301 redirects. The method depends on your server (Apache or Nginx).

For Apache Servers (Most Shared Hosts)#

Edit your site’s .htaccess file (in your root directory, accessible via FTP or cPanel File Manager). Add one of the following snippets:

• If preferring www:

  # Redirect non-www to www with HTTPS
  RewriteEngine On
  RewriteCond %{HTTP_HOST} ^yoursite\.com [NC]
  RewriteCond %{SERVER_PORT} 80
  RewriteRule ^(.*)$ https://www.yoursite.com/$1 [R=301,L]
   
  # Also redirect HTTPS non-www to www
  RewriteCond %{HTTP_HOST} ^yoursite\.com [NC]
  RewriteCond %{SERVER_PORT} 443
  RewriteRule ^(.*)$ https://www.yoursite.com/$1 [R=301,L]

• If preferring non-www:

  # Redirect www to non-www with HTTPS
  RewriteEngine On
  RewriteCond %{HTTP_HOST} ^www\.yoursite\.com [NC]
  RewriteCond %{SERVER_PORT} 80
  RewriteRule ^(.*)$ https://yoursite.com/$1 [R=301,L]
   
  # Also redirect HTTPS www to non-www
  RewriteCond %{HTTP_HOST} ^www\.yoursite\.com [NC]
  RewriteCond %{SERVER_PORT} 443
  RewriteRule ^(.*)$ https://yoursite.com/$1 [R=301,L]

For Nginx Servers (VPS/Dedicated Hosts)#

Edit your Nginx server block (e.g., /etc/nginx/sites-available/yoursite.com). Add:

• If preferring www:

  server {
      listen 80;
      listen [::]:80;
      server_name yoursite.com;
      return 301 https://www.yoursite.com$request_uri;
  }
   
  server {
      listen 443 ssl;
      listen [::]:443 ssl;
      server_name yoursite.com;
      ssl_certificate /path/to/cert.pem;
      ssl_certificate_key /path/to/key.pem;
      return 301 https://www.yoursite.com$request_uri;
  }

• If preferring non-www:

  server {
      listen 80;
      listen [::]:80;
      server_name www.yoursite.com;
      return 301 https://yoursite.com$request_uri;
  }
   
  server {
      listen 443 ssl;
      listen [::]:443 ssl;
      server_name www.yoursite.com;
      ssl_certificate /path/to/cert.pem;
      ssl_certificate_key /path/to/key.pem;
      return 301 https://yoursite.com$request_uri;
  }

Test Nginx configs with nginx -t and reload with systemctl reload nginx.

8.4 Step 4: Set Canonical Tags#

Even with redirects, canonical tags reinforce your preferred URL to search engines. Most SEO plugins (e.g., Yoast SEO, Rank Math) auto-generate canonical tags, but ensure they point to your preferred version.

In Yoast SEO:

• Go to Yoast SEO > Settings > General > Site Basics.
• Under “Preferred Domain,” select your version (www or non-www).

8.5 Step 5: Update Google Search Console and Bing Webmaster Tools#

• Google Search Console (GSC): Add both versions (www and non-www) as separate properties, then set your preferred version in Settings > Site Settings > Preferred Domain.
• Bing Webmaster Tools: Do the same—add both versions and set a preferred domain.

8.6 Step 6: Fix Mixed Content and Broken Links#

Use these tools to find and fix issues:

• Mixed Content: Run your site through SSL Labs’ SSL Test to find insecure resources. Fix with the Really Simple SSL plugin.
• Broken Links: Use Screaming Frog SEO Spider or the Broken Link Checker plugin to find links pointing to the old domain. Update them manually or with Better Search Replace.

9. Common Mistakes to Avoid#

• Forgetting Redirects: Skipping 301 redirects after updating WordPress settings will break your site.
• Using 302 Redirects: These are temporary—use 301s to pass link equity.
• Mismatched WordPress URLs: Ensure “WordPress Address” and “Site Address” in Settings > General match your preferred domain.
• Ignoring Search Console: Failing to set a preferred domain in GSC can lead to duplicate indexing.
• Not Updating Internal Links: Old links in posts/pages will still point to the non-preferred version—use search/replace tools to fix them.

10. Conclusion#

The www vs. non-www debate isn’t about which is “better” for SEO—it’s about consistency, technical compatibility, and branding. Google doesn’t favor one over the other, but mixing them can tank your rankings through duplicate content and split link equity.

Final Recommendation:

• Choose www if you use a CDN, plan to add subdomains, or want better cookie isolation.
• Choose non-www for a minimalist brand, shorter URLs, or if you don’t need subdomains/CDNs.

Whichever you pick, follow the step-by-step setup guide to enforce redirects, update WordPress settings, and fix broken links. With consistent configuration, your site will avoid SEO pitfalls and rank its best.

11. References#

1. Mueller, J. (2020). “WWW vs non-WWW for SEO” [Google Webmaster Central Blog].
2. Google. (2014). “HTTPS as a ranking signal” [Google Webmaster Central Blog].
3. Rand, A. (2010). “The Definitive Guide to 301 Redirects” [Moz].
4. Google. (2021). “Page Speed as a Ranking Factor” [Google Search Central].
5. Cloudflare. (n.d.). “CNAME Setup for Root Domains” [Cloudflare Support].
6. WordPress Codex. (n.d.). “Changing the Site URL” [WordPress.org].

---

Disclaimer: This guide is based on current best practices as of 2024. Always verify with official documentation (e.g., Google Search Central, WordPress.org) for updates.