Google Search visits in your log, beside Search Console clicks
Salience now identifies Google Search visits the way Google says to, counts the Google app on Android instead of calling it direct, and puts the log's Google visits beside Search Console clicks per day and page with the blank-referrer share that explains the gap.
Google documents how a visit from Search shows up in a server log: the referrer is the Google host and nothing else (https://www.google.com/, https://www.google.co.uk/), the Google app on Android sends android-app://com.google.android.googlequicksearchbox instead, only the landing-page request counts, and privacy settings often blank the referrer altogether. Salience Logs now follows those rules.
Google Search on the Referrers page. A Google Search card groups every google.<tld> country domain and the Android app into one figure for human page requests, with the split by source. The Android app's referrer used to fall through the host parser and count as direct; it is now a referrer in the list, in referrer detail and in inbound broken links.
Visits beside clicks on the Search Console page. A new panel puts the log's Google-referred page visits beside the clicks Search Console reported for the same Pacific days and the same pages: visits per 100 clicks over the days both sides have reported, a daily series, the pages where one side is empty, and the share of human page requests that carried no referrer at all, which is the ceiling on what a log cannot attribute. Google's own list of why the two disagree sits under the figures.
API, MCP and CLI. GET /public/v1/websites/{id}/seo/search-visits and the MCP tool get_search_visits return the same report; GET …/referrers and get_referrers carry a google_search block; salience seo search-visits prints it. Read the log side as a floor: Discover, Images and the other Google surfaces send the same referrer as Search and cannot be told apart in a log.