Crawler Watch · one public site

Know when a deploy changes indexability.

A deploy can add noindex, move a canonical, change robots policy, or alter what AI search crawlers receive. Crawler Watch checks from outside your stack every 15 minutes, confirms a change twice, then emails the evidence.

15-minute checks · 30-minute confirmation

One site. $9 each month.

Enter the public domain during Stripe checkout. Monitoring starts automatically, and the baseline goes to the checkout email—normally within 15 minutes.

  • Homepage status, robots meta, X-Robots-Tag, and canonical target
  • OpenAI, Anthropic, Perplexity, and Google crawler policy
  • External homepage responses using major search-crawler user agents
  • robots.txt, sitemap.xml, and llms.txt state
  • Confirmed change and recovery emails, without duplicate alerts
The alert contract

Changes that can alter indexability—not a stream of green checks.

01

Build a baseline

The first run records homepage status, index directives, canonical, crawler rules, public response classes, and discovery-file state. You receive the exact starting evidence.

02

Confirm the change

A changed state must appear in two consecutive 15-minute checks before an email is sent. One transient request does not become an alert.

03

Suppress repeats

The same state is sent once. A recovery is a new state and gets its own message, so the inbox reflects decisions rather than polling.

What the monitor can—and cannot—tell you.

Measured

Homepage HTTP status, returned robots meta, X-Robots-Tag, canonical target, public robots policy for eight current tokens, synthetic crawler response status, and default sitemap and llms.txt paths.

Not proved

Provider identity, IP allowlisting, indexing, citation, ranking, recommendation, referral traffic, or complete uptime. A synthetic user-agent request is evidence from one external path, not a provider crawl.

Homepage checks inspect returned HTML and headers without running browser JavaScript. Crawler names and provider behavior change. ActableSite reports the evidence it can observe—never an “AI visibility” score.

Inspect before subscribing

Run today’s crawler policy check free.

The public checker shows the current robots.txt decision for all eight tokens. Use it to see the evidence format before deciding whether ongoing monitoring is useful.

Check one site now

Need a portfolio dashboard, real crawler logs, general page-change detection, or edge enforcement instead? Compare current monitoring approaches by what they actually watch.

Before you subscribe

Do I install anything?

No. Enter one public website during Stripe checkout. The monitor runs externally and uses the checkout email for activation and change alerts.

Can I change the domain?

Cancel through Stripe, then start a new subscription with the replacement domain. The $9 plan covers one public site at a time; it is not an agency portfolio plan.

What happens after cancellation?

Stripe keeps access active through the paid period, then the domain is removed from active checks. Cancel before renewal to avoid the next charge.

Is there an uptime guarantee?

No. Checks normally run every 15 minutes, but this is a change-detection utility without a service-level agreement. It should complement—not replace—security or uptime monitoring.