> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/marketing/google-search-console.md).

# Google Search Console

Google Search Console (GSC) is Google's free tool for monitoring your website's presence in Google Search results. By connecting Google Search Console to Coupler.io, you can automatically export search performance data, Discover metrics, Google News stats, and URL indexing information to spreadsheets, BI tools, or data warehouses — without manual CSV downloads or custom API integrations.

Coupler.io's Google Search Console integration pulls data from the GSC API using **Google OAuth authentication**, covering 5 report types: Search results performance, Search results performance by appearance, Discover performance, Google News performance, and URLs index performance.

## Why connect Google Search Console to Coupler.io?

* **Automate SEO reporting** — Schedule regular exports of search performance data with clicks, impressions, CTR, and position breakdowns so your dashboards always reflect the latest organic search trends.
* **Analyze by multiple dimensions** — Break down search data by query, page, country, device, and date to identify high-performing content and optimization opportunities.
* **Monitor indexing health** — Export URL inspection data to track which pages are indexed, identify crawl issues, and monitor AMP and mobile usability status.
* **Flexible destinations** — Export to AI tools, Google Sheets, Excel, BigQuery, Looker Studio, or other supported destinations.

## Prerequisites

Before connecting, make sure you have:

* A **Google Search Console** account with verified site ownership or delegated access
* A Coupler.io account

{% hint style="info" %}
You must have at least **Restricted** or **Full** user access to the GSC property you want to export. Owner-level access is not required for performance reports, but may be needed for URL inspection data.
{% endhint %}

## Quick start

{% hint style="success" %}
Start with the **Search results performance** report, select a single site, and add the **Date**, **Query**, and **Page** dimensions. Leave the date range at the default (last 60 days) and use the **Final** data state for settled numbers. Run once to review the output columns, then refine dimensions and add filters as needed before setting up a daily auto-refresh.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
In Coupler.io, create a new **data flow** and select **Google Search Console** as the source.\
Click **Connect** and sign in with your Google account.
{% endstep %}

{% step %}
Grant Coupler.io permission to access your Search Console data.
{% endstep %}

{% step %}
Select one or more **Sites** and a **Report type** — Search results performance (default), Search results performance by appearance, Discover performance, Google News performance, or URLs index performance.
{% endstep %}

{% step %}
Configure the **Report period** (Start date / End date), select **Dimensions** and optional **Filters by dimensions**, and adjust **Advanced settings** (Search results type, Aggregate data by, Data state) as needed.
{% endstep %}

{% step %}
Choose your **destination** and run the import.
{% endstep %}
{% endstepper %}

### Available report types

| Report type                                  | Description                                                                                                                        | Typical use case                                         |
| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| **Search results performance**               | Clicks, impressions, CTR, and average position for Google Search results. Supports dimensions: Date, Country, Device, Page, Query. | SEO dashboards, keyword tracking, page-level performance |
| **Search results performance by appearance** | Same metrics as Search results performance, but automatically grouped by search appearance type (e.g., AMP, Rich result, Video).   | Identifying which search features drive traffic          |
| **Discover performance**                     | Clicks, impressions, CTR, and position for Google Discover. Supports dimensions: Date, Country, Page.                              | Content marketing analysis, Discover traffic trends      |
| **Google News performance**                  | Clicks, impressions, CTR, and position for Google News. Supports dimensions: Date, Country, Device, Page.                          | News content performance, editorial reporting            |
| **URLs index performance**                   | Indexing status, coverage state, crawl details, AMP status, mobile usability, and rich results for a list of specified URLs.       | Technical SEO audits, index coverage monitoring          |


---

# 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://docs.coupler.io/sources/category/marketing/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.