document root

blackhorse

Some hosting apache set up the site document root as "/site1/www/" instead of "/site1/www".

Should it be better to use "/site1/www"? For SEO reason? Or it is the same for SEO?

My question is that when we called the variable, $_SERVER['DOCUMENT_ROOT'], should we always assume that the it always should be "/site1/www" without "/" at the end?

So for example the image folder physical path should always be

1) $image_physical_path= $_SERVER['DOCUMENT_ROOT']."/images";

not

2) $image_physical_path= $_SERVER['DOCUMENT_ROOT']."images"; //without that /

Because in case 1, no matter how the site set up their document root "/site1/www/" or "/site1/www", it will turn out to be "/site1/www/images" or "/site1/www//images". Both will work.

But if use case 2)

then it will turn out to be "/site1www/images" or "/site1/www/images". "/site1www/images" will not work.

For the portable reason, we should always use

$image_physical_path= $_SERVER['DOCUMENT_ROOT']."/images"; // with the "/"

Right?

bradgrafelman

blackhorse wrote:
Should it be better to use "/site1/www"? For SEO reason? Or it is the same for SEO?

Well, since search engines can't download your source code, view it, and evaluate its style to rank pages, then yes, neither will come into play with SEO. :p

As for which to use, I think you answered the question yourself; if you have two options, and you know that option A always achieves the desired result whereas option B will usually work, it seems logical that you should always use option A.

blackhorse

As for SEO, my question is

Give it as

http://www.mysite1.com

http://www.mysite1.com/

No difference, right? Someone claimed that there were. I don't see why.

Weedpacket

http://www.example.com will be turned into http://www.example.com/ - the first one has an empty path, the second one specifies the site root (which is where you really want it to point to).

For example, because the "http" scheme makes use of an authority component, has a default port of "80", and defines an empty path to be equivalent to "/", the following four URIs are equivalent:
  [url]http://example.com[/url]
  [url]http://example.com/[/url]
  [url]http://example.com:/[/url]
  [url]http://example.com:80/[/url]
In general, a URI that uses the generic syntax for authority with an
empty path should be normalized to a path of "/".
RFC3986: Uniform Resource Identifier (URI): Generic Syntax, §6.2.3: Scheme-Based Normalization

If the abs_path is not present in the URL, it MUST be given as "/" when used as a Request-URI for a resource (section 5.1.2).
RFC2616: Hypertext Transfer Protocol -- HTTP/1.1, §3.2.1: http URL