Hi there @clhalsell,
Thanks for reaching out. Changing a site from http to https can indeed result in this notice. In most cases clicking on the “reconnent” button within the notice and following the plugins setup steps allows users to remain connected.
In your case I noticed that the unsecure version of your site (http) is still accessible. This means both your secure (https) and unsecure (http) are accessible, so it’s possible you may encounter the notice once more. In order to resolve this you can follow the steps below. Performing the below is also encouraging best practices, now that you have a https site, and not just ensuring Site Kit remains connected.
- Ensure that your “WordPress Address (URL)” and “Site Address (URL)” are both reflecting your secure (https) status in your WordPress general settings (Settings > General). I can see both reflect your unsecure (http) site at present from checking your REST endpoints.
- Ensure that you have https redirection in place, so anyone who may happen to visit the http version of your site is automatically redirected. Your hosting provide can assist with this, or you can use a free plugin that performs this action.
Once you perform the above you’ll not longer be asked to reconnect. If your site records at present are reflecting the http version of your site you may be asked to reconnect once more, to the https version. This however would only be one, as your site would be fully secure with redirection in place.
Let me know if you have any questions with the above, or if you need any help following the suggested steps.