FindmetryBot
A bounded crawler with a public identity.
FindmetryBot collects public website evidence for Findmetry technical diagnostics. This page explains how it identifies itself, what it may request and how to ask Findmetry not to crawl your domain again.
Crawler specification
What site operators should know.
The static crawler is designed to be bounded, policy-aware and identifiable. It is not intended to bypass access controls or conceal its requests.
- Static crawler user agent
FindmetryBot/0.1- robots.txt
- Findmetry checks robots policy before a bounded audit and fails closed when required access state cannot be established.
- Request pacing
- Runs use explicit request, page, runtime and related safety limits rather than unrestricted crawling.
- Rendered evidence
- When browser evidence is needed, Findmetry may use a normal Chromium browser to render a bounded set of pages. Rendering can load the ordinary page assets and subresources that a browser normally requests.
- Search-engine impersonation
- Findmetry does not impersonate Googlebot in production.
- Interaction
- Rendered checks may use bounded, non-destructive interaction to reveal public page states. Findmetry does not submit purchases, booking actions, login forms or other destructive/private workflows as part of the public diagnostic.
- Private areas
- Login-protected, account-only and other non-public customer areas are outside the normal public-site diagnostic.
- Crawl suppression
- Site operators can request future domain suppression by emailing [email protected]. Verified requests are recorded before future audit preflight.
A visibility note
Rendered visits can look like browser visits.
The static crawler identifies as FindmetryBot. Browser-rendered evidence uses normal Chromium and executes page JavaScript, so those bounded visits can appear in analytics or server logs as ordinary browser traffic from the executing network.
This is a technical consequence of browser rendering, not an attempt to evade site operators.
Site operator contact
Questions or concerns?
Email the domain, the approximate time of the request and what you observed. Do not send credentials or private access material.