WordPress setups

If you’re having trouble setting up or using Site Kit, check the list below. If you encounter a problem that’s not listed here, please open a new support topic and we’ll be happy to help you troubleshoot.

Site Availability

  • Your site needs to be publicly accessible with no password protection on the homepage
  • 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. 

Google Accounts

  • Setup requires a WordPress login with the role of Administrator
  • You must also have access via your own Google account to the Google services that you are connecting to Site Kit


  • Opera: Temporarily disable the Ad Blocker feature while you’re setting up Site Kit.
  • Brave: As of version 1.38, the Brave browser auto-redirects AMP pages by default. With this setting enabled, you will not be able to complete Site Kit setup, and will also get an Error: Bad Request: missing parameter: ‘code’ message when trying to grant Site Kit permissions as part of setup or module connection. To complete setup or connect a module, disable this setting from Settings > Shields > Auto-redirect AMP pages.
  • All browsers: Temporarily disable any ad blocking extensions, such as AdBlock, when setting up Site Kit. Ad blockers can mistake API requests for the AdSense module in Site Kit as serving ads directly and block them.

WordPress REST API

The WordPress REST API is used by Site Kit to communicate between your site and the connected Google services. It must be enabled and accessible for site administrators during setup and when viewing the Site Kit dashboards. It is enabled by default on every WordPress site. 

Hosting configurations, firewall restrictions, or third-party plugins can cause WordPress REST-related errors. Please check these services to ensure that the WordPress REST API is not blocked or restricted.


Google services may be blocked in some regions for reasons outside of our control. These regional restrictions may impact Site Kit set up.

If you think that Google services are being blocked for you or are unsure then you can open a support topic for further assistance here.

Plugin Conflicts

  • Caching plugins (WP Super Cache, Breeze, Autoptimize): Caching plugin configurations can impact Site Kit setup. Temporarily disable caching plugins while you’re setting up Site Kit.
  • URL Conversion plugins (Make Paths Relative, Relative URL): Plugins that convert absolute URLs to relative URLs can cause issues with setting up Site Kit and connecting modules. Buttons which are required to complete setup/connecting modules may be unclickable. Temporarily disable these plugins before setting up Site Kit or connecting any modules within the plugin to avoid these issues.
  • Translation plugins (WPML, TranslatePress): Plugins that store language variations in the database as opposed to creating new language-specific pages can result in “no data available” notices. This is because Analytics is unable to track data for content that does not have its own individual post or page.
  • WPML: Analytics cannot be viewed for sites using WPML multi-domain setup.
  • JWT Auth: Users may encounter a report must be an array to partition dashboard error with the JWT Auth plugin active. This occurs because  the plugin blocks third-party plugin REST endpoints by default unless they have been whitelisted or authorization headers have been configured. There are more details on this added to the related GitHub issue.  
  • RegistrationMagic: Update to the latest version of RegistrationMagic to avoid a Cannot read properties of undefined (reading ‘Pe’) dashboard error, related to a Google Charts library conflict. A fix for this was included with RegistrationMagic version

WordPress Setups

  • Multisite: Currently, Site Kit doesn’t support WordPress multisite networks. If you want to use Site Kit in a WordPress multisite installation, activate the plugin for each individual site you would like to use it on.
  • Headless: Headless setups are not supported at this time.