Connect Google Search Console
The only real numbers in this product: what people actually searched for, how often your pages were shown, and how many people clicked. Everything else we show is our own measurement of your page.
What this key lets us do. Read-only. It lets us read your search performance. It cannot submit pages, change settings, or remove anything from Google.
Step by step
- First, make sure the site is already verified in Search Console itself at search.google.com/search-console. Note the property name exactly as it is written there.
- Go to console.cloud.google.com and create a project (any name).
- In that project open APIs & Services → Library, search for Google Search Console API, and enable it.
- Open APIs & Services → OAuth consent screen, set it up as External, and add your own Google address under Test users.
- Open APIs & Services → Credentials → Create credentials → OAuth client ID, choose Desktop app.
- Google gives you a client ID and a client secret. Use them to sign in once and approve read-only access to Search Console; that sign-in returns a refresh token.
- Paste the property name and the refresh token into your site settings here.
Bold words are the exact buttons and menu names to look for. These are screens of other companies and they move them — if the layout does not match, searching that bold name in their own help usually finds where it went.
What to paste here
| Field | What it looks like |
|---|---|
| Property | Exactly as Search Console writes it: https://example.com/ with the trailing slash, or sc-domain:example.com |
| Refresh token | A long string beginning 1// |
What usually goes wrong
- This one is genuinely hard, and we would rather say so than pretend. If you would like the one-click version instead, it is being built — everything else in the product works fully without this.
- The property must match character for character.
https://example.comwithout the slash is a different property to Google, and the answer is a 404, not a helpful error. - A refresh token is not the same as an access token. Access tokens expire in an hour; the refresh token is the long-lived one, and it is what we store.
Now do it
Site settings →Whatever you paste is encrypted the moment it arrives. It is never shown back to you and nobody here can read it — support sees a fingerprint like “ending 7f3a2c”, never the value.
Stuck? The help desk answers this exact question, and it is a real answer rather than a form. Open the help desk → If you would rather go to the source, read the official documentation: Google: Search Console API access