Which HTTP method does a Hydrozen monitor use?

The default is GET. Hydrozen lets the customer customize the request and the response expected from the target.

How can I recognize Hydrozen traffic?

The operator documents `Hydrozen.io/1.0` and provides dynamic source-address lists in JSON and CSV formats. Check both when investigating a claimed monitor request.

Is Hydrozen's robots.txt compliance known?

No operator statement was found. The record includes a positive flag, but Hydrozen's public request documentation does not explain whether a monitor reads or obeys robots.txt.

Will blocking Hydrozen stop AI systems from using my page?

No. Hydrozen's documented role is availability monitoring. A block affects the check result, not AI indexing, citations, or model training.

Hydrozen: What It Is & How to Handle It

What is Hydrozen?

Hydrozen visits a web address because one of its customers configured an availability monitor for that target. Website and API checks make HTTP requests, while the service's server, port, heartbeat, domain, and certificate features may use other request patterns or no page request at all.

An HTTP monitor sends GET by default. The customer can change the request and define the response that should count as healthy. A normal monitor therefore returns to the configured endpoint on a schedule instead of following links into the rest of the site.

Hydrozen documents Hydrozen.io/1.0 as the user agent for monitor access. It also maintains downloadable JSON and CSV lists of source addresses. The operator calls those lists dynamic and asks customers who allowlist the service to refresh every address rather than treating an old copy as permanent.

These requests measure service availability. Hydrozen does not document an AI search, content indexing, or model-training use for them. Rejecting a check can make the monitor report a failure, but it does not keep the target page out of generated answers.

Not relevant for AI search

Is Hydrozen relevant for AI search?

No. Hydrozen is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

Hydrozen runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle Hydrozen

Give an owned monitor a dedicated route with the smallest response it needs. If a firewall exception is necessary, automate it from Hydrozen's current address list and also check for Hydrozen.io/1.0. Pause or remove the monitor in Hydrozen instead of returning a deliberate error to an obsolete check.

The catalog token can express a crawl preference:

User-agent: Hydrozen
Disallow: /

Compliance is not documented. Hydrozen publishes the request identity and network list, but its monitor guide does not say that a direct uptime check retrieves robots.txt. Use monitor configuration or a server-side rule when the endpoint must be unavailable to the checker.

Examples

A team points Hydrozen at `/health/live`, keeps the default GET method, and defines the application's normal response as healthy. Logs then show the same route requested with `Hydrozen.io/1.0`.
An allowlist copied months earlier begins dropping checks. The operator reloads Hydrozen's current JSON address list and removes the stale entries rather than opening the endpoint to every source.

Frequently asked questions about Hydrozen

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Its uptime guide describes a configured URL or IP target, not link discovery. An HTTP monitor repeats the chosen endpoint and evaluates the resulting response.