A number becomes useful when its source, population and counting rule are clear. Search Console measures activity within Google’s reporting system. Site analytics measures instrumented activity on your property. Third-party tools estimate or model a wider environment from their own data.
First-party does not mean complete
First-party measurement is closer to the system or property being measured, but collection rules still matter. Search Console can omit query detail; analytics can lose observations through consent choices or blocked scripts. Neither is an unrestricted record of every user action.
| Metric | What it describes | Interpretation limit |
|---|---|---|
| Clicks | Interactions counted as clicks by the search report | Not identical to people, sessions or pageviews |
| Impressions | Exposure counted under the result type’s visibility rules | Does not mean the reader noticed the result |
| CTR | Clicks divided by impressions for the selected population | Changes with position, query mix and presentation |
| Average position | An average of reported result positions under the platform’s rules | Not one fixed rank or a measure of screen distance |
| Organic sessions | Analytics sessions classified as organic search | Depends on session, attribution and channel definitions |
| Conversions | Actions designated as valuable in the measurement setup | Only meaningful when the action and tracking are valid |
For example, 20 clicks from 400 impressions gives a CTR of 5%. This is illustrative arithmetic, not a site result or a benchmark. Compare equivalent segments before deciding whether a change in that ratio needs action. Google’s metric definitions explain counting differences across result types.
Third-party discovery and demand metrics
| Metric | Typical basis | What to check |
|---|---|---|
| Backlinks | Links found in a provider’s crawl or index | Live versus historical data, deduplication and URL scope |
| Referring domains | Distinct domains associated with observed links | Subdomain treatment and current link status |
| Search volume | Estimated query demand for a place and period | Grouping, seasonality, location and update date |
| Keyword difficulty | A provider’s modeled estimate of competition | Inputs and target market; it is not your probability of success |
| Traffic estimates | Modeled visits based on sampled visibility and assumptions | Coverage and click-model assumptions |
| Visibility scores | Weighted visibility within a tracked keyword set | Query list, weights, locations and device |
DA, DR, TF and CF belong to their providers
Domain Authority (DA) is Moz’s proprietary domain-level score. Domain Rating (DR) is Ahrefs’ relative backlink-profile metric. Trust Flow (TF) is Majestic’s link-quality-oriented metric, and Citation Flow (CF) is its link-influence metric. They are not Google’s ranking metrics and are not interchangeable with one another.
Keep the provider, date and scope with the value. Domain-level scores do not establish the value of a particular source page or link. Read why backlink metrics disagree before combining exports.
Use a metric contract
For each reported number, record its definition, source, date range, timezone, filters, unit and known omissions. State the decision it supports. If the definition changes, annotate the series rather than presenting the discontinuity as performance.
Choose measures close to the question. Crawl requests help inspect access; conversions help evaluate a defined action. A visibility score alone cannot diagnose either. Use Search Diagnostics to locate the issue and SEO Research Methods to judge the strength of the explanation.