Skip to main content
Connect Google Search Console (GSC) to pull in impressions, clicks, CTR, and average position for every query and landing page on your site. Hiveku uses this data to power SEO dashboards, content recommendations, and reporting.
Before you start: Set up a Google Cloud OAuth app and enable the Google Search Console API in your Google Cloud project.

​
Before You Start

  • A Google Cloud OAuth app registered in Hiveku’s Settings > OAuth Apps
  • The Google Search Console API enabled in your Google Cloud project (APIs & Services > Library > Google Search Console API)
  • At least one verified property in Search Console that the connecting Google account has access to

​
Two Ways to Connect

GSC can be connected in Hiveku via:
  • One-click OAuth (recommended) — browser-based flow using your registered Google app
  • Manual refresh token (fallback) — generate a refresh token via OAuth Playground and paste it in. Useful when the OAuth flow isn’t practical, e.g., for service-account style setups

​
Connect via One-Click OAuth

1

Open the integration

Go to Marketing > SEO > Add Connection > Google Search Console in Hiveku.
2

Select your Google OAuth app

Pick the Google app you registered under Settings > OAuth Apps. If none exist, create one first — see Set up a Google Cloud OAuth app.
3

Authorize with Google

Click Authorize. You’re redirected to Google, sign in with an account that has access to your Search Console property, and consent to the webmasters.readonly scope.
4

Pick a property

After consent, Hiveku shows a dropdown of every verified GSC property the account can see. Pick the one to connect.Property formats:
  • Domain property — sc-domain:example.com — covers all subdomains and both HTTP/HTTPS
  • URL-prefix property — https://www.example.com/ — only this exact prefix
Choose a Domain property when possible — it captures all traffic for the domain.
5

Confirm the connection

The connection saves and Hiveku starts fetching performance data.

​
Connect via Manual Refresh Token (Fallback)

Use this path when you can’t complete the browser flow or want to generate tokens out-of-band.
1

Open OAuth Playground

Go to developers.google.com/oauthplayground.In the gear icon (top right), check Use your own OAuth credentials and paste your Client ID and Client Secret from your Google Cloud OAuth app.
Also add https://developers.google.com/oauthplayground as an authorized redirect URI in your Google Cloud OAuth client — temporarily, for this flow. Remove it after you’ve generated your token.
2

Authorize the Search Console scope

In OAuth Playground, find Google Search Console API and select the scope:
https://www.googleapis.com/auth/webmasters.readonly
Click Authorize APIs, sign in with your GSC-owning Google account, and consent.
3

Exchange for a refresh token

Click Exchange authorization code for tokens. Copy the Refresh token value.
4

Paste into Hiveku

In Marketing > SEO > Add Connection > Google Search Console, switch to the Manual tab. Paste:
  • Refresh token
  • Site URL — sc-domain:example.com or https://www.example.com/
Save.

​
What You Get

Once connected, Hiveku pulls:
  • Impressions, clicks, CTR, and average position for every query
  • Landing page performance — which pages get the traffic
  • Device breakdowns — desktop, mobile, tablet
  • Country breakdowns
Historical data is backfilled up to GSC’s 16-month window, then refreshed on an ongoing schedule. Expect data to appear on the SEO dashboard within a few minutes of connecting.

​
Connect Multiple Properties

Repeat the flow for each additional GSC property. Each becomes its own connection in Hiveku and can feed different sites or reporting views.

​
Verify the Connection

  • Connection status shows Active
  • The SEO dashboard populates with query and page data within 5-10 minutes of connecting
  • Top queries, top pages, and trend charts all show data

​
Troubleshooting

The Google account you authorized with isn’t a verified owner or user of any Search Console property. Go to search.google.com/search-console and verify that the account has access to your site. Then disconnect and reconnect.
The webmasters.readonly scope wasn’t granted during authorization. This usually means the user unchecked a scope on the consent screen, or the scope isn’t listed in your OAuth consent screen config. Review the scopes on your OAuth consent screen and reconnect.
Some properties genuinely have no recent search data — verify in Search Console directly. If you see data there but not in Hiveku, check that the right property was selected (a URL-prefix property won’t capture traffic from other subdomains; try a Domain property).
Disconnect the GSC connection and reconnect — you’ll get the property picker again.
Enable the Google Search Console API in your Google Cloud project: APIs & Services > Library > Google Search Console API > Enable. Retry the connection.

​
What’s Next?

Set up SEO

Use GSC data for content and optimization workflows

Connect Google Business Profile

Add local SEO data alongside search data