I mistakenly allowed development sites to get indexed -- how to fix?

Author Topic: I mistakenly allowed development sites to get indexed -- how to fix?  (Read 955 times)

Offline webprguyTopic starter

  • Trade Count: (0)
  • Newbie
  • *
  • Thank You 0
  • Posts: 1
  • Karma: 0
I have a blog at mydomain.com and my hosting acct allows for multiple sites in subfolders. So I use this hosting account for development sites, such as mydomain.com/client1, mydomain.com/client2, etc.

I should have put these development sites behind a password, or used the WordPress settings to discourage SE indexing, but I didn't. Moreover, I failed to close down the development sites when they went live (on other hosting accounts and domains).

The content of these sites is now in the Google index. Won't this eventually cause duplicate content problems? If I shut down the development sites now (or put them behind a password), won't that create a lot of 404s and won't that negatively affect my blog in the root folder?

What would be a good strategy to deal with this?


Related Topics

  Subject / Started by Replies Last post
0 Replies
Last post 07-03-2011, 21:33:17
by Walalayo
0 Replies
Last post 09-10-2011, 10:19:42
by Maddy
0 Replies
Last post 10-04-2012, 10:01:13
by jckdear
1 Replies
Last post 10-14-2014, 03:10:13
by PatriaCoutee
1 Replies
Last post 01-22-2016, 13:10:00
by Sevam