Google Search Console
June reads how your sites do in Google Search: clicks, impressions, index status and sitemaps. Read-only.
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.
How did clicks to the pricing page change over the last 28 days?
Is the new guide indexed yet, and which URL did Google pick as canonical?
Do any of my sitemaps have errors?
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.
What June does not do
- It never submits sitemaps, requests indexing or changes a setting. The connection is read-only.
- 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 and Gmail; to stop only Search Console, disconnect it on the Integrations page.
Google Contacts
June looks people up in your Google contacts and, in a Google Workspace account, your company directory: email, phone, company and title. Read-only.
GitHub
June works on your repositories as you: reads code, reviews and opens pull requests and issues, pushes branches. From Slack it uses GitHub's API, not git.