Welcome to the Q&A Forum

Thanks, guys! Both of your answers are right in line with my suspicions. I think at the end of the day, I'm going to opt for one domain, one URL-set, different wrappers, and canonical tags just in case the crawler ever wriggles its way through the pay wall... which, given callbacks to server-side user data, should be impossible.

Thanks again,

-m

Hello!

I'm launching a premium service on my site that will deliver two fairly distinct user experiences, but with nearly identical page content across the two. I'm thinking of placing the "upgraded" version on a subdomain, e.g. www.mysite.com, premium.mysite.com. Simple enough. I've run into two obstacles, however:

-I don't want the premium site crawled separately, so I'd like to use canonical tags to pull all premium.* back to their www.* parents.

--How different can page content be before canonical tags backfire?

--Is there any other danger in using canonicals across subdomains like this?

-Less importantly: with Google Analytics, if I track against the subdomain my visits will split naturally, and it should generate a second cookie for a new registrant who crosses subdomains. I could also use a visitor-level custom var. Good idea? Bad idea?

Thanks!

-m