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.
  • 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.
  • Disable REST API: This, and other plugins that can disable the REST API can result in set up failure – usually with warnings, and also errors within the Site Kit dashboard, such as a “Data error in Search Console: DRA: Only authenticated users can access the REST API.” error. Your WordPress REST API is something that Site Kit uses in order to communicate with your site.
  • Relative URL: Unable to set up Site Kit or connect modules. Temporarily disable this plugin when setting up Site Kit or connecting modules .
  • Merge, Minify + Refresh: The Site Kit admin toolbar won’t load on hover. Disabling the plugin will allow you to see the admin toolbar once more.

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.