Member Avatar for Goldfinch

A few months ago I launched a website. As of today or a little earlier it was averaging 10 unique visits a day and there is a rising trend. Thing is, I'm trying to figure how much of it is really people looking at the webpage and therefore evidence that I am doing something right. I know I get search indexers and SpamBots, and some of the visitors definitely seem to be real but its hard to read. Will there be a level of visitors when I'll know its mostly real people? Is there a better way to tell than that? Any insight would be really useful.

Edited by Goldfinch
  • 3 Contributors
  • 2 Replies
  • 202 Views
  • 3 Months Discussion Span
  • Latest Post Latest Post by <M/>

Dani AI

Generated

No single unique-visitor threshold proves traffic is “real.” Small launches (like ’s ~10/day) commonly mix search crawlers, legitimate users and automated bots. The links posted by and offer useful reading; below is a compact, practical checklist and a few commands that make verification fast and repeatable.

Quick checks to separate humans from bots:

  • Engagement: humans usually generate multi-page sessions, measurable session duration and conversion events; bots often show single-page hits, 0s duration, or unnaturally regular intervals.
  • Sources: organic search and varied referrals look different from repeated hits from the same referrer or a string of odd domains (referral spam).
  • Hostname and JS: compare JavaScript analytics (GA/other) to raw server logs; hits that appear only in analytics or only in logs are both worth investigating.
  • IP / UA patterns: clusters of visits from one IP or ASN, or repeated identical user-agent strings, are strong bot signals. Verify major crawlers with a reverse DNS + forward lookup and check WHOIS/ASN data before trusting a “bot” UA.

Quick, repeatable commands (run on the server where logs are stored):

# top client IPs
awk '{print $1}' access.log | sort | uniq -c | sort -rn | head -n 40

# top user-agents (combined log format)
awk -F'"' '{print $6}' access.log | sort | uniq -c | sort -rn | head -n 40

# reverse DNS example (replace with a suspect IP)
host 203.0.113.45
# then forward-check the returned name:
host returned-name.example

Practical next steps and cautions: add event tracking for real interactions (form submits, clicks, scroll depth), create an analytics include-filter that only allows valid hostnames (e.g. ^(.+\.)?example\.com$), deploy a simple honeypot URL to detect automated crawlers, and block IPs only after confirming behavior across logs + analytics. False positives are easy; block cautiously and monitor for unintended consequences.

Recommended Answers

All 2 Replies

Member Avatar for Member #949455

A few months ago I launched a website. As of today or a little earlier it was averaging 10 unique visits a day and there is a rising trend. Thing is, I'm trying to figure how much of it is really people looking at the webpage and therefore evidence that I am doing something right. I know I get search indexers and SpamBots, and some of the visitors definitely seem to be real but its hard to read. Will there be a level of visitors when I'll know its mostly real people? Is there a better way to tell than that? Any insight would be really useful.

This blog has answer some of the questions you ask:

http://www.dailyblogtips.com/get-real-about-your-traffic/

Member Avatar for <M/>

This may help

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.