GSC not connected or no data returned

Complete step-by-step diagnostic

The 5 possible causes

  • Wrong Google account connected: you clicked Connect Google with your personal address but GSC is managed by professional account. Disconnect and reconnect with right account.
  • Site not verified in GSC: go to search.google.com/search-console and verify your property appears. Otherwise, verify it (HTML file, DNS, Google Tag Manager or via Analytics).
  • Wrong property selected: in Projects > open project, GSC dropdown lists all account's properties. Verify the right one is selected.
  • Incorrect URL format (frequent cause): GSC distinguishes sc-domain:example.com, https://www.example.com/, https://example.com/. Using wrong format produces silent 403 error. Project dropdown fixes this by listing exact formats.
  • Search Console API not enabled in Google Cloud: go to console.developers.google.com/apis/api/searchconsole.googleapis.com and enable it. 2 minutes propagation.

Use automatic diagnostic

In Projects > open a project, scroll to Connections section. A blue « Google connection diagnostic » button displays detailed JSON with token scopes, refresh result, separate GSC and GA4 probes. Tells you exactly which API fails and with which error code.

Warning :Non-consolidated data: GSC takes 24 to 72 hours to consolidate recent data. If you just launched a site, wait at least 3-5 days before concluding connection problem.