Tag Info

Hot answers tagged

4

I would recommended either using the www or non-www and stick with it. Set a preferred URL in Webmaster Tools and then 301 to either your www or non-www. The reason for this would be Google would see both the non-www and www sites as two separate websites. If the content is exactly the same, then you could be penalized with duplicate content.


4

Yes you can, try setting the cookie for .example.com as domain. That way, the cookie will be valid for every subdomain of yours. For example, PHP sessions would be like this: session_set_cookie_params(0, '/', '.example.com');


3

This is relatively easy to do. Using example.com, you have: An A record for the example.com A CNAME (as an alias) pointing www to example.com (www is a sub-domain) --where www = example.com -- or -- An A record for www.example.com To have sub-domain.example.com you would have: An A record for sub-domain.example.com --where the IP address is for the new ...


2

No. I run several sites like this. The binding determines which app takes the requests, and each app can only have one app pool. An app pool can use multiple processes (a web garden) but that is completely unrelated to wildcard domain names (even a single domain gets split across multiple processes in this scenario). An app domain (a security construct ...


1

If you move your blog to a subdomain, you shouldn't, by any means, keep it in the folder due to duplicate content problems. You can only move it, not copy it. About your question, for my experience it's not true and you should keep your blog where it is right now. This happens because the main domain has the main strength and power and dividing it to ...



Only top voted, non community-wiki answers of a minimum length are eligible