An error occurred: Your temporary access code is invalid or expired
Checking requirements failed
cURL errors
Error: The response is not a valid JSON response
Error: You are probably offline
http request failed
Looks like the URL of your site has changed
Maintenance mode and coming soon plugins
Moving domains
Quota errors
Sign in loop
Site Kit has already been configured by another admin of this site
Stuck on Checking Compatibility
The caller does not have permission
The link you followed has expired
The necessary verification token could not be found on your site
Unknown Error (code: ‘redirect_uri’ mismatch)
Your site may not be ready for Site Kit: amp_cdn_restricted
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 you may be using a caching plugin that could interfere with setup
Your site may not be ready for Site Kit: Site Kit cannot access the WordPress REST API

An error occurred: Your temporary access code is invalid or expired

A screenshot of the temporary access code error.

This error occurs if you have waited too long to proceed to the next step and the temporary access code that is created during setup has expired. Click Cancel to exit setup and restart the setup process.

Checking requirements failed

This error occurs when Site Kit is unable to check whether all plugin setup requirements are met. Most often, this requirement is a lack of permissions in Google Workspace for your Google account to access the appropriate Google service that you are trying to set up via Site Kit. Note that Site Verification and Search Console are required for initial Site Kit setup in addition to any other services that you want to connect. 

To resolve this issue, reach out to your Google Workspace administrator to ask them to turn on permissions for the service for your Google account.

cURL errors

cURL-related errors such as cURL 60 error – no curl.cainfo set in PHP and cURL error 7: Failed to connect to sitekit.withgoogle.com are the result of a misconfiguration at the hosting level, so you’ll need to communicate with your hosting provider or check your hosting configurations to ensure that your site can communicate successfully with https://sitekit.withgoogle.com.

Error: The response is not a valid JSON response

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. If you encounter this error, the troubleshooting steps below may help you determine the cause:

  • Try refreshing the page, as this could have been an intermittent error.
  • Log into your WordPress admin panel from your browser’s incognito window or private browser mode with no extensions activated. If the error does not appear, one of your browser extensions is likely causing a conflict.
  • Check your site’s Site Health status by going to Tools > Site Health > Status. If there is an issue with your WordPress REST API, which Site Kit and many other plugins depend on, it will be highlighted here. Depending on the error, the solution may involve changes at the host level.
  • Use the Health Check and Troubleshooting plugin to enable Troubleshooting Mode, which will allow you to test how your site runs with only the Site Kit plugin active, without the need to disable other plugins. This doesn’t impact the front-end of your site as troubleshooting mode is active for logged-in administrators only. 
  • Search the Fixing WordPress forum for assistance and review previous topics regarding this error for possible solutions

Error: You are probably offline

This error can appear if you’re experiencing temporary internet or network-related issues. 

It may also occur if you have mismatching WordPress Address and Site Address URL values in your general WordPress configuration in Settings > General. Your WordPress Address (URL) value must match your Site Address (URL) (including http/https) or be a subfolder URL of the Site Address. For example:

Site Address (URL): https://www.example.com

WordPress Address (URL): https://www.example.com

or

Site Address (URL): https://www.example.com

WordPress Address (URL): https://www.example.com/wordpress

You can change your Site and/or WordPress Address by following this guide from WordPress.

http request failed

This message indicates that something is blocking the ability for your site to make external connections. Site Kit must be able to make an external connection to https://sitekit.withgoogle.com for setup. Hosting providers, firewalls, or CDNs can block external connections. Please check with your hosting provider for assistance with troubleshooting.

Maintenance mode and coming soon plugins

Be aware that your site needs to be live (with no temporary “coming soon” page) in order for data to be collected and displayed within the Site Kit dashboard for the connected Google services. 

Maintenance mode and coming soon plugins typically overwrite your WordPress front-end so that your site is not able to connect to Site Kit. Temporarily deactivate these plugins before proceeding with Site Kit setup.

When setup is complete, you can reactivate your coming soon or maintenance mode plugin. 

Looks like the URL of your site has changed

This message displays when Site Kit cannot find your site’s current URL in the Site Kit service because your site’s URL has changed as part of a site migration, adding/removing HTTPS, and/or using plugins that can change your site’s URLs, such as language plugins. 

Performing a reset of Site Kit by going to Tools > Available Tools > Reset Site Kit will clear your site’s previous URL from Site Kit and allow you to reconnect using the new URL. Note that resetting will cause all previously connected Site Kit modules to be disconnected for all Site Kit users.

Moving domains

While Site Kit can recognize domain name changes, if you plan on moving domains, we recommend resetting Site Kit before migrating your site to your new domain by going to Tools > Available Tools > Reset Site Kit. This ensures your site records are reset on the Site Kit service. 

If you’ve already moved domains and you’re encountering any issues you can perform a site reset in order for the plugin to recognize your new domain. 

Note that by resetting Site Kit, all services will become disconnected for all connected users. You’ll need to configure the plugin and set up each service once again.

Quota errors

Error: Quota Error: You have exceeded the maximum number of writes/day for this project. may occur from time to time when trying to set up Google services. This error is temporary and will often resolve within the next day. Please try setting up again later.


Error: Quota Error: User Rate Limit Exceeded. can occur when individual user quota limits have been exceeded and are typically resolved within an hour Please try again later. To prevent abuse, Site Kit has a limit on the number of “writes” per hour per Site Kit user, where the creation of an Analytics account, property, and/or view via Site Kit is a “write.”

Sign in loop

If you’re being redirected to your homepage or your wp-admin page after a particular stage during the Site Kit setup flow this may be because of a hosting configuration or your site records not matching those on the Site Kit service. 

If you’ve changed your site URL or your WP admin path you can perform a plugin reset to reset your site on the Site Kit service. Note that this will result in you and all other connected users having to set up the plugin and each service once more.

Site Kit has already been configured by another admin of this site

This message indicates that another WordPress user with administrator permissions on your site has already installed and configured Site Kit. 

To use Site Kit, sign in with your own Google account. If you have permissions to access all of the Google services being used via Site Kit (i.e. Analytics), you will see the appropriate statistics in the Site Kit Dashboard. If you see permissions errors, please contact your site administrator to request the necessary access to the associated Google services.

The caller does not have permission

This error can occur if you use a Google Workspace account to try and connect the Google Analytics or AdSense modules and these modules are restricted at the Google Workspace level. 

To resolve this issue, reach out to your Google Workspace administrator to ask them to turn on permissions for Analytics and/or AdSense for your Google account.

Stuck on Checking Compatibility

If your site gets stuck on the Checking Compatibility screen while trying to set up Site Kit, please create a post on our support forum for assistance.

This error occurs when necessary query parameters are stripped from the URLs that redirect you from Google back to your WordPress site to complete Site Kit setup. Query parameters can be stripped by browser extensions, so redo the Site Kit setup process in a Chrome incognito browser window where no extensions will be activated.

The necessary verification token could not be found on your site

This error occurs when the Site Kit service is unable to verify your ownership of your site.

In the first step of the Site Kit setup process, Site Kit places a verification token (as an HTML file or meta tag) on your website which the Google Site Verification service then checks for to confirm your site ownership. This error message is displayed if the token cannot be found for any reason.

Before trying setup again, please ensure that your site is publicly available and your host, firewall, plugin, maintenance mode plugin, or another configuration is not blocking the Site Verification service. If you try setup again and still experience the issue, please create a post on our support forum for assistance.

Unknown Error (code: redirect_uri mismatch)

This message displays when Site Kit cannot find your site’s current URL because it has changed as part of a site migration, adding/removing HTTPS, and/or using plugins that can change your site’s URLs, such as language plugins. Performing a reset of Site Kit by going to Tools > Available Tools > Reset Site Kit will clear your site’s previous URL from the Site Kit service and allow you to reconnect using the new URL. Note that resetting will cause all previously connected Site Kit modules to be disconnected for all Site Kit users.

Your site may not be ready for Site Kit: amp_cdn_restricted

The AMP framework is used during Site Kit setup. At this time, AMP is restricted in some regions, and this error may be encountered if you are located in one of these regions. 

As AMP is required during setup only, you can attempt setup later when/if you are outside of the restricted region. There is also an open GitHub issue in relation to AMP usage in Site Kit; however there are no plans at present to stop using AMP as part of the Site Kit setup workflow. 

Your site may not be ready for Site Kit: Looks like Site Kit is unable to place or detect tags on your site

As part of the setup process, Site Kit conducts several checks to ensure that your site will be able to connect to Google and successfully use Site Kit. This message displays when one of those checks has failed. This message should always display with another error message that provides more details about the particular error.

Your site may not be ready for Site Kit: Looks like you’re using a caching plugin which could interfere with setup

Caching plugins can conflict with Site Kit, in particular during setup. If you encounter this notice, temporarily deactivate any caching or optimization plugins during setup only. After setup, you can re-activate these plugins.

If you’re not using a caching plugin and you encounter this notice, reach out to our support team in the WordPress support forums. This notice may be triggered by a hosting optimization with features similar to a caching plugin or other optimizations at the browser level. 

Your site may not be ready for Site Kit: Site Kit cannot access the WordPress REST API

This message displays when Site Kit cannot connect to the Google Search Console API, which is required for Site Kit. This can occur if your host, a firewall, plugin, or another configuration is blocking the ability to make external API requests, so please check these services to ensure that API connections are not blocked.