# Google Search Console

> See the Google searches and pages that bring people to each website, read with your own Google account, and use them in Databunny answers.


import { Callout, Steps, Step } from "@/components/docs";

Connect Google Search Console to see a website's Google searches next to its traffic. Each website gets a **Search Console** page with clicks, impressions, click-through rate, and average position over the date range you pick, a daily trend, and its top queries and pages. Databunny can read the same data to answer questions such as which keywords lost rankings or which pages dropped in impressions.

Search Console data belongs to Google accounts, not organizations, so each person connects their own Google account and sees the properties that account can see. Teammates connect separately.

## Connect

<Steps>
  <Step title="Open Integrations">
    In the dashboard, open [Organization Settings → Integrations → Google Search Console](https://app.databuddy.cc/organizations/settings/integrations/search-console). You can also choose **Connect Search Console** on any website's Search Console page.
  </Step>

  <Step title="Allow read access">
    Choose **Connect** and pick the Google account that can see your site in Search Console. Google asks for read-only access to your Search Console data. If you already sign in to Databuddy with that Google account, Google asks only for the extra access.
  </Step>

  <Step title="Open a website's Search Console page">
    Open a website and choose **Search Console** in its sidebar. The page reads with your Google account each time you open it.
  </Step>
</Steps>

## Which property a website uses

Databuddy matches the website's domain against the Search Console properties your Google account can see, in this order:

1. A domain property for the website's domain, such as `sc-domain:example.com`.
2. A URL-prefix property for the website's own address, such as `https://example.com/`, then for the same address with or without `www`.
3. A domain property for a parent domain, such as `sc-domain:example.com` for `docs.example.com`.

A domain property also holds searches for the domain's other subdomains, so Databuddy counts only pages on the website's own host, with or without `www`. For example, `example.com` doesn't include searches that led to `app.example.com`. Properties you added but haven't verified are not used.

## Fresh data and time zones

Google publishes search data 2 to 3 days late and can update recent days after that, so the page offers ranges of whole days and notes when the range includes days Google may still change. Search Console counts days in Pacific time (America/Los_Angeles), so its daily totals can differ from Databuddy's own daily charts.

## When search data isn't showing

| What the page says | What to do |
|--------------------|------------|
| **Connect Google Search Console** | No Google account of yours has given Databuddy Search Console access yet. Choose **Connect Search Console**. |
| **Reconnect Google Search Console** | Google stopped sharing your Search Console data with Databuddy, for example after you removed Databuddy's access in your Google account. Choose **Reconnect Search Console** and allow access again. Integrations shows **Needs attention** with the same choice. |
| **Search data isn't available** | Your Google account can't see the website in Search Console, or you haven't verified it yet. Choose **Open Search Console** to add or verify the site, connect another Google account that can see it, or ask the site's Search Console owner to add you. |
| **Google Search Console is busy** | Google limited how often Databuddy can ask. Try again in a minute. |

## Disconnect

In [Organization Settings → Integrations → Google Search Console](https://app.databuddy.cc/organizations/settings/integrations/search-console), choose **Disconnect**. Databuddy asks Google to revoke its access, then forgets your tokens. You can still sign in with Google.

<Callout type="info">
  Google revokes Databuddy's whole access to your Google account, so the next time you sign in with Google it asks for consent again.
</Callout>
