Connecting Search Console
Connect your Google Search Console account to Opus Growth.
Before you start
- Your property must already be verified in Search Console; we do not perform site ownership verification.
- The Google user you authorize with needs to be at least a restricted user on that property.
- This connection is independent of your Google Ads token and does not touch it.
Connection steps
- Run the tool. Tell your assistant
connect_search_console. It returns a one-time authorization link tied to your account; nothing is connected yet at this point. - Open the link. The link is valid for one hour. Open it in a browser where you are signed in as the person who has access to the Google Search Console account.
- Grant access. Approve the requested permissions on the Google Search Console screen. This is Google Search Console's own consent screen, so the sign-in happens there, not with us.
- Select an account. Your accounts are listed after authorization. Tick the ones you want to manage and save; every later operation runs on the account you picked.
- Confirm. Run
gsc_list_sites; if your verified properties are listed, the connection is ready.
Requested permissions
openidhttps://www.googleapis.com/auth/userinfo.emailhttps://www.googleapis.com/auth/webmasters
Nothing outside this list is requested, and the token is stored encrypted at rest. If you decline any permission on the consent screen, the flow stops and no token is written.
Notes
- This is a separate connection — your Google Ads token is not touched (its own encrypted token is stored).
- Your verified properties in Search Console (site / sc-domain) are accessed; they are listed with
gsc_list_sites. - Beyond read-only, only sitemap submission is a write operation.
Troubleshooting
What is the difference between a domain property and a URL-prefix property?
A domain property arrives as sc-domain:site.com and covers every subdomain and protocol; a URL-prefix property arrives as a full address and covers only that prefix. If both are verified, both appear in the list, and you just say which one you mean when asking for a report.
Why is yesterday's data missing?
Search Console data completes with a lag of a few days, so the most recent day or two can be partial or absent. That is the natural delay in Google's pipeline rather than a sign that something is wrong with the connection.
Does this connection change anything on my site?
Beyond reading, the only write operation is sitemap submission, and we do not do that unless you ask. It changes no rankings, no content and no Search Console settings.
Why does the link say the connection is invalid or expired?
An authorization link expires one hour after it is generated and it is single use; opening a link that was already used produces the same error. Run the connect tool again, and you get a fresh link to continue with.
I selected several accounts but only one was saved. Why?
Free and Pro are locked to a single account; managing several is an Agency feature. Even if you tick more than one on the selection screen, the first is kept when it saves. Agency work means upgrading the plan; after that you refresh the selection from the panel's account switcher, which reuses the stored token so you never authorize again.
I authorized with the wrong user. What happens?
The stored access is limited to the accounts that the authorizing user can see; an account that user cannot reach is not visible to us either. Disconnect from the panel and connect again with the right user, and the old token is deleted.
Disconnecting
Open the panel, find Google Search Console under connected platforms and choose disconnect.
The stored token is deleted immediately, not just hidden, so we can no longer reach the account.
Reconnecting later means running connect_search_console again and going through
authorization from scratch. Disconnecting does not delete anything inside your
Google Search Console account.