Link previews, prefetch and click counts

Definition in plain language

Link previews and prefetches are automated or speculative requests made before a person deliberately navigates to a destination.

Why link previews, prefetch and click counts matters

Messaging apps fetch page metadata for previews, security products inspect links, and browsers may preload likely destinations. Counting those requests as deliberate visits inflates engagement and can prematurely exhaust usage limits.

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:

1. Inspect HTTP method, purpose headers, and known preview or crawler signals.
2. Serve a safe response where appropriate without treating the request as engagement.
3. Exclude speculative requests from normal capture and human-click counters.
4. Record separately only when the product has a meaningful classified event.

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.

How DrutoLink handles this

DrutoLink excludes recognized speculative requests from normal click capture and human-click limits. Bot traffic can be reported separately for owned links when it reaches the classified analytics path.

HEAD requests and prefetch-like probes should not be interpreted as page reads, even when they touch the short URL.

Limitations to keep in mind

• Clients do not use one universal header, so speculative detection is necessarily heuristic.
• A preview request can be followed by a real click; these are separate events.
• Blocking all automation can break useful previews and safety checks.

Frequently asked questions