Welcome to WebmasterWorld Guest from 18.104.22.168
I have a domain whose spelling is very difficult, so what i did was bought 3 common misspelled domains for my original domains and got my site running on them
Now, the thing is google has indexed all those domains and same data is running on all these domains, will google penalize me for running duplicate content, if so what is the standard method for dealing in such a situation, i know many people might have the same problem here, wat have u guys done about this...
But positioning the content in SE for misspelled keywords would be a different and more difficult issue.
As for sites with .co.uk and .com domains with different prices, this is a bigger problem. I wonder if you marked languages of the versions properly - en-us for .com and en-gb for .co.uk - would Google show UK version in google.co.uk and US version in google.com? I don't know if Google cares for language version while deciding what result to hide with duplicate filter, perhaps it don't, but it would be great in the case, wouldn't it?
Hi all, this brings up another question. If you 301 one site or URL to another (A to B), do the spider-bots of SE's still see the meta tags of the site "A" or page "A" that's directed, or do they ignore it and read/index the meta tags of the final site "B" or page "B"?
If you 301 one site or URL to another (A to B), do the spider-bots of SE's still see the meta tags of the site "A" or page "A" that's directed, or do they ignore it and read/index the meta tags of the final site "B" or page "B"?
301 is a server redirect. This means that when a client (human or bot) asks for URL A, the server will return a statuscode 301 together with URL B. The info of URL A is not returned by the server. There is no way for the client to read the information on URL A when it is 301 redirected to B. So spider-bots only see the meta tags of site B.
Next you should dump that hosting. Finally put the redirect file (.htaccess) on the same server as the content, and point all of your domains to the same server space.
When someone next requests site A then their browser will attempt to access the content at site A, but instead the server will detect that you are attempting to access site A and send back the redirect information instead. The browser will read this redirect information and then attempt to access site B instead. The server will see that access to site B as being OK, will allow it, and will then serve the content to the browser.
Yes! The redirect file and the content can be on the same physical server. The redirect redirects you to a different domain name, but that other domain name does not actually have to be hosted in a different place to where the redirect file actually is.
Is there another type of redirect or some way to accomplish this (where the spiderbot will see and index both pages)?
Yes there is, but it is extremely dangerous. You can put a 302 redirect in your .htaccess file or a meta refresh in the head section of your document. In this case the search engines will index both pages, BUT some algorithm inside the search engine will decide which one will be shown in the SERPs. History has shown that for Google, this algoritm is not always doing what the webmaster intended. Please read some posts on this forum about "302 hijacking" and "canonical URLs" before you try this type of redirect. It can have disasterous results.
Thanks in advance for any feedback,
I'm almost certain that the PR from will pass to the refering site - so your old domain PR should increase the PR of your new site. Although it may not be as expected... an example is if site A with PR of 5 redirects to site B with PR of 5, you might still end up with PR of 5, but most probably a stronger one. An other example is if Site A with PR of 5 redirects to site B which has 0 PR, then the chances are that site B will obtain PR of 5. A 5 redirecting to another 5 will never make the second site 10...
Anyway, the short of it all is yes, redirect your old site and the ranking will increase, but perhaps not visually (i.e. in the PR toolbar), but it should increase in strength (i.e. from a low PR5 to a stronger PR5 or PR6..)
What happens to PR then - does it then have to stand on own two feet or is there a lag whilst google works out what has happened?
A redirect would work (if it comes from your server spiders will pick up the meta tags and possibly index them), also, why not just do domain forwarding via your domain host? This works outside of the engines.