Best way to remove full demo (staging server) website from Google index

[iam-sold]

I've recently taken over an in-house role at a property auction company, they have a main site on the top-level domain (TLD) and 400+ agency sub domains!

• company.com
• agency1.company.com
• agency2.company.com...

I recently found that the web development team have a demo domain per site, which is found on a subdomain of the original domain - mirroring the site. The problem is that they have all been found and indexed by Google:

• demo.company.com
• demo.agency1.company.com
• demo.agency2.company.com...

Obviously this is a problem as it is duplicate content and so on, so my question is... what is the best way to remove the demo domain / sub domains from Google's index?

We are taking action to add a noindex tag into the header (of all pages) on the individual domains but this isn't going to get it removed any time soon! Or is it?

I was also going to add a robots.txt file into the root of each domain, just as a precaution! Within this file I had intended to disallow all.

The final course of action (which I'm holding off in the hope someone comes up with a better solution) is to add each demo domain / sub domain into Google Webmaster and remove the URLs individually.

Or would it be better to go down the canonical route?

[EugeneSong]

Why couldn't I just put a password on the staging site, and let Google sort out the rest? Just playing devil's advocate.

[hammadrafique]

If you've enough time to verify each subdomain in WMT and also removing 400+ domains one by one, then you can go for solution 2. You can't remove subdomain from verified WMT account of main domain, that's why you need to verify each domain.

Adding canonical is a better option, it wouldn't remove all of the demo domains from Google's index rapidly, you have to wait for few months, but you'll be on the safe side.

[iam-sold]

Out of curiosity, why wouldn't you recommend solution 2?

You mentioned that you faced a similar kind of situation in the past, how did that work out? Which of the 3 solutions (or all) did you opt for?

[iam-sold]

Good advice but an IP restriction for the demo sites won't be possible on this occasion as our router throws out a range of different IP addresses and we occasionally need the sites to be viewed externally! Any other suggestions to help?

[customerparadigm.com]

I'd also recommend putting in an IP restriction for any of the demo sites.

So that if anyone visits the demo sites from a non-whitelisted IP address, then you can display an error message, or simply redirect them over to the live site.

That will likely have the search results quickly removed from the search engine.

Hope this helps!

-- Jeff

[hammadrafique]

Solution 1:

Add robots.txt on all demo domains and block them, or add noindex in their header.

Solution 2: Verify each domain in webmaster tools and remove it entirely from the link removal section ( I wouldn't recommend this).

Solution 3:

If your both domains like agency1.domain.com and demo.agency1.domain.com have same coding and are clone then you should just add canonical url to the agency1.domain.com and canonical will be http://agency.domain.com/ it will work if it will be automatically shown in the demo domain. if it doesn't show up in the demo domain automatically then add the same canonical to the demo domain.

It will take some time to deindexed from serps, but it will surely work. I've faced the same kind of situation in past.

[Lumina]

Noindex is your best option, really. It might take weeks, but I don't think any other method is going to be faster. Plus, technically speaking, "noindex" is the proper method for what you want to do - canonical tags or a robots.txt may do the job, but they aren't exactly the right way.

Good luck!