Fixing common issues with Site Kit

As noted in the Troubleshooting Setup guide, cURL-related errors are the result of a misconfiguration at the hosting level. Reach out to your hosting provider to ensure that your site is able to communicate successfully with ​​https://sitekit.withgoogle.com/.

As noted in the Troubleshooting Setup guide, this is a general WordPress error that can occur for a wide variety of reasons, including plugin conflicts, server errors, REST API errors, or browser extensions. Follow the steps outlined in this guide to resolve.

The “Your site may not be ready for Site Kit” error message typically includes more details, e.g. Site Kit is unable to place or detect tags on your site. Check out the Setup guide for specific troubleshooting steps for the error message that you are seeing. The setup guides related to this error include:

• Your site may not be ready for for Site Kit, google_api_connection_fail
• Your site may not be ready for Site Kit: Looks like Site Kit is unable to place or detect tags on your site
• Your site may not be ready for Site Kit: Looks like your site is having a technical issue with connecting to the Site Kit authentication service.
• Your site may not be ready for Site Kit: Site Kit cannot access the WordPress REST API

It can take a few days after connecting Site Kit to a Google service for data to begin to display in your dashboard if you connected Site Kit to a new property. The “gathering data” message typically appears when you’ve recently set up a Google service (e.g. just created a new Analytics account) and/or your site is new, and data is not yet available for display. You’ll find out more on this by visiting this guide.

If you are still seeing this message after a few days, feel free to create a new topic on our WordPress.org support forum.

There can be various causes if your site visits are not registering in Analytics, whether using Site Kit. Some such causes include:

• A non standard or wrongly placed Analytics snippet
• A modification to the standard Analytics snippet placed on your site
• A change to your Site Kit configuration (For example, an administrator may have togged off the option to Place Google Analytics code)
• A consent mode configuration, meaning users from some regions may not be counted in Analytics until they grant consent. See this guide for more information. 
• A consent management or cookies type plugin configuration, resulting in users not being counted until a user consents. Alternatively, if you have consent mode enabled within Site Kit without having configured a consent management plugin active, meaning users are unable to grant consent. 
• You may be checking for your own site visit. The default setting within Site Kit is to not count logged in traffic for Analytics reporting. With this default setting enabled, your own site visits won’t register if you are logged in while visiting your site. 
• You may have a WP_ENVIRONMENT_TYPE defined as something other than production in your wp-config.php file. If you do have a WP_ENVIRONMENT_TYPE value, it must be set to production. A local or other value will result in Site Kit not placing the Google Analytics snippet, which will mean site visits won’t be recorded unless you placed your Analytics snippet via other means.

You can use the tagassistant.google.com service to check whether any Analytics snippet is firing as expected for your site. Alternatively, you can reach out in the Site Kit support forums for further assistance.

If you’re new to AdSense when you connect via Site Kit, your new AdSense account and your site will need to be manually reviewed and approved for ads by the AdSense team. Ads will not display until your account and site have been approved. Check out our Managing AdSense guide for more information about how AdSense works within Site Kit, and the approval process.

Note that you can check your approval status within Site Kit at any time by going to Settings > Connected Services > AdSense and clicking “Check your site status.” This link will direct you to AdSense. If you see “Ready,” your account and site have been approved and should be displaying ads. If you see “Getting ready…,” your account and site are still under review and your site will not display ads until they have been approved.

If the AdSense code snippet is successfully embedded on your site and both your account and site have been approved, but your site is still not showing ads, there can be a number of causes, including modifications to the AdSense snippet placed via Site Kit, configurations at AdSense level, ads not set to appear for you as a logged in user – which is expected or something else. You can reach out in the Site Kit support forums for assistance, contact the AdSense Help Center for assistance, or contact the AdSense Help Center should the issue be related to your AdSense account. You can also check the Ads Serving Troubleshooter to highlight any possible causes.

As noted in the Troubleshooting Analytics guide, this error occurs when the Google account that you used to connect to Analytics with Site Kit does not have permission to access the necessary Universal Analytics data in Google Analytics. Check with an administrator for the Analytics account to ensure that you have Viewer permissions or above for this property in Analytics.

There were changes in WordPress to how plugin translations work, resulting in some plugin translations reverting to English during plugin updates.

If this occurs, you can uninstall the plugin before installing once more. Your language will switch back to your defined language from your WordPress general settings. To ensure this no longer happens going forward, you can also use the Performance Translations plugin. If this plugin is active during Site Kit updates, the plugin language won’t switch to English upon each Site Kit update

If you’re experiencing a different issue with Site Kit (for example, your data isn’t updating or you’re seeing a blank screen), try the following troubleshooting steps:

• Check does the same occur from a Chrome browser incognito window. This can help with any browser caching, extensions or configurations that may be impacting Site Kit set up or functionality. 
• Update to the latest version of Site Kit: In the WordPress administrator menu, go to Plugins > Installed Plugins. If there is a message that says “There is a new version of Site Kit by Google available” in the Site Kit section, click update now to update to the latest version of the plugin.
• Ensure that your site is publicly accessible: For initial Site Kit setup, your site must be publicly accessible with no password protection and cannot be using a maintenance mode or coming soon plugin. Check out the Known limitations in Site Kit guide for more details and other known limitations.
• Ensure that your environment fulfills all minimum requirements: See the Installation requirements guide for more details.
• Try using a different computer to set up Site Kit: Sometimes local software, applications, or settings can impact Site Kit installation.
• Try using a different computer to set up Site Kit: Sometimes local software, applications, or settings can impact Site Kit installation.
• Use the Health Check & Troubleshooting plugin to check for potential plugin conflicts: Sometimes users may be encountering issues based on a conflict with another plugin. See this guide for details on how to use the Health Check & Troubleshoot plugin which can be used to check for such conflicts. 
• Attempt set up from a disposable WordPress site, or another site you have access to: In the event that the issue you’re facing is host or environment related, use a service such as TasteWP or InstaWP to quickly create a free WordPress site for testing, while checking does the same occur. Alternatively, if you have access to another WordPress site, perform some checks on that site.

If you’re still encountering issues, check out our documentation or create a new topic on our WordPress.org support forum.