Every website can technically be accessed through two versions of its domain: one with "www" and one without. For example, www.example.com and example.com may both load the same content. While this seems harmless, search engines can treat these as separate URLs. Without proper configuration, you may end up with duplicate content, split backlinks, and diluted ranking signals. Choosing a preferred version and redirecting the other is a fundamental technical SEO task. This guide explains how to redirect www to the non-www version safely and effectively.
How AAMAX.CO Handles Technical SEO Configurations
Redirects seem simple, but small mistakes can cause redirect loops, lost traffic, or indexing problems. AAMAX.CO is a full-service digital marketing company providing web development, digital marketing, and SEO services worldwide. Their developers and technical specialists configure domain redirects, HTTPS, canonical tags, and server settings correctly from the start. Through their SEO services, they audit existing setups, resolve duplicate domain issues, and ensure that every signal points search engines to a single, authoritative version of your website.
Why Choosing One Version Matters
When both versions of your domain are accessible, search engines may index both, splitting authority between them. Backlinks pointing to the www version and others pointing to the non-www version will not fully consolidate. Analytics data may also become fragmented. By selecting one canonical version and redirecting the other with a permanent 301 redirect, you consolidate ranking signals and present a consistent experience to users and crawlers.
WWW Versus Non-WWW: Does It Matter for Rankings
From a ranking perspective, neither version is inherently better. Search engines treat them equally as long as you choose one and remain consistent. Non-www domains are shorter and cleaner, which many brands prefer. Www domains can offer some technical flexibility with cookies and DNS configuration for large sites. The key is consistency, not the choice itself.
Use a 301 Permanent Redirect
A 301 redirect tells search engines that a page has permanently moved, passing nearly all ranking signals to the destination URL. Avoid using 302 temporary redirects for this purpose, as they signal that the change is not permanent. Your redirect should forward every URL on the www version to its exact equivalent on the non-www version, preserving paths and query strings.
Redirecting With Apache
On Apache servers, redirects are commonly configured in the .htaccess file. Enable the rewrite engine, then add a condition that checks whether the host begins with www. If it does, rewrite the request to the non-www host using the same path and return a 301 status. Always back up your .htaccess file before editing, as syntax errors can take your site offline.
Redirecting With Nginx
On Nginx, create a separate server block that listens for the www version of your domain. Inside that block, return a 301 redirect to the non-www domain while preserving the requested URI. Then configure your main server block to serve the non-www domain. After saving changes, test the configuration and reload Nginx.
Redirecting Through Hosting Platforms and CDNs
Many hosting platforms, website builders, and content delivery networks provide built-in settings for domain redirects. Modern hosting providers often let you assign a primary domain and automatically redirect alternate versions. CDNs typically offer redirect rules that can handle this at the edge, improving speed. These options are often simpler and less error-prone than editing server files manually.
Do Not Forget HTTPS
Your redirect strategy should also include HTTPS. Ideally, all variations, such as http with www, http without www, and https with www, should redirect directly to https without www in a single step. Avoid redirect chains, where a URL redirects multiple times before reaching its final destination, as they slow down page loads and can dilute signals.
Update Internal Links and Canonical Tags
After implementing the redirect, update internal links to point directly to the preferred version. Ensure canonical tags reference the non-www URLs. Update your XML sitemap to include only the preferred version. These steps reinforce your choice and reduce reliance on redirects.
Configure Search Console
Verify your preferred domain in Google Search Console, ideally using a domain property that covers all variations. Submit your updated sitemap and monitor coverage reports for errors. Watch for changes in indexing as search engines process the redirects.
Test Your Redirects
Use browser testing and HTTP header checkers to confirm that each variation returns a single 301 redirect to the correct destination. Test multiple pages, not just the homepage, to ensure paths are preserved. Check for redirect loops, which occur when rules conflict and send requests back and forth.
Common Mistakes to Avoid
A frequent mistake is redirecting every www URL to the homepage instead of its matching page, which wastes link equity and frustrates users. Another is forgetting subdomains or staging environments that also need rules. Some site owners apply redirects at both the server and CDN level, creating conflicts or chains. Finally, avoid changing your preferred version repeatedly, since each switch forces search engines to reprocess your entire site.
Final Thoughts
Redirecting www to non-www is a simple but essential SEO task. Choose one version, implement permanent 301 redirects that preserve paths, include HTTPS in your strategy, update internal links and canonical tags, and verify everything in Search Console. A clean, consistent domain setup consolidates authority and creates a stronger foundation for search performance.
Want to publish a guest post on aamconsultants.org?
Place an order for a guest post or link insertion today.