Who This Topic Is For
Site owners who publish crawler rules and want a daily answer when the server does not follow them.
Documentation
AI Access Watch
Daily comparison of published crawler rules and the live homepage. $9 per origin per month or $90 per year.
Prerequisites
Before You Start
Use this checklist to make sure the workflow guidance applies cleanly to your current task.
- You can sign in.
- You know the public origin, such as https://example.com.
- An admin has saved the AI Access Watch Stripe Price IDs before checkout can open.
Expectations
What To Expect
Use this section to set the right outcome before you start the workflow.
One origin, one seat
AI Access Watch is $9 per origin per month or $90 per year. It does not replace Website Watch, Mail Watch, or the robots and sitemap checker.
The first check is quiet
The first successful day stores the mismatches, private URLs, and open agent paths that already exist and does not email them. Later days email only fingerprints that are new, unless you muted that fingerprint or quiet hours are active.
Playbook
Step-By-Step Guidance
Follow these steps in order for a reliable and repeatable outcome.
Open AI Access from the dashboard.
Sign in and go to /watch/ai-access. Website Watch stays at /watch.
Add the origin.
Enter a name, the site URL, and monthly or yearly billing. The first origin opens Stripe Checkout at $9 or $90.
A later origin on a full seat asks you to confirm the prorated charge and the new total before quantity increases.
Read the crawler table and tune alerts.
Open the site.
The table lists each crawler, the robots. txt decision, and the live fetch.
Extra recipients takes up to five email addresses. Pause keeps the seat.
Cancel site asks you to confirm. The paid seat drops at period end.
There is no mid-cycle refund.
Examples
Worked Examples
These scenarios show how the workflow looks in practice, including the result you should see.
GPTBot was already served
robots.txt disallows GPTBot, and the first live fetch still returns the homepage. The row is stored and the first day stays quiet.
The control request was challenged
The homepage returns a challenge to Vulnify-Tooling as well as to the crawlers. Every crawler row is not comparable.
Cancel one unused origin
Two origins are paid and one is still in use. Cancel site asks you to confirm. The unused seat stays available until the period ends.
Validation
Validation Checklist
Use this checklist to confirm the workflow was completed correctly.
- The site is one origin, not a path on a different host.
- The first day did not email existing mismatches.
- A new mismatch, private URL, or open agent path emails after the baseline, unless it is muted or inside quiet hours.
- A blocked control fetch is marked not comparable and is not a policy failure.
- Extra recipients were saved with Save alerts. The cap is five addresses.
- Cancel drops the unused seat at period end. There is no mid-cycle refund.
Troubleshooting
Common Problems And Fixes
If something does not match expectation, check these common failure modes first.
Checkout says billing is not configured
The $9 or $90 Stripe Price ID is empty or the amount does not match. An admin saves it under Website Watch settings before checkout can succeed.
Every crawler says not comparable
The control fetch was blocked or challenged. That is not a robots.txt mismatch. Fix the path that blocks the checker, then run the check again.
Cancel looked like an immediate refund
Cancel site drops the unused seat at period end. The local seat stays usable until then. There is no mid-cycle refund.
Navigate
Related Pages
Use these links to continue your workflow without losing context.
AI Access Watch
Open AI Access Watch to continue this workflow.
Free AI Access Checker
Open Free AI Access Checker to continue this workflow.
Documentation: Website Watch
Open Documentation: Website Watch to continue this workflow.
Help: AI Access Watch
Open Help: AI Access Watch to continue this workflow.
FAQ
AI Access Watch FAQs
Common questions for this topic.
No. A high finding requires a JSON tool list with no login. An HTML page is not an open agent. The check never calls a tool.
Next Recommended Action
Continue to the best next page based on where you are in your workflow.