Connect Search Console to Tatheon and organic search becomes a channel you can measure against revenue rather than a separate report nobody opens. This guide is for whoever owns the Search Console property. It covers granting access, what Search Console can and cannot tell you, and why its numbers lag the rest of the board.
Before you start
You need Owner access on the Search Console property. Full and Restricted users cannot add other users, so if the Users and permissions screen will not let you add anyone, you hold the wrong level.
If your property was verified by a developer or an agency years ago, they may still hold the only owner account. That is worth resolving regardless of Tatheon, because it means nobody at the business controls the property.
Grant access
Open the source wizard and choose Google Search Console. Copy the Tatheon service account address it shows you.
In Search Console, open Settings, then Users and permissions, and add a new user with that address. Grant Full access. Search Console requires Full rather than Restricted for the performance data Tatheon reads, which is a limitation of their permission model rather than a request for more than is needed.
Return to the wizard. Tatheon detects the property once access is granted.
Expect a lag, and know it is normal
Search Console data is not available for the current day, and it is usually not complete for the previous two either. Google finalises it on its own schedule.
Tatheon accounts for this rather than treating the gap as a fault. Search Console is expected to sit a couple of days behind the rest of the board, and the freshness reporting reflects that. If you are looking at yesterday and the organic numbers are absent, that is Google, not the sync.
This is also why organic performance is best read weekly rather than daily. A daily organic number is mostly noise plus an incomplete final day.
What it tells you
Search Console reports impressions, clicks, average position and the queries people used. It is the only source for what people actually searched before arriving, because that information is stripped from analytics referrers.
It reports on your site as a whole, not on individual visitors, and it samples queries with very low volume rather than reporting them all. So the totals are reliable and the long tail of individual queries is indicative.
Confirm it is working
Compare total clicks for a settled week against Search Console’s own performance report. They should match closely, because both are reading the same finalised data.
If they differ substantially, check whether your property is a domain property or a URL prefix property. A URL prefix property covers only one protocol and subdomain combination, so a site that serves both the apex and the www version can be split across two properties, each seeing part of the traffic.
Common problems
A property that connects and reports nothing is nearly always a permission level issue, because Restricted access silently returns no performance data rather than raising an error.
Numbers that stop after months of working usually mean the granting owner’s account was removed. Search Console does not warn anyone when this happens.
Next
With Search Console and Google Analytics 4 both connected, the website section can show the full path from search query through landing page to order, rather than each step in isolation.