Google Search Console is the foundation of everything Guru does. Connecting it takes about two minutes and unlocks the data that powers your audit, your content strategy, and your indexation monitoring. This guide walks through the setup process and explains exactly what Guru reads from GSC and how it's used.

What Guru reads from Search Console

Guru connects to GSC via OAuth, you authorize read access using your Google account, and Guru imports the data it needs. No API keys, no manual exports.

The data Guru reads:

  • Page-level performance. Clicks, impressions, average position, and CTR for every URL in your property over the last 16 months (the full GSC retention window).
  • Query data. The search terms driving traffic to each page, used to identify keyword gaps and title optimization opportunities.
  • Coverage data. Which URLs are indexed, which have errors, and which are excluded, used to populate the indexation monitor.
  • Crawl data. When Googlebot last visited each URL, used to trigger re-crawl requests after implementations.

Guru does not read or store any private user data from GSC. The data types above are all site-level performance data, not individual user information.

Setting up the connection

1

Go to Settings in your Guru portal

From your client portal, navigate to Settings → Integrations. You'll see the Google Search Console connection card in the list.

2

Click "Connect with Google"

You'll be redirected to Google's OAuth flow. Sign in with the Google account that has access to your GSC property. If you manage the property through a shared account, make sure you're using that account, Guru reads the properties available to the account you authorize.

3

Select your property

After authorization, Guru will list all GSC properties accessible from your Google account. Select the one that matches your site. If you have both a domain property (example.com) and a URL prefix property (https://www.example.com), the domain property is recommended, it captures all subdomains and protocols in a single data set.

4

Wait for the initial data pull

The first import takes 2-5 minutes depending on the size of your site. During this time, Guru is pulling your full GSC history (up to 16 months). Once complete, you'll see your top pages, query data, and indexation status in the dashboard.

What happens after connection

Once GSC is connected, several things in Guru become active:

  • Audit findings get traffic context. Every issue found during the technical audit is overlaid with GSC data, you can see how much traffic a page with a weak title tag is currently losing, rather than just that it has a suboptimal title.
  • Content strategy proposals use real keyword data. Instead of generic topic suggestions, Guru surfaces article ideas based on your actual search position data, queries where you rank on page 2 or have impressions but low CTR.
  • Indexation monitor goes live. GSC coverage data populates the per-URL indexation status for every page on your site. Pages that are excluded, have errors, or are missing from the index are flagged immediately.
  • Re-crawl triggers are enabled. When you implement a change and mark it as complete, Guru automatically submits the affected URL to the Google Indexing API so the update gets picked up as quickly as possible.

Keeping the data fresh

After the initial connection, Guru syncs GSC data daily. Your performance trends, query data, and indexation status are updated each morning with the previous day's data.

If you ever need to force a refresh, for example, after a major site change or if you suspect a delay in the data, you can trigger a manual sync from the Settings page. The sync typically completes within a few minutes.

Permissions and access

Guru requires only read permissions on your GSC property. It cannot make changes to your GSC settings or verification. The OAuth token can be revoked at any time from your Google account's security settings, which will immediately disconnect the integration.

For agencies managing multiple clients, each client portal has its own independent GSC connection, client A's data is never accessible from client B's workspace, even if the same agency account manages both.