WWW / non-WWW Checker: Check host variants
Free individual check · without registration
Compare the four start page variants of your domain with and without www as well as over HTTP and HTTPS. See where they redirect to and if a common target version emerges.
- www and non-www variants
- HTTP and HTTPS target version
- Redirect consistency
- Double 200s accessibility
- Preferred host version
| Variant | Status | Final URL | Host | Assessment | Note: |
|---|---|---|---|---|---|
| — | |||||
www or non-www: Set up a consistent domain version
What the WWW Checker actually retrieves
From the entered domain, the tool forms four addresses: http://example.org, http://www.example.org, https://example.org and https://www.example.org. are compared to answers and forwardings of the start page. An entered underside path is not checked. The test does not control all subpages, canonical tags, sitemap entries, or internal links of your site.
Which host version is better for SEO?
What is crucial is a permanently consistent choice. Select the already established variant and match redirects, internal links, canonicals and sitemap. Two achievable variants are not automatically a punishment; they are an occasion to check the preferred URL and possible duplicate content. A change only because of the spelling can cause unnecessary migration effort.
When variants achieve different goals
If HTTP and HTTPS or www and non-www land on different hosts, check the forwarding rules for Hoster, CDN and CMS. Often, several configurations compete with each other. With a permanent change, 301 or 308 are possible. Direct as directly as possible to the matching HTTPS landing page and prevent loops between two systems.
Why subpages need to be checked separately
A correct homepage redirect does not prove that /products/lamp moves correctly as well. Open this specific URL in the Redirect Checker and compare destination path and required parameters. The forwarding HTTPS variant also requires a working TLS connection: The forwarding is only delivered after the connection has been set up.
Host change must not lose the sub-path
Practical example · for illustration
Starting position
First, check the four start page variants in the WWW-Checker. After that, test /products/lamp with full URL in the separate redirect checker.
Classify the findings
www.example.org/products/lamp should not accidentally end up on example.org/.
Specific amendment
Set preferred host and receive path and necessary query parameters during forwarding.
Control and border
Control final URL, status and canonical of the subpage. A correct start page redirect does not yet occupy a correct rule for all paths.
Questions about use and boundaries
Does the tool check a entered subpage?
No. It determines the host and checks its four start page variants. For a specific subpage, use the Redirect Checker with the full URL.
Do I have to change from non-www to www?
No. Both variants are possible. Maintain a proven configuration and implement the preferred version consistently.
Is Twice HTTP 200 Automatically an SEO Error?
First of all, it shows that several variants can be reached directly. Whether conflicting signals arise from this depends, among other things, on content and canonical information. These must be examined separately.
Why does only the HTTPS variant with www fail?
DNS, certificate or hosting assignment can be configured differently for www. Check the affected host with the SSL Checker and the hosting provider.