When you move your site to ssl, you have to adjust your settings in Google Analytics and Google Webmaster Tools/Search Console accordingly. It’s not much work, but it’s important you fix it. In short, you need to set your primary domain in both Webmaster Tools as in Google analytics to your https domain. I’ll discuss Search Console first, but it really doesn’t matter in which order you do it.
Webmaster Tools / Search Console
In Google Search Console (Google Webmaster Tools), you should add the https variant, and you should set it to your preferred domain as well. You should add all variants of your domain:
If you don’t know how to add a new property, follow these instructions from Google.
As you will have for properties for each site, you can also create a set, in which you bundle all properties for one domain. To create a set, click the “create a set” button to the right of the red “create property” button.
The preferred domain should match the one in the general settings of WordPress, the site url. To set as your preferred domain, do the following:
- On the Search Console Home page, click the site you want.
- Click the gear icon, and then click Site Settings.
- In the Preferred domain section, select the option you want.
After you move to SSL, you should change your domain in Google Analytics to https. This way, GA starts registering your hits again. I would recommend using the .htaccess redirect if you’re on apache. GA might not register hits if the site is not redirecting properly to https.
The language on the screenshots is not English, but it will look the same in English.
To update the GA settings, in Google Analytics, first go to your website dashboard, and click the cogwheel at the bottom, “Admin” .
Now there are two urls that need to be changed. For tracking, only the url under “view settings” appears to be important, but I would change both anyway. So first, click “property settings”, and change the default url. Then click “view settings” and change the website url.
Now, change the protocol to https for both url’s
That’s it! Your site is now correctly configured for SSL.
If Really Simple SSL fixed your issues and/or saved you time, you might consider buying the premium plugin to support the continuing development of the plugin. You’ll get some great additional features, like HTTP strict Transport Security, the SSL certificate expiration warning and premium support.