Connecting Google Search Console
You can add your own Google Search Console connection so that Cora can read how your websites do in Google Search, in the missions you choose. It is read-only. Cora can look at clicks, impressions, pages and queries for the sites you share with her, and she cannot change anything in Search Console.
It works the same way as Connecting Google Analytics. The connection is yours: you decide which missions Cora may use it in, and nobody else can use it. See Personal connections for the rules. Unlike Google Analytics, Google offers no server for this, so Cora AI runs a small read-only server of its own. There is nothing to host or install. You only create a key in Google and add it in the console. This page uses an invented company, Kestrel Cycles, and its analyst, Leah Thompson.
What you need
Section titled “What you need”- MCP turned on for the organisation (see Connecting an MCP server). An org admin does that once.
- Someone who can create a service account in your Google Cloud project, and an owner of the Search Console property.
- The Google Search Console connection turned on by the operator. Until then it says “Not available yet”.
Step 1: make a service account in Google
Section titled “Step 1: make a service account in Google”A service account is a robot login for one job. Leah makes one for Cora in the Google Cloud console:
- Pick the Google Cloud project to use (or create one, for example
kestrel-search). - Turn on the Search Console API: open APIs & Services, then Library, search for Google Search Console API and choose Enable.
- Open IAM & Admin, then Service Accounts, and choose + Create service account. Give it a name such as
cora-gscand choose Done. It needs no Google Cloud roles. Its email looks likecora-gsc@kestrel-search.iam.gserviceaccount.com. - Open the new service account, choose the Keys tab, then Add key, Create new key, JSON and Create. A small file ending in
.jsondownloads. Keep it safe: it is the key you add in step 3, and Google cannot show it again.
You can use the same service account and key for Google Analytics 4 and Search Console. Add the Search Console API to the mission and add the account in both products.
Step 2: give the account access to your property
Section titled “Step 2: give the account access to your property”In Search Console, choose the property, then Settings, then Users and permissions, then Add user, and add the service account’s email. Restricted is enough to read, and it is all Cora asks for. Do this on each property Cora should read. A property is either a domain (sc-domain:kestrel.example) or a web address (https://www.kestrel.example/).
Step 3: add the connection in the console
Section titled “Step 3: add the connection in the console”- Open Connections on the left rail and press Connect beside Google Search Console (it says Your Google key).
- In the Account section, choose Add your key. The address is filled in for you (“Hosted by Cora”) and the sign-in is fixed to Google service account.
- Choose the key file. Your browser reads it and sends it once. The page then shows only the account’s email, which is the one to add as a user in step 2.
- Choose Test connection. Cora signs in with the key and says how many sites the account can see, for example “Connected. 2 sites found.” If it finds none, the account has not been added to a property yet.
- Choose Add connection. Then, in the Shared with missions section, choose + Share in a mission. There is no approval role to pick, because this connection only reads, and reading never asks for approval.
You can have one Google Search Console connection. To use another account, choose Replace key.
Step 4: share it in a mission
Section titled “Step 4: share it in a mission”On your connection, choose + Share in a mission and pick a mission you belong to. Cora can then read your search performance in that mission, and in no other. You can also open a mission’s details (the Details button at the top right), choose the Tools tab, and under Connections choose Share mine next to Google Search Console.
A mission can use one Google Search Console connection. If the mission already uses a colleague’s, the page says whose it is, and only they can stop sharing it. Choose Stop sharing at any time to take it back from a mission.
If you are an org admin you can instead choose Make available to the whole organisation on your connection, as for any personal connection. Do this only for a service account meant for the team.
Step 5: ask Cora
Section titled “Step 5: ask Cora”In a mission where you shared the connection, ask Cora in the dialogue, for example:
- “Which ten pages got the most clicks from Google last month?”
- “Which queries had many impressions but few clicks in the last 28 days?”
- “Is https://www.kestrel.example/bikes/ indexed, and when did Google last crawl it?”
- “Which sitemaps has Google read for our site?”
Cora lists your sites if she needs to know which one to use, then reads the data and answers with the figures and the dates they cover. She can only read: she never changes anything in Search Console. If she says the mission has no Google Search Console connection, go back to step 4.
What Cora can read
Section titled “What Cora can read”The server has four tools, and all four only read:
- List sites: the properties the account can see, and its permission on each.
- Query search analytics: clicks, impressions, click-through rate and average position, grouped by date, page, query, country, device or search appearance, for a date range, with filters. A reply holds at most 1,000 rows (100 unless Cora asks for more), and Cora can ask for the next page.
- Inspect a URL: whether Google has indexed one page, when it was last crawled and any issues it found.
- List sitemaps: the sitemaps Google knows for a site and their last read time.
Search Console keeps about 16 months of data, and Google may leave some rows out of a large report, so Cora treats a total as a floor, not an exact count.
What stays private
Section titled “What stays private”- The key is kept in one place. It goes straight to the secrets store and is never shown again. It is not in the database, a log, an audit entry, a prompt or Cora’s worker. To change it, choose Replace key and choose a new file.
- Only you can use it. No colleague can use your connection, and an org admin cannot either, unless you are an org admin yourself and choose to make it available to the whole organisation. Org admins can see who owns which connection and where it is shared, and can stop sharing or remove one for safety. They never see the key.
- Cora gets a short-lived pass, not the key. Before each connection, Cora AI’s API swaps the key for a one-hour Google token that can only read Search Console. Cora’s worker holds that token, together with a shared passcode for our own server, in memory for the step and nowhere else.
- Read-only. The token asks for Google’s read-only Search Console permission, and the server we run has no tool that changes anything. It never submits a sitemap or adds or removes a site.
- Closed to everyone else. The server we host only answers Cora AI’s own API. A Google token alone does not open it. It passes your token to Google and nowhere else, and it never writes a token in a log.
- If you leave, it goes. When you leave the organisation, your connections are removed and the keys deleted, and Cora says so in each mission that used one.
- Everything is on the record. Adding, sharing, stopping sharing and removing a connection, and every tool call, are in the audit log.
When it stops working
Section titled “When it stops working”If Google refuses the key, the connection shows Failing with a plain reason and you are told. The usual causes are a key that was deleted or turned off in Google, the Search Console API being off in the key’s mission, or a service account that was removed from the property. Add the account again, or make a new key and choose Replace key. If Google simply does not answer for a moment, nothing is marked as failing and nobody is emailed. Cora tries again on her next step.
Coming next
Section titled “Coming next”Signing in as yourself with your own Google account, submitting sitemaps and any other change in Search Console are not part of this step. See Personal connections for what is planned.