Awesome! That did the trick -- thanks for your help. The site is no longer listed

Yeah. As of yet, the site has not been de-indexed. We placed the conditional rule in htaccess and are getting different robots.txt files for the domain and subdomain -- so that works. But I've never done this before so I don't know how long it's supposed to take?

I'll try to verify via Webmaster Tools to speed up the process. Thanks

Awesome. We used your second idea and so far it looks like it is working exactly how we want. Thanks for the idea.

Will report back to confirm that the subdomain has been de-indexed.

Thanks for the suggestion. I'll definitely have to do a bit more research into this one to make sure that it doesn't have any negative side effects before implementation

We have a plugin right now that places canonical tags, but unfortunately, the canonical for the subdomain points to the subdomain. I'll look around to see if I can tweak the settings

Hey Ryan,

I wasn't directly involved with the decision to create the subdomain, but I'm told that it is necessary to create in order to bypass certain elements that were affecting the root domain.

Nevertheless, it is a blog and the users now need to login to the subdomain in order to access the Wordpress backend to bypass those elements. Traffic for the site still goes to the root domain.

Hey Andy,

Herein lies the problem. Since the domain and subdomain point to the exact same place, they both utilize the same robots.txt file.

Does that make sense?

Is it possible to block an entire subdomain with robots.txt?

I write for a blog that has their root domain as well as a subdomain pointing to the exact same IP. Getting rid of the option is not an option so I'd like to explore other options to avoid duplicate content. Any ideas?