Is there any way to change the domain in a campaign here?

[oznappies]

When I started the campaign I used site.com but now I have an external blog at blog.site.com and is hosted on tumblr. This site gets lots of errors showing on the campaign because insists on following no-follows. If I change the campaign to www.site.com then blog.site.com will not be part of the campaign.

It does say in the help that it will NOT track sub-domains, but it does and hence my problem. So, I am not sure if the rest of the info there is old.

'Does the Web App track the subdomains of my campaign’s domain?
A.  Unfortunately we do not currently track subdomains as a part of the
domain you enter. Instead, you must create another campaign slot for any
subdomains you wish to track.'

Any ideas on where or how to do this?

[SteveOllington]

Do you need to keep the existing info on it?

If not, you can archive the domain and re-enter a new one in its place.

[Guest]

This post is deleted!

[kenneth_martin]

Unfortunately, you cannot alter the domain after the campaign is created or the way that we track your domain. So you couldn't switch from tracking a subdomain for your campaign to tracking the root domain. You will have to create a new campaign if you wish to alter the way your campaign is currently setup

It does appear that the FAQ is currently out of date.

You can setup a new campaign to track the root domain (*.example.com) and it will track all the subdomains in one campaign (ex. blog.example.com and www.example.com). Another option would be to setup two separate campaigns to track subdomains. One campaign for blog.example.com and one campaign for www.example.com

This will of course depend on your needs.

[oznappies]

Thanks guys, I hoped that if some of the info was out of date on the 'subdomain reach', there may have now been a way to add a prefered subdomain to my campaign

The reason for the request is currently Roger reports lots of duplicate tags on the blog which Google does not reports because they are restricted in robots.txt or with NOINDEX, NOFOLLOW, NOARCHIVE in the meta tag..

Since I do want to keep the historic data, I will just sift through the errors reported by the blog.