Is a subdomain OK as your product's web site?

I don't know why the web isn't more friendly to sub domains. We keep wasting domain names. Reusing domains and using sub domains is an elegant solution.<p>I hate going to web sites that dump every product they own on one page, along with support, company information ,etc. It just makes it harder to find info for what I want when I have to look at everything. If they had a subdomain they can dedicate what appears as a whole site to just that product. Then their company info, career portion, etc can be on their main domain, and keep it all separated.

This might help (if you haven't read it already): <a href="http://www.mattcutts.com/blog/subdomains-and-subdirectories/" rel="nofollow">http://www.mattcutts.com/blog/subdomains-and-subdirectories/</a><p>I use subdirectories.

<i>Some yays for subdomains:<p>- they allow me to share all administrative code behind the scenes (logging framework, key generator, common scripts, etc.);<p>- they're free for me on my current hosting plan;</i><p>With all due respect, I'd say this guy has bigger problems than subdomain vs. own domain. I reads a lot like he's on a $5/month plan, and it's a deal-breaker to spend eg. $20 for a slice or linode where all those considerations goes away.

I would think if you can't afford the extra $10 registration for a new domain that you yourself probably aren't very confident in your products recouping their domain cost.<p>If such is the case, a company has bigger problems than even the great ones outlined previously.

It works, but I wouldn't do it. For one it makes selling a product line a tough thing to do.

Subdomains are best for separate "apps" on your server.<p>www.company.com/product1, product2, etc. store.company.com/product support.company.com/product . . .

Why not "yourcompany.com/productname/"?

Just like altavista.digital.com. How did that work out?

Subdomains loose you SEO juicyness. So no, better to use diretories (unless you're say Yahoo I suppose).