Hot answers tagged subdomain
Yes. Whatever the web root for the subdomain is where you would put a robots.txt for that subdomain's contents. It will not affect the root domain and the root domain's robots.txt will not affect the subdomain.
Create a subdomain foo.bar.com via your control panel or do it manually on your Linode server. Then, set your DNS at Namecheap to point to your server IP when someone request foo.bar.com. In the public_html of foo.bar.com on your Linode server, you can create an .htaccess file: Redirect 301 http://bar.com/foo
I would go with topic.example.com or example.com/topic and not a separate domain for each topic. Basically, use the silo approach. This will allow each topic to rank on its own without being too diluted. Also, having your keywords in the domain does not proved very much SEO value now a days. P.S. While topic.example.com or example.com/topic are both sound ...
mod_proxy can be configured from .htaccess to serve content from a different server or host as a subfolder. You would use a rewrite rule with the [P] flag (for proxy) in your .htaccess to do so: RewriteRule ^/subdomain/(.*) http://subdomain.example.com/$1 [P] ProxyPassReverse /subdomain/ http://subdomain.example.com/
I would pick subdomain if it only needs to separate logical parts of a site. Imagine car site, you writing about cars and maybe you have classified ads, one day you realize that you can copy this to be also a motorcycle site so you use a subdomain , or auto parts also a subdomain, but if you want to separate ie make of car to a subdomain it wont be good ...
This has changed. As of sep-2014: The CNAME target should be: ghs.googlehosted.com And you enable the URLs from dashboard -> Company Profile > Custom URLs Google's support page
Only top voted, non community-wiki answers of a minimum length are eligible