Connect Google Search Console and GA4
Updated
Want to bring your search and analytics data into LLMIC? Start with the right property access.
Google Search Console and GA4 need their own setup, and they answer different questions. This guide helps you connect each source and keep the reporting scope clear.
These integrations require Pro. Connecting them does not install analytics or create missing historical data.
Two sources, different evidence
- Search Console → search performance
Enable the Search Console API, grant property access and choose the correct property. - GA4 → collected analytics
Enable Data/Admin APIs, grant Viewer access and select the GA4 property.
Both require the correct credentials and reporting scope. Search Console and GA4 totals measure different things.
1. Give Search Console the right access
In Google Cloud, prepare a service account and enable the Search Console API for its project. Add the service-account email to the right Search Console property with access suitable for the reports you intend to use.
In LLMIC’s Google Search Console settings, save the service-account JSON through the available credential control. Treat the JSON file as a secret because it contains authentication material.
2. Set up access to the GA4 property
For GA4, the app’s setup guidance calls for the Analytics Data API and Analytics Admin API. Give the service account Viewer access to the matching GA4 property, then save its JSON in the GA4 connection settings.
Choose the actual GA4 property rather than a similarly named website or account. Check the property identifier carefully when multiple environments or clients have similar names.
3. Test the client and property you selected
Use the connection tests where available, then open the matching dashboard and select the correct property and dates. Check the active client before assuming a saved credential belongs to this project.
A valid key can still lack permission for a particular property. If a test fails, verify API enablement, access grants and the saved credential before changing the reporting period.
When totals differ, check the scope
When reconciling results against Google, match the property, date range, filters and reporting scope. Search Console and GA4 measure different events and should not be expected to have identical totals.
Preliminary or delayed provider data can change. A dashboard with no returned rows is not automatically evidence of zero traffic, and an API error should remain an error rather than becoming a zero-value report.
Keep your service-account credentials private
Grant only the access needed for reporting, and remove unused credentials when a project ends. Never place the service-account JSON in a public document or screenshot.
If access changes at Google, a previously saved connection may stop working. Re-test after rotating the key and confirm the property again.
Consult the current provider setup screens for the exact permission choices available to your account.
Quick reference
| Source | Preparation | Interpretation |
|---|---|---|
| Search Console | Enabled API and property access | Search performance for that property |
| GA4 | Data/Admin APIs and Viewer access | Collected analytics for the GA4 property |
| Client scope | Correct client and property | Prevents mixing separate projects |
| Empty results | Check dates and access | Not automatically zero traffic |
Continue learning
Ready for the next step? Start here: manage provider credentials, export scoped results.
If you still need help, contact support with your app version and the steps you tried. Leave out passwords, API keys and private account details.
Provider references: Google Search Console API prerequisites and Google Analytics API setup.
Published by LLMIC. Documentation reviewed on 24 September 2026.