WWW Redirect Checker

Why WWW vs non-WWW matters

Technically, example.com and www.example.com are different hostnames, and if both serve the same content without one redirecting to the other, search engines can treat them as duplicate content. This tool checks both versions of a domain, follows any redirects, and reports whether they correctly converge on a single canonical version.

Reading the two results side by side

Each version's final destination URL is shown after following any redirects, plus the HTTP status code returned along the way - comparing the two final URLs is how you confirm whether both versions actually converge on the same canonical page, or whether they're serving as two separate, competing versions of your site.

What a good result looks like

Both the bare and www versions being reachable and ending at the identical final URL is the healthy configuration - it means one version is correctly redirecting to the other (or a canonical tag is otherwise resolving the ambiguity), so search engines see a single, consistent version of your site rather than two competing ones.

What to do if they diverge

If both versions are reachable but end up at different final URLs, that's a sign your server configuration needs a redirect rule added - typically a 301 redirect from whichever version you don't want indexed to the one you do, configured at the web server or DNS/CDN level depending on your hosting setup.

الأسئلة الشائعة

Which version should I redirect to - www or non-www?

Either works fine for SEO as long as you pick one and redirect consistently - it is a matter of preference, not a ranking factor. The important part is that one version always redirects to the other.

What if only one version is reachable?

That is also fine and common - some sites intentionally only configure one version (usually the non-www one) and never set up the other, which avoids the duplicate-content question entirely.

What does it mean if both versions are reachable but lead to different final URLs?

It means your site is currently serving two separate, un-unified versions - search engines may index both as distinct pages with split ranking signal. Add a 301 redirect from one version to the other to fix this.

Is this the same as checking HTTP vs HTTPS?

No - this checks the www/non-www hostname question specifically. A similar duplicate-content risk exists between HTTP and HTTPS versions of a URL, which is a separate configuration to verify.

Does the redirect type (301 vs 302) matter here?

For SEO purposes, yes - a 301 (permanent) redirect passes ranking signal to the destination URL, while a 302 (temporary) redirect is intended for short-term redirects and search engines treat it differently. Check your server configuration if you need the 301 behavior specifically.