URL Typo Handling

In the section URL Typo Handling in the single Page Analysis, we take a closer look at the URL itself. "Let's see what happens if the URL gets called by a valid variation."

 

WWW Resolve 

With or without www is up to you. Once set on one of the two options you should consequently stick to it and all requests that alternate should be redirected. 

 

Non-SSL canonicalization

If your website is SSL encrypted all content should be accessed via HTTPS. In this step, the analysis checks what happens if the URL is accessed by a different protocol. 

If your HTTPS URL is also accessible by HTTP it's inefficient, because you provide a secure User experience with the SSL encryption and a bypass at the same time.

 

404 error page

We test if the server issues the status code 404 when a random URL (one that is not existing within your Domain) is called. It's best to have a 404 respond in order to identify issues and fix them.

 

Special Characters in URL

The URL should follow the RFC 3986 standard and should not contain special characters.

 

Case-Sensitive URL

A URL should not have uppercase characters.

 

IP Canonicalization

If the IP of this domain gets called, it should redirect to the real homepage of this domain. Not redirecting requests on the IP can cause Duplicate Content issues.

 

Troubleshooting:

We only analyze the direct redirection target. An example for https://domain.de and WWW Resolve:

if the redirect chain is as follows:

https://www.domain.de/ -> http://domain.de/ -> https://domain.de/

The second redirect will not be analyzed.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk