# Google Search Console

> June reads how your sites do in Google Search: clicks, impressions, index status and sitemaps. It submits or removes a sitemap and adds a property when you approve.

Source: https://www.dearjune.ai/docs/integrations/google-search-console

Connect Google Search Console and June can tell you how your sites do in
Google Search: clicks, impressions, click-through rate and position per page
or query, whether a page is indexed, and what state your sitemaps are in.
When you approve it, June also submits or removes a sitemap and adds a new
property.

1. On the **Integrations** page, choose **Connect** on the Google Search Console row.
2. Sign in with the Google account that has access to your Search Console properties, and allow June to view and manage your Search Console data.
3. Ask about a site.

> Example prompt: How did clicks to the pricing page change over the last 28 days?

> Example prompt: Check whether [https://example.com/guides/getting-started](https://example.com/guides/getting-started) is indexed and which URL Google picked as canonical.

> Example prompt: Submit [https://example.com/sitemap.xml](https://example.com/sitemap.xml) to my example.com property.

## What June can do

- List the properties your Google account sees, domain properties and
  URL-prefix properties alike.
- Read search performance for a date range, grouped or filtered by page,
  query, country, device or search appearance.
- Check one URL: whether it is indexed, the canonical Google chose, and its
  mobile usability and rich results. Google allows 2,000 of these checks per
  property per day.
- List your submitted sitemaps with their errors, warnings and pending state.
- Read one property's or one sitemap's details straight from Google,
  read-only.
- Submit a sitemap to a property, remove a sitemap from it, or add a new
  property (Google still asks you to verify that you own it). June follows
  your approval settings. When it asks, the card shows what the change
  does, the property and sitemap, and the exact request. You can approve
  it in June on the web, in the app or in Slack
  ([how approval works](/docs/how-june-works/connections#a-step-that-needs-your-confirmation)).

If June cannot access a property, ask it to list the properties this
account can see and use the exact one from that list. Reconnecting does not
grant access to a site; add the account in Search Console or connect the
account that already has access. Submitting a sitemap does not guarantee
that Google will index its pages.

## A connection from before

A Search Console connection made before June could submit sitemaps only
allows reading. June keeps reading through it, and when you ask for a
change it tells you to reconnect instead of showing a card. Reconnect
Search Console on the **Integrations** page and allow June to manage your
Search Console data.

## What June does not do

- It never removes a property: getting one back means verifying it again,
  so do that in Search Console yourself.
- It never requests indexing, verifies a property, adds or removes users,
  or changes any other setting.
- It connects one Google account. If your properties sit in several
  accounts, grant one of them access to the others in Search Console.

Removing June from your Google account's third-party access also ends
[Google Drive](/docs/integrations/google-drive) and
[Gmail](/docs/integrations/mailbox); to stop only Search Console, disconnect
it on the **Integrations** page.