Neither www nor non-www has an inherent SEO advantage. Google treats https://www.example.com and https://example.com as different hostnames, so the important choice is to select one HTTPS version as your canonical origin and make every other variant resolve to it consistently.
For most sites, that means choosing either https://www.example.com or https://example.com, redirecting HTTP and the unchosen hostname with a single permanent redirect, and using the preferred form everywhere: canonicals, internal links, sitemaps, hreflang, structured data, campaign URLs and asset references.
As an Amazon Associate I earn from qualifying purchases.
Is www or non-www better for SEO?
No. Google does not award a ranking advantage to either hostname format. The SEO risk comes from allowing both versions to remain crawlable as separate URL sets, not from choosing one over the other.
www.example.com and example.com are separate hostnames. A page available at both addresses can look duplicated to crawlers, split signals between URLs and create inconsistent reporting in analytics and Search Console. Google recommends choosing one preferred (canonical) destination and using redirects from the alternatives.
Make the decision a product and infrastructure choice, then implement it consistently. A short non-www address may suit a consumer-facing brand. A www hostname can be convenient when the main site is treated as one subdomain alongside services such as api.example.com or app.example.com. Neither preference changes Google’s ranking rule.
What actually affects the SEO outcome
- One preferred HTTPS origin is used across the site.
- Every alternate protocol and hostname redirects directly to that origin.
- Preferred pages carry self-referencing
rel="canonical"tags. - Internal links, XML sitemaps, hreflang annotations, structured-data URLs, Open Graph URLs and absolute asset URLs all use the same origin.
- Search engines and users do not encounter redirect chains, mixed protocols or conflicting canonical signals.
www versus non-www: practical differences
The table below describes operational and branding trade-offs, not ranking benefits.
| Decision axis | www hostname | non-www (apex) hostname | SEO implication |
|---|---|---|---|
| Brand and memorability | The hostname visibly uses the conventional www prefix. |
The address is shorter and omits the prefix. | Branding choice only; Google gives neither form an automatic advantage. |
| Subdomain flexibility | Already operates as a subdomain, which can be convenient when separating cookies or services. | Is the domain apex; other services normally use separate subdomains. | Choose the arrangement your infrastructure team can operate consistently. |
| DNS and hosting architecture | A conventional CNAME target is often available for www. |
Apex DNS may require provider-specific ALIAS, ANAME or CNAME-flattening support. | Confirm provider behavior before changing an established site. |
| Migration cost | Changing to or from this form requires redirects, link updates, testing and monitoring. | Changing to or from this form requires redirects, link updates, testing and monitoring. | For an established site, keeping the currently consistent host is usually the lower-risk option unless there is a strong reason to move. |
| Operational consistency | Must be used consistently in canonicals, sitemaps, links, hreflang, structured data and campaigns. | Must be used consistently in canonicals, sitemaps, links, hreflang, structured data and campaigns. | Consistency, not the spelling of the hostname, consolidates signals. |
Why HTTPS should be your canonical protocol
HTTP and HTTPS are different URL protocols, just as www and non-www are different hostnames. HTTPS should be the canonical version because Google treats protocol as a canonicalization signal and because encrypted delivery protects the connection.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Moving from HTTP to HTTPS is a URL migration, even when the hostname stays the same. A complete migration updates redirects, canonical tags, internal links and sitemaps. If you standardize both protocol and hostname at once, consolidate all four common variants:
http://example.com/http://www.example.com/https://www.example.com/https://example.com/
Each alternate should resolve directly to the selected HTTPS origin, preserving the path and appropriate query-string behavior. Avoid implementing one redirect for HTTP, another for www and a third for HTTPS; that creates a chain and adds latency.
Choose the canonical origin before changing anything
For an established site
Inventory the URLs that users, partners, campaigns and internal systems already publish. If one hostname is already used consistently and works with your DNS and TLS setup, retaining it avoids a needless migration. A hostname change should have a clear operational or product reason, because it requires redirects, link replacement, validation and monitoring.
For a new site
Pick the form that fits your naming and hosting model. Select www if treating the public site as a subdomain makes service separation, cookie scope or DNS management easier. Select non-www if the shorter address is more important and your DNS provider supports the required apex configuration.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Record the decision
Write the canonical origin in your deployment documentation, for example https://www.example.com or https://example.com. Use the same value in application configuration, redirect rules, sitemap generation and SEO templates so separate teams do not reintroduce the other variant.
How Google consolidates the variants
Permanent redirects
Google Search Central recommends server-side permanent redirects, such as HTTP status 301 or 308, when possible. A redirect tells browsers and crawlers that the alternate URL has moved and transfers users to the preferred destination.
Use one direct redirect per alternate URL. For example, if https://example.com/article is canonical, send http://example.com/article, http://www.example.com/article and https://www.example.com/article straight to that final URL. Do not send HTTP to www, then www to HTTPS, then HTTPS to the final hostname.
Canonical tags
Every preferred page should include a self-referencing tag such as:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →<link rel="canonical" href="https://example.com/article">The URL in the tag must use the chosen HTTPS origin and the page’s final path. Google describes a canonical declaration as a hint, not a rule, so it should agree with redirects, internal links and the sitemap rather than serve as the only signal.
Internal and discovery signals
Replace the old origin in navigation, contextual links, pagination, hreflang references, structured data, Open Graph metadata, feeds, JavaScript-generated absolute URLs and asset URLs. Generate the XML sitemap with preferred URLs only. A sitemap containing redirected or mixed-host URLs weakens the clarity of the migration.
Step-by-step setup
- Decide the canonical origin. Choose either
https://www.example.comorhttps://example.com. Do not publish both as equal destinations. - Prepare DNS. Point the chosen hostname to the production service. Configure the redirecting hostname as well so it can answer requests and return a redirect. For an apex domain, confirm whether your DNS provider requires ALIAS, ANAME or CNAME flattening; for www, confirm the CNAME target and any platform-specific restrictions.
- Configure TLS coverage. Obtain a certificate that covers the canonical hostname and every hostname that will receive HTTPS requests before redirecting. A request to
https://www.example.commust be able to complete TLS negotiation before the server returns its redirect. - Define direct permanent redirects. Configure the web server, load balancer, CDN or hosting platform to send HTTP
301or308responses from each alternate origin to the matching path on the canonical HTTPS origin. Preserve query parameters when they are needed for application behavior or campaign measurement, and deliberately remove tracking parameters that should not create separate indexable URLs. - Eliminate redirect chains. Test the rule order so a request goes from its original URL to the final HTTPS hostname in one hop. A chain such as HTTP → www → HTTPS → final host adds latency and gives crawlers more work.
- Add self-referencing canonicals. Update the page template so each indexable page names its final HTTPS URL, including the canonical host, path and the intended query-string policy.
- Replace absolute references. Update internal links, hreflang, structured data, Open Graph URLs, feeds and absolute asset references. Relative links can remain relative, but verify that they resolve under the canonical origin.
- Regenerate the sitemap. Include only final, preferred HTTPS URLs. Remove HTTP and unchosen-host entries, then submit the updated sitemap.
- Verify Search Console properties. Verify the relevant HTTP, HTTPS, www and non-www properties so you can inspect old and new URLs and monitor coverage. Do not use Change of Address for a www/non-www switch within the same domain; Google says to use canonical tags and/or redirects instead.
- Test and monitor. Check representative pages, redirects, assets and URLs with browser requests,
curl -I, URL Inspection and server logs before and after launch.
Testing the implementation
Check status codes and hop count
Run a header request against each origin and a representative path:
curl -I http://example.com/article
curl -I http://www.example.com/article
curl -I https://www.example.com/article
curl -I https://example.com/articleFor alternate URLs, expect a single 301 or 308 response with a Location header pointing to the canonical HTTPS URL. Request the final URL and expect a successful response, normally 200 for a live page. Repeat the test with a URL containing a meaningful query string to confirm your chosen parameter behavior.
Inspect the final page
- View the HTML and confirm the canonical tag exactly matches the final URL.
- Follow an internal link and verify it does not switch hostnames or protocol.
- Check hreflang and structured-data URLs for the same origin.
- Open images, stylesheets, scripts and feeds to catch mixed-content or redirect problems.
- Use Search Console URL Inspection on old and new examples to see which URL Google selected and whether the page is indexed.
Search Console, indexing and the transition period
A hostname or protocol change is not instantaneous. Google says a medium-sized site can take a few weeks or more for new URLs to replace old ones, and larger sites can take longer. Temporary visibility fluctuations during crawling and reprocessing are normal; they do not by themselves prove that the migration failed.
Watch the old and new properties for coverage changes, crawl errors, duplicate or alternate-page reports and unexpected canonical selections. Compare organic traffic and conversions in analytics by hostname, and inspect server logs for requests that still arrive at old URLs. Resolve broken redirects, loops, missing certificates and pages that return errors before interpreting ranking changes.
Keep redirects from the old origins for at least a year where practical. Google notes that longer retention can help users who follow old links and can preserve signal transfer. Do not remove redirects simply because the new URLs appear in the index.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common failure modes and fixes
Both hosts return a 200 response
Symptom: The same page loads at www and non-www without a redirect, and both forms appear in reports or external links.
Fix: Select one HTTPS origin and add a direct permanent redirect from the other hostname. Add self-referencing canonicals and update internal references and the sitemap.
HTTP redirects through several intermediate URLs
Symptom: A browser or crawler follows HTTP → www → HTTPS → final host.
Rank #4
Fix: Replace separate, competing rules with one rule per alternate origin that targets the final HTTPS URL. Test every variant after changing the order of server, platform and CDN rules.
The redirecting HTTPS host has no valid certificate
Symptom: Requests to the old HTTPS hostname fail with a certificate warning before the redirect can run.
Recommended Free Tools
Fix: Include the redirecting hostname in TLS coverage and deploy the certificate before enabling the redirect.
Canonical tags disagree with redirects
Symptom: A page redirects to one host but its HTML canonical points to another, or canonicals still use HTTP.
Fix: Generate canonicals from one canonical-origin setting and make every value match the final HTTPS URL. Remember that a canonical is a hint, so eliminate contradictory signals elsewhere.
The sitemap still lists old URLs
Symptom: Search Console receives a sitemap containing HTTP or unchosen-host URLs.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsFix: Regenerate the sitemap from the canonical-origin configuration, remove redirected entries and resubmit it.
Best Value
Search Console Change of Address is used for www/non-www
Symptom: An administrator attempts to submit a same-domain www/non-www switch through the Change of Address tool.
Fix: Do not use that tool for this case. Verify the relevant properties and rely on permanent redirects and consistent canonical signals.
Traffic appears to dip immediately after launch
Symptom: Visibility or reported clicks fluctuate during the first days or weeks.
Fix: Check crawl errors, redirect status, TLS, canonical selection, sitemap contents and server logs first. Google describes a migration transition of a few weeks or more for medium-sized sites, so assess the complete period rather than one day’s data.
Will changing from www to non-www hurt rankings?
A correctly implemented change is a URL migration, not an automatic ranking penalty. The risk is implementation failure: inaccessible redirect targets, chains, inconsistent canonicals, broken internal links, missing sitemap updates or prematurely deleted redirects. Because Google must crawl and process the new URLs, temporary fluctuations are possible while signals consolidate.
If the current hostname is stable and there is no compelling reason to change, leaving it in place avoids migration work. If you do change, launch all related updates together, verify one-hop redirects and monitor both old and new URL sets until the transition has settled.
A concise launch checklist
- One documented canonical origin:
https://www.example.comorhttps://example.com. - TLS certificates cover the canonical and redirecting hostnames.
- HTTP, www and non-www alternatives redirect directly with
301or308. - Paths and required query parameters are preserved correctly.
- Preferred pages use self-referencing HTTPS canonicals.
- Internal links, hreflang, structured data, Open Graph, feeds and assets use the preferred origin.
- The XML sitemap contains only preferred URLs.
- All relevant Search Console properties are verified; Change of Address is not used for a same-domain www/non-www switch.
- Representative URLs return one redirect hop and a final successful response.
- Redirects, indexing, crawl errors, logs and traffic are monitored for the transition and retained for at least a year where practical.
The Bottom Line
Use whichever hostname fits your brand and infrastructure, but make the choice unambiguous: canonical HTTPS pages, one-hop permanent redirects from every other variant, matching internal signals and sustained monitoring. Google does not prefer www or non-www; it prefers a site that consistently identifies one canonical URL.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
