- The Agency plan costs $199 a month for 10 client sites and 100 key pages per client.
- Every site has its own alert recipients and Slack webhook, so each client's alerts go to the right channel.
- Critical changes and warnings reach each client's Slack channel within minutes; minor changes wait in that site's alert feed.
- The free scan needs no signup and produces a shareable report link for any domain.
- Every alert names the agent, the page and what changed, which gives the client's developers somewhere specific to look.
Who is the Agency plan for?
It's for agencies that are accountable for a client's visibility in AI search without owning the client's infrastructure. That usually means GEO and AEO agencies, SEO agencies that added AI search to their retainers, and web agencies that build and maintain marketing sites.
What these teams share is a gap in control. You write the content and recommend the fixes, while the client's developers, IT team or hosting provider change robots.txt, firewall rules and templates on their own schedule. When AI crawlers lose access, the content work stops paying off, and nobody tells you.
What problems does it solve for agencies?
It closes the window between a client-side change and you finding out about it.
- Changes you don't see. A security team turns on a bot setting at the CDN, a plugin update rewrites robots.txt, a redesign ships pages that render in the browser. None of it reaches your inbox.
- Slow signals. Without a direct check, the first sign is a drop in AI referrals or mentions weeks later, after the client has noticed it in a report and asked what happened.
- Vague diagnoses. "AI visibility is down" doesn't help a developer. "PerplexityBot gets a challenge page on the homepage since Tuesday" does.
- Manual checking doesn't scale. Testing robots.txt rules for 18 agents and 100 pages per site by hand across a roster isn't something anyone does every day.
What kinds of client changes does Monitor catch?
Three examples of the changes Monitor is built to catch. They're illustrations of how the alerts work, not client stories.
The CDN setting nobody mentioned
A client's IT team turns on stricter bot protection after a traffic spike. Browsers load the site normally. The next daily check requests the homepage as seven AI agents, two of them get a challenge page twice in a row, and the client's alert channel gets a critical alert naming both agents and the response they got. You forward it with a link to the relevant setting in our Cloudflare guide.
The redesign that emptied the pricing page
The client launches a new site. The pricing page now loads its plans from an API in the browser, and its raw HTML drops to a few dozen words. Monitor flags the page as needing JavaScript within a day of launch, while the client is still celebrating, and the fix is a rendering change rather than a recovery project.
The robots.txt pasted from a forum
A developer adds a block list meant for scrapers and training crawlers. It also disallows OAI-SearchBot and Claude-SearchBot. The site check sees the change, compares which agents lost access, and raises a critical alert that lists the search agents now blocked, separately from the training crawlers the client meant to block.
Which Monitor features matter most for agencies?
| Feature | Why it matters for an agency |
|---|---|
| 10 sites on one plan | A roster of clients on one account, each with its own score and history |
| Alert recipients and Slack per site | Each client's alerts go to that client's team and channel |
| Weekly report per site | A Monday email summary of the score, healthy key pages and the week's changes, starting when email delivery goes live |
| Editable key pages | Monitor the pages your strategy targets, not only what the sitemap ranks first |
| Score breakdown | One number per client, with the points lost in each part shown |
| Log connectors | Proof of which pages ChatGPT, Claude and Perplexity actually fetch |
The AI Access Score works as a shared reference point with clients: it's capped at 60 while a critical issue is open, so a client can see at a glance whether something urgent is wrong. The alerts reference explains each alert in language you can paste into a ticket.
How do I set up a client roster?
- Start the trial and add your first client's domain. Monitor reads the sitemap, picks the key pages and checks the first ones straight away.
- Review the key pages. Replace the list with the pages your strategy targets: the comparison, pricing, integration and solution pages you want cited.
- Route the alerts. In the site's settings, add your team's address and, if the client wants them, the client's contacts, plus a Slack webhook for the shared channel.
- Add the other clients during the trial, up to 10 sites, then choose Agency on the billing page before it ends.
- Connect logs where you can. Clients on Cloudflare, Next.js, WordPress or Node can add a connector in minutes; the log connector docs have each snippet. Clients without one still get full daily monitoring.
Can I use the free scan with prospects?
Yes. The free scan checks any domain's homepage without an account and creates a report link you can share, kept for 60 days. Running it on a prospect's site before a call gives you a concrete starting point: which AI agents their robots.txt and firewall let through, whether the homepage carries noindex or needs JavaScript, and whether they publish JSON-LD and llms.txt.
Treat it as a snapshot of one page at one moment. The point of monitoring is everything that changes after the snapshot, which is what you'd be watching once they're a client. Plans and limits are on the pricing section.
Frequently asked questions
How many client sites does the Agency plan cover?
Ten sites for $199 a month, and each can have 100 key pages monitored. Each site has its own score, alerts, key page list, alert recipients and Slack webhook. If you need more than 10, email editors@airanked.ai and tell us how many sites you manage.
Can I send a client's alerts to the client directly?
Yes. Each site posts to its own Slack incoming webhook, so a channel shared with the client's marketing or web lead gets that client's alerts and nobody else's. Each site also holds up to 10 alert email addresses, which start receiving alerts once email delivery is switched on.
Can I white-label the reports for clients?
Not today. Slack alerts and the dashboard carry the AI Ranked Monitor name, and email alerts and the weekly report will too once email delivery is live. The weekly report, which starts with email delivery, is written to be forwarded as is: it covers the score, how many key pages are healthy, critical issues that week and, with logs connected, which AI agents visited.
Does Monitor replace a prompt or rank tracking tool?
No, and it isn't meant to. Prompt trackers report whether AI answers mention a brand. Monitor checks whether AI crawlers can actually fetch and read the pages those answers would cite. Agencies running GEO programs often need both: one measures the outcome, the other catches the access problems that quietly undo the work.
Can I try it before moving all my clients over?
Yes. The 14-day trial has Agency limits, up to 10 sites, and asks for no card, so you can run the full workflow on several clients at once. Pick a client with recent deploys or CDN changes and you'll likely have findings to discuss by the end of the first week.