Monitoring, History, and Notifications

Monitoring frequency

Monitoring frequency depends on the active plan. Free projects run on a weekly schedule; eligible paid projects can run daily. The project page shows whether automatic monitoring is active, paused, or not configured.

Manual reruns, model coverage, project count, prompt count, history, and export access also depend on plan entitlements.

Keep the schedule meaningful

Scheduled runs are most valuable when monitoring conditions stay stable:

• approved prompt wording;
• country and prompt language;
• brand aliases and direct competitors;
• configured logical models.

After a material change, record it and establish a new baseline when needed.

Review history

Use project history to open previous runs and compare valid samples. When a metric changes:

1. check the number of completed responses;
2. identify which prompts changed;
3. read the old and new answers;
4. review model routes and citation availability;
5. connect the movement to a documented website or positioning change only when evidence supports it.

Notifications

Notification settings can control monitoring emails such as completed checks, weekly summaries, visibility declines, and failures. Choose the events that require action and set a decline threshold that is meaningful for the sample size.

A failure alert indicates that monitoring needs attention; it is not evidence that brand visibility dropped.

Exports

Eligible paid plans can export run data as CSV. Exports are useful for audits, analysis, and client deliverables. Check that the selected run is complete and retain the model, prompt, country, language, and timestamp context.

Pause or stop monitoring

Pausing a schedule stops future automatic runs but does not necessarily delete existing history. Project or account deletion is a separate destructive operation and may be subject to retention workflows.