# LantadBot: the scanner crawler policy

> What LantadBot fetches, how it identifies itself, and how to block it. It never spoofs another crawler's user agent on the baseline fetch.

- Canonical page: https://lantad.co/bot
- This file: https://lantad.co/bot.md

## Key facts

- **User agent:** LantadBot/1.0 (+https://lantad.co/bot)
- **Spoofing:** Never on the baseline fetch. It identifies itself honestly on every request.
- **Scope:** Only URLs a person submits for a scan, plus that origin's robots.txt.
- **How to block it:** A robots.txt disallow for LantadBot. It is obeyed.

## Why the honest user agent matters here

A tool that measured crawler access while disguising itself would be reporting on a request nobody else can reproduce.

The per-crawler probes DO send the published user agent of the crawler being tested, because that is the only way to observe user-agent enforcement. The report distinguishes that probe from the baseline fetch rather than blurring the two.

## Related

- https://lantad.co/methodology (markdown: https://lantad.co/methodology.md)
- https://lantad.co/tools/robots-txt-tester (markdown: https://lantad.co/tools/robots-txt-tester.md)
- https://lantad.co/privacy (markdown: https://lantad.co/privacy.md)

---

Lantad measures whether AI crawlers can actually read a page: it fetches as a non-rendering
crawler, renders as a browser, and reports the gap. Free scan, one URL, no signup.

Method and weights: https://lantad.co/methodology | All pages as markdown: https://lantad.co/md | Crawler policy: https://lantad.co/bot