Forum Moderators: open
ie. a large provider subdomain as opposed to a smaller isp. The site in question does not have proper hosting but has www.a-large-isp.com/~somesite.
the site has good incoming links and still is not listed after over 2.5mnths.
never had a problem with subdomains before which is leading me to beleive that the more there from one isp the harder it is to get listed.
would really appreciate any comments.
If it hasn't, then you should wait to draw any conclusions unti it is spidered.
However, the picture seems pretty bleak. If you have a good number of inbound links, and you've been trying to get the site listed for 2.5 months, it's quite likely there's a problem.
Can you break out of that domain and get your own? Otherwise, my only other suggestion would be for you to write to Google to find out if there's a problem with the doamin or IP.
The case mentioned here is not a subdomain. Subdomains are the domains that are preceding a domain name, not following them, ie. not a, but b:
(a) http //example.com/~somesite/
(b) http //somesite.example.com/
Example (a) is a subfolder on the regular domain "example.com" and example (b) is a subdomain. In this example, "www" is a subdomain of example com, too:
(c) http //www.example.com/
And for that reason, (c) and (b) is the very same thing. I've never seen or experienced problems with a subdomain that was not caused by something else than the fact that it was a subdomain.
You can even have sub-sub-domains like this real world example with no problems at all - here, the domain is "go.com":
(d) http //msn.espn.go.com/
/claus
"www" is a subdomain of example.com
Interesting but then example.com/www would have to be the same thing wouldn't it? Or can subdomains exist without a subdirectory to link it to?
How do you upload files to a subdomain if it doesn't have a folder?
With apache and most other web servers, the files for the site can live anywhere, and you tell them in the configuration where each one lives.
For example, for my sites, I have a /home/www/ folder, and sub folders like this...
/home/www/mydomain/
/home/www/subdomain/
/home/www/anothersubdomain/
In apache, I then configure "mydomain.com" to point to /home/www/mydomain/ "subdomain.mydomain.com" to point to /home/www/subdomain/ and "anothersubdomain.mydomain.com" to point to /home/www/anothersubdomain/
On the server, your subdomain folder can be named virtually anything but in the browser (and to Google) it will always be displayed with the "external" path and folder name. Here's two examples of possible subdomain folders on the server:
(1) /usr/www/something/example.com/subdomain/
(2) /usr/www/something/subdomain.example.com/
Both of these (and even more) can be set up to show "subdomain.example.com" in the browser (and to Google and everyone else) - nobody apart from those with access to the server wil ever know the true location of these folders.
BTW: i really don't think there's anything to this:
>> a large provider subdomain as opposed to a smaller isp
In both cases your (sub)domain will point to some folder that is yours on some server. The only typical difference will be how many domain names that are attached to each IP-number, and regardless of the size of the hosting firm you can have one IP-number for the domain as well.
Google (and everyone else) will be able to indentify your "document root" (the topmost level of your domain, your root folder) in any case, as this is decided in the server configuration and visiting User-Agents have no influence over this.
On the other hand, there are some SE's that will not accept subfolders (a) but only subdomains (b) as being an individual site. This is typically SE's/Directories where you can only include your front page address. It is not the case with Google, as Google indexes both perfectly well and doesn't really care to which domain the individual page belong, afaik:
(a) http //example.com/~somesite/
(b) http //somesite.example.com/
/claus
the url is a subdirectory of a subdomain.
ie. users.large-isp.com/somesite.bnb
I am thinking that maybe the naming convention of the large isp is causing the problem.(the .bnb part of it)
I have seen similar addresses in the listings from the same isp but not with the 3 character extension.
could a three character extension like this possibly be confusing google ie seeng it as a file name or something instead as of part of the url?
At one host I use, a subdomain is located as follows:
/html/index.htm (domain.com or www.domain.com)
/xyz/index.htm (xyz.domain.com)
/abc/index.htm (abc.domain.com)
Subdirectories of a subdomain are indexed, at least the typical ones (not .bnb). Since a dot extension is mainly a Windows/DOS concept, I don't think Google treats them as file names as opposed to directories.
You could try naming a directory, say xxxx.bnb and place an index file in it, then view it with a browser without the index file name. If the index file displays, I would expect Googlebot to see it too.
it does display correctly but google still seems unable to find it for some reason.(plenty of incoming links pointing straight at it)
ie users.somesite.com/somesite.bnb/somepage.htm (with somepage.htm having links to all other pages)
any opinions before I waste my time. thanks :)
