- The free scan checks one homepage in about 15 seconds and needs no account.
- No card is asked for during the 14-day trial, which includes the Agency allowance of 10 sites.
- Key pages come from your sitemap, with pricing, product, comparison and integration pages ranked ahead of blog posts.
- Critical changes and warnings reach Slack within minutes; every alert, minor ones included, stays in the dashboard feed.
- Log connectors are optional: daily monitoring works on every host without them.
What does the free scan check?
The free scan checks your homepage once, without an account, and gives it an AI Access Score out of 100. Type a domain at monitor.airanked.ai and the report is ready in about 15 seconds.
In that time Monitor works out what your robots.txt allows each of 18 AI agents, requests your homepage as seven agents from OpenAI, Anthropic and Perplexity, compares each answer with a normal browser request, and looks at the homepage the way a crawler that doesn't run JavaScript would: status code, noindex, words in the raw HTML, JSON-LD and llms.txt.
Each report gets its own link, which you can share with a developer or a client. Reports are kept for 60 days. Scanning the same domain again within 10 minutes returns the report you already have.
How do I start the free trial?
Go to the trial sign-up, enter your work email and you're in. It runs for 14 days, lets you add as many sites as the Agency plan allows (10, each with 100 key pages) and never asks for a card.
There's no password. A new account opens straight away, and the session lasts 30 days on that browser. Signing in again after that uses a one-time link sent by email, which works once and expires after 30 minutes. Email sending isn't switched on yet, so until it is, write to editors@airanked.ai from your account address and we'll get you back in the same day.
Running an agency or several brands? Add those sites during the trial. When it ends, Agency keeps all 10 monitored, while Pro covers only your oldest site and the others wait, paused; the billing guide covers how plans and downgrades work.
What happens when I add my site?
Type your domain on the dashboard, such as example.com. Monitor always checks the HTTPS version, follows redirects (so www and the bare domain both work) and refuses IP addresses, private hosts and custom ports.
- Site check. Monitor fetches robots.txt and llms.txt, requests your homepage as a browser and as the seven probe agents, and records what each one got back.
- Page discovery. It reads up to three sitemaps listed in your robots.txt plus
/sitemap.xmland/sitemap_index.xml, then ranks the URLs it finds. Your homepage is always first. - First page checks. The first few key pages are checked right away. The rest finish within the hour, and you'll see a "Monitoring started" message with the number of pages mapped.
- Baseline. These first results become the baseline. Alerts start from the next check, so day one shows what's already broken and day two onward shows what changed.
How do I choose which pages are monitored?
Open your site in the dashboard and go to Settings > Key pages. The box holds one URL per line. Add a line to monitor a page, delete a line to stop, then click Update pages. New pages are checked within the hour.
The automatic list favors the pages AI answers tend to quote for commercial questions: pricing, product, features, solutions, comparison and alternatives pages, integrations, customers, security and about pages. Blog, news, tag, category and author pages are pushed down. Sites with fewer than 100 URLs get all of them.
Two limits apply. Every URL has to be on the site you added (the www and bare host count as the same site), and a site's list is capped at 100 URLs. URLs on other domains are ignored.
Where do alerts go?
Every alert lands in the Alerts feed on your site's dashboard. To have alerts pushed to you, open Settings > Alerts and paste a Slack incoming webhook URL, which has to start with https://hooks.slack.com/. The same screen takes up to 10 email addresses separated by commas, starting with the one you signed up with. Alert emails aren't being sent yet, though: email delivery is marked Coming in the changelog, so use Slack for now.
Critical alerts and warnings go to Slack shortly after the check that caught them, usually within 10 minutes. If several things break at once, they arrive as one message, and a site that was just alerted waits 30 minutes before the next one so an outage doesn't flood the channel. Minor changes, such as an edited page title, aren't pushed; they wait in the dashboard feed. The alerts reference lists every alert and its severity.
Want a check sooner than tomorrow? Check now reruns the site checks and the next batch of key pages on demand, once every 10 minutes per site.
Should I connect my logs?
Connect logs if you want to see real AI visits: which agents come, which pages they request and which pages ChatGPT, Claude and Perplexity fetch while answering someone's question. Daily monitoring doesn't need it.
AI crawlers don't run JavaScript, so analytics tags never record them. The connector is a short snippet that runs where your site is served and reports only requests from AI agents. Pick the guide for your stack:
- Cloudflare: a Worker in front of any site whose DNS is proxied through your Cloudflare account.
- Vercel and Next.js: a middleware file.
- WordPress: a must-use plugin you upload once.
- Webflow: what works when your host doesn't expose logs.
For Express and other Node servers, the code and a curl test are in connecting logs.
What should I look at in the first week?
Start with the findings on your first check, because they're problems that exist today: a search agent blocked in robots.txt, a firewall that rejects one of the probe agents, a page set to noindex or a page whose copy only appears after JavaScript runs.
Then look at the Who can get in panel. It lists all 18 agents with a red "robots" or "firewall" label where something stops them. Training crawlers marked as blocked are often deliberate; search and user agents marked as blocked usually aren't.
By the end of the week your Alerts feed shows what changed since the baseline, and the dashboard sums up the score, the healthy page count and, with logs connected, the agents that visited and the pages AI assistants fetched for real users.
Frequently asked questions
Do I need a developer to set up AI Ranked Monitor?
No. Monitoring works from the outside, the way an AI crawler reaches your site, so you only type your domain. A developer is only useful for the optional log connector, which is a short snippet (Cloudflare, Next.js, WordPress or Node versions) that takes a few minutes to install.
How long does the first check take?
Adding a site runs the site-level checks straight away and checks the first few key pages in the same request. The rest of your key pages are checked within the hour. After that, every page is rechecked about once every 24 hours and compared with its previous result.
Which pages does Monitor pick as key pages?
It reads your sitemap and puts your homepage first, then pricing, product, features, comparison, alternatives, integrations and similar commercial pages, then shallow pages before deep ones. Blog, news, tag and author pages go last. You can replace the list with your own URLs at any time.
Can I monitor a staging site or a subdomain?
You can monitor any public domain or subdomain that answers on HTTPS, such as docs.example.com. Private addresses, IP addresses and custom ports are refused, and a site that requires a login or blocks all outside requests can't be checked from outside.
What happens when the trial ends?
Monitoring pauses and your data stays in the account. Nothing is charged, because the trial never asks for a card. Choose Pro (one site) or Agency (10 sites) on the billing page to resume checks on the same sites with the same history.