Back to Community
Home / Community / Plugin → Site kit by google

Troubleshooting Common Google Site Kit Connection Errors

59 threads Sep 16, 2025 Plugin → Site kit by google

Content

Connecting your WordPress site to Google's services with Site Kit by Google should be straightforward, but sometimes you can hit a frustrating roadblock. Based on community reports, here are the most common connection errors and the steps you can take to resolve them.

1. The Spinning Wheel of Death (Stuck on Loading)

This is a prevalent issue where the setup process, particularly for Analytics, gets stuck on a loading screen without displaying an error.

Why it happens:

  • A known conflict can occur if Google Tag Manager is connected before Analytics.
  • A temporary glitch in the connection between your site and Google's servers.

How to fix it:

  • Disconnect Tag Manager First: Navigate to Site Kit > Settings > Tag Manager > Edit and disconnect the Tag Manager module. Then, try connecting the Analytics module again.
  • Use a Private Browser: Attempt the setup process from an incognito or private browser window to rule out browser extension conflicts.
  • Plugin Reset: As a last resort, perform a full reset of the Site Kit plugin (found under Tools > Available Tools > Reset Site Kit). Note that this will require you to reconnect all services.

2. Quota Errors (429 or "User Rate Limit Exceeded")

These errors indicate that too many requests have been sent to Google's API in a short period.

Why it happens:

  • This is typically a limit enforced by Google's API, not the Site Kit plugin itself.
  • It can happen if you are repeatedly attempting setup on a site or across multiple sites from the same Google account.

How to fix it:

  • Wait it out: The simplest solution is often to wait for an hour or more before trying again, as the quota limit resets.
  • Use a Different Google Account: If you need immediate access, try disconnecting and reconnecting with a different Google account that has not recently hit the quota limit.

3. "Site Not Found" or Proxy Errors

This error suggests that the Site Kit service cannot find your site's unique identifier in its system.

Why it happens:

  • This often occurs after a site migration, domain change, or if the plugin was not reset before changing the site's URL.
  • It can also be caused by a corrupted setup state.

How to fix it:

  • Reset Site Kit: A full plugin reset is usually required to clear the old site records and establish a new connection with the current site URL.

4. "Insufficient Permissions" in Analytics

You see this message after setup, preventing you from viewing Analytics data in your dashboard.

Why it happens:

  • The Google account you are currently using to view the Site Kit dashboard does not have "View" or "Edit" permissions on the Google Analytics property that was connected by another administrator.

How to fix it:

  • Contact the Administrator: Reach out to the person who set up Site Kit and ask them to grant your Google account the necessary permissions in Google Analytics.
  • Reset and Reconnect: If you are an administrator and cannot contact the original person, you can reset Site Kit and reconnect it with your own Google account that has full access to Analytics.

5. "The response is not a valid JSON response"

This is a WordPress REST API error, indicating something is blocking communication on your site.

Why it happens:

  • Security plugins or firewalls (like Cloudflare) may be blocking or altering API requests.
  • Corrupted WordPress core files or a conflicting plugin.

How to fix it:

  • Check your Site Health status (under Tools > Site Health) for any critical issues related to the REST API.
  • Temporarily disable security plugins or configure them to allow requests to the /wp-json/google-site-kit/ endpoint.

General Troubleshooting Tips

  • Always Share Site Health Info: When seeking help, your WordPress Site Health Information is the most critical data for troubleshooters to understand your site's environment.
  • Check the Browser Console: Errors logged in your browser's JavaScript console (F12) can provide vital clues.
  • Test in Incognito Mode: This is a quick way to eliminate browser cache and extensions as the cause.

Most connection issues with Site Kit by Google can be resolved by methodically working through these common causes. If problems persist, the community often finds that sharing detailed information leads to a solution.

Related Support Threads Support