WWW vs Non-WWW Splitting Your Site? How to Fix It

2. What a WWW vs Non-WWW Split Actually Means

Quick Answer: A www vs non-www split happens when both www.yoursite.com and yoursite.com load your website without one redirecting to the other. Your browser, Google, and your analytics all see two different addresses for the same pages — so every signal that should build one site gets divided between two.

The “www” in front of a domain is technically a subdomain — a label sitting in front of your real domain name. The version without it, like zenweb.my, is called the bare or naked domain. Both can point to the same server and serve the exact same pages, but they are still two separate web addresses. As Mozilla’s developer documentation puts it, one domain name represents one single server — so you need to decide which one is the official, or canonical, version.

The problem is that on a fresh install or after a careless migration, both often answer at once. Two things end up true at the same time:

• Both versions load. Visitors reach your site whether they type www or not — which feels fine until you see what it does behind the scenes.
• Neither one is the boss. Without a redirect, no version is marked as the real one, so search engines are left to guess and often index both.

A tidy version choice is one of the small foundations of a properly built website: invisible when it is right, quietly expensive when it is wrong.

3. Why a WWW vs Non-WWW Split Quietly Costs You

Quick Answer: A split site divides everything that should add up. Google can index both versions as duplicate content, backlinks point to two URLs instead of one, and your analytics undercount by spreading sessions across two hostnames. None of it is dramatic on its own — which is exactly why it goes unnoticed for months.

The damage is quiet because your site still works. Nobody complains, nothing breaks, and the numbers just sit slightly lower than they should. The biggest hit is to your SEO: when the same page earns links and ranking signals under two addresses, Google splits the credit instead of stacking it on one strong URL.

Notice the last row. If a campaign points at the non-canonical version, every click takes an extra redirect hop before the page loads. That is small on its own, but it slows the landing experience ad platforms score you on.

4. How to Check If Your Site Is Split

Quick Answer: Type your domain both ways — with and without www — and press enter on each. If both load and the address bar does not snap to a single version, you have a split. While you are there, check that the http:// version forwards to https://. Two minutes tells you everything.

You do not need a tool for the first check — your browser is enough. Run through these quick tests:

• Type both versions. Enter www.yoursite.com, then yoursite.com. Watch whether one rewrites to the other or both stay as typed.
• Check the padlock too. Try http:// in front of each. It should jump to https://. If it does not, you may also be seeing a “Not Secure” warning on your website that needs sorting at the same time.
• Look at your own links. Hover over your menu and footer links. If some use www and some do not, your internal links are mixed — a milder form of the same split.

If every version lands on one consistent address over https, you are already clean and can stop here. If not, the next question is which version to keep.

5. WWW or Non-WWW — Which Should You Choose?

Quick Answer: For SEO it makes no real difference — Google ranks both equally once you pick one and redirect the other. The choice comes down to technical needs: www gives more flexibility with cookies, subdomains, and CDNs; non-www is shorter and cleaner to share. Most small Malaysian business sites are fine either way.

This is the part people overthink. There is no ranking bonus hiding in one option — Mozilla’s documentation calls the decision largely a matter of preference, as long as you commit to one. For a well-built business website, the practical differences look like this:

Our rule of thumb for Malaysian small businesses: pick non-www for simplicity unless you already run subdomains or a CDN that prefers www. Either way, the winner is whichever you can apply consistently.

6. How Often This Happens — What We See in Audits

Quick Answer: In website audits across Malaysian SMEs, a www vs non-www problem is one of the most common technical faults we find. Most sites show some version of it — both addresses loading, a redirect pointing the wrong way, or internal links that mix the two — and owners are almost never aware.

When we run a technical check as part of a website build or care plan, the version split shows up again and again. Here is how often each symptom appears in our audit sample. Sites can show more than one, so these do not add to 100%.

The most common fault is not a missing redirect at all. It is mixed internal links, where the site owner or an old plugin used both forms over the years. That is why the fix has two halves: the redirect, and the cleanup after it.

7. How to Fix It — Pick One and 301 Redirect

Quick Answer: Choose your canonical version, then send every other version to it with a permanent 301 redirect. Set the preferred address in WordPress, add the redirect at the server or with a plugin, force HTTPS, then update Search Console, your sitemap, and internal links. Done once, it holds for good.

Work through these steps in order. Back up first — a redirect touches how every URL on the site resolves, so you want a safety net if something is misconfigured.

1. Back up your site. Take a full file and database backup before you touch anything. If a rule goes wrong, you restore in minutes — the same habit behind a solid website backup and restore plan.
2. Pick your canonical version. Decide on www or non-www using the table above, and commit to it everywhere from here on.
3. Set it in WordPress. Go to Settings → General and make both WordPress Address and Site URL use your chosen version, with https.
4. Add the 301 redirect. Send the other version to your canonical one — through your host’s control panel, a redirect plugin, or an .htaccess rule. Use a permanent 301, never a temporary 302.
5. Force HTTPS as well. Make sure http:// versions of both www and non-www all land on the secure canonical address in one hop, not a chain.
6. Update Google Search Console. Confirm the canonical version is the one submitted and check the Pages report for duplicate coverage as it clears.
7. Fix internal links and the sitemap. Update menu, footer, and in-content links to the canonical version, and regenerate your XML sitemap so it lists only that version.
8. Test and clear cache. Type every version again to confirm one clean hop, then clear your caches so visitors see the corrected setup.

It is the same routine we follow when we move a site. After a host migration without downtime, or when syncing a staging and live site that drifted apart, the version and redirect rules are the first thing we lock back down.

8. What Changes After You Fix It

Quick Answer: Once the redirect is live, Google gradually drops the duplicate version and consolidates all the ranking signals onto your chosen URL. It is not instant — it follows Google’s crawl schedule — but within a few weeks most sites see duplicates disappear and traffic settle on one address.

Nothing changes the second you save the redirect, and that is normal. Search engines need to re-crawl your pages and follow the 301 before they merge the two versions. A typical recovery on our client sites looks like this. It is an illustrative timeline — actual speed depends on how often Google crawls you.

The payoff shows up quietly: rankings firm up, analytics stop double-counting, and any campaign traffic finally lands on one clean URL — which keeps your Google Ads landing pages pointing exactly where they should.

9. Mistakes That Break the Redirect

Quick Answer: The fix is simple but easy to get wrong. The usual slips are using a temporary 302 instead of a permanent 301, chaining redirects until they loop, forgetting HTTPS, and leaving internal links pointing at the old version. Each one either weakens the fix or breaks the site outright.

Before you call it done, check you have not fallen into one of these:

• Using a 302 instead of a 301. A 302 is temporary and does not pass ranking signals the way a permanent 301 does. Always use a 301 for a version change.
• Creating a redirect loop. Conflicting rules — one in the host panel, one in a plugin — can bounce a URL back and forth until the browser gives up. That is a classic redirect loop error, and it can take the whole site down and stop it loading.
• Forgetting HTTPS. Redirecting www to non-www but leaving http alive just creates a new split. Every combination should end on the secure canonical URL.
• Leaving old internal links. If your own pages still link the non-canonical version, every click fires an extra redirect hop and muddies the cleanup.

10. Conclusion

A www vs non-www split is one of those problems that never announces itself. The site works, visitors get through, and yet your rankings, backlinks, and reporting are all running at half strength because Google sees two sites where there should be one.

The fix is simple: pick one version, send everything else to it with a permanent 301 over https, then tidy your internal links, sitemap, and Search Console. Do it once and it holds. If you would rather have it checked and fixed properly, along with the rest of your technical setup, ZenWeb handles this for Malaysian businesses as part of our web design and maintenance service.

11. Frequently Asked Questions

1. Is www or non-www better for SEO?

Neither is better for SEO. Google ranks both equally as long as you pick one version, redirect the other to it, and stay consistent. The real ranking risk is running both at once without a redirect, which splits your signals — not the www or non-www choice itself.

2. Will fixing a www vs non-www split hurt my rankings?

No — a proper permanent 301 redirect preserves your ranking signals and consolidates them onto one URL, which usually helps. Rankings only suffer if you use a temporary 302, create a redirect loop, or forget to update internal links. Done correctly, the fix is safe.

3. How long until Google merges the two versions?

It is gradual, not instant. Google has to re-crawl your pages and follow the 301 before it drops the duplicate. Most sites see duplicates clear within a few weeks and signals fully consolidate by about six to eight weeks, depending on how often Google crawls the site.

4. Do I still need the redirect if I have a canonical tag?

Yes. A canonical tag is a hint to search engines, while a 301 redirect actually sends every visitor and crawler to one address. The strongest setup uses both — a 301 for the redirect and canonical tags that point to the same version — so humans and search engines never see the split.

5. Does the www vs non-www choice affect my SSL certificate?

It can. Your certificate should cover both the www and non-www versions so no visitor hits a security warning. Once the certificate covers both, redirect every http and non-canonical version to your single secure address, and confirm the padlock shows on the version you chose.