Features
AI prompt groups
The “AI prompt groups” sub-tab of AI visibility lists each prompt group of the site, its engines, its budget and its latest observation, then every prompt with each engine's latest verdict. This is where you manage what NeoRank asks AI engines.
What the view shows
A prompt group (or query set) is a list of questions asked to the verified AI engines. The view shows its current version; retired versions are filed under it. For each group: its status (“Active” or “Retired”) and version, the number of prompts × repetitions, the engines, the “Budget per observation”, the number of observations and the date of the latest, then a “Next action” derived from its state.
| KPI | Reading |
|---|---|
| Active groups | Groups in force; the hint under the figure counts the retired groups. |
| Tracked prompts | Active prompts across all groups in force. |
| Engines queried | Engines configured in the active groups, with their names. |
| Prompt × engine | “Cited” or “Mentioned” cells over the sampled cells; unsampled cells are counted separately. |
| Latest observation | Date of the latest completed run. |
Where the groups come from
| Group | Origin | Content |
|---|---|---|
| Prompts par défaut (analyse) | Created by a site analysis, or by “Create the suggested group” | Five questions about the brand, up to ten questions built from the site's top non-brand Search Console queries (last 28 days), and the known competitors, on every verified engine |
| Prompts suivis (tableau de bord) | Your prompts, added from this view or from AI visibility | A prompt of 3 to 1,500 characters, asked to “All verified engines” or to a single engine |
| Mots-clés suivis (IA) | Rank tracking, “Track … in AI engines” | One prompt worded from each chosen keyword |
“Create the suggested group” (or “Update the suggested group”) is offered while the site tracks no group, or to top up the default group: new queries, new competitors, engines realigned on the verified ones. A group you created is never changed by this button. No observation is started: the button only prepares the prompts.
Reading the verdicts
A group's table gives, for each prompt and each engine, the verdict of the latest successful answer, with its date:
| Verdict | Meaning |
|---|---|
| Cited | The answer cites a page of your site as a source. |
| Mentioned | The answer names your brand without citing your site. |
| Not cited | The engine answered without citing or naming you. |
| Not sampled | No answer from this engine for this prompt over the group's last ten runs: nothing is assumed. |
Adding or removing a prompt creates a new version of the group; verdicts are tied to the prompt's text, so an answer obtained on a previous version stays shown, dated. Details opens the prompt's resolution panel (answers read, sites cited in your place, steps), the same as in AI visibility.
Common actions
- Track a new prompt: type the question as a buyer would ask it, choose “All verified engines” or one engine, then “Track this prompt”. No verdict appears before the next observation.
- Add an engine: when a verified engine is missing from your prompts, an “Add …” button adds it; it will be asked at the next observation.
- Start observation: each active group has its own button. The maximum cost is reserved on the monthly AI budget before any call.
- Stop tracking: removes a prompt; answers already stored stay in the history. A keyword prompt of the default group may be added back by the next analysis while that keyword stays among the top-ranked ones.
- Check in Google: records a manual reading of Google's AI Overview for a prompt, labelled “manual reading — not automated”.
When the verdicts update
- With every observation started from the view or from AI visibility.
- With every site analysis: if your plan includes AI, the analysis creates the default group when needed, then observes every active group.
- An observation follows your click or a site analysis. No frequency can be set in the dashboard: a prompt's “Frequency” line in AI visibility reads “On demand” unless the site already has a schedule.
The header says “Observed on …”, “Never observed” or “Observation stuck”. A stuck observation (no sign of activity) does not prevent starting another: the previous one is closed on launch. Run states are described in AI visibility.
Roles and plan
- A client viewer role, or an account that is not an active member of the workspace, sees the view read-only: the reason is shown above the groups.
- Adding a prompt or an engine and starting an observation need a plan that includes AI requests; removing a prompt only needs write access. See the plans and the AI budget.
Limits
- A prompt's country and language travel in its text: no country parameter is sent to the engines.
- A retired group can no longer be observed; its results stay readable.
- Google's AI Overviews are never queried by NeoRank itself; see AEO.