Google Site Kit Configuration Problem

Thanks for reaching out. On the main site it sounds like you have Site Kit already connected. If you’re encounter these Analytics related messages can you confirm whether you’ve tried to disconnected the Analytics module on this particular site, or reset the plugin on this site? Note that resetting the plugin will result in all other connected administrators also having to connect once more.

If you’ve already tried the above please share the following information so we can check your setup.

1. Your Site Health information. You can use this form to share privately if preferred.
2. While you mention you can’t connect AdSense or Tag Manager is Analytics reporting for you fine?
3. Can you share a screenshot of the error message with your browser console errors tab open? You can use a service such as Imgur or Google Drive to share any screenshots.

Let me know if you have any questions on the above.

Many thanks for the update. In additional to the extra insights you kindly provided it would be great if you could share the below:

1. Your Site Health information. You can use this form to share privately if preferred.
2. Can you share a screenshot of the error message with your browser console errors tab open?
3. As you’re encountering REST messages using a diagnostics tool please share any errors or recommendations you find when accessing your Site Health status.

We’ve also tried resetting the Google Site Kit and even reinstalling it.

Thanks for performing this check. Once we have the information above we can hopefully help determine the cause, nothing stands out from inspecting your site alone. I’m also able to access your publicly available REST endpoints.

Many thanks for sharing your Site Health information. As nothing obvious stands stands out from initial inspection can you also share the below information:

1. Any browser console errors that appear on the same screen whereby you encounter the “Error: Request parameter is empty: accountID” notice?
2. Do you have any security or caching component active at host level?

Based on other similar reports there may be something at host level which is block Analytics within Site Kit. If you can check with your hosting provider and compare Nginx configuration files for both websites you may be able to determine why one site is working while the other won’t.

Let me know if you need any assistance on the above.

Thanks for sharing. While I do see one console error that looks to be CDN related I’m not certain this is impacting plugin configuration. To rule this out please follow the steps below:

1. Login to your site from a Chrome browser incognito window
2. As you already have the Health Check & Troubleshooting plugin active please navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
3. From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google”
4. Attempt to connect Analytics within Site Kit once more

You can exit troubleshooting mode afterwards. Let me know if you have any questions on the above.

Thanks for reaching out. I suspect this may be hosting related, based on one users previous experience with similar errors – also with multiple sites, one including a subdomain.

While I’ve created a GitHub issue so we can investigate this further can you perform the steps below:

1. Reinstall your WordPress files (as advised from checking your Site Health status in your last response)
2. Reset Site Kit once more – while you’ve done so previously I’d like to check your site after resetting. Note that resetting will result in you having to connect all services once more.
3. Setup the plugin once more and share any errors you encounter during setup. If you don’t encounter any setup issues please try to connect Analytics to the same account previously connected. If you once again encounter any Analytics related error messages please share the error, along with any console errors.

Let me know if you have any questions on the above. The steps mentioned will reset your site to a default state, making it easier to troubleshoot specific issues, with all the standard WordPress files intact. From checking your Site Health information previously it looks like various modules remain connected, although with various error messages.

Thanks for sharing the additional insights. So I can add the above and request the team to review can you share the following:

1. A screenshot of your full Site Health status. I’d like to see if the REST message remains for this impacted site.
2. On your hosting account (and not your CDN) can you temporarily deactivate any ModSecurity of other WAF feature before checking once more?
3. While you mentioned this occurs when connecting the Tag Manager or AdSense modules can you try and disconnect the Analytics module once more, before attempting to connect once more? I’m curious to see if exact same message appears when connecting or setting up a new Analytics account.

Let me know if you have any questions on the above. Once I have this information I’ll discuss with the engineers.