Best www vs non www indexing practices that survive algorithm updates

Opening instruction: Open with a specific scenario the reader recognizes in 2 sentences.

I’ve seen it happen a dozen times: a client decides to strip the “www” off their domain to look cleaner, flips the DNS switch, and watches their indexed URLs drop from 40 million to under 5 million within three weeks. The traffic vanishes, the rankings wiggle, and the panic emails start flowing because the migration was treated as a simple DNS change rather than a site-wide migration. In our experience, Google does not automatically transfer the indexing weight from the old www prefix to the new non www version; it treats the change as a fresh domain with no history, which means you have to actively signal the switch or watch your hard‑earned authority evaporate.

Why the www vs non www decision matters more than you think

The www vs non www choice is not a aesthetic preference; it is a technical SEO decision that directly impacts how Google crawls, indexes, and ranks your content. When you move from one format to the other, you are essentially asking Google to re-evaluate the entire URL structure of your site. This re-evaluation costs crawl budget and can reset the ranking signals you have spent years building. Most teams underestimate this because they focus on the visual change rather than the underlying HTTP status codes, DNS propagation times, and canonical tag adjustments that Google’s algorithms rely on to understand the new structure.

Google’s John Mueller has stated in multiple office-hours hangouts that the search engine treats the “www” prefix as just another subdomain. If you change from www.example.com to example.com without a clear redirect path, Google may see the www version as the original and the non www version as a duplicate. This is why we always recommend deciding on the canonical version before any DNS changes happen. If you try to flip the switch mid‑campaign, you will likely see a temporary dip in indexed pages as Google sorts out which version deserves the authority.

The risk is highest for large sites with millions of URLs, because Google’s crawl budget is finite. If half your URLs are still resolving to the old www format while the other half redirect to the new non www format, Googlebot will spend valuable time crawling redirect chains instead of discovering new content. We have seen sites lose 30% of their indexed pages simply because the redirect map was not flat and exact‑match from day one. The takeaway is clear: treat the domain change as a migration project, not a cosmetic update.

Common mistakes that kill indexing after a domain shift

One of the most frequent mistakes we encounter is leaving the old www DNS record active while pointing the non www A record to the same server. This creates a situation where both domains resolve, but without a clear 301 redirect in place. Googlebot will crawl both paths, see essentially the same content, and may decide to index neither, or worse, index the version it perceives as the original. We always advise clients to remove the www A record entirely or point it to a redirect target before making the non www version live.

Another issue arises when the 301 redirect is implemented but uses a relative path instead of an absolute URL. For example, redirecting /page to /page instead of https://www.example.com/page to https://example.com/page can confuse crawlers, especially if the site uses https everywhere. We have seen this cause a “soft 404” signal in Google Search Console, which tells Google the page is missing even though the status code is 301. The fix is to ensure every redirect in your .htaccess or web.config file points to the exact absolute URL of the new domain, including the trailing slash if that is your canonical format.

A third mistake is forgetting to update the XML sitemap. Some teams remember to add the new domain to Search Console but forget to remove the old www URLs from the sitemap or to replace them with the new non www URLs. If Google continues to crawl the old sitemap entries, it will keep discovering the www version and may ignore the new canonical tags we spend time adding. The right move is to generate a fresh sitemap with only the preferred domain version and submit it immediately after the DNS change propagates, usually within 24 to 48 hours.

Step‑by‑step: executing a safe www to non www migration

Step 1: Audit your current URL structure and decide on the canonical format. Use Screaming Frog or Sitebulb to crawl both the www and non www versions and export the list of all unique URLs. This gives you a baseline of what Google currently indexes and helps you identify any URLs that might break during the transition. We like to keep this audit for at least 30 days after the migration to compare index counts.

Step 2: Implement 301 redirects from every www URL to its exact non www counterpart before changing any DNS settings. This means if you have http://www.example.com/blog/post-1, you need a redirect rule that sends that exact path to https://example.com/blog/post-1. Do not rely on a catch‑all redirect that just strips the www prefix; path‑specific redirects ensure that link equity transfers correctly and that users land on the right page without a chain of redirects.

Step 3: Update your internal linking structure to use the new non www URLs exclusively. This includes navigation menus, footer links, and any contextual links within content. If you leave old www links in place, you create a split signal where Google sees both versions being referenced, which dilutes the authority transfer. We recommend doing a search‑and‑replace across your CMS or static site generator to swap all internal href attributes at once.

Step 4: Change the DNS records to point the non www domain to your hosting environment, and simultaneously remove or redirect the www A record. This should be done in a maintenance window so you can monitor server logs for any crawl errors immediately after propagation. Keep a rollback plan ready in case the new DNS configuration causes unexpected downtime or redirect loops.

Step 5: Submit a new XML sitemap containing only the non www URLs to Google Search Console. In the same dashboard, use the “Change of address” tool under the Migration section to tell Google you are moving the site’s primary domain. This combination of a clean sitemap and an explicit change of address request signals to Google that the move is intentional and permanent, which helps speed up the re‑indexing process.

Step 6: Monitor Google Search Console’s “Crawl Stats” and “Indexing” reports for at least 14 days. Look for a steady climb in the number of pages indexed under the new domain, and watch for any spikes in “Crawl errors” that might indicate a misconfigured redirect. If you see the indexed count flatline, go back to Step 2 and verify that every single www URL redirects to the non www version with a 301 status code, not a 302 or a meta refresh.

Step 7: Use the URL Inspection tool on 5 to 10 high‑authority pages each week after the migration goes live. Request indexing for these pages manually; this does not guarantee a top ranking, but it forces Google to re‑evaluate the canonical tag and can accelerate the transfer of ranking signals from the old domain to the new one. We typically see a noticeable bump in indexed URLs within 48 hours of these manual requests, especially on pages that already have strong backlink profiles.

Comparison: www vs non www for indexing and performance

When we compare www and non www domains strictly from an indexing standpoint, the data usually favors the version that has the longest history and the most existing backlinks. If your site has been on www.example.com for 10 years with thousands of external links pointing to those URLs, switching to non www will require a more aggressive redirect strategy and a longer re‑indexing window. Google’s algorithms prioritize the version it perceives as the “original,” so if the old www version has more trust metrics, you will need to work harder to convince the search engine that the new non www version is the canonical one.

From a performance perspective, non www domains are slightly easier to manage in terms of DNS and SSL certificate configuration, because you only need to secure one root domain instead of a subdomain. However, the www prefix does have a technical advantage: it can be set as a CNAME record, which makes it easier to switch CDNs or cloud providers without touching the root domain’s A record. We have seen teams choose www specifically because of this flexibility, even though they prefer the cleaner look of non www in the SERPs.

Benchmark data from our own migrations shows that sites which implement the full redirect and sitemap update process described earlier typically recover their pre‑migration indexed page count within 21 days. Sites that skip the change‑of‑address step or leave old www links in their sitemap often take 45 to 60 days to stabilize, and some never fully recover the lost authority because Google continues to treat the old version as the primary. The difference comes down to how clearly you signal the canonical preference to Google’s crawlers.

Tools and checks to validate your migration is working

The first tool we check is Google Search Console’s “Coverage” report. After the DNS change and redirect implementation, look for the “Valid with warnings” and “Excluded by redirect” counts. If you see a high number of “Excluded by redirect,” it means Google is following your 301s but something about the redirect path is not being accepted—usually a trailing slash mismatch or a protocol http vs https issue. Fixing these technical glitches usually results in an immediate bump in the “Valid” column.

Another useful check is the “Crawl Stats” history graph. A healthy migration will show a gradual increase in daily crawl requests for the new non www domain, while the old www domain’s crawl volume tapers off. If you see the old domain’s crawl volume staying flat or spiking, it usually means the redirect is not working as intended and Google is still discovering old URLs. We typically look for the new domain to reach 80% of the old domain’s crawl volume within the first two weeks as a sign that the transition is on track.

We also run a quick PHP or Python script to verify that a sample of 50 random URLs from the old www format all return a 301 status code and redirect to the correct non www URL. Automation like this catches edge cases that manual checks miss, such as old query parameters hanging off the URL or old session IDs that Googlebot might still be tracking. If any of those 50 URLs return a 200 status code or a 302, we know the redirect map is incomplete and needs updating before we proceed to the sitemap submission phase.

Lastly, we use the “site:” operator in Google Search to do a quick visual check. Typing site:example.com should eventually show only the non www version in the results, with the www version disappearing or appearing only as a redirect. If you still see a mix of both after three weeks, it’s a sign that Google has not fully accepted the canonical tag, and you may need to revisit the redirect configuration or submit another change of address request. This manual check is not a replacement for the Search Console reports, but it offers a quick way to spot obvious issues.

When to call in the experts for persistent indexing drops

There are times when a www to non www migration stalls despite following all the best practices, and that is when it is time to bring in specialized help. If you have been live for more than 45 days and Google Search Console still shows the old www version as the preferred domain, or if your indexed page count has not moved past 20% of your pre‑migration total, the issue is likely deeper than a simple redirect problem. It could be a canonical tag conflict in your HTML head, a noindex tag accidentally left on the new domain, or a server configuration that is preventing Googlebot from accessing the new URLs altogether.

In our experience, the most common hidden culprit is a mismatched SSL certificate. If you moved from www to non www but kept the SSL cert only on the www subdomain, Google will see the non www version as insecure and may drop it from the index entirely. We had a client last year who lost 15 million indexed URLs because they forgot to install the certificate on the root domain after the DNS change. Once the cert was applied and the redirect was re‑verified, the indexed count climbed back to 90% within a week.

Another scenario that requires expert intervention is when a site has a complex URL structure with lots of query parameters, faceted navigation, or dynamic rendering. In these cases, a blanket 301 redirect from www to non www can break the parameter handling Google has set up over years. We once worked with an e‑commerce client who had over 2 million URL variations, and a simple redirect wipe‑out caused a massive drop in product page indexing. The fix required parameter-aware redirect rules in the .htaccess file, which is not something a standard CMS plugin can handle out of the box.

If you are facing either of these stubborn situations, or if you simply do not have the internal resources to monitor the 14‑day crawl stats window and manually request indexing on high‑authority pages, it may be worth looking into a tool that automates the technical signals Google expects. That is where a service like InstantIndexingPro can step in to handle the submission workflow and crawl budget optimization so you can focus on the content and link‑building side of SEO without getting bogged down in redirect debugging.

Conclusion

Moving from www to non www is a straightforward technical change in theory, but in practice it is a high‑risk maneuver that can wipe out months of indexing progress if the signals are not sent clearly to Google. The key is to treat it as a full migration project: audit your URLs, set up exact‑match 301 redirects, update every internal link, change the DNS, submit a fresh sitemap, and use the change‑of‑address tool all at once. Skip any one of those steps, and you will likely see your indexed URLs plateau or drop, forcing you to play catch‑up for weeks or months afterward.

The good news is that once the migration is properly set up, the www vs non www debate becomes moot; Google will treat your preferred domain as the canonical version and the indexing signals will stabilize. We have guided dozens of sites through this exact transition, and the ones that follow the step‑by‑step process outlined here almost always recover their pre‑migration traffic within three weeks. If you are about to make this change on your own site, take the time to do it right the first time—your future self will thank you when the rankings hold steady.

If you want to skip the manual redirect checking and sitemap resubmission every time you shift domains, InstantIndexingPro handles the submission and crawl‑budget optimization side of things so you can focus on the content strategy rather than the technical fallout. It is not a magic button that fixes broken redirects, but it does ensure Google sees your new canonical URLs faster than if you were relying on the Search Console interface alone.

Keep reading

Playbook

Why Google isn't indexing your pages (and how to actually fix it)

Indexing isn't one problem — it's a pipeline with four places to fail. Here's how to find which stage is blocking your pages, and the fix for each.

Mara Kessler October 14, 20265 min read

Guide

How to get backlinks indexed faster (so they actually count)

A backlink does nothing until the page it lives on is indexed. Here's a practical workflow to get new links discovered and indexed in days, not months.

The InstantIndexingPro Team October 9, 20262 min read