Available
Link safety and bot filtering
Cleaner analytics and safer destinations by default.
Interactive product demo
Link safety and bot filtering
What happens
DrutoLink scans destinations, separates likely bot traffic, protects health checks from internal-network access, and avoids counting browser prefetches as real visitors. Short-link safety separates known automated requests, reviews destinations, and avoids treating speculative browser requests as human engagement. No automated check can guarantee that every destination remains safe forever.
- Safe Browsing checks on new and edited destinations
- Bot, blocked, and dead traffic reported separately
- Privacy-aware IP hashing and speculative-request filtering
What this feature does
Cleaner analytics and safer destinations by default.
DrutoLink scans destinations, separates likely bot traffic, protects health checks from internal-network access, and avoids counting browser prefetches as real visitors. Short-link safety separates known automated requests, reviews destinations, and avoids treating speculative browser requests as human engagement. No automated check can guarantee that every destination remains safe forever.
Use this capability when you need more control than a basic short URL provides.
Implementation and operating details
The workflow stays attached to the short link, so you can manage the destination and its rules without replacing the URL already in circulation.
- Safe Browsing checks on new and edited destinations
- Bot, blocked, and dead traffic reported separately
- Privacy-aware IP hashing and speculative-request filtering
How it works
Scan the destination
New and edited destinations enter a safety check before being trusted for normal traffic.
Protect the redirect
Rate limits, unknown-link shielding, and guarded routing reduce abuse without breaking valid links.
Keep reports cleaner
Likely bots, blocked requests, and dead traffic are reported separately from human engagement.
Operational guide
How DrutoLink processes it
Destination validation, network protections, request classification, and link state checks work together before normal traffic is served. Flagged or disabled links can be prevented from redirecting.
Understand the signals, processing order, fallback, and checks that matter before you rely on this capability.
Required inputs and signals
- Configuration input
- Safety checks run around link creation, destination changes, and redirect requests.
- Signals and connected controls
- Health checks, analytics filtering, password links, and smart links
Decision, fallback, and common mistakes
No automated scan guarantees that a destination remains safe forever. Bot and speculative-request detection is heuristic and should be reviewed alongside the underlying event context.
This capability is available now. Results still depend on visitor signals, destination availability, campaign setup, and the quality of the traffic being measured.
Practical setup checklist
- 01 Scan the destination. New and edited destinations enter a safety check before being trusted for normal traffic.
- 02 Protect the redirect. Rate limits, unknown-link shielding, and guarded routing reduce abuse without breaking valid links.
- 03 Keep reports cleaner. Likely bots, blocked requests, and dead traffic are reported separately from human engagement.
Why teams use it
Measurement and reporting
Review click activity and the relevant link, campaign, audience, or variant breakdowns in DrutoLink analytics. Use consistent UTM parameters when results must also be reconciled with destination-side analytics.
What you can evaluate
Reduce exposure to malicious destinations · Avoid treating prefetches as real visitors · Keep bot and blocked traffic visible but separate
How to interpret results
A redirect click confirms that the link served a destination. It does not by itself prove a signup, purchase, or qualified visit. Compare the same date range and traffic definition before making a decision.
Current status and limitations
This capability is available now. Results still depend on visitor signals, destination availability, campaign setup, and the quality of the traffic being measured.
Important boundary
Use the default destination and documented fallback behavior for cases where a rule cannot be evaluated. Test important links from representative devices and networks before broad distribution.
Does DrutoLink store visitor IP addresses? Analytics use daily-salted hashes rather than storing plain visitor IP addresses.
Best use cases
Practical examples
These are common situations where the capability can reduce manual link changes or make reporting easier to understand.
- 01 Public campaigns exposed to automated scanners
- 02 Teams that need cleaner human-engagement metrics
- 03 Privacy-conscious link measurement
- 04 Reduce misleading click counts from previews and bots while preventing known unsafe destinations from serving normal traffic.
Is this the right fit?
Choose this feature when
You need one controlled short URL, a repeatable operating workflow, and reporting that stays connected to the link. Reduce exposure to malicious destinations
Use another approach when
Your requirement depends on a capability marked partial or planned, requires identity-level certainty, or needs conversion attribution that must be measured in the destination product.
Build the complete workflow
Combine this feature with the controls that affect how traffic is routed, organized, and measured.
Terms used on this page
Frequently asked questions
Does DrutoLink store visitor IP addresses?
Analytics use daily-salted hashes rather than storing plain visitor IP addresses.
Are link previews counted as clicks?
Known speculative requests such as browser prefetches, prerenders, and HEAD checks are detected and not counted as real clicks.
What happens if a destination is flagged?
Unsafe links can be flagged and prevented from serving normal traffic; editing the destination triggers a fresh safety review.
Keep exploring
Smart link controls
One short link with rules for timing, limits, redirects, and access.
Geo-targeting
Send visitors to the right destination, wherever they are.
Device targeting
Send every device to the destination built for it.
A/B testing
Let data pick your best destination.
UTM builder
Clean tracking parameters, every time.
Campaign management
Organize related links and measure the campaign as a whole.
Real-time analytics
Know what every click did.
Live click activity
Watch meaningful clicks arrive as they happen.
Raw click viewer
Inspect the click behind the aggregate.
Link health monitoring
More comingCatch dead links before your audience does.
Password-protected links
Add a simple access gate before the destination.
QR codes
More comingFrom link to scan in one click.
Team workspaces
More comingShip links together.
Custom domains
Short links that carry your brand.
Bulk operations
Coming soonCSV import and export for high-volume workflows.
REST API
Coming soonA supported integration API is on the roadmap.
Webhooks
Coming soonEvent delivery for your stack is planned.
Link-in-bio pages
One link, your whole world.
Conversion tracking
Coming soonKnow which links make money.