Google Search Console Integration

Connecting Google Search Console (GSC) to a project brings real organic search data — impressions, clicks, CTR, and position — into your SitePulse audit context. This data appears on the project overview page and enriches SEO recommendations with real-world search performance.

Prerequisites

• A Google account with GSC access to the property you want to connect
• The property must be verified in Google Search Console (domain property or URL prefix)
• The audited domain must match the GSC property

Connecting GSC

Go to Project → Settings → Integrations → Google Search Console.

Enter the Property name exactly as it appears in Search Console's property picker:

• Domain property: sc-domain:acme-coffee.example
• URL-prefix property: https://www.acme-coffee.example/ (protocol, www, and trailing slash must match)

Then click Connect Google Search Console. You are redirected to Google's OAuth consent screen. Review the requested scopes and click Allow.

SitePulse requests:

• https://www.googleapis.com/auth/webmasters.readonly — read-only access to your GSC data

After authorization, you are redirected back to SitePulse and data is fetched for the property you entered. You can change the property name later without reconnecting — edit it and click Save.

What GSC data is shown

Once connected, the following data appears:

On the project overview page:

• Total impressions (last 28 days)
• Total clicks (last 28 days)
• Average CTR
• Average position

On URL audit detail pages:

• Per-URL impressions, clicks, CTR, and position (where GSC has data for that URL)
• Top queries for the audited URL
• GSC-derived recommendations (e.g. "This page has high impressions but low CTR — improve the meta description")

Data refresh

GSC data is fetched on demand when you open a project or audit page. It is not stored in SitePulse's database — each load queries the GSC API directly. GSC data has a ~48-hour processing delay — very recent changes to search performance may not be reflected.

OAuth token management

The GSC OAuth token is stored per-user, per-project. If your Google account password changes or you revoke SitePulse's access in your Google account, the token becomes invalid and you need to reconnect.

To reconnect: go to Project → Settings → Integrations → Google Search Console → Reconnect.

Disconnecting GSC

Go to Project → Settings → Integrations → Google Search Console → Disconnect. This removes the OAuth token from SitePulse. GSC data no longer appears on the project.

To fully revoke access, also remove SitePulse from your Google Account → Security → Third-party apps page.