Connecting Google Search Console to DENVORA SEO: what happens, step by step
Before connecting any Google account to a new tool, it's normal to want to know exactly what will happen. This page describes, without marketing spin, the real steps of the Search Console connection — what is asked for, what isn't, and what to do if something doesn't show up.
The steps, exactly as they happen
- Click "Connect with Google" inside DENVORA SEO. If pop-ups are blocked in the browser, they need to be allowed for this site.
- Google's own consent screen opens — never a DENVORA SEO form. Choose the Google account that already has Search Console access to the site in question and authorize the requested access.
- Google hands control back to DENVORA SEO, which automatically lists every Search Console property that account can access.
- Pick the site from the list — real data (clicks, impressions, pages, queries) appears on the dashboard right away.
The whole process, from the first click to the first data on screen, usually takes under 60 seconds.
What DENVORA SEO asks for — and what it doesn't
The authorization request uses Google's webmasters.readonly scope, plus basic account identification (email and profile). In practice, this means:
- It never sees your password. Authentication happens entirely on Google's own screen — DENVORA SEO only receives an access token after authorization.
- It can only read, never write. With webmasters.readonly, it cannot change settings, add or remove properties, or delete anything in your Google account — those actions only exist in Search Console itself.
- The token is stored encrypted. The authorized access is stored encrypted, tied to the organization that made the connection — not to an individual user.
- You can revoke it at any time. Like any Google OAuth connection, you can remove access directly in your own Google account (Security → Third-party apps), without depending on DENVORA SEO to do it.
Who can start the connection
Only members with the owner or admin role can start or swap the Google connection — a safeguard against any team member changing, without oversight, which account the data comes from. Once connected, every member with access to the organization keeps seeing reports normally.
If no sites show up
The most common cause isn't an error — the chosen Google account simply doesn't have access to any Search Console property yet. Confirm at search.google.com/search-console that the site is there under that same account, then go back to DENVORA SEO to refresh the list — no need to reauthorize from scratch.
Multi-client: one connection, many sites
For agencies, the common pattern is adding the Google account used to connect to DENVORA SEO as a user on each client's Search Console property. From there, every one of those properties appears in the same list, and each site stays tied to the right project within the organization — with no data mixed between clients.
Frequently asked questions
Is it safe to connect my Google account to DENVORA SEO?
Yes. It's the same OAuth mechanism behind "Sign in with Google" used by thousands of apps. DENVORA SEO never sees or stores your password.
Can DENVORA SEO change or delete anything in my Search Console?
No. The access requested is read-only (webmasters.readonly) — it never writes or deletes anything on Google's side.
How long does the connection take?
Under 60 seconds, from the first click to real data on the dashboard.