Citation Scans - CiteMetrix

Citation Scans

How CiteMetrix queries AI platforms on your behalf, what gets stored, and how to control scan frequency.

A citation scan is the unit of work behind everything CiteMetrix shows you. Each scan asks one of your configured queries to one of your configured AI platforms, captures the response, parses it for brand mentions and citations, and stores the result. Roll those results up over a 30-day window and you get the Mention Score component of your ModelScore. Filter to a single platform and you get that platform’s view of your brand. Diff against your brand facts and you get hallucination reports.

This article explains how scans actually run.

What gets scanned, and how often

For each AI platform you have an API key configured for, CiteMetrix runs every query in your list against that platform on a regular cadence. Scans are unlimited — there’s no monthly cap, so you can monitor as often as you want. What your plan sets is how many queries you monitor per domain (10 on Solo up to 200 on Enterprise, or a shared pool on Agency plans), not how often they run.

A “scan” means one query × one platform × one execution. So if you monitor 20 queries across 5 platforms, one complete sweep is 100 scans. CiteMetrix runs sweeps on a schedule, and you can trigger extra ones on demand; a high daily safety cap runs in the background purely to stop a runaway loop, set well above normal use.

CiteMetrix paces scans automatically — it doesn’t fire everything at once and then go silent. The scheduler distributes scans across the day so your data freshness is consistent, not spiky.

The three-lane cron architecture

Behind the scenes, CiteMetrix runs three independent cron lanes so that a slow operation in one category doesn’t block a fast one in another:

If something goes wrong in one lane (a slow API response, a stuck job), the other lanes keep running. This is the kind of detail you don’t normally need to think about — but if you ever wonder why your competitor data is a few minutes behind your citation data, this is why.

What CiteMetrix stores per scan

For every scan, the following gets captured to the database:

This is what powers the dashboard’s drill-down: you can click any data point and see the actual scan that produced it. There’s no hidden math — the numbers come from rows in your database.

Forcing a fresh scan

Sometimes you want to bypass the schedule and run a scan right now — typically when:

From the dashboard, click Run Scan in the top-right. A confirmation modal will tell you how many keywords and platforms will be scanned, and the estimated total API call count. The results land in the database the same way scheduled scans do — the only difference is you triggered it manually.

Force-rescans count against your daily quota.

A note on AI cache behavior: Even after you publish new content, AI platforms don’t immediately know about it. Most platforms refresh their training or retrieval data on schedules ranging from days to months. A force-rescan tomorrow will likely return similar results to today. CiteMetrix can show you when that data finally shifts; it can’t make the shift happen faster.

Scan failures

Scans can fail for a few reasons:

CiteMetrix retries failed scans automatically with exponential backoff. If a scan fails three times in a row, it’s logged as a permanent failure and you’ll get a notification (email, push if you have the PWA, or both depending on settings). The dashboard’s Alerts feed shows recent scan failures with the underlying error so you can diagnose API key problems quickly.

Scan history

Every scan you’ve ever run is preserved indefinitely (subject to data retention policy — see your Account Settings). The dashboard shows the most recent results by default, but you can navigate to any historical date to see what AI was saying about you that day. Useful for:

What scans don’t do

A few things people often expect citation scans to do that they don’t:

Next steps