LatigidAEOBot

LatigidAEOBot reads a small number of pages from a website so we can report how that site is represented in AI-generated answers. It is operated by Latigid, a digital consultancy based in Portugal.

If you are here because you saw this bot in your logs: it fetched at most eight pages of your site at roughly one request per second, and it did not submit forms, log in, or follow links outside your domain. It obeys robots.txt. Instructions for blocking it are at the bottom of this page.

Identity

User-agent	`LatigidAEOBot/1.0 (+https://latigid.dev/bot)`
robots.txt token	`LatigidAEOBot`
Source IP	`37.120.184.202` (IPv4, single address)
Reverse DNS	`server.latigid.dev` (forward-confirmed, see below)
Operator	Latigid — latigid.pt
Contact	hello@latigid.pt

Verifying that a request is really us

Do not trust the user-agent string on its own — anyone can send it. Verify with forward-confirmed reverse DNS, the same method Google and OpenAI document for their crawlers. Look up the PTR record for the requesting IP, then resolve the hostname you get back and check that it returns the original IP:

$ dig +short -x 37.120.184.202
server.latigid.dev.

$ dig +short A server.latigid.dev
37.120.184.202

If both halves agree and the hostname ends in .latigid.dev, the request is ours. If they do not agree, it is not, regardless of what the user-agent claims.

What it requests

Up to eight HTML pages per audit, starting at the homepage, at about one request per second.
Your robots.txt, and your sitemap when one is declared.
The homepage a second time for each AI crawler identity we test, to check whether your server answers them differently from a browser. These requests carry the other crawler's user-agent and come from the IP above.

It does not execute purchases, submit forms, authenticate, or crawl areas disallowed in robots.txt. It runs only when a person asks for a report on a given domain, so it is not a continuous crawl.

Allowing it

If your site is behind a WAF or bot-management service, LatigidAEOBot is not on any vendor's verified-bot list and will usually be challenged by default. To let it through, allowlist the IP above, or add a rule matching the user-agent together with the reverse-DNS check.

Being challenged is not a problem with your site. But note that the same default rules often challenge ClaudeBot, OAI-SearchBot and PerplexityBot while allowing GPTBot — and that is worth knowing, because those crawlers are how several AI assistants read the open web.

Blocking it

Add this to robots.txt and we will stop:

User-agent: LatigidAEOBot
Disallow: /

We re-read robots.txt on every audit, so the change takes effect immediately. You can also block the IP outright, or email hello@latigid.pt and we will exclude your domain at our end.