Read-only authorization
The connection requests the narrow scope needed to analyze Search Console data.
Native integration
Bring first-party search performance into the decision loop.
Connect a verified property with read-only access and analyze the queries and pages behind local discovery.
G
Google Search Console
Google OAuth · user controlled
1Sign in with your Google account
2Choose an authorized property
3Disconnect whenever you need
Normal users authorize Localense. They do not create or configure their own Google Cloud project.
How access works
One Localense connection, controlled by each user.
Localense uses Google OAuth so each user signs in with their own Google account, chooses an authorized property, and can disconnect access from the product.
What it unlocks
Use Google Search Console in the full local search context.
User-selected properties
Each user chooses from the properties their Google account is already allowed to access.
Query and page analysis
Use clicks, impressions, CTR, and average position with their source and date range visible.
Three-step connection
Familiar to the user. Secure by default.
The exact resources available always come from the permissions on the Google account that signs in.
- 01
Sign in
Authorize Localense through Google's OAuth consent flow.
- 02
Select
Choose the Search Console property for the current Localense project.
- 03
Sync
Import performance on demand or through an approved schedule.
Start with your own data
See what is holding back local visibility, and what to do next.
Connect read-only Google data, run the first audit, and build an evidence-backed action plan. No charge for the first 14 days.