Who This Topic Is For
Owners who publish crawler rules and want mail only when the live result changes.
Help
AI Access Watch
Daily crawler, llms.txt, and agent-path checks for one origin. $9 per month or $90 per year. The first day is quiet.
Prerequisites
Before You Start
Use this checklist to make sure the workflow guidance applies cleanly to your current task.
- You can sign in and open AI Access Watch.
- You know the public origin, not a path on a different host.
Expectations
What To Expect
Use this section to set the right outcome before you start the workflow.
A quiet first day
Open the site and read the crawler table. No email on day one means the baseline was stored.
Mail only for a new gap
A new mismatch, private URL, or open agent path that was not in the baseline is what sends mail.
The free check stays free
The public checker runs once. It does not start the subscription.
Website Watch stays separate
Website Watch is the daily pulse and weekly scan. AI Access Watch is the crawler comparison.
Playbook
Step-By-Step Guidance
Follow these steps in order for a reliable and repeatable outcome.
Open AI Access Watch and add the origin.
Choose monthly or yearly. The first origin opens checkout at $9 or $90.
Later origins confirm the prorated charge when the paid quantity is full.
Read the first table.
Existing mismatches are listed and not emailed. That quiet day is the expected start.
Paste a disallow group only if training crawlers were served.
The free result includes a copy box for training crawlers that still received the homepage. If none were served, the box says there is nothing to paste.
Set who should hear about a change.
Save alerts stores extra recipients. Set quiet hours if overnight mail should wait.
Mute a fingerprint you already accept.
Examples
Worked Examples
These scenarios show how the workflow looks in practice, including the result you should see.
GPTBot was already served
The first check records the served-despite-block row and stays quiet. Blocking GPTBot later does not email that old gap again.
A second origin needs a seat
The account already has one occupied origin. Adding another asks for the prorated charge and the new monthly or yearly total.
Cancel did not drop the seat today
Cancel on an unused origin keeps the seat until the period ends.
Operations
Operational Playbook
Use this long-form guidance to execute the workflow consistently across planning, implementation, and validation.
Who it is for
Use AI Access Watch when a site publishes robots.txt rules for AI crawlers and you want to know the day the server stops following them. It is a per-origin subscription, separate from Website Watch.
What you pay
The first origin is $9 per month or $90 per year. When every paid seat is occupied, the next origin asks you to confirm the prorated charge and the new total before quantity increases.
What day one does
The first successful check stores the mismatches, private URLs, and open agent paths it already sees. It does not email that list. Mail starts when a later day finds a fingerprint that was not in the baseline and is not muted.
What a mismatch means
A mismatch is a finding only when the control homepage loaded. The file says blocked and the page still came back, or the file says allowed and the server blocked that crawler. A blocked control fetch marks every row not comparable.
Who else gets mail
Save alerts stores up to five extra addresses. Quiet hours hold a check until the window ends. Mute one fingerprint when you accept that gap. Unmute from the same site page.
How cancel works
Pause keeps the seat and stops checks. Cancel site asks you to confirm. The paid seat drops at the end of the period. There is no mid-cycle refund, and you can reuse that seat until then.
Validation
Validation Checklist
Use this checklist to confirm the workflow was completed correctly.
- The first day stored a summary and sent no email.
- A later new fingerprint emailed, or waited for quiet hours.
- A muted fingerprint stayed out of new mail.
- A blocked control fetch was not emailed as a policy failure.
- An HTML llms.txt was not treated as a map.
- An HTML agent path was not treated as an open agent.
Troubleshooting
Common Problems And Fixes
If something does not match expectation, check these common failure modes first.
I expected mail on the first day
The first successful check is the baseline. Open the site summary. Email starts on a later new fingerprint.
Every row says not comparable
The control request was blocked or challenged. Those rows are not policy failures. Fix that path, then run the check again.
Checkout said the price does not match
AI Access Watch is $9 per month or $90 per year. An admin replaces the Stripe Price ID when the saved amount is different.
Navigate
Related Pages
Use these links to continue your workflow without losing context.
FAQ
AI Access Watch FAQs
Common questions for this topic.
The first successful check stores existing findings and does not email them. Later days email a fingerprint that is new and not muted.
Next Recommended Action
Continue to the best next page based on where you are in your workflow.