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

# Google Search Console

Use your real Google search data to see what ranks, find quick wins, and get alerted when traffic drops.

{% hint style="info" %}
Each teammate can connect their own Google Search Console account.
{% endhint %}

## Connect Google Search Console

{% stepper %}
{% step %}

### Open Settings

Go to **Settings → Integrations,** locate Google Search Console, and click **Connect**.
{% endstep %}

{% step %}

### Pick the property to sync

Map your Search Console property to the matching site in **Site Settings**, especially if you've added more than one site.
{% endstep %}

{% step %}

### Let your data import

Data starts importing automatically within 24 hours. You can sync again any time.
{% endstep %}
{% endstepper %}

## What you get once it's connected

* **Real rankings and clicks** in [SEO Analytics](https://docs.frase.io/feature-reference/seo-analytics), so you can tell keywords that just rank from keywords that drive traffic.
* **Quick wins** in [Content Opportunities](https://docs.frase.io/feature-reference/content-opportunities), like pages sitting in positions 3 to 10 that are close to page one.
* **Alerts** by email or [Slack](/integrations/connectors/slack.md) when rankings or traffic drop.
* **Better recommendations** across Frase, since they're based on your actual search data.

Next: [connect Google Analytics 4](/integrations/connectors/google-analytics-4.md) to see traffic from AI assistants too.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.frase.io/integrations/connectors/google-search-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.