Welcome to the Q&A Forum

Hi again!

In the same screenshot that I provided in my previous response: http://screencast.com/t/RDOJAu8ykW you would set the url in the top field to the specific section of the site you're interested in targeting your campaign for and then click the "Advanced" link and then click the checkbox next to "Exclude subdomains to restrict this campaign to the domain you entered".

Hi there - thanks for writing in! Kristina from Moz's Help Team here.

Campaigns are site-specific (meaning you can't track multiple sites within a single campaign) and within the Campaign Settings that you set when you initially set-up the campaign, you can choose to track all pages within the entire root-domain of a site, or restrict it to only pull in data for a particular subdomain.

Here's a screenshot of the campaign setup section where you would set these settings upon the creation of your campaign: http://screencast.com/t/RDOJAu8ykW

I hope this helps answer your question! If not, or if you're needing further assistance, please don't hesitate to reach out to our team anytime by emailing [email protected]!

Have a great day,

• Kristina

Hi there - Kristina from Moz's Help Team here. Just as the helpful responses stated before mine, unfortunately at this time our crawler isn't compatible with Server Name Indication (SNI), which appears to be in use on your site (https://www.kitchenstuff.com). In general, SNI is a totally acceptable security configuration, but our crawler simply isn't equipped to be able to handle these settings.

If you are able to disable the SNI configuration on your site, then we should be able to crawl it normally. While it's something that we'd love to be able to accommodate for the future, we don't yet have the resources to be able to make those changes.

Also as mentioned previously by Dirk, this thread in our Community Q&A forum with lots of other users running into the same problem, so it's definitely something we're aware of and working to address: https://mza.bundledseo.com/community/q/804-https-ssl-error

We're sorry about the trouble & inconvenience this causes.