> For the complete documentation index, see [llms.txt](https://help.seoutils.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.seoutils.app/guide/google-search-console.md).

# Google Search Console

SEO Utils' Google Search Console integration provides a powerful alternative to the standard GSC interface. By connecting your GSC account, you get access to all your search data with advanced features like unlimited historical data storage, natural language filtering, bulk operations, and AI-powered insights - all while maintaining the familiar GSC functionality you already use.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-10a0c4a86973464b4aaeb7b6c25c7107166a9362%2FXnapper-2025-08-28-21.47.11.png?alt=media" alt=""><figcaption><p>See how the keyword is mentioned in your content.</p></figcaption></figure>

### Setup the Integration

There are two methods to connect SEO Utils to your Google Search Console data:

1. **Google OAuth Token** (Recommended for most users)
2. **Google Service Account** (Advanced option for automation)

***

## Method 1: Google OAuth Token

The Google OAuth Token method is the simplest way to connect your Google Search Console data to SEO Utils. This method uses your own Google account credentials.

### Benefits of OAuth Token Method

* **Quick setup** - No need to create service accounts or manage API keys
* **Direct access** - Uses your existing Google account permissions
* **Multiple accounts** - Easily connect multiple Google accounts
* **Automatic permissions** - Access all GSC properties your account can see

### Setup Steps

1. Open SEO Utils and navigate to **Settings menu in the left sidebar > Google OAuth Tokens**
2. Click the **Connect for Search Console** button
3. Authorize SEO Utils to access your Google Search Console data
4. Your Google account will be connected and ready to use

For detailed setup instructions, see the [Google OAuth Token guide](https://help.seoutils.app/guide/google-oauth-token.md).

{% hint style="info" %}
The OAuth Token method is perfect for individual users and small teams who want a simple, secure way to access their GSC data.
{% endhint %}

***

## Method 2: Google Service Account

The Google Service Account method provides more control and is suitable for advanced users who need programmatic access or specific permission management.

### Benefits of Service Account Method

* **Granular control** - Manage permissions for specific properties
* **Automation-ready** - Ideal for scheduled tasks and API automation
* **No expiration** - Service account keys don't expire like OAuth tokens
* **Team sharing** - Share service account across team without sharing personal credentials

### Setup Steps

#### **Step 1: Enable Google Search Console API**

Visit the [Google Cloud Console](https://console.cloud.google.com/) and create a project if you don't have one. Then search for "**Google Search Console API**" in the top search bar, click on it, and hit **Enable**.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-36957c4cdf5e19ba5d3e16315dfca84df4f0dad5%2FXnapper-2024-01-08-21.51.21.png?alt=media" alt=""><figcaption><p>Google Search Console API is enabled</p></figcaption></figure>

#### Step 2: Create and Add a Google Service Account

Follow the comprehensive guide to create and add a Google Service Account to SEO Utils:

1. **Create the Service Account**: Follow [this guide](https://help.seoutils.app/guide/google-service-accounts.md#create-a-google-service-account) to create a service account and download the JSON key file
2. **Add to SEO Utils**: Follow [this guide](https://help.seoutils.app/guide/google-service-accounts.md#add-the-google-service-account-to-seo-utils) to add the service account to SEO Utils
3. **Important**: Copy the service account email address - you'll need it in the next step

#### Step 3: Grant Service Account Access in GSC

Now you need to grant the service account access to your Google Search Console properties:

1. Go to your [Google Search Console Tool](https://search.google.com/search-console)
2. Select the property you want to integrate
3. Navigate to **Settings → Users and permissions**
4. Click **Add user**
5. Enter the **service account email** (e.g., `gpapp-932@gpapp-1607908720839.iam.gserviceaccount.com`)
6. Select permission level:
   * **Full**: For pulling performance data only
   * **Owner**: Required if you want to use the [Auto-indexing tool](https://help.seoutils.app/guide/auto-indexing-tool.md) to submit indexes

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-ef2a8f9a1fdc1517dd28332fff930e4531b22967%2FXnapper-2024-01-08-22.11.53.png?alt=media" alt=""><figcaption><p>Add the service account email with appropriate permissions</p></figcaption></figure>

{% hint style="warning" %}
**Important**: To submit indexes via the Google Indexing API, the service account must have **Owner** permission. Full permission is sufficient for reading performance data only.
{% endhint %}

Once you complete this step, the Google Service Account will gain full access to the website data in your Google Search Console. With this, you're all set to utilize this integration on SEO Utils 🎉

***

## Data Storage and Retention

After connecting your properties, SEO Utils will pull all data from the Google Search Console API and store it locally on your machine.

{% hint style="success" %}
The application automatically pulls new data every day, which means you can view and analyze data for **more than the standard 16-month limit** imposed by Google Search Console.
{% endhint %}

### Key Benefits of Local Storage

* **Extended Historical Data**: While Google Search Console only provides 16 months of data, SEO Utils stores everything locally, allowing you to build an unlimited historical archive
* **Daily Automatic Updates**: New data is automatically fetched every day without any manual intervention
* **Offline Access**: Your data is available even without an internet connection since it's stored locally
* **No API Limits**: Browse and analyze your data without worrying about API rate limits

## Available Features

The SEO Utils integration contains all features from the Google Search Console dashboard, plus advanced features that GSC doesn't provide. Whatever you can do on the GSC dashboard, you can do in SEO Utils - and more.

### Standard GSC Features Available in SEO Utils

* Performance reports with clicks, impressions, CTR, and position data
* Search analytics with query and page filtering
* Date range comparisons
* Country, device, and search appearance filtering
* Sitemap management
* URL inspection and indexing status

### Advanced Features Not Available in Standard GSC

* Extended data retention beyond 16 months
* Filter data using Natural Language
* Bulk mention checking across all content
* Keyword cannibalization detection
* AI-powered insights and opportunities
* Bulk URL indexing submission
* Complete data export without sampling limitations
* Multi-account management in a single dashboard
* SEO Tests: Time-based Test, URL Switch Test, Split Tests
* Chart annotations with automatic Google algorithm update tracking
* Internal link suggestions: find the pages that need links and the sentence to add each one to
* GSC Rank Tracker: free daily keyword rankings with 16 months of history, movers, alerts, AI explanations and reports, from your own Search Console data
* GA4 traffic next to your clicks: organic sessions on the performance chart, an organic share card and GA4 columns on the Pages table

Please follow the guides below to learn how to use these features:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Annotations</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2FKtff0oA3eDtd6EHn8OA8%2FXnapper-2026-01-31-11.44.00.png?alt=media&amp;token=0e06fbe8-d577-4a62-955d-0e357917611d">Xnapper-2026-01-31-11.44.00.png</a></td><td><a href="https://help.seoutils.app/guide/google-search-console/annotations.md">Annotations</a></td></tr><tr><td>Topic Clusters</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-5c10bef4f945ccd81d22657da6e407519d354a4d%2FXnapper-2025-08-28-21.55.51.png?alt=media">Xnapper-2025-08-28-21.55.51.png</a></td><td><a href="https://help.seoutils.app/guide/google-search-console/topic-clusters.md">Topic Clusters</a></td></tr><tr><td>Keyword Metrics</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-cb34e488f71b3795019b989cdb3fe81c61809a3c%2FCleanShot%202025-09-01%20at%2022.18.29%402x.png?alt=media">CleanShot 2025-09-01 at 22.18.29@2x.png</a></td><td><a href="https://help.seoutils.app/guide/google-search-console/keyword-metrics.md">Keyword Metrics</a></td></tr><tr><td>SEO Tests</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-273f9ee846bb6f8351acefcb9052b19a4d0b7226%2FCleanShot%202025-09-08%20at%2013.18.11%402x.png?alt=media">CleanShot 2025-09-08 at 13.18.11@2x.png</a></td><td><a href="https://help.seoutils.app/guide/google-search-console/seo-tests.md">SEO Tests</a></td></tr><tr><td>Internal Links</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-23706452980da93a610748dc3288e115c241b73c%2Fplaceholder.png?alt=media">placeholder.png</a></td><td><a href="https://help.seoutils.app/guide/google-search-console/internal-links.md">Internal Links</a></td></tr><tr><td>GSC Rank Tracker</td><td><a href="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-48b4e5790222b9cfd29c3ff039ef5a5b3cc5bada%2Fgsc-rankings-overview.png?alt=media">gsc-rankings-overview.png</a></td><td><a href="https://help.seoutils.app/guide/google-search-console/gsc-rank-tracker.md">GSC Rank Tracker</a></td></tr></tbody></table>

## GA4 traffic next to your clicks

When a [Google Analytics 4](https://help.seoutils.app/guide/google-analytics-4.md) property is mapped to the same site, the property's **Performance** page shows what happened after the click. Open **Your Sites > Search Console** and click the property.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-7d38f38c803e0c6204ec6cede5fb8688269533d1%2Fgsc-property-ga4-chart.png?alt=media" alt="The Performance chart with a Google organic sessions line, the metrics menu with its Google Analytics group and the organic share card"><figcaption><p>The Google Analytics group in the metrics menu (1), the Google organic sessions line (2), the organic share card (3) and View GA4 traffic (4)</p></figcaption></figure>

* **Chart lines (1, 2).** Open the **metrics** button above the chart. Its **Google Analytics** group has **Google organic sessions** (on by default), **All organic sessions** and **Organic key events**. Google organic sessions is the line to compare with clicks, because Search Console only covers Google. All organic sessions also counts the other search engines. A click is not always a session, so sessions run lower than clicks: hover the (?) next to the line to see why.
* **Organic share card (3).** **Organic share of sessions** is the part of all GA4 sessions that came from organic search, and **Google share of organic sessions** is Google's part of those. **View GA4 traffic (4)** opens [GA4 Traffic](https://help.seoutils.app/guide/google-analytics-4/ga4-traffic.md).
* **When the lines are off.** GA4 cannot apply Search Console's filters, so the lines are disabled, with the reason, while the chart uses a query, page, country or device filter, a search type other than **Web**, or a search-type comparison.
* **Which GA4 property.** If several GA4 properties match the site, the chart asks you to choose one. SEO Utils remembers your choice for the Pages table and the [Rankings](https://help.seoutils.app/guide/google-search-console/gsc-rank-tracker/read-your-rankings.md#page-sessions-and-key-events) tab, and **Change GA4 property** lets you pick again.

A property that covers only part of a site, such as a URL prefix with a path, has no chart line or share card, because GA4 cannot split a site's traffic by path.

### GA4 columns on the Pages table

Open the **Pages** tab under **Dimension Analytics** to see **GA4 sessions** and **GA4 key events** next to each page's clicks and impressions: the organic sessions and key events GA4 recorded for pages that visitors landed on. Click a GA4 column's header to sort all pages by it, not only the ones on screen. A page with no GA4 traffic counts as 0. The sort is unavailable, with the reason in the header menu, when the date range starts before GA4's page data does: choose a range that starts on or after the date the menu gives. Hide the other columns with the column button to make room.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-fae363b2793ce35a7b86ca641f89c3769dee93aa%2Fgsc-property-ga4-pages.png?alt=media" alt="The Pages tab with Clicks, Imp., CTR and Pos. columns followed by GA4 sessions and GA4 key events"><figcaption><p>GA4 sessions (1) and GA4 key events (2) on the Pages table</p></figcaption></figure>

## Rankings across properties

If you track keywords with the [GSC Rank Tracker](https://help.seoutils.app/guide/google-search-console/gsc-rank-tracker.md), the properties page can show every tracker in one table. Open **Your Sites > Search Console** in the sidebar and switch from **Properties** to **Rankings** (1).

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-202057a97951f1e45840d15edabe9cc8ab9e2541%2Fgsc-rankings-portfolio.png?alt=media" alt="The Rankings view of the Search Console properties page with three trackers"><figcaption><p>The Rankings switch (1) and a tracker's property link (2)</p></figcaption></figure>

Each row is one tracker, with its market and these figures:

* **Items**, **Avg position**, **Top 3** and **Top 10**, with the change over 7 days.
* **Movers · 7 days**: how many keywords improved and declined, confirmed on two days.
* **Unread alerts**, **Bands** (how many keywords sit in each position band) and a **90-day trend** of the average position.

The figures match the tracker's [KPI strip](https://help.seoutils.app/guide/google-search-console/gsc-rank-tracker/read-your-rankings.md#kpi-strip) with its default date range. Click the property name (2) to open that tracker. Sort by a column, search by domain or tracker name, and use **View** to choose the columns. The **Rankings** tab shows a badge with the unread alerts of every tracker in the workspace. A figure that shows "…" is being recalculated and fills in after the next refresh.

***
