EnterraHost
Search Console says what people looked for and whether they clicked. Analytics says what they did when they arrived. Joined together they answer the question that neither can answer alone, which is whether the traffic a page earns is traffic that stays.
Connecting it
The connection is per site, not per account, and it sits on the same Search & Traffic screen as the Search Console one. A site can have either, both, or neither.
You authorise a Google account with read access to the Analytics property. The product reads sessions, engagement and page paths. It cannot change a property, edit a conversion or delete a report.
Which property to choose
Choose the property that actually receives this domain's traffic. A company with several sites and one shared property will see numbers that look plausible and are wrong, because the property counts every site inside it.
EnterraSEO reads only the pages that belong to the domain you added, so a shared property is filtered rather than trusted wholesale. A property dedicated to the site is still the cleaner arrangement.
Why sessions and search clicks never match
Two different instruments counting two different things. This mismatch is the most common cause of a support ticket about analytics, and it is not a fault.
- Search Console counts clicks. A click is a recorded visit from a search result.
- Analytics counts sessions. A session starts when somebody arrives, from any source, and one person can start several.
- Consent, ad blockers and script failures remove some sessions from Analytics and none from Search Console.
- Search Console lags by two to three days while Analytics reports within hours.
Sessions will usually be higher than clicks, because search is one source among several. In a month where paid traffic ran, they can be much higher.
What to do with the engagement figure
Engagement rate in Analytics is the share of sessions that lasted ten seconds or longer, or had a conversion, or viewed two pages. It is a rough proxy and it is useful in one direction only, which is comparisons between pages of the same kind.
A guide page with 70 percent engagement and a service page with 30 percent may both be fine. A service page at 30 percent that used to be at 60 percent is a change worth understanding.
Disconnecting
Disconnect revokes the stored token immediately. The crawl history stays, because it is our data about your site. Revoking access from the Google account side also works, and the next read simply fails rather than returning stale numbers.