Google Search Console integration

Search Console data appears on the dashboard. Deeper SEO analysis comes from Rankfinity, not from a second engine.

Request access All integrations

Google Search Console

ROASfinity

Read-only firstWrites only after a yes

Stock photos and example labels, not customers.

How the data moves

From Google Search Console to your report. Back only with a yes.

The top row is reading, which is all a new connection does. The bottom row is writing, switched on per account only after you grant the rights.

Google Search ConsoleReads search Analytics
🔑Token vaultRead-only token, encrypted on the server
One recordStored per client, with currency and time zone kept
▦Your reportSource, formula and sync time on every number
✎ProposalA change such as: very few write operations apply
✓Preview and yesBefore and after, then a person with the right role approves
⎙Written onceAn idempotency key, so a retry cannot repeat the change
↻Read back, loggedGoogle Search Console is read again, compared and logged

Read: on by default, read-onlyWrite: off until you grant it, then every change needs approval

Google Search Console in daily use

What it reads first

Search Analytics

What it can change, after a yes

Very few write operations apply

Photos are stock images. App screens show test data.

In numbers

2things it reads

1things it can change, after approval

1things you need to connect

1limits stated

Google Search Console: reads, writes and limits

Search Analytics
Sites and properties

Very few write operations apply

Always after preview and approval.

Google OAuth with rights on the property

Search Analytics has its own sampling and delay.

Before you connect

Your ticks stay in this browser only.

Ask for a user with the lowest role that can read the reports. Do not share one login between team members.
Confirm the property type and the exact address. Write down the protocol, the subdomains and the version the client treats as the main site.
Write down the country, the language and the search markets that matter to the client.
Check whether the site answers on more than one version of its address, such as with and without www, or http and https. Note which one is the main version.
Compare one closed week of clicks with the site analytics as a sense check only. Do not expect the two to match.

Common data differences

General practice, not a claim about any one account.

Difference

Data delay and recent days

Search data often arrives with a lag, and recent days look incomplete. Numbers can also shift after a later update. Compare closed periods only, and say in the report which dates are still settling.

Difference

Hidden queries and filters

Some queries can be left out for privacy, so a list of queries may add up to less than the total. A country, device or page filter also changes the figures shown. Check the filter before you compare totals.

Difference

Clicks in search and visits in analytics

A click in search is not the same as a visit in analytics. Redirects, slow pages, consent choices and blocked scripts can make analytics count fewer visits. The two tools measure different steps of the same journey.

Modules that use Google Search Console

Each module page says what it reads and what it will not claim.

SEO with Rankfinity

Rankings, local map scans and AI visibility from Rankfinity, attached to the right client and site.

Reports

Client, channel, campaign and product reports where every figure shows its source, formula and update time.

Questions about Google Search Console

Is the Google Search Console connection read-only?

It starts read-only. Changes are added only where the platform grants the permission, and each one is previewed, approved, sent once, read back and logged.

Where is the token stored?

In an encrypted vault on the server, never in the browser, in logs or in an AI prompt.

Is the Google Search Console connector available now?

Not yet. It goes live after the platform access is in place. Request access to be told when it does.