Guides 15 Aug 2026 4 min read by Kalum

Google Site Kit: what it is actually good for (and what it is not)

Site Kit connects Search Console, Analytics and AdSense to WordPress with one sign-in. That is genuinely useful. The dashboard it puts in your admin is mostly not. Here is how to set it up and what to ignore.

Site Kit is Google's own free WordPress plugin. Its real value is not the charts it adds to your admin — it is that it handles the one genuinely annoying part of Google's tools: authentication.

What Site Kit actually is

Connecting Search Console, Analytics 4 and AdSense to a site normally means verification files, tracking snippets in your theme, and — if you want the data programmatically — a Google Cloud project, an OAuth consent screen and API credentials. That is a genuinely unpleasant afternoon.

Site Kit replaces all of it with one Google sign-in. After that, your WordPress install holds valid credentials for those services, and any plugin that knows how to ask can read your own data without you ever touching an API key.

That last part is the bit people miss. Site Kit is not only a dashboard; it is a credential store other tools can use.

Setting it up without the mistakes

1. Plugins → Add new → "Site Kit by Google" → Install → Activate.
2. Sign in with the right Google account. This is the mistake that costs people an hour: use the account that already owns your Search Console property and your Analytics property. Signing in with a different one creates duplicate properties and you will be untangling it later.
3. Connect Search Console — offered first, and it is the one that matters most.
4. Connect Analytics. If you already have a GA4 property, pick it rather than letting Site Kit create a new one. If you let it create one, you start your history from zero today.
5. Connect AdSense only if you actually run ads. It will offer to place the ad code for you; if your theme or another plugin already inserts it, decline, or you will end up with the snippet twice.
6. Check the owner. Site Kit ties the connection to one WordPress user. If that user is later deleted, the connection dies with it. Connect as an administrator account that will exist in two years.

What it is good for

• One sign-in instead of three setups. Genuinely the best reason to use it.
• Verification handled. No meta tag to paste, no HTML file to upload.
• Per-post numbers where you edit. Opening a post and seeing its clicks and impressions in the editor is a small thing that changes behaviour — you notice the decaying posts because you keep walking past them.
• Other tools can use the connection. Once Site Kit holds the credentials, a plugin running inside WordPress can read Search Console, Analytics and AdSense on your behalf. That is how Fix My SERP pulls your real clicks, visitors and ad revenue without you ever creating a Cloud project.

What it is not good for

Being straight about the limits, because a lot of people install it expecting an SEO tool:

• It does not tell you what to do. It shows your top queries and your traffic trend. It will not tell you which page is closest to page one, which snippet is underperforming, or what the pages above you cover that yours does not.
• The date ranges are short and the rows are few. You get a summary, not the full export. For real analysis you still want the CSV from Search Console itself.
• It adds weight to wp-admin. Not fatal, but noticeable on cheap hosting.
• It is not a substitute for Search Console. Indexing reports, the URL inspection tool, sitemaps, manual actions — all still live in Search Console, and all matter more than the charts Site Kit shows.

The property question that trips everyone up

Search Console has two kinds of property and the difference bites constantly:

• URL-prefix — https://example.com/. Covers exactly that protocol and subdomain. This is what Site Kit and most SEO plugins create, because it can be verified with a meta tag.
• Domain — sc-domain:example.com. Covers every subdomain and both protocols. Needs a DNS TXT record.

Why it matters in practice: the "request indexing" deep links that tools generate include the property in the URL. Point one at a property you never verified and Google shows a 404, which looks like a broken tool and is actually a mismatch. If a link like that fails for you, the property type is almost always the reason.

The tidy setup is to have both — a Domain property for coverage and the URL-prefix one that Site Kit made — and to know which one your tools are using.

What to do after it is connected

1. Submit your sitemap in Search Console itself, not in Site Kit. Sitemaps → paste the URL → Submit.
2. Check the Pages report for indexing problems. This is the part Site Kit does not surface and the part that can silently cost you everything.
3. Export the last three months from Performance and turn it into an action plan. Site Kit's dashboard is for noticing; the export is for deciding.
4. Leave it alone for a month. Daily traffic charts on a small site are noise, and watching them is a hobby, not work.

Install it, connect it properly, then get your decisions from the export rather than the dashboard. That is the whole trick.

Read next

Striking distance keywords: the traffic you already own

Positions 4 to 20 are where most small sites are quietly sitting on their next 40% of traffic. Here is how to find those keywords in a free Search Console export, work out which ones are worth the afternoon, and move them.

Keyword research without Ahrefs or Semrush

Paid keyword tools sell you two things: a volume number and a difficulty score. Both are estimates. Here is how to get better answers for free, using sources that are closer to the truth than either.

Turn your Search Console export into an action plan

Everyone exports the CSV. Almost nobody does anything with it. Here are the six things to pull out of that file, in order, and what each one tells you to do this week.