Site Kit is a connector, not a content plugin — everything it shows a public visitor is a fixed <script>/<meta> tag baked into the page head (Analytics/gtag.js or Google Tag Manager, an optional AdSense snippet, a Search Console verification tag). None of that needs WordPress once the page is built; the visitor's browser talks directly to Google's own servers, the same as on a live site. The dashboard widgets and the one-time Google account connection run entirely inside wp-admin.
Fully Static
The tracking and verification tags are captured as-is in the static build and keep reporting real visitor analytics straight from the browser to Google, with no per-request WordPress involvement.
None — the Site Kit dashboard widgets and the OAuth account-connection flow both run entirely inside wp-admin against Google's own APIs and are unaffected by serving mode.
None needed — Site Kit declares no public routes of its own.
No special setup — detected automatically once active.
Analytics/Tag Manager/AdSense reporting depends on the visitor's own browser being able to reach Google's servers — an ad blocker, browser tracking-protection setting, or an outage on Google's side can affect data collection, entirely independent of the static build or WordPress. If analytics numbers look incomplete after switching to a static build, check for client-side blockers first rather than assuming the static build dropped the tag.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp