Google Site Kit

Site Kit's real value is the setup, not the dashboard. It verifies your site with Search Console, places the Analytics tag correctly, and connects AdSense and PageSpeed Insights — all through an authenticated flow instead of you pasting snippets into the theme. The summary widgets it adds to the admin are a convenience, and a smaller one than it looks.

What it connects

Search Console is the one worth having, and the one people most often never set up. Impressions and queries tell you what the site is actually being found for, which is information nothing on your own server can give you — the point made in the SEO checklist and the first thing to check when a site is not showing in Google.

Why the setup path matters

The alternative to Site Kit is pasting tracking code into the theme header. That works, and it fails in three predictable ways: the code is lost at the next theme update if it went into a parent theme, it is duplicated when someone adds it a second time, and it is placed in a way that blocks rendering.

Site Kit removes all three. The tag goes in through the proper hooks, it goes in once, and it survives theme changes because it lives in a plugin. If you have added code by hand before, adding code to a page explains why the placement question is not trivial.

Duplicate tracking is the specific problem to watch for. If a theme option, a tag manager container and Site Kit all place Analytics, every session is counted several times and every number you report is wrong. Check for exactly one tag before trusting anything.

The dashboard, assessed honestly

Site Kit surfaces a summary of each connected service inside wp-admin. Whether that is useful depends on who you are.

For a site owner who never opens Analytics, it is genuinely valuable — the numbers appear where they already are, so they get looked at.

For anyone who does open Analytics, it is a slower, thinner version of a tool they already use. The summary cannot answer a real question; the moment you want a segment, a comparison or a funnel, you leave for the full interface anyway.

That is the case against carrying it purely for the dashboard: an extra plugin making authenticated API requests on admin page loads, so that a subset of numbers appears in a second place. Admin performance is a real thing to protect — see speeding up wp-admin.

What it does not do

• It does not manage consent. Placing a tracking tag where consent is required is your obligation, and Site Kit places the tag whenever it is configured. Pair it with cookie consent if that applies to your visitors.
• It does not anonymise anything for you. Configuration of what Analytics collects belongs in Analytics.
• It does not improve performance. The PageSpeed panel reports a score; acting on it is speeding up the site.
• It does not do SEO. It reports search data. Titles, structure and internal linking are elsewhere, as Yoast SEO covers on the plugin side.

How it compares with the alternatives

Against MonsterInsights and similar commercial analytics plugins, Site Kit is free, is published by the service it connects to, and does less. The commercial plugins add event tracking, ecommerce reporting and dashboards with more depth — and charge annually for it. If the reason you are choosing is "I want the numbers in the admin", the free one already does that.

Against pasting the tag yourself, Site Kit costs a plugin and saves you the three failure modes above. Against a tag manager, it is simpler and less flexible; a site with several marketing tags is better served by one container. The broader comparison is in analytics plugins.

Common mistakes

• Running two tracking implementations and reporting doubled traffic for months.
• Connecting every service including ones the site does not use, adding API calls for nothing.
• Assuming the plugin handles consent, which is the most common compliance gap around any tracking plugin.
• Treating the PageSpeed score as the goal rather than the field data behind it.
• Granting the connection from a personal Google account that later leaves the organisation, taking the site's verification with it. Connect from an account the business owns.

Deciding

Install Site Kit for the setup: verified Search Console, one correctly placed Analytics tag, no code in the theme. That alone justifies it on most sites. Keep it afterwards if the in-admin numbers are the only ones anybody looks at, and remove it if your team lives in Analytics anyway — the tag can be placed a dozen other ways, and one fewer authenticated plugin in the admin is a small, real win.