Skip to main content
Track AI answers and website activity, turn useful evidence into Opportunities, run Agents and re-check what changes. Analytics routes: /ai-visibility?tab=overview, ?tab=citations, ?tab=prompts, /analytics/pages, /agent-analytics, /ai-traffic, /ai-visibility?tab=generator, ?tab=sentiment, ?tab=technical. Experiments and Page audits remain available through New and existing deep links. Competitors lives in Settings without the extra monitoring header or Settings button. Legacy ?tab=competitors redirects there. Legacy ?tab=citation opens Prompts, including prompt deep links; it does not open the new Citations report.

​
Choose the right view

  • Overview: one period for website activity and visibility statistics. Region/engine filters inside Visibility Score apply to monitoring. Information explains source coverage; metric labels offer short help.
  • Citations: which domains are cited in monitored answers, their observed share/rank and competitor follow controls.
  • Prompts: tracked buyer questions, results, diagnosis and monitoring settings. Add prompt needs only the question.
  • Prompt Factory: generate and review questions before tracking them.
  • Pages: connect citations, bot access, AI referrals and page authority on each owned URL. See Pages.
  • Agent Analytics: AI crawler requests from Vercel Drains, by bot and page.
  • AI Traffic: identifiable human AI referrals from GA4 and a selected primary business action. See Data integrations.
  • Sentiment / Technical analysis: answer descriptions and technical readiness.

​
From evidence to work

Create an Opportunity from a monitoring gap, page audit, page evidence or AI request error. Review the proposed work and use Agents to execute supported jobs. Re-check answers afterward; an observed change alone does not prove causation. Open New → Page audits for a URL review or New → Experiments for optional visitor experiments. Ask Anvero is the conversational entry to the central agent; action availability depends on connected capabilities and deployment. Fill Knowledge with the Brand Model and company files to ground content work. Projects and usage belong to a workspace. Existing plan and role limits still apply; moving a screen does not grant new permissions.