---
title: "Search Console"
description: "Connecting Google Search Console, what it brings into the workspace, and what Blogged does with it."
updated: "2026-08-28"
verifiedAgainst:
  - apps/web/app/api/gsc
  - packages/shared/src/free-grant.ts
  - docs/gsc-production-runbook.md
---

Connecting Google Search Console is the single highest value integration for a
blog, because it is the only source that says what search actually did with your
pages.

<Callout variant="note" title="Not included in the Free grant">
  Search Console is a paid-only feature. On a Free Project the connection is
  refused with an upgrade prompt rather than a quota message, and upgrading that
  exact Project turns it on without losing any work.
</Callout>

## Connecting

Settings, then Search Console. You authorise access with Google and choose the
property that matches your blog's primary domain.

<Callout variant="note">
  Connect the property for the hostname your blog is actually served from. If you
  are on a custom domain, that is your domain rather than the blogged.dev
  subdomain.
</Callout>

## What it brings in

- Clicks, impressions, position and click through rate, per page and per query.
- Indexing verdicts per URL.
- Confirmation that your sitemap was submitted and read.

## Where it appears

In the workspace analytics, and per post in the editor's Search Console panel:
the verdict for that URL and its thirty day performance, next to the article
itself.

## Sync

Data is synchronised on a schedule rather than on demand. Search Console's own
data lags by a day or two, so a post published this morning has nothing to show
yet, and that is Google rather than Blogged.

## Disconnecting

Disconnecting stops the sync and leaves what was already imported. Tokens are
stored encrypted and are removed when you disconnect.