Crawler information

eewabot

eewabot is the automated web crawler operated by eewa.io. This page explains what it does, how it identifies itself, how it honours robots.txt, and how to reach a human if you have questions about its traffic on your site.

What the crawler does

eewabot visits publicly accessible web pages and reads their content. It requests pages the way an ordinary browser does — over HTTP(S), following links it finds — and stores the responses for processing on our side.

How to identify it

User agent
Mozilla/5.0 (compatible; eewabot/1.0; +https://bot.eewa.io)
robots.txt token
eewabot
Information page
https://bot.eewa.io (this page)

Any traffic claiming to be eewabot from an unrelated source is not ours. If you see requests using our user agent that you believe are being spoofed, please tell us — we want to know.

How it respects robots.txt

eewabot follows the Robots Exclusion Protocol (RFC 9309). In practice:

Blocking the crawler

You are always free to block us. To stop eewabot from crawling your site entirely, add this to the robots.txt at the root of your domain:

User-agent: eewabot
Disallow: /

To allow most of your site but keep certain paths out:

User-agent: eewabot
Disallow: /private/
Disallow: /checkout/
Crawl-delay: 10

The change applies as soon as the bot re-reads your robots.txt. If you would rather not wait, or if you want us to stop immediately and permanently, email us and we will add your domain to our exclusion list by hand.

Being a good neighbour

The crawler is rate-limited per host and spreads its requests out over time so that it does not put meaningful load on a site. It backs off automatically when a server responds slowly or returns 429 or 5xx status codes, and it caches content to avoid re-requesting pages that have not changed.

If eewabot is nonetheless causing problems for your infrastructure, get in touch and we will throttle or stop it.

Contact us

Questions, complaints, block requests, or reports of suspected spoofing — one address, read by a person:

info@eewa.io

Including the affected domain and, if you have them, a few example log lines with timestamps helps us track down what happened faster.