Where the counters actually live
The last step of adding a counter here has a section called "Where does it go?" — a short paragraph for each platform, explaining where the code belongs. WordPress, WordPress.com, Blogger, Ghost, Wix, Squarespace, Neocities, and the static site generators.
On 24 August 2026 we counted, for the first time, where the counters that exist are actually installed. The page addresses counters report are in the database; grouping thirty days of them by host takes one query.
| chomikuj.pl | 672 counters | not in the list |
| Blogger | 92 | in the list |
| Wix | 9 | in the list |
| Ghost | 4 | in the list |
| WordPress | 4 | in the list |
| Squarespace | 0 | in the list |
| Neocities | 0 | in the list |
672 out of 1,147 counters whose page we know — 58.6 percent, more than every other platform in the list put together. The word "chomikuj" appeared nowhere in the source code. Meanwhile two platforms with zero counters each had their own paragraph.
The list was almost exactly inverted from reality, and had been since it was written. It was assembled the way such lists usually are: from what a developer knows the web to look like.
One caveat on the numbers. The host test is reliable for platforms whose free tier lives on a platform subdomain. Self-hosted WordPress and Ghost run on their owners' own domains, so those two are undercounted — how far, we cannot say from here. chomikuj's share stands regardless.
The paragraph that was missing
chomikuj.pl is a Polish file-hosting community. Each account has a description field, and that is where the counter goes. The field does not accept scripts — which is exactly why every counter there shows up in the log as an image request rather than a script load, and why the default first tab of the embed step is the wrong one for most of the people using this service.
So the entry now says that: use the <img> tab in the embed step rather than the first line, and fill in your page address in the field underneath so the statistics know where the counting happens.
It is one paragraph in eleven languages. What it cost was a query that could have been run at any point in the last two years, against data the service collects about itself and had never looked at.