Welcome to WebmasterWorld Guest from 18.104.22.168
About three years back on one of the sites i worked on from time to time i created about half a dozen subdomains off the main site. Widget1-abc.com, Widget2.abc.com etc, etc.
The site abc.com had large sectors anyway for widget1, widget2 but i thought i would give them their own dedicated sub-sites.
I guess the truth is that back then it wasnt for users benefit but for ranking reasons. I thought having keyword.domain was going to help rankings - I am obviously more experienced now but this is how i thought at the time and how i see a number of other webmasters thinking!
What i have noticed recently is that on google, when doing a search for the term widget1, i might find that abc.com rank say position 23 in one data centre. I may try another data centre and find that either abc.com or subdomain.abc.com rank in exactly the same position.
Clearly google in this example rates both the subdomain site and the main site as equals depite them both pages having the same Page Rank but abc.com having far, far more backlinks than subdomain.com.
My question is this:-
If i re-visit this website and remove all of the sub domains , do you think the search positions in google will improve for abc.com? or get worse?
Also, i noticed a site that had every area known to man as a subdomain, area1.cde.com, area2.cde.com etc. It had 400,000 back links from its own pages!- my thoughts were that surely this site will get crushed by Google yet some of its subs are filtering into the index! so google must think subs are OK.
In conclusion im thinking that in truth a sub-domain is a bit spammy to be honest - ive not seen any genuine cases where a sub-domain is really that vital, so im thinking that perhaps i should re-visit the site and remove the subs from it, but obviously the webmaster wont be to pleased with me if i advise they should go and his site drops off the map!
Any thoughts anyone or has anyone any experience of this?
Quote from Blog:
"my current pet peeve (subdomain spam, which BigDaddy does better on). "
I hope they aren't too hard on it because it is a very logical way to break up a site for many reasons.
I'd keep it the same as you have it if it's 20 or less subdomains. You can check on your subdomains and BigDaddy at the 3 datacenters where they have updated.
If you are using a ton of subdomains - I'd change them. I'm sure MSN will get smarter soon too (if you go to search.msn.com and search for credit cards you will see the first couple results are subdomain spam.) They can't continue with bad results like that for large volume keywords.
I'm not saying it's good in all situations, but they do have their place. As I said - if you have only a few areas that need to be clearly defined such as corporate.domain.com or investors.domain.com.
This obviously makes it easier to maintain your inbound links when doing overhauls.
About.com has redone their site for this and a few other reasons. It works great - IMO. This way I don't have to remember about.com/od/blah/
When you are working with a site that is huge and has a lot of traffic - it is much easier to manage the DNS to split up onto multiple servers. All you have to do is point forum. or members. to a diff. IP.
One more thing.. yes i get fired up about subdomains.. Yahoo spams the internet with their duplicate content on their subdomains - google and msn should not be listing Yahoo results that are duplicate content used from their partner sites.
there are perfectly good reasons to have subdomains so i can't see blanket bans coming into force.
now if you've been getting advantage in the serps because of them, then good luck to you...
i can certainly think of at least one site that is getting a big advantage from using sub-domains and i always thought that some day they were going to get nailed. that day sounds like it is coming closer...
How is it any more logical than using a good directory structure?
I use subdomains for seperating localised language versions of my sites i.e. es.domainname.com for spanish, de.domainname.com for german.
That way, I can use the same scripts and pull the localised text from a DB.
They should look at a subdomain - see how many pages are within that sub, links directly to the sub from other non-sub sites, are the pages in the sub content rich, etc.
Looks like google is having a sharp eye on subdomains, and any spammy sign as multiple dashes might be a bad idea. Without subdomains you might have more margin to "mess", until you are "caught". ;)
I've had excellent success with using a sub-directory structure for websites. I've not yet had the opportunity to develop sub-domains as we can logically build into the existing site structure.
There are a couple of cons that I see when using sub-domains. For one, they are not user friendly for many. Why? Because people have this inherent nature and want to type in www.sub.domain.com not realizing that the sub is to be used in place of the www.
You want your sub-domains to be short and sweet, one word, highly targeted. For instance...
If you have 7 buttons for main navigation at the top of your site and you are using a sub-domain structure, those seven buttons are most likely going to be your primary sub-domain links.
Remember, sub-domains are one level above the root and will typically have more power than a sub-directory which is one level below the root. But, site architecture, inbound links, etc. will all have a final say-so in the matter.
That www. thing is the main reason why I've not made the trek into sub-domains. There are also additional maintenance/management issues to content with using a sub-domain structure.
I ended up choosing the latter --mainly because so many "spammy" sites were using subdomains ("clean" sites like About notwithstanding)...
While I *may* have given myself a minor disadvantage at the time, I now feel it was the right long-term decision! :-)
There's no need for a domain to have 9000 subdomains with just one page per subdomain.
This is where I think many make a mistake. I do believe that there are routines (filters) in place to determine if a site is large enough to justify a sub-domain structure. Obviously if a domain has "too many" sub-domains with little content, it may raise a flag.
There was a time where this worked in Google. They've since corrected much of it. There are still a few who know how to work the sub-domain structure very well. I've even seen instances of sub-domains outranking the root domain.
Because people have this inherent nature and want to type in www.sub.domain.com not realizing that the sub is to be used in place of the www.
You can have www.widgets.example.com redirected to widgets.example.com.
I personally prefer the first option - looks more like an URL to a regular Internet user.