Starting point: what you need before measuring anything
Before opening tools, confirm that you have access to the domain’s control panel or the site’s Google Analytics account. Without administrator permissions, any check is left half done. In projects where you only have read access, the list changes: you won’t be able to verify the code installation or the internal filters.
It’s also worth knowing whether the site is your own, a client’s, or someone else’s. If it’s someone else’s, forget Search Console and Analytics; you’re limited to external estimates, and that conditions the entire checklist.
Checklist: free sources by level of access
1. Internal verification (own site or with permissions)
- Google Search Console: review the performance report with the last 3 months filter and compare impressions against clicks. If impressions go up and clicks don’t, the problem is in titles or meta descriptions, not in visibility.
- Analytics (GA4): check that the data stream receives events in real time from a clean session. A common mistake is measuring with the ad blocker active and concluding that the tag doesn’t work.
- Server or CDN logs: if your hosting offers hit statistics, they’re useful for detecting bots that inflate visits. According to documentation from the main providers, automated traffic can represent a significant share of requests on small sites.
- CMS panel: plugins such as internal statistics ones give quick figures, but they count administrator visits and don’t distinguish sessions well. Use them only as a rough guide.
2. External estimation (any site)
- Traffic estimation tools: they offer approximate volumes based on user panels and search engine clicks. They aren’t real measurements: treat them as orders of magnitude.
- Searches with operators: check site:domain.com to see how many pages are indexed. A sharp drop in results usually anticipates crawling problems.
- Keyword data: free search volumes tend to group variants together and round figures. They aren’t useful for calculating exact traffic, only for prioritizing.
- Industry forums and communities: sometimes there are one-off screenshots of panels, but don’t take them as a reliable reference.
3. Consistency checks
- Compare organic traffic from Search Console with the organic channel in GA4. Differences of 10-20% are normal due to attribution models and cookies; larger differences indicate a tagging problem.
- Check whether there are pages with many impressions and a CTR close to zero: it may be a search intent problem.
- Check whether the declared sitemap matches the URLs that actually receive visits.
- Look at the distribution by device: a site with a lot of mobile traffic and poor performance loses clicks that don’t show up in external estimates.
Mistakes I’ve seen repeated
A typical case: a local business compares its traffic with an estimation tool and concludes that it has lost half its visits. On reviewing Search Console, the decline came from an old link campaign and from category pages with duplicate content. The external tool couldn’t see even half of those URLs because they weren’t indexed.
Another frequent mistake: measuring the traffic of a recently migrated website without waiting at least two weeks. The data mixes redirects and old pages, and the conclusions come out distorted.
Limits worth acknowledging
No free combination gives exact figures for someone else’s visits. Estimates fail especially in small niches, in branded traffic, and on sites with a lot of direct or app traffic. They’re also no good for auditing conversions: without access to the owner’s panel, there’s no way to know what happens after the click.
If you need financial or business data, the free route runs out. That’s when you have to request access or work with aggregated industry data.