Google Site Kit provides a connection layer between WordPress and selected Google services, but a successful setup depends on more than installing a plugin. The site must be publicly accessible, the WordPress REST API must respond correctly, and the person completing the process must have the right WordPress and Google permissions. Site URL settings, maintenance mode, browser extensions, plugin conflicts and hosting restrictions can also affect the connection.
This guide explains the complete Google Site Kit setup path, including ownership verification, the required Search Console connection and the optional Analytics connection. It also presents a staged troubleshooting process for REST API, valid JSON, URL, verification and migration problems. An empty dashboard is not, by itself, proof that installation failed: connected services may need time to populate reporting data.
What to Check Before Starting Google Site Kit Setup
Pre-installation checklist
Before installing Site Kit, review the documented environment and access requirements. The listed requirements include WordPress 5.2 or newer, PHP 7.4 or newer, a modern browser and a publicly accessible production site. The WordPress REST API must also be available, because Site Kit relies on it for communication.
Check the REST API from Tools > Site Health. Record any warning or error before changing settings. Setup should be performed by a WordPress administrator using the Google account intended to manage the site and connect the relevant Google properties.
Also check whether a maintenance-mode or coming-soon feature is hiding the site from public access. Such a barrier can prevent setup and verification. If it must be temporarily deactivated for testing, do so in a controlled way and reactivate it after the connection has been checked.
Required setup versus optional connections
Search Console is part of the required Site Kit setup. Google Analytics is different: it can be connected during the initial flow or added later. Keeping this distinction clear helps diagnose an incomplete setup. A missing Analytics connection does not necessarily mean that the initial Site Kit installation failed, while an unfinished Search Console stage can prevent the required setup from being completed.
How to Install and Configure Google Site Kit in WordPress
Install and activate the plugin
In the WordPress administration area, go to Plugins > Add New. Search for Site Kit, select Install Now and then activate it. After activation, open Site Kit > Dashboard to begin configuration.
Use the production site for this process, not a site that is inaccessible to the public. Exact screens and labels may change as the product documentation changes, so follow the prompts presented in the current setup flow rather than relying on an older visual sequence.
Authorize the initial setup
Sign in with the intended Google account and approve the permissions requested by Site Kit. The initial flow includes site ownership verification, metrics authorization and the Search Console step. The account should have appropriate access to the site and the Google properties that you intend to connect; being a WordPress administrator does not automatically provide every Google-service permission.
Complete each presented stage before judging the dashboard. A connection status and the later availability of reports are separate matters. Reporting data depends on the connected Google services and their processing, so an initially empty view does not alone establish that the installation is broken.
Complete Site Verification and Connect Search Console
Ownership verification
Site Kit uses a token-based ownership verification process. The documented methods include an HTML file or a meta tag. Follow the method shown in the setup flow and allow Site Kit to check whether the verification token can be detected.
If verification fails, first confirm that the site is publicly reachable and that no maintenance or coming-soon barrier is interfering. A verification error does not identify one universal cause. It may require checking token detection, URL configuration and the accessibility of the site from the verification service.
Search Console property selection
Search Console is required for Site Kit setup. When a relevant property already exists, Site Kit can connect it. When one is not already associated with the site, Site Kit can create a URL-prefix property. Select the property that corresponds to the site address being configured.
Do not treat the completion of this connection as a guarantee that all Search Console data will appear immediately or be complete in every view. Connection status confirms the setup path; reporting availability depends on the connected service and its processing.
Connect Google Analytics Through Site Kit
Connect Analytics during or after setup
Analytics can be connected during the initial Site Kit setup or later. To add it after setup, go to Site Kit > Settings > Connect More Services > Analytics > Set up Analytics. This makes Analytics an additional configuration step rather than a requirement for every initial Site Kit installation.
Use the Google account with suitable access to the intended Analytics resources. If the account does not have the necessary permissions, the connection may not offer the expected properties or streams.
Choose the Analytics resources
The Analytics flow allows selection of an existing account, property and web data stream. The documented flow also allows creation of Analytics resources through Site Kit. Choose the resources that belong to the site being configured and review the selections before completing the connection.
Analytics reporting should not be presented as guaranteed to be complete or real-time. The information available in Site Kit depends on the connected Google service and its processing, so configuration success and reporting availability should be evaluated separately.
Fix REST API, JSON and WordPress URL Connection Errors
Check REST API and valid JSON responses
When Site Kit reports a REST API, JSON or unexpected-response error, begin with Tools > Site Health. Inspect the REST API status and record the exact message. A valid JSON error can have several causes, including a plugin conflict, a server error, a REST API problem or a browser extension.
This means the message should be treated as a diagnostic category, not as proof of one specific failure. Site Health can show whether the problem is visible at the WordPress level. Further investigation may require controlled testing, server information or hosting configuration details.
Verify WordPress and Site Address values
Compare the WordPress Address and Site Address values. Mismatches can contribute to offline or connection errors, particularly when the addresses differ in http versus https, domain, or subfolder structure. Site Kit states that the WordPress Address must match the Site Address or be a subfolder URL of it.
Do not change production URLs casually. A URL change affects the WordPress installation, not only Site Kit. Before changing site-wide configuration, make a backup and establish a clear rollback plan. A migration, domain move or HTTPS change can also leave Site Kit records associated with the previous URL.
Test browser, plugin and hosting causes
Use a staged process instead of permanently disabling controls. Retry the setup in a private browser window without extensions. If the problem continues, use Troubleshooting Mode to test Site Kit with other plugins deactivated for the logged-in administrator session. This is a controlled compatibility test, not proof that a particular plugin is responsible.
Next investigate infrastructure categories. Hosting providers, firewalls or CDNs may block external requests to Site Kit services. cURL errors can indicate server-level configuration or connectivity problems. Ask the hosting or infrastructure provider to investigate outbound requests and relevant server configuration rather than assuming that every host has the same cause.
After testing, restore temporarily changed plugins and controls, then verify the public site and the Site Kit connection again. Do not leave security, firewall, maintenance or coming-soon protections disabled merely to make setup proceed.
Troubleshoot Verification, Migrations and Agency Access
Migration and URL-change recovery
After a domain move, HTTPS change, migration or URL-changing plugin configuration, Site Kit may retain records for the previous URL. If normal URL checks and reconnection steps do not resolve the issue, the documented reset path is Tools > Available Tools > Reset Site Kit.
Use this step cautiously. Resetting Site Kit disconnects connected modules for all users, so those modules must be configured again. Before resetting, record the Google account, properties and streams involved, confirm the current site URL and ensure that the site is publicly accessible. The reset is a recovery option, not a first response to every setup error.
For verification failures after a migration, check the current address, public accessibility and whether the verification token can be detected. If maintenance or coming-soon mode was used during the migration, temporarily remove that barrier only for the controlled setup test and restore it afterward if needed.
Permissions for freelancers and agencies
Only WordPress administrators can initially set up Site Kit and configure its services. That does not mean every client or collaborator should receive administrator access simply to view reports. Dashboard sharing can provide other WordPress users with a restricted view. Google-service permissions may still be required for users who need service-specific data access.
For agency work, document which administrator completed setup, which Google account was used and which properties were connected. This reduces uncertainty during future maintenance without expanding permissions unnecessarily. If a client needs only a restricted dashboard view, use the documented sharing model rather than granting broad WordPress or Google access solely for reporting.
Reliable Google Site Kit setup starts with prerequisites: supported WordPress and PHP versions, a modern browser, public accessibility, administrator access and a working REST API. Install and authorize Site Kit, complete ownership verification and the required Search Console connection, then add Analytics during setup or later if needed. When errors appear, work from Site Health and URL checks through private-browser testing, Troubleshooting Mode and hosting investigation. Treat migrations and resets with extra care because connected modules can be disconnected for all users. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.