3 {{ upvoteCount | shortNum }}
3 {{ upvoteCount | shortNum }}

Google Slap - moving site to a new domain

by elperuanito
2 replies
  • SEO
    • |
Guys,

So a while back I bought a site off the WF (could have done it myself, was a newbie). The site was slapped and so I decided to move it to a new domain, with everything exactly the same including content. I know some people have said this is a mistake and you should start with new content, but the SEO guy I'm using advised this and I'm just testing this theory at the moment. So I've moved the site twice now and each time I get the PR for the home page to transfer across about a week later. I'm not doing a 301 or anything so what could cause this? The SEO guy is asking me what I've done to trigger this, but I've not done anything! I think anyway :p

Ideas welcome.
#domain #google #moving #site #slap
  • Profile picture of the author TheContentAuthority
    Elperuanito,

    This is some truly odd behavior. The only thing that I can think of is if you simply applied a new domain name to the hosting account where all the content resided. In this way, the site was still be found at the same IP address but with a different URL.

    Also, PR is not updated that often so this could be why you are seeing PR on the new domain still.

    More info in this thread,

    How often is Page Rank updated? Google SEO News and Discussion forum at WebmasterWorld

    Best,

    Shawn
    Signature
    Outsource to the experts...

    We customize your Blog, eBook, Press Release and Sale Copy content with your message.

    {{ DiscussionBoard.errors[7681830].message }}
  • Profile picture of the author jxam69
    I've seen this before when both the old and new domains are pointing at the same site - Google realizes they are the same site and assigns the PageRank of the old domain to the new domain - IE both domains will show the same PageRank.
    Signature

    This space will be awarded to the first WSO owner who can prove they make Million$ from their methods.

    {{ DiscussionBoard.errors[7681839].message }}

Trending Topics