Official Website · Documentation
Business Data + AI Behavior → Intelligence → Opportunities → Actions
Ansvisor is an open-source AI Search Intelligence Platform that helps brands understand, measure, and improve their visibility across AI Search.
Connect business data and traditional search signals with AI Search behavior across ChatGPT, Google AI Overviews, Google AI Mode, Gemini, Claude, Perplexity, Microsoft Copilot, Grok, and other AI platforms to discover opportunities, prioritize what matters, and improve brand visibility.
Track prompts, mentions, citations, competitors, AI traffic, and the sources AI systems rely on — all in one platform.
Self-host Ansvisor for free or use the managed Ansvisor Cloud.
We're building Ansvisor in the open because we believe companies shouldn't need another black box to understand a black box.
Our goal is to make AI Search intelligence more transparent, measurable, actionable, and accessible.
⭐ If you believe AI Visibility should be open and community-driven, star the repo — it's how the next team discovers Ansvisor.
AI Search is changing how people discover, evaluate, and choose brands, making Answer Engine Optimization (AEO), Generative Engine Optimization (GEO), and AI SEO increasingly important for improving brand visibility in AI-generated answers.
Traditional search data tells you how people find you through search engines. AI Search introduces another layer: how AI systems understand your brand, which sources they trust, when they mention or cite you, how competitors appear, and which prompts influence discovery.
Ansvisor brings these signals together.
With Ansvisor, you can:
- Monitor Answer Engine Insights & AI Visibility — Track how your brand appears, performs, and is represented across leading AI platforms.
- Discover Prompts — Find relevant prompt opportunities using Google Search Console, Google Analytics, Google Keyword Planner, and AI systems.
- Track Prompts — Monitor the questions and conversations that matter to your audience and measure your visibility over time.
- Analyze Citations — Discover which domains, URLs, competitors, and third-party sources AI systems cite.
- Track Mentions — Understand when, where, and how AI systems talk about your brand, products, and services.
- Benchmark Competitors — Compare your visibility, citations, mentions, and share of voice with competitors.
- Understand AI Traffic — Connect AI Search visibility with visits and performance on your website.
- Discover Query Fan-Outs — Explore the supporting queries AI systems may generate and use before producing an answer.
- Find Content Opportunities — Identify content gaps, optimization opportunities, and topics based on real AI Search behavior.
- Audit AI Discoverability — Analyze technical and content signals that can affect how AI systems discover, understand, and retrieve your website.
- MCP Server — Connect Ansvisor's AI Search intelligence with AI assistants and agent workflows through the Model Context Protocol (MCP).
The result is a clearer path from fragmented data to useful intelligence:
Business Data + AI Behavior → Intelligence → Opportunities → Actions
- 📜 Read the Ansvisor Manifesto
- 🎯 Take an Interactive Product Tour
- 📖 Explore the AI Visibility Glossary
- ✍️ Read the Blog
- 🔍 Compare Ansvisor vs Alternatives
Ansvisor is built for teams that want transparency, flexibility, and control.
You can inspect the code, understand how the platform works, contribute to its development, and deploy it on your own infrastructure.
Or use Ansvisor Cloud without managing infrastructure yourself.
Whether you're an enterprise, agency, e-commerce brand, SaaS company, startup, or developer, Ansvisor provides an intelligence layer for understanding and improving your presence across AI Search.
Ansvisor helps you monitor and analyze brand visibility across:
- ChatGPT
- Google AI Overviews
- Google AI Mode
- Gemini
- Claude
- Perplexity
- Microsoft Copilot
- Grok
- ChatGPT Shopping
- and other AI-powered discovery experiences
AI Search is still evolving, and we don't believe its measurement and optimization should happen behind another black box.
We're building Ansvisor together with our open-source community around a few simple principles:
- Evidence over dogma
- Measurement over assumptions
- Transparency over black boxes
- Outcomes over vanity metrics
- Collaboration over closed innovation
Developers, marketers, SEO/AEO/GEO practitioners, researchers, agencies, and companies are welcome to contribute.
You can help by:
- Reporting issues
- Suggesting features
- Opening pull requests
- Testing new releases
- Improving documentation
- Sharing feedback
The fastest way to get started without managing infrastructure.
Deploy Ansvisor on your own infrastructure and maintain control over your environment and data.
AI Search shouldn't become another ecosystem where companies have to rely entirely on opaque tools, unexplained scores, and assumptions.
We're building Ansvisor to help companies understand what happens between a user's prompt and an AI-generated answer — from the questions people ask and the sources AI systems use to citations, mentions, competitors, traffic, and opportunities.
Our goal is to move beyond visibility monitoring toward intelligence that helps teams understand where opportunities exist, why they matter, and what to improve next.
Business Data + AI Behavior → Intelligence → Opportunities → Actions
| Service | Purpose | Where to get |
|---|---|---|
| Supabase | Database, Auth, API | supabase.com |
| AI Provider (at least one) | Brand tracking across AI engines | OpenAI / Google Gemini / Anthropic |
| Cloro | Web scraping for AI platform responses | cloro.ai |
| Service | Purpose | Where to get |
|---|---|---|
| DataForSEO | Keyword volume data for prompt analysis | dataforseo.com |
| Scrape.do | Page fetching for Site Audit (proxy + JS render); required only if you use Site Audit | scrape.do |
| Stripe | Payments (cloud mode only, not needed for self-hosted) | stripe.com |
git clone https://github.com/ansvisor/ansvisor.git
cd ansvisor
cp web/.env.example web/.env.local
cp server/.env.example server/.envEdit both .env files and fill in your credentials. See the comments in each file for guidance.
Run the migration SQL to create all tables, indexes, RLS policies, and triggers:
Option A — Supabase Dashboard (fresh install, one paste):
- Go to your project's SQL Editor
- Paste the contents of
supabase/schema.sql— the full schema (every migration in one file) — and click Run
Option B — Supabase CLI:
npx supabase link --project-ref <YOUR_PROJECT_REF>
npx supabase db push
supabase/schema.sqlis a generated convenience for fresh installs. The numbered files undersupabase/migrations/stay the source of truth and the upgrade path — an existing install adds only the new migration(s) (ordb push). Regenerate the consolidated file after adding a migration withbash supabase/build-schema.sh.
For local development, supabase/seed.sql ships a small fixture (one demo org, brand, prompts, ~120 prompt results across all tracked engines, competitors, content opportunities, AI traffic logs). It runs automatically the next time you do:
npx supabase db resetSign in with demo@ansvisor.local / demo123 and you'll land on a populated dashboard — no provider API keys needed to iterate on UI. The seed only runs against a local Supabase via the CLI; hosted projects are unaffected.
cd web && yarn install && cd ..
cd server && npm install && cd ..# Terminal 1 — frontend
cd web && yarn dev # http://localhost:3000
# Terminal 2 — backend
cd server && npm run dev # http://localhost:80# Configure env files first, then:
docker compose up --buildSet IS_CLOUD=false (default) in server/.env and NEXT_PUBLIC_IS_CLOUD=false in web/.env.local for self-hosted mode. All features are unlocked automatically — no Stripe or payment setup needed.
ansvisor/
├── web/ # Next.js 16 frontend (TypeScript)
├── server/ # Express backend (Node.js ESM)
├── supabase/ # Database migrations and config
├── scripts/ # Version management tooling
├── docker-compose.yml # Containerized deployment
├── CONTRIBUTING.md
├── CHANGELOG.md
└── LICENSE
Frontend — Next.js 16, React 19, TypeScript, Tailwind CSS 4, Supabase Auth, Stripe, Zustand, Recharts, next-intl
Backend — Express, Vercel AI SDK, multi-provider AI (OpenAI, Anthropic, Google, Perplexity, Grok), Supabase, Socket.IO, Zod
What we're planning to build next. React with 👍 on the linked issue (or open a new one) to push something up the list. PRs welcome on any of these.
- Ansvisor MCP server — expose insights through a Model Context Protocol server so Claude Desktop, Claude Code, Cursor, Zed, and any other MCP client can query your brand visibility directly. Remote (Streamable HTTP) endpoint at
/api/mcp— zero install, paste a URL + API key into your client and you're done. Ships withlist_brandsandget_visibility_summarytoday; more tools landing as we go. - Anthropic Skills — opinionated AEO knowledge that turns Claude into an analyst on your account. Ships in two flavours: an MCP-tool flavour for Claude Desktop / Claude Code / Cursor / Zed, and a standalone REST flavour for claude.ai web (no MCP required). First skill (
ansvisor-aeo-coach) is live — seeskills/. More (page-audit, rewrite-for-aeo, content-brief) on the way. - In-product conversational AI assistant — chat with your dashboard about visibility trends, competitor moves, and content gaps without leaving the page
- ScrapeLLM integration — add ScrapeLLM as an alternative scraping backend alongside Cloro for users who prefer it or need a fallback
- PostHog integration — pipe AI-referred sessions and tracking events into PostHog for users already running it as their product analytics layer
- Daily Pulse — a per-brand daily digest email after each tracking run: KPI strip, highlights (first citations, prompt gains, leaderboard overtakes) and anomaly warnings (sharp visibility drops, competitor surges, lost citations), plus a
daily_pulse.createdwebhook event for Slack/Notion delivery (#540) - BYO LLM keys — bring your own OpenAI / Anthropic / Gemini API key for tracking and content generation, so you control cost and data handling
- Webhook recipe library — one-click Notion / Linear / Asana / Slack templates so a Content Brief can land in your editorial workflow with zero glue code
See an idea missing? Check the Ideas discussions — upvote an existing one or open a new thread.
We welcome contributions! See CONTRIBUTING.md for development setup, branch naming, commit conventions, and PR guidelines.
MIT — Copyright (c) 2026 Empler AI Inc.
