Search Console
Join Google Search Console's search data to the companies that landed on each page.
Search Console tells you which searches bring people to your site. It cannot tell you who those people are. Logspot takes the pages Google says are earning clicks and shows which companies started a visit on those pages in the same period, so a keyword stops being an anonymous number and starts pointing at accounts you can act on.
Rolling out. Search Console is being enabled account by account. Contact us to turn it on for your organization.
Connect a Property
Go to Project Settings → Search Console and connect your Google account, then choose a property. Logspot lists the properties your Google account already has access to, and suggests the ones matching the project's tracking domains first.
Logspot requests read-only access. It never writes to Search Console, submits sitemaps, or changes anything in your property.
Once connected, the report appears at Analytics → Search.
Reading the Report
The page has three parts, and they do not come from the same request.
The totals for clicks, impressions, CTR, and average position come from a request with no breakdown, which is how Google returns a true total.
The Pages tab groups Google's rows by page and joins each one to the companies that landed there.
The Queries tab groups the same rows by query, and splits each page's companies and revenue across the queries that drove it.
CTR is calculated as total clicks divided by total impressions rather than averaged across rows, and average position is weighted by impressions. Averaging rows would let a single-impression row count as much as one with ten thousand.
Why the Table Does Not Add up to the Total
Google returns its top rows for a breakdown, not every row, and only gives a true total when you ask without one. Logspot shows Google's real total on the cards and Google's top rows in the table, rather than summing a sample and calling it a total. A gap between the two is expected and is not a bug.
How the Company Join Works
Google never identifies a searcher, so the join happens at the page level, not the click level.
For each page in the breakdown, Logspot counts the distinct companies whose Google organic session
started on that page inside the same date window. Both sides of the join are normalized the same way:
the query string and fragment are removed and a trailing slash dropped. The host is kept, so
example.com/docs and www.example.com/docs are different pages, exactly as Search Console reports
them.
Companies and revenue are scoped to Google organic visitors, mirroring how Google itself pairs Search
Console with analytics. Paid clicks are excluded, detected both from a paid utm_medium and from the
click identifiers Google Ads adds to a landing URL automatically.
This is not click-level attribution, and it should not be described as such. "Google organic visitors who started on this page" is the honest ceiling.
No Match
No match means no session started on that page in the window, which is different from a page that had
zero identified companies. Pages Logspot has no data for are counted and reported separately rather than
being shown as zero.
Estimates and the Tilde
A page's companies and revenue are divided across the queries that drove it, in proportion to each query's share of that page's clicks.
A ~ in front of a number means the figure is a split rather than a count. It disappears when a query
was the only one driving every page it touched. Hovering the cell shows what share of the query's clicks
the estimate rests on.
An em dash (—) means all of that query's clicks landed on pages with no match, so there is nothing to attribute.
Two things to understand about query-level numbers. The companies figure can exceed the number of distinct companies you have, because each page contributes its own count and one company visiting three pages counts three times. It answers how much company activity sits behind a query, not how many different companies. And a single click can carry a whole page's revenue, since page revenue accrues from all of that page's Google organic customers. That is the estimate working as designed, which is why it is marked.
Revenue
Page revenue is grouped by the first-touch landing page. A customer who first arrived from a Google search in January and paid in August is credited to their January landing page.
So page revenue means revenue from customers Google search originally delivered to that page, not sales that happened after a search this week.
Dates and Limits
Search Console reports days in Pacific time. Rather than shifting Google's data, Logspot converts your window to the same Pacific calendar days, so both halves of a row cover the same hours.
Google's most recent days are still being processed when they are fetched, which is why the ranges on offer stop at six months rather than a year. Where Google marks data as still incomplete, the report says so.
The report covers a date range of up to 200 days, requests the API maximum of 25,000 rows, and displays the top 100 per tab. Results are cached briefly, so two loads in quick succession return the same numbers.