When will redirect.pizza recheck a destination?

Enabled destinations are checked hourly. The customer can also start a recheck from the redirect details after addressing a failure.

How do I prove a request came from redirect.pizza?

Validate the `Signature` and `Signature-Input` headers using the public HTTP message-signature directory. The user-agent string is useful for matching but can be copied.

Will redirect.pizza honor a robots.txt disallow?

The operator does not promise that behavior, and the supplied Cloudflare data says the monitor does not follow robots.txt. Use a server or edge rule for enforcement.

Does this monitor contribute to AI search or training?

No such purpose is documented. It checks whether a redirect destination is reachable and does not build an AI index or training corpus.

Redirect pizza destination monitor Bot Guide

What is Redirect pizza destination monitor?

A redirect can return the right location while sending visitors to a dead page. redirect.pizza's destination monitor checks that final target for customers who enable the feature, separately from the service that delivers the redirect itself.

Enabled destinations are requested every hour. A failed target appears as broken in the redirects overview and can be included in the customer's summary email. After repairing the page, the redirect owner can request another check from the redirect details.

The full user agent is Mozilla/5.0 (compatible; redirect.pizza/1.0; +https://redirect.pizza/destination-monitor). Every outgoing check also carries Signature and Signature-Input headers under the HTTP Message Signatures standard. redirect.pizza publishes the verification material at https://redirect.pizza/.well-known/http-message-signatures-directory.

This monitor answers a narrow reachability question about a configured destination. It does not index links from that page, and no AI search or model-training use is documented. Blocking the request can give the redirect owner a broken-destination warning without reducing the page's exposure to AI systems.

Not relevant for AI search

Is Redirect pizza destination monitor relevant for AI search?

No. Redirect pizza destination monitor is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

Redirect pizza destination monitor 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 Redirect pizza destination monitor

For destinations tied to redirects your organization owns, verify the signature and allow the check to the public target. Disable destination monitoring in redirect.pizza when the check is no longer wanted. That avoids deliberately making a healthy endpoint fail its hourly test.

The stable product token supports this preference:

User-agent: redirect.pizza
Disallow: /

The operator documents the user agent for allowlisting, not robots compliance, and the supplied Cloudflare record marks compliance as false. Enforce a denial at the edge or origin if necessary. Expect that denial to appear as a broken destination to the redirect owner.

Examples

An old product domain redirects to a support article. When that article starts returning an error, the hourly destination check marks the redirect as broken even though the first redirect response still works.
A site owner receives an allowlist request for `redirect.pizza/1.0`. They validate the message signature with the published directory instead of trusting the header text.

Frequently asked questions about Redirect pizza destination monitor

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

No. redirect.pizza serves the redirect separately. The monitor requests the configured target to see whether visitors will arrive at a reachable destination.