Loading...
Loading...
Ready
Enter a domain on the left and run the test. Results stream in here.
Paste any URL on your domain. We derive the http, https, www, and non-www variants automatically.
We request each variant without following redirects, recording the status code and Location header so we can see exactly where each one points.
You get a matrix showing which variants redirect, where they land, and whether they all consolidate to one single canonical URL.
Canonicalization is making sure every variant of your homepage URL — http vs https, www vs non-www, and with vs without a trailing slash — resolves to one single preferred version via 301 redirects. Without it, search engines can treat http://example.com, https://www.example.com, and https://example.com as separate pages, splitting ranking signals across duplicates.
If both https://www.example.com and https://example.com return 200 OK without redirecting to one another, Google sees two copies of the same content. Link equity, crawl budget, and ranking signals get diluted between them. Picking one (it doesn't matter which) and 301-redirecting the other consolidates everything onto a single authoritative URL.
Yes. Every http:// request should return a 301 redirect to the https:// equivalent. Serving content on both http and https creates duplicate URLs and a security warning. The ideal chain is: http://www → https://www (or http://non-www → https://non-www) in a single 301 hop, landing on your chosen canonical host.
A rel=canonical tag is a hint inside the HTML that suggests the preferred URL. This audit tests something stronger and more reliable: the actual server-side redirect behavior of your domain variants. Redirects are an enforcement; canonical tags are a suggestion. You want both aligned — redirects to consolidate variants, and self-referencing canonicals on the final URL.
Ideally one. A request to http://www.example.com should reach https://example.com (or your chosen canonical) in a single 301. Chains like http→https→https-www→https-non-www waste crawl budget, slow page loads, and can leak a small amount of link equity per hop. This tool reports the redirect status returned by each variant so you can spot multi-hop chains.
It can. For directory-style URLs, /page and /page/ may be served as two different URLs unless one redirects to the other. Inconsistent internal linking to both forms creates duplicates. Pick one convention site-wide and 301-redirect the other. This tool flags when trailing-slash variants behave inconsistently.
From an SEO standpoint, www vs non-www makes no ranking difference — choose based on preference and technical constraints (some CDN/cookie setups favor a subdomain). What matters is consistency: pick one, redirect all other variants to it with 301s, use it in your canonical tags, sitemap, and internal links, and declare it in Search Console.