Your built-in site analytics are overcounting. Why, and how to see real visitors
If you built your site with an AI/no-code builder and you're trusting its built-in analytics, the numbers are almost certainly inflated — and not in a good way.
ChatGPT Sites is a good example. Its built-in view counter counts technical requests, not just real people. Builders report tens of thousands of pageviews on paths like /*, .rsc and /robots.txt while actual unique visitors are in the dozens. OpenAI hasn't confirmed whether those platform/bot requests count toward usage, so reading the built-in totals as "real traffic" is misleading.
Three things that make your numbers trustworthy regardless of builder:
Track unique visitors, not raw pageviews. Pageviews are easily inflated by reloads, crawlers and SPA/CSR routes collapsing into /*.
Look at referrers/sources, not just volume. Where the traffic actually came from tells you a lot more than a headline number.
Keep the platform's own counter separate from your own visitor tracker, so the two don't get mixed up.
On adding a third-party tracker to a no-code site: most builders don't block external scripts by default. The one gotcha is if your site ships its own strict CSP — then allow the tracker's host in script-src, img-src and connect-src.
Disclosure: I run Hitsteps, and we published a free one-prompt kit for ChatGPT Sites (you paste one prompt into the chat that built the site, it drops the tag once into the shared layout, and you get live visitors, sources and routes in your own dashboard). It's optional and not required for any of the above — just a resource if it's useful.

