You installed your counter, but the numbers are not showing, the display is missing or the reports stay at zero. Almost every case comes down to a small number of causes: the code is not on the page, something prevents it from running, or the visit is not being counted for a good reason. This troubleshooting checklist takes you through each cause in the order that finds most problems fastest.
Step 1: Confirm what you expect to see
- Text counter: a small box with the statistics you selected should appear exactly where you placed the code.
- Hidden counter: nothing appears on the page. That is correct. Check the reports instead of the page.
Also remember that reports show recorded activity for the selected date and timezone. If you test just before midnight in your reporting timezone, your visit may appear under the next day.
Step 2: Check that the code is on the page
- Open the page in a private browser window.
- Right-click and choose View page source (not “Inspect”, which shows the page after scripts have run).
- Search for
gnrcounter.com/counter.php.
If you cannot find it, the code was not saved, was placed in a template that this page does not use, or was removed by your editor. Common causes:
- The code was pasted into a text or paragraph block, which escapes or strips scripts. Use a Custom HTML block, an HTML/JavaScript gadget or a code area.
- Your user role or hosting plan does not allow scripts, so the editor removed them on save. See our WordPress guide and Blogger guide for platform specifics.
- The code is in a sidebar or widget area that this page layout does not show.
- A page builder or landing page tool uses its own template without your footer.
Step 3: Check that the code is complete and unchanged
The embed code should look like this, with your own ID:
<!-- GNRCounter -->
<script src="https://gnrcounter.com/counter.php?accId=YOUR_COUNTER_ID"></script>
<noscript><a href="https://gnrcounter.com">Free hit counter</a></noscript>
<!-- End GNRCounter -->- The ID must be your own. A placeholder or an ID copied from an example will not record your visits.
- Do not add
asyncordefer. The text counter is written into the page at the script’s position while the page loads. Loading it later prevents the display from appearing. - Check for “smart” quotes. Copying code through a word processor can turn straight quotes into curly ones, which breaks HTML.
- Keep the code in one piece. Line breaks inside the address or a missing closing tag stop it from working.
Step 4: Check for scripts being delayed or blocked
Performance and caching plugins
Settings such as “delay JavaScript execution”, “load scripts on user interaction”, “defer JavaScript” or “combine JavaScript” move or postpone scripts. Add gnrcounter.com to the exclusion list, then clear the page cache and any CDN cache.
Content Security Policy
If your site sends a Content Security Policy header, it must allow scripts from https://gnrcounter.com. Otherwise the browser refuses to load the counter. Open your browser’s developer console (usually F12) and look for messages mentioning the policy.
Consent tools
Consent managers often block analytics scripts until a visitor accepts. That is correct behaviour where consent is required. When testing, accept analytics cookies in the consent banner, or check how your consent tool categorises the counter.
Ad blockers and privacy browsers
Extensions and some browsers block tracking scripts. If the counter works in one browser but not in another, test in a clean browser profile without extensions.
Step 5: Single-page applications and dynamic pages
Sites built as single-page applications change content without loading a new page. The counter runs when a page is loaded, so in-app navigation may not create new page views, and inserting the script after the page has finished loading can prevent the text display from appearing. Place the code in the initial HTML of the page rather than injecting it later.
Step 6: Check whether your own visits are excluded
If you previously opened your site with ?gnrc-hideme=1, your browser is excluded from counting on that domain. That is useful, but it can make you think the counter is broken. Open a page with ?gnrc-hideme=0 to include your browser again, or test from another device.
Step 7: Check the reports correctly
- Open the report link for the right website and counter.
- Select today’s date and confirm the timezone.
- Look at online users for an immediate check: a visit from the last five minutes should appear there.
- Remember that reloading the same page creates page views, while visitors are counted once per period.
Step 8: The display looks wrong
- Unreadable text: choose background and text colours with stronger contrast.
- Squeezed or overflowing box: place the code in a wider area, or show fewer statistics.
- Counter appears twice: the code is installed in two places, such as a widget and a footer plugin. Keep one copy; duplicates also double your page views.
- Counter appears at the very bottom of the page: the code was added through a footer hook. For a visible counter, place it in a widget or block where you want it to appear.
Quick reference
| Symptom | Most likely cause |
|---|---|
| Code shows as text on the page | Pasted into a text block instead of an HTML block |
| Code disappears after saving | Role or plan does not allow scripts |
| Nothing in source code | Wrong template, widget area or page builder |
| In source, but no display | Script deferred, delayed or blocked |
| Works for others, not for you | Ad blocker or gnrc-hideme exclusion |
| Hidden counter shows nothing | Expected; check the reports |
| Page views look doubled | Code installed twice |
Still not working?
If you have worked through every step, contact us with the public address of a page that contains the code, the browser you used and what you expected to see. Never send your private management link or passwords; the public page address is enough to start.
Frequently asked questions
How quickly should a test visit appear?
A visit normally appears in online users and today’s figures shortly after the page loads, provided the code ran and the visit was not excluded or blocked.
Why do my numbers differ from another analytics tool?
Different tools count differently. See why analytics numbers differ.
Can I move the counter to another place on the page?
Yes. Move the code to the new position and remove it from the old one, then clear any cache.
Does reinstalling the code reset my statistics?
No. Statistics are linked to your counter ID. As long as you use the same code, existing data remains.
Next steps
Once your counter works, read unique visitors vs page views to understand your first figures, and browse all guides for more help.