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

# Connecting and using Google Search Console

Connect your Google Search Console account to a client, understand the data sync process, and navigate the GSC Performance card with its three tabs, granularity toggle, and comparison mode.

The Google Search Console (GSC) integration brings your real search performance data directly into Rankability. Once connected, you can view clicks, impressions, CTR, and average position trends alongside your Reporter data.

## Connecting GSC to a client

1. Navigate to a client and open **Track**.
2. In the GSC Performance card, click **Connect Google Search Console**.
3. Sign in with the Google account that has access to the Search Console property.
4. Select the property you want to connect (the one matching your client’s domain).
5. Rankability begins importing historical data automatically. A progress indicator shows the backfill status.

The initial import can take a few minutes depending on how much data is available. Once complete, the card updates with your performance metrics.

## Understanding the GSC Performance card

The GSC Performance card has three tabs:

* **GSC performance** – A time-series chart showing clicks, impressions, CTR, and average position. Toggle each metric on or off by clicking the metric pills above the chart.
* **Low-hanging fruits** – Keywords ranking in positions 2–15 that represent the easiest wins for improved traffic.
* **Content decay** – Pages where traffic has declined compared to their historical peak.

## Controls

* **Date range** – Choose 7, 14, 28, or 90 days from the dropdown.
* **Granularity (D / W / M)** – Switch between daily, weekly, and monthly views. Weekly and monthly aggregate data points so the chart is easier to read over longer time ranges.
* **Compare** – Toggle comparison mode to overlay the previous period’s data on the chart (shown as dashed lines). This makes it easy to spot trends at a glance.
* **Annotate** – Add notes to specific dates on the chart (see [Using GSC annotations](/track/using-gsc-annotations.md)).

## Data freshness

Google Search Console data is typically delayed by 2–3 days. A small badge in the card header shows the date of the most recent available data (e.g., “through Feb 24”). Rankability syncs new data automatically each day.

## Related articles

* [Finding low-hanging fruit opportunities](/track/low-hanging-fruit-opportunities.md) — Identify keywords closest to page one.
* [Detecting content decay](/track/detecting-content-decay.md) — Find pages losing traffic over time.
* [Using GSC annotations](/track/using-gsc-annotations.md) — Mark important events on the chart timeline.
* [Setting up keyword tracking](/track/setting-up-keyword-tracking.md) — Track keywords across search engines and AI platforms.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.rankability.com/track/connecting-google-search-console.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.