Link terminology
Bot clicks vs human clicks
A bot click is an automated request from a crawler, preview service, scanner, or scripted client; a human click is a qualifying request associated with a person intentionally following the link.
Also called: bot click, human click, crawler click
Definition in plain language
A bot click is an automated request from a crawler, preview service, scanner, or scripted client; a human click is a qualifying request associated with a person intentionally following the link.
- 1Request
Inspect the HTTP method and speculative-request signals.
- 2Evaluate
Classify known crawlers, preview services, headless clients, and suspicious user agents.
- 3Decide
Apply blocking, access, and routing rules without treating automation as human engagement.
- 4Report
Record eligible owned-link events with a human, bot, or blocked classification.
Why bot clicks vs human clicks matters
Bots open links to build social previews, inspect safety, index pages, test availability, or automate browsing. If those requests are mixed with deliberate visits, campaign totals can look stronger than the human response really was.
The useful question is not merely whether a request happened. It is what kind of request it was, which rule handled it, and what conclusion the resulting data can support. Clear terminology prevents teams from treating every technical event as a person, every redirect as engagement, or every click as a conversion.
How it works step by step
A short-link system evaluates a request in a defined order. The exact sequence matters because an earlier status, access, or routing decision can prevent later rules from running.
For this concept, the practical workflow is:
- Inspect the HTTP method and speculative-request signals.
- Classify known crawlers, preview services, headless clients, and suspicious user agents.
- Apply blocking, access, and routing rules without treating automation as human engagement.
- Record eligible owned-link events with a human, bot, or blocked classification.
How to interpret the result
Read the result in the context of the configured link and the evidence available at request time. Browser signals, network location, cookies, referrers, and user agents are useful but imperfect.
Compare like with like: use the same date range, traffic filters, link ownership, and campaign definition. A change in classification or routing can change a report even when audience demand has not changed.
Deterministic example
The values below are example data, shown so every total can be checked from the visible rows.
Human click compared with Bot click
How DrutoLink handles this
DrutoLink separates detected bots from normal redirected traffic for account-owned links. Detected bots do not consume a configured human-click cap and do not receive the normal visitor cookie.
Detection is heuristic. The product reports the classification it can support from request signals; it does not claim perfect knowledge of whether a person was behind every client.
Limitations to keep in mind
- A sophisticated bot can resemble a browser, while privacy tools can remove signals from a real visitor.
- A social preview may be useful operational traffic, but it is not evidence that somebody read the destination.
- Guest links redirect without collecting analytics, visitor identifiers, or counters.
Frequently asked questions
Do bot clicks count toward a link click limit?
Detected bot and speculative requests do not consume DrutoLink human-click limits. The limit is intended for qualifying human redirects.
Why do social apps open my short link?
Messaging and social platforms commonly fetch links to create a title, description, and image preview before a person opens the post.
Can bot detection be completely accurate?
No. Classification relies on request signals and known patterns, so it should be treated as a useful estimate rather than proof of identity.