> 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.

You need access to the intended Search Console property through the Google account used for authorization and permission to manage the client's integrations. Decide whether the client uses a Domain property or URL-prefix property and select the one whose scope matches the site you intend to analyze.

## 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.

The import runs in the background and can take longer for a large property. The progress, stored-row count, latest-data date, and any visible sync issues are more reliable than repeatedly reconnecting. Leaving the page does not cancel an active backfill.

## 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.

## Verify the connection

1. Confirm the selected property includes the client's canonical URLs.
2. Wait for the initial backfill to finish or reach a usable range.
3. Match one date range with Search Console using the same property, search type, and dates.
4. Check the **through** date before interpreting recent changes.
5. Use the query and page views, low-hanging fruit, or content decay only after their required history exists.

Search Console is an aggregated reporting source. Average position is not a live rank check, and query/page totals can differ from exported or filtered Google views because of privacy thresholds, property scope, aggregation, and data delay. Use Rankability Track scans when you need monitored platform/location results for a specific keyword.

## Common issues

* **The property is not listed** — Verify access in Search Console, then reconnect with the correct Google account.
* **Backfill appears slow** — Leave the active import running and check its status later. Do not create repeated connection attempts.
* **No recent dates appear** — GSC commonly lags by two to three days; check the freshness badge.
* **Rows or metrics differ from Google** — Match property type, dates, dimensions, and filters before comparing.
* **The connection reports an authorization issue** — Reauthorize it in client integrations. If it repeats, record the client, property, time, and visible error.

## 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.