Site versions
HTTP, HTTPS and variants with www. A 200 response on multiple versions without a redirect can divide the weight of the pages.
Check which technical URLs respond with a 200 code and may create duplicates in searches. The service does not follow redirects: this way you can immediately see the original response of each option.
HTTP, HTTPS and variants with www. A 200 response on multiple versions without a redirect can divide the weight of the pages.
Checking///, /?, and alsoindex.html, index.php, index.htmand home files.
We show the response when accessing via external IP. This helps to find the default virtual host and erroneous copies of the site.
Green code 200 in itself is not always an error. The risk arises when multiple URLs serve the same page without a permanent redirect, canonical address, or indexing ban.
The page is available. Check to see if it is a copy of the home page or another landing page.
This is usually the correct option: the address constantly redirects the user and the search robot to the main version.
This is a temporary redirect. To link permanent versions of a site, 301 or 308 are most often used.
Define one primary address: HTTPS and an option with or without www.
All other versions, index files and technical paths must lead with a 301 or 308 code to the canonical URL.
On the main pages, specify the absolute canonical that matches the selected address.
This shows the source code of each URL. If you go straight to the final address, it is impossible to understand whether a redirect is configured and which one.
If the file serves the same page as the domain root, it is better to permanently redirect it to the main URL. This reduces the risk of duplicates in the index.
A 200 IP response may open another virtual host's page or a copy of the site. For most sites, it is more correct to give an error or redirect to the canonical domain.