Connect Search Console and GA4

Use separate Google identities, select exact properties, and read joined page evidence.

01

Treat the connections separately

Search Console supplies query and page search evidence. GA4 supplies landing page, session, engagement, and configured conversion context. They use separate authorization records and may belong to different Google accounts.

02

Select the exact property

Choose the property that matches the audited hostname and protocol. An account can authorize successfully while lacking access to the required property, so the final usable state matters more than the sign-in screen.

03

Read joined data by date and URL

The application maps connected page evidence to crawled URLs. Check reporting period, timezone, canonical differences, and excluded traffic before comparing a traffic value with a crawl finding.

04

Reconnect safely

When access expires, reconnect the affected integration with the identity that owns the property. A reconnect should refresh that connection without silently replacing a separate Google source.

Apply the guideReturn to the evidence and complete one verifiable action.
Open the app ↗
Did this guide solve the task?No account or workspace data is recorded here.