Source-labelled metrics
Search Console and GA4 values retain their source and date context; one is not used to manufacture a missing value from the other.
Traffic and engagement fields from connected Search Console and GA4 sources.
Review sessions, engagement, conversions, geography and device fields only where the corresponding connected source supplied them.
Why it is useful
Traffic counters tell you people arrived, not what they did next, where they came from, or what device they used. Without behavior, geography, and technology tied to the same pages, you cannot separate a page that converts from one that quietly loses every visitor.
Search Console and GA4 values retain their source and date context; one is not used to manufacture a missing value from the other.
Geography and Devices & Browsers show which countries, devices and browsers your audience really uses.
GA4 engagement and conversions connect SEO effort to outcomes, not just pageviews.
Data and evidence
Web Analytics reads your connected analytics and Search Console, and reports per-URL behaviour, search audience geography and the browsers, systems and devices actually recorded. Windows of 7, 30 and 90 days are anchored to real data, so a window with no data is shown as empty rather than drawn as a flat line at zero.
Search Console and GA4
URL-level reconciliation
Engagement opportunity board
No GA4 connection means no sessions, bounce, city, browser, or device claim; Search Console remains visible as its own source.
Core capabilities
You get sessions, pageviews, bounce rate and duration per URL, search clicks by country and continent, technology breakdowns, and opportunity quadrants with a high-bounce action board that turns behaviour into a list of pages to look at. Every figure resolves to the URLs behind it.
Sessions, pageviews, bounce rate, and average session duration are aggregated per URL over a rolling window anchored to your latest analytics day. Each page is cross-referenced against the crawl and Search Console, so behavior, technical health, and search demand sit on one row. Opportunity quadrants sort every page into Protect, Fix CTA, Improve intent, Grow, or Investigate.
The Search Console country dimension shows exactly where your search clicks and impressions come from, rolled up to continents with CTR and average position. Cities and languages are drawn from Google Analytics 4 when connected, and stay clearly empty until then rather than showing a guessed visitor number.
See the browsers, operating systems, and device categories your visitors actually use, with real visitor and session counts from Google Analytics 4. The device view adds a second authoritative source, the Search Console device dimension, so desktop, mobile, and tablet search clicks are covered even before GA4 is connected. Visitor counts and search clicks are never conflated.
How the work moves
Connect your sources, pull the window you want to read, work through the cockpit, then act and export. The window is part of the finding, so a comparison always states the period it covers instead of implying that a number is timeless.
Link Google Search Console and Google Analytics 4 to the project so behavior, geography, and technology data can flow in.
The tool syncs the recent window of engagement, country, and technology data, anchored to your most recent real data day.
KPIs, opportunity quadrants, and quality distributions surface which pages, markets, and devices need attention first.
Open a page drawer for its top queries and next action, or export the filtered workbench to CSV.
Built around real work
Finds high-traffic pages with weak engagement and a concrete reason to fix them before they waste more search demand.
Sees which markets and languages a page already reaches so new content targets real audiences.
Compares device and browser mixes against page behavior to prioritize where UX friction costs the most.
Connected outcomes
Measure & Prove
Prove SEO results with source-linked metrics, dated crawl evidence and a report the client can inspect.
Open workflowDiscover & Diagnose
Interpret the change by metric, source and comparison window before deciding whether it is good, bad or only contextual.
Open workflowMeasure & Prove
A real zero comes from a connected source that observed zero; missing data means the required source captured nothing.
Open workflowMeasure & Prove
Tie each headline metric to its source, the pages and queries behind it, and the next decision leadership needs to make.
Open workflowCreate & Grow
Prioritize pages with observed demand and a fixable content gap before creating more content.
Open workflowResources
Written by the team that built it, and free to read without an account.
Step-by-step walkthroughs, five minutes each.
What the terms on this page actually mean.
How this works once you are inside a workspace.
Connected products
Frequently asked questions
Clear answers about data, availability and how the product fits into the wider workflow.
Search geography and device search clicks work from Search Console alone. Per-URL engagement, cities, languages, browsers, and operating systems need GA4 connected, and are clearly marked as not connected until then.
Search Console reports geography by country only. Cities and languages come from Google Analytics 4, so those views stay empty rather than show an estimate until GA4 is linked.
Engagement uses a rolling 7-, 30-, or 90-day window anchored to your latest analytics day, while geography and technology use the last 28 days, refreshed on demand.
It lists pages with meaningful traffic and a high bounce rate, each paired with a reason drawn only from real crawl evidence such as an error status, thin content, slow load, or a weak query match. It never guesses.
Measure & Report
Start with a real project, keep unavailable data visible and follow the connected workflow when the result is ready for action.