Forum Moderators: buckworks & webwork

Message Too Old, No Replies

Virtual Domain Names

are they still recommended?

         

old_expat

4:35 am on Jun 3, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



We are working on a very large site. The domain name is an easy to remember 8 letter non-hyphenated with a pretty good keyword. The site is not an affiliate site.

The site is an international one and certain issues make an all-countries site cumbersome unless we use different directories.

Okay, it's only one more click, but that can be a diversion or cause confusion as well

One way to handle it would be with short subdomains, i.e. these.wigets.com, those.wigets.com, etc

There are 2 issues I am wondering about

1 - in another thread, one post implied that sub-domains are going to be penalized by the SEs, possibly as policy, possibly because of attempted 302 hijacking fixes

2 - re the 302 redirect issue. Will we be able to use some version of a .htaccess mod rewrite that says "don't go to those non-www pages unless they are "this" or "that"?

We wouldn't mind registering additional domains, but finding them is the problem.

Glamba

6:16 am on Jun 3, 2005 (gmt 0)

10+ Year Member



1 - in another thread, one post implied that sub-domains are going to be penalized by the SEs, possibly as policy, possibly because of attempted 302 hijacking fixes

Depend's on the content of the subdomain in question. I haven't seen any problems with keyword.example.tld versus keyword.tld. Infact keyword.example.tld has in my case a higher rank in just about every search engine I checked than keyword.tld.

How about using 301 redirects instead of 302?

2 - re the 302 redirect issue. Will we be able to use some version of a .htaccess mod rewrite that says "don't go to those non-www pages unless they are "this" or "that"?

That's what modrewrite is for ;)

old_expat

9:55 am on Jun 3, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



"That's what modrewrite is for ;)"

Yes, I know that. The 302 issue I referred to was the Googlejacking issue that a 301 is used in an attempt to mitigate.

But the 301 I'm using now redirects everything that *isn't* a www.mysite.com to a www.mysite.com, so I assume it would redirect this.mysite.com to www.mysite.com, which defeats the virtual domain.

Dijkgraaf

2:58 am on Jun 8, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Well then add another condition that says and doesn't start with this.mysite.com into that rule