Home About Stats Changelog Privacy Contact

Site stats: impressions and indexing

CalcProMaster is a young site, so the honest numbers change every week. These are the ones we track, taken from Google Search Console rather than estimated, with the date each figure was captured.

Last updated 2026-10-28 · impression data as of 2026-10-24

52
search impressions per day (7-day run-rate, 2026-10-18 → 2026-10-24) — about 1,579 a month

Search impressions

Every window is shown separately because a growing site's 28-day average always reads lower than its current speed.
MeasurePer dayPer monthWindow
7-day run-rate52 impressions/day1,579/month2026-10-18 → 2026-10-24
3-day run-rate4 impressions/day112/month2026-10-22 → 2026-10-24
28-day average748 impressions/day22,780/month2026-09-24 → 2026-10-22 (lagging)

The 28-day figure is a lagging number, not today's speed: it still carries the days before the site's impressions started climbing. The 7-day window is the one to read for “how fast is it going now”.

Other 28-day figures, for context.
Clicks22search clicks in 28 days
Click-through rate0.1%20,954 impressions
Average position32.5most impressions still sit on pages 2-5

Indexing progress

Google Search Console coverage and URL Inspection data.
Pages Google has indexed952of 1,875 known URLs
Share indexed50.8%coverage snapshot 2026-10-04
Waiting to be crawled40technically sound, no fixable blocker
Not indexable by design4redirects, noindex and duplicate canonicals
Measured indexing rate0.0 pages/week20 URLs tracked
What this page does not claim. The rate above is measured from a tracked sample of URLs, not the whole site, so it is an observation rather than a forecast. Indexing is decided by Google — the calculators themselves have no technical blocker left; they wait for a crawl. Nothing here promises a traffic figure on a date.

Weekly health check

Run-rate watch: waiting for a newer settled day. Search Console has not settled a day after 2026-10-24, so the seven days to 2026-10-24 were already measured on 2026-10-28. Search Console chart data runs to 2026-10-27, but its newest days are still being filled in, so 2026-10-24 is the newest reading worth trusting. This run re-read that same window: no new reading was stored and no stall is called, because a window that has not moved cannot be evidence of a decline.

What these numbers do not measure

Impressions count a result appearing on screen, not a person reading it. A page that ranks on page four can collect impressions for months without a single click, and a page that ranks first for a question already answered in the snippet can get plenty of impressions and few visits. Search Console also omits anonymised queries, so the long tail is undercounted. Nothing here measures whether a visitor found the answer useful: a session that ends in eight seconds after the number was read is a success for a calculator, and there is no metric on this page that would know the difference.

How often this page updates

The page is regenerated by the weekly refresh workflow, not edited by hand. Search Console data lags by roughly two to three days, coverage reports lag further, and URL Inspection is a snapshot of one moment for one URL. Each table states the window it covers; comparing two windows of different lengths is the fastest way to misread a young site, which is why the run-rate rows sit beside the 28-day average instead of replacing it.

How to read this

Two things move a new site: how many pages Google has indexed, and how high each indexed page ranks. Impressions respond to both, and clicks follow impressions at the position the page holds — so a growing impression line with a low click count simply means the pages are still on pages 2-5. The about page describes how the calculators themselves are verified.

Figures come from Google Search Console (performance and coverage exports) and from a weekly automated refresh. The repository keeps the raw exports, so any number on this page can be traced back to the file it came from. Copy changes are dated in the changelog, so a movement in these numbers can be tied back to a specific edit.

Last updated