Seotoolsdesk.com
Bulk up to 100 • Detect inconsistent rules

WWW & Non-WWW Redirect Checker

Paste domains or URLs — we’ll test both variants (www and non-www) and show what each resolves to.

Paste up to 100 domains/URLs (one per line)
Tip: if you paste a URL with http://, we’ll test in http. Otherwise default is https.

Results

Domain Preferred Non-WWW WWW Issues
Run a check to see results here.
“Both serve” = both hosts return 2xx without redirect → duplicate host issue.

What a “correct” setup looks like

You usually want one canonical host (WWW or Non-WWW) and the other should redirect in 1 hop.

  • OK both variants resolve to the same final host
  • Warning both serve content (no redirect)
  • Error inconsistent finals, loops, timeouts, TLS/DNS issues
Canonical host check

WWW & Non-WWW Redirect Checker: fix duplicate hosts fast

This tool verifies how a website behaves on www and non-www versions. You paste up to 100 domains or URLs, and it tests both host variants, follows redirects, and shows the final destination — so you can confirm the canonical host setup without guesswork.

How the checker works

For every input, the tool generates two requests: https://example.com/ and https://www.example.com/ (or http if you pasted an http URL). Each variant is checked separately: we record the initial status code, follow each redirect step, count hops, and capture the final URL and final status. That side-by-side view makes problems obvious within seconds.

Why WWW vs Non-WWW redirects matter for SEO

Search engines treat example.com and www.example.com as different hosts. If both return 200 and serve content, you create duplicates, split link equity, and send conflicting canonical signals. The safest setup is simple: choose one canonical host (WWW or Non-WWW) and redirect the other to it with a clean permanent redirect (typically 301) in one hop.

A correct redirect rule improves crawling consistency, prevents “double indexing”, and makes migrations, CDN changes, and HTTPS rollouts much less risky.

What issues you can spot instantly

  • Both serve: www and non-www return 2xx without redirect → duplicate host problem.
  • Inconsistent finals: each variant lands on a different final host/path.
  • Too many hops: long redirect chains that slow bots and waste crawl budget.
  • Loops: redirects that circle back and never resolve.
  • Failures: DNS/TLS/timeout errors that prevent crawling.

Best times to use this tool

Run this check after launch, after switching hosting or CDN, during HTTPS enforcement, and before/after migrations. If rankings drop, indexing slows down, or you see both hosts indexed in Google — start here. HTTP behavior is the foundation: once the canonical host is stable, everything else (sitemaps, canonicals, internal links) becomes easier to control.

Fast workflow tip

Check a few representative URLs: homepage, one deep URL, and a typical category/article page. Your goal is not to “run tools because they exist”, but to confirm one fact: do both hosts resolve to the same final destination, cleanly, in minimal hops. Export results when you audit a batch, and you’ll have a clear action list for redirects and host canonicalization.

FAQ

Why check both www and non-www?

Search engines treat www.example.com and example.com as different hosts. Without a redirect between them, both can be indexed separately, splitting link equity and producing duplicate content. Checking both variants ensures users and bots reach a single canonical version.

What is considered the correct redirect setup?

A correct setup means one variant consistently redirects to the canonical host using a permanent redirect (usually 301) in a single hop. Serving both hosts with 200 OK responses instead of redirecting produces conflicting canonical signals.

Which version is better for SEO: www or non-www?

SEO impact is the same. What matters is consistency: internal links, canonical tags, redirects, and sitemaps must all point to the same host. Both strategies perform equally well when implemented properly.

What does “both serve” mean?

“Both serve” indicates both host variants return 200 OK responses without redirecting to each other. This creates duplicate host content and requires resolving which version should be canonical, then redirecting.

Why do redirect chains cause issues?

Long chains waste crawl budget, slow down users, and increase the risk of timeouts, especially through CDN layers. A canonical redirect should be a clean one-hop transition from non-canonical host to canonical host.

Why do I see status code 0?

Status 0 indicates a network-level failure rather than an HTTP response. Typical causes include DNS failures, TLS handshake errors, CDN blocks, firewall restrictions, or dropped TCP connections.

Does fixing host redirects solve all duplicate URL issues?

No. This tool solves host-level duplication only. Path-level trailing slashes, parameters, uppercase paths, and inconsistent canonical tags still need review separately. Host canonicalization is just the first step.

Do CDN settings affect redirect behavior?

Yes. CDNs can override origin redirect rules and introduce loops or inconsistent behavior. Many canonical host issues occur because redirect logic exists both at CDN and server layers. Always test after changing DNS/CDN rules.