> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daoco.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Google Search Console

> Read what your site actually earns in Google Search: clicks, impressions, and position by query and page, with read-only OAuth.

Search Console sits in the **Dev Testing** category because Google is still reviewing our request for the Search Console read scope. A workspace owner or admin turns that category on under **Settings** -> **Preview features** -> **Dev Testing integrations**, and Search Console then appears under **Connections** -> **Integrations** -> **Dev Testing**. Until Google approves the scope, authorization can be limited to accounts we have added to the review, so contact us if the Google screen refuses the request.

Connecting it changes what the SEO agent can say. Without it, an audit can tell you a page's title is too long. With it, the audit can tell you that page has 4,000 impressions at 0.9% click-through and rank the fix by the traffic actually at stake.

## What daoco can read

* **Search performance.** Clicks, impressions, click-through rate, and average position, broken down by search query, page, country, device, or date.
* **Verified properties.** The sites the connected Google account is verified on.
* **Sitemap status.** What you submitted, when Google last downloaded it, and any errors or warnings.
* **Index coverage for a URL.** Whether Google has indexed a page, why not if it hasn't, and whether Google chose a different canonical than the page declares.

The connection is read-only. daoco cannot submit or remove sitemaps, request indexing, change property settings, or add and remove users.

## Before you start

The Google account you connect must already be **verified on the Search Console properties you want to read**. daoco cannot verify a property for you. Search Console requires you to prove site ownership through Google directly. If you connect an account with no verified properties, the connection succeeds and returns an empty property list.

## Connect Search Console

<Steps>
  <Step title="Turn on Dev Testing integrations">
    A workspace owner or admin opens **Settings** -> **Preview features** and enables **Dev Testing integrations**.
  </Step>

  <Step title="Open Search Console">
    Open **Connections** -> **Integrations** -> **Dev Testing** and choose **Google Search Console**.
  </Step>

  <Step title="Choose Connect">
    Choose **Connect**. A Google authorization window opens.
  </Step>

  <Step title="Approve read-only access">
    Sign in with a Google account that is verified on the properties you want, and approve read-only Search Console access.
  </Step>

  <Step title="Verify from chat">
    Ask the agent which Search Console properties it can see. It should list them by their exact property name.
  </Step>
</Steps>

## Domain properties and URL-prefix properties

Search Console keys a property one of two ways, and they are different resources:

* **Domain property** (`sc-domain:example.com`) covers every subdomain and both `http` and `https`.
* **URL-prefix property** (`https://example.com/`) covers only that exact prefix.

The agent uses whichever name Search Console returned. If a report looks like it is missing traffic, check which of the two you verified. A URL-prefix property will not show data for a subdomain.

## Data is about three days behind

Search Console settles its data on a delay, so the last few days of any range are incomplete. daoco ends its default reporting windows where the data actually ends and says so in the report, specifically so a partial final day is not read as a traffic collapse. If you ask for a range ending today, expect the last entries to be low.

## What you can ask for

* "Which queries am I close to ranking for?"
* "Find pages Google isn't indexing and tell me why."
* "Run an SEO analysis on my site". The audit uses search performance to rank its recommendations once this is connected.
* "How did organic search do last month compared to the month before?"

## Disconnecting

Disconnecting removes the agent's access immediately: the Search Console tools stop being offered in chat, and any automation that depended on them stops pulling search data. Audits you already ran keep their history; they just stop refreshing.