1
Most Helpful
Most Helpful
"Apparently without the / the URL is invalid however browsers are able to
cope and redirect . "
That is so so so wrong! The redirect will be triggered by the server hosting the requested page behind the URL. So not having a trailing / at the end of your links would mean double requests for your server and therefore, lower performance with the same resources.
cope and redirect . "
That is so so so wrong! The redirect will be triggered by the server hosting the requested page behind the URL. So not having a trailing / at the end of your links would mean double requests for your server and therefore, lower performance with the same resources.
0
As we are aware that our website is initially saved in same hierarchy structure as we can see in windows explorer i.e. Folders and sub folders ... "/" denotes the hierarchy level in the URL for example if the URL showing "designreviver.com/" denotes visiting the root directory folder as one "/" is present and "designreviver.com/answers/" denotes visiting sub-folder answers of the website .... And it is initial part of the web URL should not be skipped ...
0
@glynthomas tweeted this answer (thanks for this):
Apparently without the / the URL is invalid,
browsers are able to cope and redirect. This is what I was advised. Google will count both url's separate pages when
it comes to link juice.
Apparently without the / the URL is invalid,
browsers are able to cope and redirect. This is what I was advised. Google will count both url's separate pages when
it comes to link juice.
1
Apparently without the / the URL is invalid however browsers are able to cope and redirect . Google will count both url's separate pages when it comes to link juice.
1
If I start URL with http:// then at the end I always write /: www.google.com
In case I start URL with www., there is no / at the end: Www.google.com.
In case I start URL with www., there is no / at the end: Www.google.com.