Plausible Not Tracking Visitors (No Stats Showing)
Workaround available Web Updated October 21, 2026
Quick answer
If Plausible shows no visits, the snippet is usually missing from the <head>, an old cached page is still served, or a consent banner, CSP or ad blocker stops the script. Confirm the snippet in the page source and a 200 request to plausible.io in the Network tab.
Most likely fix: Check the snippet is in the page.
Symptoms
The dashboard stays on the blinking green dot 'waiting for first pageview' screen, or visits stop appearing after a site change.
Why it happens
- Snippet not placed in the <head> of every page
- Page cache, CDN or optimisation plugin still serving old HTML
- Consent banner (e.g. Cookiebot) loading the script only after consent
- Content Security Policy not allowing plausible.io
- Testing on localhost, where the script disables itself
- Your own ad blocker, extension or VPN blocking the request
- Duplicate snippets or a modified snippet
How to fix it
Try these in order — the most common fix is first.
1. Check the snippet is in the page
- Open your site and view the page source (Ctrl+U, or Option+Command+U on Mac)
- Search for plausible.init or your plausible.io script
- Make sure it is inside <head> and matches the snippet from site settings exactly
- Remove any second copy of the snippet
2. Purge every cache
- Clear your CMS/plugin cache (WP Rocket, LiteSpeed, etc.)
- Purge your host and Cloudflare/CDN cache
- Reload the page in a private window
3. Check the network request
- Open DevTools > Network and reload
- Look for the plausible.io script request (starting with pa-) returning 200
- Check the Console for Plausible or CSP errors
- If blocked by CSP, add plausible.io to your allowed script and connect sources
4. Test without blockers
- Disable ad blockers, privacy extensions and VPN, or use another browser
- Visit the live domain, not localhost or a staging URL
- Check the realtime view in the dashboard
5. Check Shields rules
- Go to Site settings > Shields
- Make sure your IP, country, page or hostname isn't excluded
- If using hostname allowlist, add the domain you're testing
This guide also covers
- plausible not tracking
- plausible not showing stats
- plausible analytics not working
- plausible waiting for first pageview
Still not working?
If Plausible Analytics keeps failing, you're not alone. See every Plausible Analytics problem users report or the alternatives people switch to.
Other Plausible Analytics errors
- Plausible Verification Failed (Couldn't Verify Installation)
- Plausible Blocked by Ad Blockers (How to Set Up a Proxy)
- Plausible Custom Events and Goals Not Showing
- Plausible Not Working in Next.js (next-plausible)
- Plausible WordPress Plugin Not Tracking
- Plausible Numbers Different From Google Analytics
- Plausible UTM Parameters and Referrers Not Showing
- Plausible Pageview Limit Exceeded (Dashboard Locked)
- Plausible Google Analytics Import Failed or Missing Data
- How to Exclude Your Own Visits in Plausible
- Self-Hosted Plausible CE Not Recording Pageviews
- Plausible Bot Traffic Spike (Fake Visitors)