Quick answer
To add a hit counter to your website, choose a style (flat, pill, digital or minimal), type a label such as "visitors" and pick a colour. Copy the HTML code and paste it where the counter should appear — any website, WordPress, Blogger, Wix, Shopify or a GitHub README (Markdown). The counter counts each visitor once per day by default, needs no account and shows no ads.
- Styles:
- Flat, pill, digital, minimal
- Counting:
- Unique visitors per day or every page view
- Works on:
- HTML sites, WordPress, Blogger, Wix, Shopify, GitHub, Notion
- Formats:
- SVG badge, Markdown, JavaScript text, JSON API
- Customisation:
- Label and colour
- Sign-up:
- Not required
- Ads or links:
- None
- Privacy:
- No cookies, no personal data stored
A hit counter is the simplest form of web analytics: a small number on the page that tells you — and your visitors — how many people have viewed it. Counters were everywhere in the early web, then disappeared as analytics dashboards took over. They are back because they do something dashboards cannot: they show social proof right on the page. A GitHub project with "12,480 visitors", a blog post with a live view count or a portfolio that proves people are looking all build trust at a glance.
The problem is that most free hit counters look dated, inject ads or hidden links, set tracking cookies or stop working when the provider shuts down. Our modern hit counter is a lightweight SVG badge that looks at home on today's websites. Choose from four designs — flat, pill, digital and minimal — set your own label and brand colour, and copy the code.
Each counter has its own Counter ID. The badge counts a visit whenever the image loads, with optional unique counting so a visitor who reloads the page is only counted once per day. There is no account, no cookies and no personal data stored — just a number that goes up.
For developers there are extra outputs: Markdown for READMEs, a JavaScript snippet that writes the number into your own styled text, and a JSON endpoint you can call from any app.
How to add a hit counter to your website – step by step
- 1 Choose a Counter IDA random ID is created for you. Keep it, or click New for another. Use a different ID for each page or site you want to count separately.
- 2 Pick the styleChoose flat, pill, digital or minimal, type a label such as "visitors", "views" or "readers", and select a colour.
- 3 Choose how to countLeave unique visitors on to count each visitor once per day, or turn it off to count every page view.
- 4 Copy the codeCopy the HTML snippet for websites, the Markdown snippet for GitHub or Notion, or the JavaScript snippet for your own design.
- 5 Paste it into your pagePaste the code into your HTML, a WordPress Custom HTML block, a Blogger HTML gadget or your README. The counter starts counting immediately.
Why use this hit counter?
Modern designs
Four clean SVG styles that stay sharp on every screen.
Your colours and label
Match your brand and say "visitors", "views" or anything you like.
Unique visitor counting
Reloads by the same visitor are counted once per day.
Works everywhere
Any platform that allows an image or HTML — including GitHub READMEs.
No sign-up, no ads
No hidden links, no ads, no tracking cookies.
Developer friendly
Markdown, JavaScript and JSON outputs for custom designs and apps.
How to add the counter on popular platforms
- Plain HTML sites: paste the <img> code into your page's HTML, for example in the footer.
- WordPress: in the block editor add a Custom HTML block and paste the code; for a site-wide counter, add it to a footer widget. In Elementor, use the HTML widget.
- Blogger: Layout → Add a Gadget → HTML/JavaScript, paste the code and save.
- Wix: Add → Embed Code → Embed HTML, and paste the code.
- Shopify: Online Store → Themes → Customize, add a Custom Liquid section and paste the code.
- GitHub README: paste the Markdown code into README.md. GitHub caches images for a few minutes, so the number updates with a short delay.
- Notion and other editors: use the Markdown or image link where images by URL are allowed.
Unique visitors vs. page views
With unique counting on, the counter records a visitor once per day, however many times they reload. That gives a more honest number and stops anyone inflating the count by pressing refresh. With unique counting off, every load of the image counts — useful for measuring total views of a page or a README. Visitors are recognised by an anonymous daily fingerprint, not cookies, so nothing is stored in their browser and no personal data is kept.
Choosing a style
| Style | Look | Great for |
|---|---|---|
| Flat | Two-part badge, label and number | GitHub READMEs, documentation, developer sites |
| Pill | Rounded, friendly badge | Blogs, personal sites, portfolios |
| Digital | Retro digital display | Fun sites, nostalgia, gaming and hobby pages |
| Minimal | Just the number and label as text | Clean layouts, footers, magazine-style blogs |
Using the counter in your own design
If you want the number in your own font and layout, use the JavaScript output. It includes an empty <span> with a data attribute and a small script; the script fills the span with the current count, formatted with thousands separators. Style the span with your own CSS. Developers can also fetch the count as JSON from the API endpoint and display it in apps, dashboards or static site generators. Add readonly=1 to show the count without increasing it — handy for showing a total on an admin page.
Hit counter vs. Google Analytics
A hit counter and an analytics tool answer different questions. Analytics (Google Analytics, Plausible, Matomo) tells you privately where visitors come from, what they read and how long they stay. A hit counter tells your visitors that the page is popular, and it works in places where analytics scripts are not allowed, such as GitHub READMEs, marketplace descriptions and many site builders' free plans. Many site owners use both: analytics for decisions, a counter for social proof.
Is a public hit counter good for SEO?
A counter does not change your search rankings directly. Its value is psychological: visitors who see that many others have read a page tend to trust it more, stay longer and share it — behaviour that indirectly helps your content perform. Because the badge is a lightweight SVG loaded lazily, it does not slow your page down or hurt Core Web Vitals. To improve SEO directly, check your page with our SEO Report, write better titles with the Meta Tag Generator and preview results with the SERP Preview tool.
Tips for using counters well
- Use a different Counter ID for each page you want to count separately, or one ID across your whole site for a site-wide total.
- Place the counter near the end of an article or in the footer, where it supports trust without distracting readers.
- Pick a colour from your brand palette — convert colours with the Color Converter.
- For brand-new pages, consider waiting until the number is respectable before showing it publicly; use readonly mode to check it privately.
- Write down your Counter ID; the tool remembers it in your browser, but clearing your browser data removes it.
Privacy and reliability
The counter stores only a number per Counter ID. It does not set cookies, does not collect IP addresses in its database and does not track visitors across sites. Each request returns a fresh, uncached image, so the count is always current. The badge is served with cross-origin headers so it loads on any domain.
Troubleshooting
- The counter does not increase. With unique counting on, your own reloads count only once per day. Test from another device, or turn unique counting off.
- The GitHub badge updates slowly. GitHub caches images through its camo proxy; updates appear after a few minutes.
- The counter does not show. Check that the page allows external images and that you pasted the code into an HTML block, not a text block.
- I lost my counter. The count is linked to the Counter ID in the code. Copy the ID from the code on your site back into the tool.
Frequently asked questions
How do I add a free hit counter to my website?
Choose a style, label and colour, copy the HTML code and paste it into your page. It starts counting immediately.
Do I need to sign up?
No. Counters work without an account, email or registration.
Does the counter work on WordPress?
Yes. Paste the code into a Custom HTML block, an Elementor HTML widget or a footer widget.
Can I use it in a GitHub README?
Yes. Use the Markdown code. GitHub caches images briefly, so updates appear after a few minutes.
Does it count unique visitors?
Yes. By default each visitor is counted once per day. Turn unique counting off to count every view.
Are there ads or hidden links?
No. The badge contains only your label and count.
Does the counter use cookies?
No. It does not set cookies or store personal data.
Can I change the style after adding it?
Yes. Generate new code with the same Counter ID and replace the old snippet; the count is kept.
Will the counter slow down my site?
No. It is a tiny SVG image loaded lazily.
Can I get the count as JSON?
Yes. Use the JSON endpoint shown in the developer outputs.
Can I start the counter at a higher number?
Counters start from zero, so the number always reflects real visits.
Can I hide the counter but still count visits?
Yes. Use the JavaScript output and keep the span hidden, then check the count with readonly mode or the JSON endpoint.
Last updated November 22, 2026 · Written and tested by the SmallEasyTools team.