Web

WWW vs Non-WWW Redirection Test

Canonical Domain

Test domain redirection

Enter a domain to check redirects across http/https and www/non-www variants.

Tool features

Comprehensive domain canonicalization and redirect analysis
4 checks

Canonical Check

Identify the preferred (canonical) domain version

Redirect Chain

View full redirect paths for all variants

Loop Detection

Detect and alert on redirect loops

SEO Friendly

Ensure proper canonicalization for search engines

What is domain canonicalization & how it works

Why www/non-www and http/https must converge

Every site is reachable as up to four variants — http/https × www/non-www. Search engines treat each as a separate URL, so unless they all funnel to one canonical address you can split ranking signals, duplicate content, and confuse analytics.

The fix is a consistent chain of 301 redirects from every variant to a single preferred host, ideally over HTTPS. This test requests all four variants, follows each redirect chain, detects loops, and reports whether they converge on one canonical host.

Canonical host
The single preferred version (e.g. https://example.com) all variants point to.
301 redirect
A permanent redirect that passes ranking signals to the target URL.
Redirect loop
A misconfiguration where variants redirect to each other endlessly.

How to use this tool

Check a domain's redirects in four steps
1
Enter a domain
Type a domain, e.g. example.com — no scheme needed, all four variants are tested.
2
Run the test
Click Test Redirection to request http/https and www/non-www and follow every redirect chain.
3
Review the chains
See each variant’s redirect path, the canonical host, and any loops or failures.
4
Fix the gaps
Add 301 redirects from every variant to your one canonical HTTPS host, then re-test.

Related tools

Keep debugging with tools from the same suite
3 tools
Website Redirect Checker
Check website redirects and status codes for any URL. Detect multi-level redirects and view final destination
HTTP to HTTPS Redirection Test
Check whether a website properly redirects HTTP traffic to HTTPS, detect redirect loops and view the redirect chain
HTTP Status Checker
Check HTTP status codes and response details for any URL with detailed analysis

Frequently asked questions

Common questions about domain canonicalization
5 Q&A

Either works — what matters is picking one as canonical and redirecting the other to it. www can have minor DNS/CDN advantages, but consistency is far more important than the choice itself.

Search engines treat www, non-www, http and https as separate URLs. If they resolve independently, ranking signals and crawl budget get split across duplicates. Redirecting all variants to one canonical URL consolidates that value.

Use a 301 (Moved Permanently) redirect. It tells search engines the move is permanent and passes ranking signals to the target, unlike a 302 (temporary) redirect which does not.

A redirect loop happens when variants redirect to each other endlessly (e.g. www → non-www → www), so browsers and crawlers never reach a final page. This test flags any variant that loops.

Yes. Redirect every http:// variant to its https:// equivalent as part of the same canonical chain, and pair it with HSTS so browsers upgrade automatically on future visits.