Built and fact-checked by the DocNectar team — see our editorial standards
Key Features
Instant Calculation
Get accurate results in real time with our optimized algorithm.
Mobile Friendly
Fully responsive design. Works on all devices & screen sizes.
Privacy Focused
Your data stays on your device. We don't store any inputs.
100% Free
No hidden costs. This tool is completely free forever.
A honeypot link is a real, legitimate anti-scraper technique: a link that's disallowed in robots.txt and hidden from real visitors with CSS, but still present in the page's HTML. Any request to it is a strong signal of a bot that ignores robots.txt — safe to flag or block.
How it works
A random (or custom) trap path is generated along with matching CSS to hide the link from real visitors, and a robots.txt Disallow rule for that exact path. A compliant crawler reads robots.txt first and never requests a disallowed path; a non-compliant scraper that blindly follows every link in the raw HTML will hit it regardless.
- Enter trap path (optional — leave blank to auto-generate a random one).
- Enter cSS hiding method.
- Click Calculate to see your results.
Examples
Identifying a non-compliant scraper
Any server log entry for the generated trap path is a reliable signal — a real visitor or a well-behaved crawler (Googlebot, Bingbot) would never see or follow that link at all.
Who should use it
- Identifying scrapers and bots that ignore robots.txt on a content-heavy site.
- Building a blocklist of non-compliant automated visitors.
Industry applications
- Web security and anti-scraping defenses
- Content protection for publishers and SaaS platforms
Advantages
- Combines both halves needed for the technique to work — the hidden link AND the matching robots.txt rule.
- Marked nofollow and aria-hidden so it doesn't affect SEO or accessibility for real users and compliant crawlers.
Limitations
- Only catches bots that don't respect robots.txt and do blindly follow raw HTML links — sophisticated scrapers may avoid CSS-hidden links entirely.
Common mistakes to avoid
- Forgetting to actually add the generated Disallow rule to your live robots.txt file — without it, well-behaved crawlers have no reason to avoid the link.
- Placing the trap link somewhere a real user could plausibly tab or click into it despite the CSS hiding — test with keyboard navigation if using it on a real site.
Best practices
- Regenerate a fresh random trap path periodically, since a known/public path could eventually be recognized and avoided by sophisticated scrapers.
- Combine hits on this trap with other signals (request rate, user-agent, known bad IP ranges) rather than blocking on a single hit alone.
Tips
- Pair this with the Disavow File Generator and general SEO tools if you're also managing how search engines treat your site more broadly.