# Vizelo.ai — Complete Reference

> Canonical longform reference of all public pages on vizelo.ai, formatted for AI ingestion. Last reviewed 2026-05-26.

Vizelo.ai is the AI-native platform that tracks, optimizes, and grows brand visibility inside ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, and Gemini. Founded in 2026 and headquartered in Irving, Texas, Vizelo offers a free-forever tier and paid plans from $49/month, with SOC 2 Type II audit in progress and a contractual commitment to never train models on customer data.

---

## /

### Private preview · SOC 2 Type II in progress

# Your brand is invisible in the answer engine era. We fix that.

ChatGPT, Perplexity, Google AI Overviews, and Bing Copilot now answer 60% of queries without sending traffic. Vizelo.ai is the first platform that measures, optimizes, and grows your visibility inside every generative engine — automatically.

- Start free — no card
- See the live dashboard

Free forever tier · Connect in 4 minutes · Cancel anytime

Tracks visibility across: ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, Gemini.

Trust strip:
- SOC 2 Type II in progress
- GDPR + CCPA aligned
- Enterprise · per-customer data isolation
- Never trains on customer data

### The bottleneck has moved

## Search didn't die. It became invisible.

- **60%** of Google queries now end without a click — answered by AI Overviews directly.
- **8×** more frequent SERP volatility since AI Overview rollout. Rankings stop meaning what they used to.
- **$80B** of organic traffic value at risk as buyers shift research to ChatGPT and Perplexity.

Ahrefs and Semrush show where you rank in 1995's search engine. Vizelo shows whether ChatGPT recommends you when a buyer asks for your category, today.

### What Vizelo does

## Visibility, end to end.

Always-on visibility into how your brand surfaces across your domain, your competitors, and the answer engines your buyers actually use.

#### Engine Tracker
Monitors how your brand surfaces inside ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, and Gemini across thousands of tracked prompts — hourly.
- Citation share-of-voice vs. competitors
- Prompt-level rank deltas and alerts
- Source-domain attribution

#### Brief Generator
Generates ranked content briefs from real demand signals — keyword expansion, SERP analysis, intent classification, and competitive gaps.
- Brief outline + FAQ + internal links
- Cannibalization detection
- Authority + freshness scoring

#### Schema Enhancer
Takes a draft or published post and upgrades it for answer engines: schema markup, JSON-LD, FAQ blocks, and llms.txt — all validated before they ship.
- One-click schema injection
- llms.txt and AI sitemap generation
- Real-time validation

#### Citation Mapper
Pulls every URL the answer engines cite for your tracked prompts, normalizes them, and tells you exactly which pages on your domain (and your competitors') are winning.
- Per-prompt citation graph
- Domain authority signals
- Competitor citation steal-list

#### Sentiment Monitor
Scores how the answer engines describe your brand over time — positive, neutral, negative, or worse: not mentioned at all.
- Sentiment delta per engine
- Quote-level evidence
- Crisis-watch alerts

#### Outreach (Q3)
Find the publications, podcasts, and aggregators that the answer engines cite most for your category — and pitch them automatically.
- AI-engine-aware PR targeting
- Templated, personalized pitches
- Reply tracking + thread review

### How it works

## From signup to first insight in under 10 minutes.

1. **Connect your domain.** Add your site, your top competitors, and the prompts you care about — or let the platform suggest 500 from your sitemap.
2. **We probe every answer engine.** Vizelo runs your tracked prompts hourly against ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, and Gemini.
3. **You get a prioritized playbook.** Citation gaps, schema fixes, content briefs, and PR targets — ranked by expected lift on your share of voice.
4. **Ship and measure.** Push schema fixes with one click, hand briefs to your writers, and watch the share-of-voice chart climb engine by engine.

### Compared to legacy SEO tools

## Ahrefs and Semrush won't save you here.

| Capability | Vizelo.ai | Ahrefs / Semrush | Surfer / Frase |
|---|---|---|---|
| Tracks Google AI Overviews | ✓ hourly | Partial | — |
| Tracks ChatGPT, Perplexity, Claude, Gemini | ✓ all | — | — |
| Citation graph per prompt | ✓ | — | — |
| Schema and llms.txt generation | ✓ one-click | — | Manual |
| Content briefs from real SERP demand | ✓ | Add-on | ✓ |
| Cannibalization detection | ✓ | ✓ | — |
| API + webhooks | ✓ | ✓ | Limited |
| Multi-tenant + SSO + SCIM | ✓ | Enterprise | — |

### FAQ

## Everything teams ask in the first call.

**How is this different from Ahrefs adding AI Overview tracking?**
Ahrefs tells you whether your URL appears in an overview. Vizelo tells you whether the AI engine recommends you, what it says about you, who it cites instead, and exactly what to ship to change that — across six engines, not one.

**Do you train on our data?**
No. Your data is yours. We never train models on customer prompts, content, or citation graphs. SOC 2 Type II in progress, GDPR/CCPA aligned, with strict per-customer data isolation.

**How accurate is the citation tracking?**
We probe each engine through their official surfaces on the cadence your plan defines. Citations are normalized and de-duplicated, and we continuously validate engine output against manual audits.

**What does setup look like?**
Sign in, add your domain, paste your competitor list, and click connect. Vizelo suggests 500 prompts in under five minutes. You'll have your first share-of-voice chart inside ten.

**Can our agency manage multiple clients?**
Yes. The Scale plan and above include unlimited workspaces, white-label exports, SSO, SCIM, and per-client roles.

## The teams that win the next decade start measuring this decade.

Free forever tier. Four-minute setup. No card required.

---

## /about.html

### Why we exist

# We're building the visibility layer for the answer-engine era.

Search didn't die. It got swallowed by AI. We watched our own work disappear inside ChatGPT and Perplexity answers without a single citation, and decided to build the platform we needed.

### Mission

## Make brands visible to the machines.

For thirty years, "winning search" meant ranking on a results page. Today, the engines summarise instead of list, and a single AI answer can replace a hundred clicks. The brands that show up inside those answers will compound forward. The ones that don't will quietly disappear. Vizelo measures, fixes, and grows that visibility — engine by engine, prompt by prompt, hourly.

### Story

## How we got here.

**2024 — Noticed our own pages were invisible.** The founders ran content for two B2B SaaS companies. Traffic was flat but conversions were dropping. We dug in and found that ChatGPT, Perplexity, and AI Overviews were confidently recommending three of our competitors and never mentioning us — for keywords we'd ranked #1 on Google for years.

**Mid-2025 — Built a hacky internal tool.** Cobbled together a pipeline that probed six engines on a cadence and diffed citations week-over-week. It was ugly, brittle, and ran on a laptop — but it worked. Eight friends asked to use it. We started saying yes.

**Q1 2026 — Opened private preview.** Rewrote the pipeline from scratch with strict per-customer data isolation and zero training on customer data baked into the contract. Shipped v0.4 with the first set of visibility, briefing, enhancement, citation-mapping, and sentiment capabilities.

**Now — Scaling the team and the platform.** SOC 2 Type II audit underway. Sixth agent (Outreach) on the Q3 roadmap. Hiring engineering and developer-relations from Irving, Texas. If this problem is also your problem, we'd love to talk (careers@vizelo.ai).

### Team

## A small team, betting big.



### How we operate

## Three rules we won't bend.

1. **Never train on your data.** Customer prompts, citations, and content stay yours. We don't train models on them, we don't pool them across tenants, and the contract says so in plain English.
2. **Show our work.** Every score, citation, and ranking links back to the prompt and the engine response that produced it. No black-box scores you have to take on faith.
3. **Ship in public.** We publish a changelog every release and a comparison page that's honest about where we lose.

## Talk to the people building this.

hello@vizelo.ai · careers@vizelo.ai

---

## /pricing.html

### Pricing

# Priced like infrastructure. Built like a team.

Start free. Upgrade when share-of-voice climbs. Every plan includes all five AI agents — only the volume and seats scale.

Billing options: Monthly · Annual (SAVE 20%)

### Tiers

#### Free — $0/forever
Diagnose your AI visibility in one workspace. No card required.
- 1 workspace · 1 seat
- 25 tracked prompts
- 3 engines: ChatGPT, Perplexity, AI Overviews
- Weekly citation refresh
- 3 content briefs / month
- Schema generation (not included)
- API + webhooks (not included)

#### Starter — $49/mo (or $39/mo billed annually)
For solo operators and small content teams. 14-day trial · cancel anytime.
- 2 seats · 1 workspace
- 250 tracked prompts
- All 6 engines
- Daily refresh
- 25 content briefs / month
- Schema + llms.txt generation
- SSO and SCIM (not included)

#### Growth — $199/mo (or $159/mo billed annually) — Most popular
For B2B teams making organic a revenue channel. 14-day trial · billed monthly or annually.
- 5 seats · 3 workspaces
- 1,500 tracked prompts
- All 6 engines + Gemini Advanced
- Hourly refresh
- 150 content briefs / month
- Cannibalization detection
- Slack + Teams alerts
- API + webhooks

#### Scale — $599/mo (or $479/mo billed annually)
For agencies and multi-brand portfolios. 14-day trial · agency-ready.
- 20 seats · unlimited workspaces
- 10,000 tracked prompts
- All engines + custom probes
- Real-time alerts
- Unlimited content briefs
- White-label reports
- SSO + SCIM + role-based access
- Priority support · 4-hour SLA

#### Enterprise
Custom prompt volume, dedicated database with customer-managed encryption keys, audit log export, SOC 2 reports, dedicated success engineer, contractual SLA. Talk to sales.

### Full feature comparison

| Feature | Free | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|---|
| Tracked prompts | 25 | 250 | 1,500 | 10,000 | Custom |
| Workspaces | 1 | 1 | 3 | Unlimited | Unlimited |
| Seats included | 1 | 2 | 5 | 20 | Unlimited |
| Refresh cadence | Weekly | Daily | Hourly | Real-time | Real-time |
| AI engines | 3 | 6 | 6 + Gemini Advanced | All + custom | All + custom |
| Content briefs / month | 3 | 25 | 150 | Unlimited | Unlimited |
| Schema + llms.txt | — | ✓ | ✓ | ✓ | ✓ |
| Citation graph | — | Basic | Full | Full | Full |
| Cannibalization detection | — | — | ✓ | ✓ | ✓ |
| Slack / Teams alerts | — | — | ✓ | ✓ | ✓ |
| API + webhooks | — | — | ✓ | ✓ | ✓ |
| SSO + SCIM | — | — | — | ✓ | ✓ |
| White-label | — | — | — | ✓ | ✓ |
| SOC 2 report | — | — | — | On request | ✓ |
| Dedicated database + customer-managed keys | — | — | — | — | ✓ |
| Success engineer | — | — | — | Shared | Dedicated |
| Contractual SLA | — | — | — | 99.5% | 99.95% |
| Support | Community | Email · 48h | Email · 24h | Priority · 4h | Slack Connect |

### Pricing FAQ

**Do I have to pick a plan to start?**
No. The Free plan stays free forever — 25 tracked prompts, 3 engines, weekly refresh. Most teams upgrade when they want hourly refresh or more than 25 prompts.

**What counts as a "tracked prompt"?**
A unique query string you want Vizelo to probe across every AI engine. Each probe across all enabled engines counts as one execution against your quota.

**Can I switch plans mid-cycle?**
Yes. Upgrades take effect immediately and we pro-rate the difference. Downgrades take effect at your next billing date.

**Do you offer annual discounts?**
Yes — 20% off Starter, Growth, and Scale when billed annually. Enterprise is always annual and custom.

**Is there a usage overage fee?**
We never surprise-bill. If you exceed your prompt quota mid-month, we pause new probes and ping you to upgrade. Existing scheduled probes keep running.

**Do you offer non-profit or student discounts?**
Yes. 50% off Growth for verified non-profits and accredited educational institutions. Reach out from your institutional email.

## Start free. Upgrade when you're ready.

---

## /demo.html

### Live demo · 90 seconds

# Watch Vizelo find every gap in your AI visibility.

A real workspace. Real prompts. Real citation gaps fixed in front of you.

The animated dashboard is a live CSS preview — not a video. Scroll for the scene-by-scene storyboard, or book a live walkthrough.

### Storyboard

## Scene by scene.

A 90-second walkthrough, scene by scene. Every timestamp maps to a real screen in the product.

#### 0:00 – 0:08 · Cold open · the problem
**SCREEN:** Split-screen. Left: Google AI Overview answering "best CRM for fintech startups" — three citations, none of which are the viewer. Right: ChatGPT answering the same query — same omission. Highlight box appears around the citation slots with a red glitch wipe.
**ON-SCREEN TEXT:** "60% of queries never click." (caption fades in at 0:04, holds 3s)
**SFX:** Low sub-bass hum, single digital chirp on caption appearance.
**VO:** "In 2026, search doesn't send traffic anymore. ChatGPT answers. Perplexity answers. Google answers. The only question is — do they recommend you?"

#### 0:08 – 0:20 · Dashboard · share of voice
**SCREEN:** Cut to Vizelo home dashboard. Camera pushes in on the share-of-voice chart. Acme line at 11% (dim), three competitor lines above (28%, 24%, 18%). Six engine chips along the top tick green one by one as data refreshes.
**ON-SCREEN TEXT:** Counter widget animates 0% → 11% in 0.8s. "LIVE · 6 ENGINES" badge in top-right.
**SFX:** Bass-line drops in. Soft tick per engine chip.
**VO:** "This is your share of voice across six AI engines. Right now, you're losing to three competitors you've never heard of."

#### 0:20 – 0:34 · Citation graph drill-down
**SCREEN:** Cursor clicks the "best CRM for fintech startups" row. Page transitions (slide-up) into prompt detail. A radial citation graph draws node-by-node: 7 outbound nodes from the prompt, color-coded by engine. Acme's domain is conspicuously absent — a dotted ghost-node labelled "you" sits at the edge.
**ON-SCREEN TEXT:** "7 CITATIONS · 0 FROM ACME.COM" pulses magenta at 0:28.
**SFX:** Subtle whoosh on transition. Quiet "blip" per node as the graph draws.
**VO:** "For this prompt, the engines cite seven URLs. Zero from your domain. Vizelo tells you exactly which articles to write, and where to win the citation."

#### 0:34 – 0:48 · One-click content brief
**SCREEN:** Cursor clicks a glowing "Generate brief" button. A side panel slides in from the right. Brief sections stream in token-by-token (real LLM stream feel): Title → Search intent → H2 outline → FAQ → Internal links → Schema preview. Timer in the corner counts up: 12s.
**ON-SCREEN TEXT:** "Brief Generator · streaming" with a typing cursor.
**SFX:** Soft typewriter clicks under the stream (low volume, fades at 0:46).
**VO:** "One click. Vizelo generates a brief in twelve seconds — outline, FAQ, internal links, even the schema."

#### 0:48 – 1:02 · Schema Enhancer · schema fix
**SCREEN:** Tab switch to "Schema Enhancer". Cursor pastes a real-looking blog URL into the input. Agent scans the page (progress bar) and surfaces a diff: missing FAQ schema (red), missing internal links (red), llms.txt absent (red). Cursor clicks "Apply all". Items flip to green checkmarks one by one. JSON-LD preview pane on the right validates with a green "VALID" badge.
**ON-SCREEN TEXT:** "3 fixes ready · 0 errors after apply"
**SFX:** Per-fix confirmation chime, slightly different pitch ascending.
**VO:** "Already published? The Schema Enhancer takes your live URL and ships the schema, FAQ blocks, and llms.txt the engines need to cite you."

#### 1:02 – 1:18 · Engine Tracker · alert in Slack
**SCREEN:** Cut to a Slack workspace (#vizelo-alerts). A new message arrives with the Vizelo bot avatar: "⚠ Brand citation share dropped 8% on Perplexity (24h). Likely cause: competitor-x.com/new-post published 3h ago." Below the message, three buttons: Open prompt · View competitor post · Snooze. Cursor hovers over "View competitor post" (does not click — Slack stays clean).
**ON-SCREEN TEXT:** Timestamp on message reads "now". The "8%" pulses magenta once.
**SFX:** Slack notification chime, then bass returns.
**VO:** "And when something changes overnight, Vizelo finds it and tells you in Slack — with the exact competitor URL that caused the drop."

#### 1:18 – 1:30 · Close · CTA
**SCREEN:** Quick cut to a clean black frame. The Vizelo V-mark assembles from three light beams (cyan, violet, magenta) over 0.6s, then settles. Wordmark fades up beneath. Tagline lands one word at a time: "Win · the · answer · engine · era." End-card holds with URL vizelo.ai and "Free forever tier · 24-hour reply on booked demos."
**ON-SCREEN TEXT:** "vizelo.ai" + small print URL. No buttons (this is a video).
**SFX:** Bass swell, then drop to silence on the final still. 1s breathing room before the cut.
**VO:** "Vizelo.ai. Start free. Connect your domain. Win the answer engine era."

#### Production notes · Tone, music, pacing
**Voiceover:** confident, lower register, no upspeak. Native NA-English. 145 wpm. Record dry; light comp + de-ess in post.
**Music:** minimal electronic. Sub-bass enters at 0:08, melodic synth at 0:48, sub-only on the close. Side-chain duck under VO.
**Visual:** all screens are real product (no After Effects mockups). Cursor moves with intent — no idle hovering. Use 16:9 1920×1080, export ProRes 422 + h.264.
**Captions:** ship a baked-in SDH track and a separate SRT for upload. Caption font: JetBrains Mono 18px, bottom-anchored with 16px padding.

---

## /compare.html

### Side-by-side

# Vizelo.ai vs the legacy stack.

Ahrefs and Semrush built the SEO category for 2015's search engine. Surfer and Frase iterated on content briefs for the click-era. The answer engines moved on. Here's what each tool actually tracks today, with no spin.

Last updated 2026-05-16 from public docs + product testing.

### The matrix

## What each tool actually does.

**Answer-engine coverage**

| Capability | Vizelo.ai | Ahrefs | Semrush | Surfer / Frase |
|---|---|---|---|---|
| Google AI Overviews tracking | ✓ hourly | Partial · daily | Partial · daily | — |
| ChatGPT visibility | ✓ all engines | — | — | — |
| Perplexity visibility | ✓ | — | — | — |
| Bing Copilot | ✓ | — | — | — |
| Claude.ai | ✓ | — | — | — |
| Google Gemini | ✓ | — | — | — |

**Citation intelligence**

| Capability | Vizelo.ai | Ahrefs | Semrush | Surfer / Frase |
|---|---|---|---|---|
| Per-prompt citation graph | ✓ | — | — | — |
| Competitor citation steal-list | ✓ ranked | — | — | — |
| Source-domain attribution | ✓ | Partial | Partial | — |
| Brand-mention sentiment over time | ✓ | — | Add-on | — |

**Content production**

| Capability | Vizelo.ai | Ahrefs | Semrush | Surfer / Frase |
|---|---|---|---|---|
| Brief generation from demand signals | ✓ | Add-on | Add-on | ✓ |
| Schema + JSON-LD one-click ship | ✓ | — | — | Manual |
| llms.txt + AI sitemap generation | ✓ | — | — | — |
| Cannibalization detection | ✓ | ✓ | ✓ | — |

**Workflow + integration**

| Capability | Vizelo.ai | Ahrefs | Semrush | Surfer / Frase |
|---|---|---|---|---|
| Slack alerts (per-prompt, real-time) | ✓ | Project-level | Project-level | — |
| Public REST API | ✓ | ✓ | ✓ | Limited |
| Webhooks | ✓ | ✓ | — | — |
| SSO (SAML / OIDC) | ✓ Scale plan | Enterprise | Enterprise | — |
| SCIM 2.0 | ✓ Scale plan | Enterprise | Enterprise | — |

**Pricing + access**

| Capability | Vizelo.ai | Ahrefs | Semrush | Surfer / Frase |
|---|---|---|---|---|
| Free-forever tier | ✓ 25 prompts | — | — | — |
| 14-day trial without card | ✓ | — | — | ✓ |
| Starting price (paid) | $49/mo | $129/mo | $139.95/mo | $89/mo |

**Trust + privacy**

| Capability | Vizelo.ai | Ahrefs | Semrush | Surfer / Frase |
|---|---|---|---|---|
| Never trains on customer data | ✓ contractual | — | — | — |
| SOC 2 Type II | In progress | ✓ | ✓ | — |
| Per-customer data isolation | ✓ | ✓ | ✓ | Limited |

We update this page quarterly. If anything here is out of date for a competitor's product, tell us (hello@vizelo.ai) and we'll correct it within 48 hours — including in our favor or not.

### The honest take

## When to use what.

**01. Stay with Ahrefs / Semrush if…**
You still get most of your traffic from blue-link organic, your buyers don't research with ChatGPT, and your team's reporting muscle is built around classic SERP rank + backlink graphs. These tools are still the best in the world at that job.

**02. Add Surfer / Frase if…**
Your bottleneck is content production volume, not visibility measurement. They're cheaper than Ahrefs and excellent at structured-brief workflows. Pair with Vizelo for the visibility layer they don't cover.

**03. Use Vizelo when…**
Your buyers ask the AI engines about your category and you have no idea if you're cited, sentiment-scored, or invisible. That's a different category than legacy SEO — measuring it is what we do.

## See your numbers vs theirs.

Connect your domain. Run a real scan in four minutes. Free forever tier, no card.

---

## /press.html

### Press & brand

# Everything you need to write about us.

Logos, palette tokens, screenshots, the boilerplate copy. Use any of it without asking — just don't restyle the logo. For interview requests, email press@vizelo.ai and we'll reply within 24 hours.

### Logos

## Mark + wordmark.

Use the mark on its own when space is tight; otherwise prefer the lockup. Maintain at least one cap-height of clear space on all sides. Never recolor, rotate, or apply effects.

Available downloads:
- Mark · dark bg — PNG 512px, PNG 180px, PNG 32px
- Mark · light bg — PNG 512px, PNG 180px, PNG 32px
- Full banner — PNG 1983×793, WebP 1983×793, WebP 1600w

### Brand colors

## Click a swatch to copy.

The cyberpunk palette is six neons + two near-blacks. Day-mode variants are derived for WCAG AA contrast on light backgrounds.

- **Neon Cyan** — `#00F0FF` — primary accent
- **Neon Magenta** — `#FF2A6D` — hover / open / featured
- **Neon Purple** — `#7B2CFF` — brand-gradient midpoint
- **Neon Yellow** — `#FFD60A` — warn / coming soon
- **Neon Green** — `#39FF14` — positive / online
- **Neon Pink** — `#FF1493` — tonal alternate to magenta
- **Bg** — `#03030D` — page background
- **Bg-2** — `#07071A` — alt section background

### Boilerplate copy

## Lifted text, ready to paste.

**One-liner:** Vizelo.ai is the AI-native platform that tracks, optimizes, and grows brand visibility inside ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, and Gemini — automatically.

**50 words:** Vizelo.ai is the first AI-native platform built for the answer-engine era. Tracks brand visibility across every major engine, surfaces citation gaps, generates content briefs from real demand signals, and ships the schema and llms.txt the AI engines need to cite you. SOC 2 in progress, never trains on customer data.

**150 words:** Vizelo.ai, founded in 2026 and based in Irving, Texas, is the AI-native visibility platform for the answer-engine era. Sixty percent of search queries now end without a click — answered directly by ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, or Gemini. Legacy SEO tools weren't built to measure that, let alone influence it. Vizelo tracks brand visibility across every major engine, builds per-prompt citation graphs, generates content briefs from real demand signals, and one-click ships the schema and `llms.txt` the AI engines need to cite a brand. The platform offers a free-forever tier and paid plans from $49/month, with SOC 2 Type II audit in progress, full tenant isolation, and a contractual commitment to never train models on customer data. Vizelo is used by B2B SaaS, fintech, and agency teams that need to win category recommendations inside the engines their buyers actually use.

### Key facts

## Numbers, dates, and the things you'll fact-check.

- **Founded:** 2026
- **HQ:** Irving, Texas, USA
- **Team size:** 6 people (placeholder — confirm before publishing)
- **Pricing:** Free forever tier · paid plans from $49/month
- **Engines tracked:** 6 — ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, Gemini
- **Capabilities:** 5 GA + 1 Q3 roadmap (Outreach)
- **Compliance:** SOC 2 Type II audit in progress · GDPR + CCPA aligned
- **Data policy:** Never trains models on customer data (contractual)
- **Investors:** Currently bootstrapped (placeholder — update at announcement)

## Need something not here?

press@vizelo.ai — 24-hour reply guarantee.

---

## /book-demo.html

### Live walkthrough · 30 min

# Book a live demo.

Half an hour. Your domain. Your competitors. We'll spin up a real workspace on the call and walk through every agent end-to-end.

- Request a demo (sends email to hello@vizelo.ai)
- Join the waitlist instead

We confirm a calendar slot within one business day.

## What we'll show you

Not a slide deck. Your real share-of-voice chart, live.

**01. Your share-of-voice.** 500 prompts auto-seeded for your domain across six engines. See where you place and where you don't.

**02. Competitor citation gaps.** The exact URLs your competitors get cited for that you don't — ranked by traffic value.

**03. The next 90 days.** What we'd ship first if you were a Vizelo customer, with realistic timing on share-of-voice gains.

---

## /contact-sales.html

### Enterprise · Procurement · Security

# Talk to sales.

Custom contracts, volume pricing, SOC 2 evidence, MSA / DPA, security questionnaires, custom data-residency — we handle it directly.

- Email sales (sales@vizelo.ai)
- Book a demo first

Typical response within one business day.

## What sales handles

**01. Custom contracts.** Master Services Agreement, Data Processing Agreement, redlines welcome. Legal turnaround typically 5 business days.

**02. Procurement & vendor onboarding.** W-9, vendor portals, NetSuite / Coupa / SAP Ariba SKUs, custom invoicing, PO-based billing on annual contracts.

**03. Compliance & security.** SOC 2 Type II evidence (in observation), GDPR / CCPA DPAs, custom data-residency, security questionnaires (CAIQ, SIG).

### Smaller team?

## Self-serve is faster

If you're under 50 seats and don't need custom compliance, our self-serve plans are public and you can be live in under five minutes once your cohort opens.

---

## /changelog.html

### Release log

# Everything we shipped, in chronological order.

What changed in the agents, the pipeline, the UI, and the contracts. Updated whenever we cut a release. Subscribe to the launch list to get it in your inbox.

### 2026 · 05 · 14 — v0.7.0 (MAJOR)
**Schema Enhancer ships JSON-LD validation inline**
- NEW · Schema Enhancer now validates generated JSON-LD against schema.org in real time. Errors highlight inline with a green/red strip in the diff pane.
- NEW · `llms.txt` generation supports the new per-section directive (rolling out at draft.llmstxt.org).
- FIX · Citation Mapper missed Perplexity citations on prompts containing em-dashes. Patched the tokenizer.

### 2026 · 04 · 28 — v0.6.3
**Hourly probe for Gemini, weekly digest in Slack**
- NEW · Gemini moved from 6-hour to hourly probe cadence on all plans.
- NEW · Slack integration ships a Monday-morning digest: top movers, new prompts, and the previous week's biggest steal/lose.
- UX · Share-of-voice chart now supports 7d / 30d / 90d / YTD ranges.

### 2026 · 04 · 09 — v0.6.0 (MAJOR)
**Sentiment Monitor agent goes GA**
- NEW · Sentiment Monitor scores how each engine describes you across positive / neutral / negative / "not mentioned." Per-engine trend lines + quote-level evidence.
- NEW · Crisis-watch alerts: if sentiment drops more than 2 std-dev in 24h, you get pinged on Slack and email.
- FIX · Workspaces with more than 5,000 tracked prompts no longer hit a UI timeout on the dashboard.

### 2026 · 03 · 21 — v0.5.4
**SOC 2 evidence portal, SCIM on Scale plan**
- NEW · Customer-facing evidence portal: pull our latest SOC 2 audit, sub-processor list, and DPA without emailing legal@.
- NEW · SCIM 2.0 endpoint on the Scale plan. Tested against Okta and Microsoft Entra.
- FIX · OAuth handoff to Google AI Overviews would intermittently drop refresh tokens. Now persisted securely.

### 2026 · 03 · 04 — v0.5.0 (MAJOR)
**Citation Mapper + per-prompt graph**
- NEW · Citation Mapper agent: pulls every URL each engine cites for your tracked prompts, normalizes them, and builds a per-prompt citation graph.
- NEW · Competitor "steal list" — pages owned by competitors that get cited for prompts you care about, ranked by frequency × impact.
- UX · Redesigned prompt detail view; we cut the time-to-insight by ~60% in user testing.

### 2026 · 02 · 18 — v0.4.0
**Private preview opens**
- NEW · Vizelo enters private preview with the first set of visibility, briefing, enhancement, citation-mapping, and sentiment capabilities.
- NEW · Free-forever tier: 100 tracked prompts, two engines, weekly cadence. No card.
- FOUNDATION · Strict per-customer data isolation; never train on customer data (built into the contract).

Older entries live in our app's release notes once you sign in.

---

## /signup.html

### Private preview

# Join the waitlist.

Vizelo.ai is rolling out in cohorts so the answer-engine indexers can keep pace with new tenants. Drop your work email and we'll send your invite when your cohort opens.

- Reserve my spot (opens email client with pre-filled message to hello@vizelo.ai)
- Book a live walkthrough

## What happens next

**01. You email us.** Tell us your domain, your top 3 competitors, and the share-of-voice question keeping you up.

**02. We send an invite.** Typical wait is 5–10 business days. You'll get a single-use link to spin up your workspace.

**03. You see your gap.** First share-of-voice chart inside ten minutes. Free forever for the first 25 prompts.

### Already invited?

## Existing customers

The hosted product isn't live yet on a public URL — if you've received an invite, your sign-in link is in your welcome email. Lost it? Reply to that email or write hello@vizelo.ai.

---

## /privacy.html

### Legal

# Privacy Policy

How Vizelo, Inc. collects, uses, shares, and protects information when you use vizelo.ai and the Vizelo platform.

**Effective date:** May 14, 2026 · **Last updated:** May 14, 2026 · **Version:** 1.0

**Plain-language summary.** We collect the minimum personal data needed to run Vizelo: your account email, billing contact, and product telemetry. We never train AI models on customer prompts, content, or citation graphs. Customer data is isolated per tenant. You can export or delete your data at any time. Questions: privacy@vizelo.ai.

### 1. Scope and definitions

This Privacy Policy describes how Vizelo, Inc. ("Vizelo," "we," "us," or "our") handles personal information collected through the marketing site at `vizelo.ai`, the application at `app.vizelo.ai`, our APIs, and any related services (collectively, the "Service").

"Customer Data" means information that customers and their authorized users submit to the Service, including tracked prompts, content briefs, citation graphs, and configuration. For Customer Data, Vizelo acts as a data processor (or service provider under CCPA). For information about prospects, marketing-site visitors, and Vizelo's direct administrative contacts, Vizelo acts as a data controller (or business under CCPA).

### 2. Information we collect

#### 2.1 Account and billing information
When you create an account or subscribe to a paid plan, we collect your name, email address, password (hashed using Argon2id), workspace name, billing contact, billing address, and tax identifier where required. Payment card data is collected and stored by our payment processor (Stripe) and is never stored on Vizelo systems.

#### 2.2 Customer Data
We process Customer Data on behalf of the customer. This includes domains and competitor domains you track, prompts you configure, content you submit for analysis, briefs generated by our agents, and the citation graphs we collect from public answer-engine surfaces. Customer Data is logically isolated per workspace under strict access controls and is processed in accordance with the customer agreement.

#### 2.3 Product telemetry
We collect product telemetry to operate, secure, and improve the Service. Telemetry includes feature usage events, API request metadata, performance metrics, error reports, and authentication events. Telemetry is associated with a workspace and user ID but does not contain Customer Data.

#### 2.4 Device and connection information
We collect IP address, user-agent, language, time zone, and approximate location (derived from IP) to provide the Service, protect against abuse, and meet legal obligations. We retain web-server logs for ninety (90) days.

#### 2.5 Communications
If you contact us by email, fill in a form, or interact with our support channels, we retain those communications and any attachments to respond and improve our support.

### 3. How we use information

We use personal information to:
- Provide, maintain, and secure the Service.
- Authenticate users and authorize access.
- Process billing and prevent fraudulent transactions.
- Detect, prevent, and respond to abuse, security incidents, and policy violations.
- Send transactional emails (account, billing, security, product changes).
- Send marketing emails to administrative contacts, where permitted, with an unsubscribe link in every message.
- Improve product reliability and performance, including aggregate analysis of usage patterns.
- Comply with legal obligations and respond to lawful requests.

**We do not train AI models on Customer Data.** Customer prompts, content, briefs, and citation graphs are not used to train, fine-tune, or otherwise improve any model operated by Vizelo or by third parties.

### 4. Legal bases (GDPR)

If you are in the European Economic Area, the UK, or Switzerland, we process personal information on the following legal bases:
- **Performance of a contract** — to deliver the Service to you under our customer agreement.
- **Legitimate interests** — to secure the Service, prevent abuse, improve reliability, and run targeted business-to-business marketing where the impact on you is minimal.
- **Consent** — for optional marketing communications, non-essential cookies, and any processing for which consent is required by law. You can withdraw consent at any time.
- **Legal obligation** — to comply with tax, accounting, or other legal requirements.

### 5. When we share information

We do not sell personal information. We share information only as follows:
- **Sub-processors** — vendors that operate infrastructure, deliver email, process payments, or otherwise support the Service. See the list below.
- **Within your workspace** — users you invite to a workspace can see workspace content and the actions other workspace users take.
- **Legal compliance and protection** — to comply with law, valid legal process, or to protect the rights, property, or safety of Vizelo, our customers, or the public. We notify customers of legal requests for their data unless prohibited by law.
- **Corporate transactions** — in connection with a merger, acquisition, financing, or sale of assets, with notice and protections appropriate to the transaction.

### 6. Sub-processors

Our current sub-processors are:
- **Amazon Web Services** — cloud hosting, storage, and managed databases (United States, with EU and APAC options for enterprise customers).
- **Stripe** — payment processing.
- **Postmark** — transactional email delivery.
- **Cloudflare** — DNS, edge caching, DDoS protection.
- **OpenAI, Anthropic, Google, Microsoft, Perplexity** — the answer engines whose public surfaces we probe to measure citation activity. We do not transmit Customer Data to these engines; we read from their public outputs and store the results.
- **Sentry** — error monitoring.
- **Linear** — internal issue tracking. Customer Data is not stored in Linear.

We post material changes to our sub-processor list and notify enterprise customers in advance of new sub-processors that will process Customer Data.

### 7. International transfers

Vizelo is headquartered in the United States. Information may be transferred to and processed in the United States and other countries where our sub-processors operate. For transfers of personal data out of the EEA, the UK, and Switzerland, we rely on the European Commission's Standard Contractual Clauses and equivalent UK and Swiss addenda, supplemented by technical and organizational measures including encryption in transit and at rest. Enterprise customers can request data residency in EU or APAC regions.

### 8. Retention

- **Account and billing** — retained while your account is active and for up to seven (7) years after closure for tax and accounting purposes.
- **Customer Data** — retained while your account is active. On termination we delete Customer Data within thirty (30) days unless legally required to retain it.
- **Product telemetry** — retained for thirteen (13) months in identifiable form, then aggregated or deleted.
- **Web-server and security logs** — retained for ninety (90) days.
- **Support communications** — retained for three (3) years.

### 9. Security

We protect personal information with administrative, technical, and physical safeguards. Highlights include encryption in transit and at rest, least-privilege access controls, MFA-enforced admin access, per-customer database isolation, audit logging, and regular third-party security audits. Email security@vizelo.ai for our current evidence pack. No system is perfectly secure, and we cannot guarantee absolute security.

### 10. Your rights

Depending on where you live, you may have the right to access, correct, delete, port, restrict, or object to the processing of your personal information, and to lodge a complaint with a supervisory authority. To exercise these rights, email privacy@vizelo.ai from the address associated with your account. We respond within thirty (30) days and will not discriminate against you for exercising your rights.

#### 10.1 California residents (CCPA / CPRA)
In the prior twelve months, we have collected the categories of personal information described in Section 2. We have disclosed personal information only for the business purposes described in Sections 3 and 5. We have not sold or shared personal information for cross-context behavioral advertising. California residents may request access, deletion, correction, and the right to limit use of sensitive personal information by emailing privacy@vizelo.ai. We verify requests using the email associated with your account.

#### 10.2 EU/UK residents
You may contact our EU representative and our Data Protection Officer at dpo@vizelo.ai. You also have the right to lodge a complaint with your local supervisory authority.

### 11. Cookies and similar technologies

We use a small number of strictly necessary and functional cookies on `vizelo.ai` and `app.vizelo.ai`:
- **Session cookies** — to keep you signed in to the application.
- **Preference cookies** — to remember settings like billing-cycle preference (`vz_billing`) on the pricing page.
- **Security cookies** — to mitigate cross-site request forgery and abuse.

We do not use third-party advertising cookies. Where required by law, we request consent before setting non-essential cookies. You can clear cookies in your browser at any time; some features may not work without them.

### 12. Children

The Service is intended for business users and is not directed to children under sixteen. We do not knowingly collect personal information from children. If you believe we have collected information from a child, contact us at privacy@vizelo.ai and we will delete it promptly.

### 13. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes we will notify you by email or by an in-product notice at least thirty (30) days before the changes take effect. The "Last updated" date at the top reflects the most recent revision.

### 14. Contact us

Vizelo, Inc.
Attn: Privacy
Irving, Texas, USA
Email: privacy@vizelo.ai
Data Protection Officer: dpo@vizelo.ai

This document is provided in good faith and reflects the practices of Vizelo, Inc. as of the effective date above. It is not legal advice and is not a substitute for the binding agreement between you and Vizelo.

---

## /terms.html

### Legal

# Terms of Service

The agreement that governs your use of the Vizelo platform. Please read it carefully. By using the Service you agree to these terms.

**Effective date:** May 14, 2026 · **Last updated:** May 14, 2026 · **Version:** 1.0

**Plain-language summary.** You can use Vizelo to monitor and improve how your brand appears in AI answer engines. You own the content you upload; we own our software. Don't abuse the Service, don't target prompts at people without their consent, and pay your bills on time. Enterprise customers can negotiate a separate master agreement that supersedes these terms.

### 1. Acceptance of these terms

These Terms of Service (the "Terms") form a binding agreement between you, or the organization you represent ("Customer," "you," or "your"), and Vizelo, Inc., a Delaware corporation ("Vizelo," "we," "us," or "our"). By creating an account, accessing, or using the Service, you agree to be bound by these Terms and by our Privacy Policy. If you are accepting on behalf of an organization, you represent that you have authority to bind that organization.

### 2. The Service

Vizelo provides software and AI-driven agents that help customers measure, optimize, and grow brand visibility inside AI answer engines, including ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, and Gemini. The Service is provided on a software-as-a-service basis through `vizelo.ai`, `app.vizelo.ai`, and our APIs.

### 3. Accounts and access

- You must provide accurate, current, and complete information when you create an account and keep it up to date.
- You are responsible for safeguarding credentials and for all activity that occurs under your account. Notify us immediately at security@vizelo.ai of any unauthorized access.
- You are responsible for the actions of users you invite to your workspaces.
- You must be at least sixteen (16) years old to use the Service.

### 4. Acceptable use

You agree not to, and not to permit any user or third party to:
- Use the Service in violation of any law, regulation, or third-party right.
- Reverse engineer, decompile, or attempt to extract the source code of the Service, except to the extent permitted by applicable law.
- Resell, sublicense, time-share, or otherwise provide the Service to third parties outside your organization without our written consent (Scale and Enterprise plans permit limited agency use).
- Use the Service to send spam, harass individuals, or target prompts that reveal personal information about identifiable individuals without a lawful basis.
- Probe, scan, or test the vulnerability of the Service except as part of an authorized disclosure program.
- Circumvent rate limits, plan caps, authentication, or other technical restrictions.
- Upload malicious code or content that infringes intellectual property, violates privacy, or is otherwise unlawful.
- Use outputs of the Service to train competing AI models or compile competing datasets.

### 5. Customer Content

"Customer Content" means the data, prompts, briefs, domains, configuration, and other materials you submit to the Service. As between you and Vizelo, you retain all rights, title, and interest in Customer Content.

You grant Vizelo a worldwide, non-exclusive, royalty-free license to host, store, transmit, copy, display, and process Customer Content solely as necessary to provide and improve the Service for you, to prevent or address technical or security issues, and as otherwise permitted by these Terms or your written instructions.

**We do not train AI models on Customer Content.** We do not use Customer Content to develop or improve any model owned or operated by Vizelo or by third parties.

You represent and warrant that you have all rights necessary to submit Customer Content to the Service and to grant the license above, and that Customer Content does not violate any law or third-party right.

### 6. Intellectual property

The Service, including all software, documentation, models, designs, and the Vizelo brand, is owned by Vizelo or its licensors and is protected by intellectual property laws. Except for the limited rights expressly granted in these Terms, we reserve all rights in the Service.

You may provide feedback, suggestions, and ideas about the Service. We may use that feedback freely without obligation to you. Feedback is not considered Customer Content.

### 7. Fees, billing, and taxes

- Paid plans are billed in advance on a monthly or annual basis at the rate shown on the Pricing page or in an order form.
- All fees are non-refundable except as required by law or as expressly stated in these Terms.
- You authorize us and our payment processor to charge the payment method on file. Failed payments may result in suspension after notice.
- Fees do not include taxes. You are responsible for all applicable sales, use, value-added, withholding, and similar taxes, except taxes on our net income.
- We may change our fees with at least thirty (30) days' notice. Changes take effect at your next renewal.
- If you exceed plan usage limits, we will notify you and either pause new probes or, for enterprise customers, bill agreed overage rates.

### 8. Free, beta, and trial features

Free, beta, preview, and trial features are provided as-is and without warranty. We may modify, suspend, or discontinue these features at any time with reasonable notice. Free-plan workspaces may be archived after extended inactivity; we will email you before doing so.

### 9. Term, suspension, and termination

These Terms remain in effect while you use the Service. Either party may terminate this agreement at any time:
- **For convenience** — you may cancel a paid plan from your workspace settings. Cancellation takes effect at the end of the current billing period.
- **For cause** — either party may terminate immediately if the other materially breaches these Terms and fails to cure the breach within thirty (30) days of written notice.
- **Suspension** — we may suspend the Service to investigate security incidents, prevent abuse, or comply with law. We will give notice when reasonably possible.

On termination, your access ends and we delete Customer Content within thirty (30) days, unless legally required to retain it. You may export Customer Content from your workspace before termination.

### 10. Confidentiality

Each party may receive non-public information from the other ("Confidential Information"). Confidential Information includes Customer Content, pricing, technical information, and roadmap details. Each party will use reasonable care to protect the other's Confidential Information and will not disclose it except to employees, contractors, and advisors who are bound by similar confidentiality obligations and have a need to know, or as required by law (with prompt notice where permitted). Confidentiality obligations survive termination for three (3) years, or indefinitely for trade secrets.

### 11. Warranties and disclaimers

We warrant that we will provide the Service with commercially reasonable skill and care.

EXCEPT AS EXPRESSLY STATED IN THESE TERMS, THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE." TO THE MAXIMUM EXTENT PERMITTED BY LAW, VIZELO DISCLAIMS ALL WARRANTIES, EXPRESS, IMPLIED, AND STATUTORY, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, AND QUIET ENJOYMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, OR THAT THE OUTPUTS OF AI ENGINES WE PROBE WILL BE ACCURATE OR UNCHANGED.

### 12. Indemnification

**By Customer.** You will defend, indemnify, and hold harmless Vizelo and its affiliates from third-party claims arising out of (a) your Customer Content, (b) your use of the Service in violation of these Terms or applicable law, or (c) your gross negligence or willful misconduct.

**By Vizelo.** We will defend, indemnify, and hold harmless Customer from third-party claims that the Service, as provided by us and used in accordance with these Terms, infringes a third-party patent, copyright, trademark, or trade secret. Our obligations exclude claims arising from Customer Content, unauthorized modifications, or combinations with non-Vizelo software not authorized by us.

Indemnification is conditioned on prompt notice, sole control of defense and settlement (subject to the indemnitee's reasonable consent), and reasonable cooperation.

### 13. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, LOST REVENUE, LOST DATA, OR BUSINESS INTERRUPTION, WHETHER IN CONTRACT, TORT, OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY.

EACH PARTY'S AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THESE TERMS WILL NOT EXCEED THE GREATER OF (A) THE FEES PAID OR PAYABLE BY CUSTOMER TO VIZELO IN THE TWELVE (12) MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM, OR (B) ONE HUNDRED US DOLLARS ($100).

These limitations do not apply to your obligation to pay fees, indemnification obligations, breaches of confidentiality, or liabilities that cannot be limited under applicable law.

### 14. Governing law and disputes

These Terms are governed by the laws of the State of Texas, excluding its conflict-of-laws rules. The exclusive venue for disputes is the state or federal courts located in Dallas County, Texas, and each party consents to personal jurisdiction there.

Before filing a claim, the parties will attempt in good faith to resolve any dispute through written notice and a thirty (30) day discussion period.

### 15. Changes to these terms

We may revise these Terms from time to time. Material changes will be communicated by email to administrative contacts or through an in-product notice at least thirty (30) days before they take effect. Your continued use of the Service after the effective date constitutes acceptance of the revised Terms. If you do not agree, stop using the Service before the effective date.

### 16. General

- **Entire agreement.** These Terms, along with the Privacy Policy and any order form executed between the parties, are the entire agreement and supersede prior agreements on the subject.
- **Order of precedence.** If there is a conflict, an executed enterprise order form controls over these Terms, which control over the Privacy Policy on subject matter unique to these Terms.
- **Assignment.** You may not assign these Terms without our written consent. We may assign these Terms to an affiliate or in connection with a merger, acquisition, or sale of substantially all of our assets.
- **Notices.** We will give notice by email to the address on your account. You may give notice to legal@vizelo.ai.
- **Force majeure.** Neither party is liable for delays caused by events beyond reasonable control.
- **Independent contractors.** Nothing in these Terms creates a partnership, agency, or employment relationship.
- **Severability.** If a provision is unenforceable, the rest remains in effect.
- **Waiver.** Failure to enforce a provision is not a waiver.
- **Survival.** Sections 5, 6, 10, 11, 12, 13, 14, and 16 survive termination.
- **US Government.** The Service is "commercial computer software" under federal acquisition regulations.

### 17. Contact

Vizelo, Inc.
Attn: Legal
Irving, Texas, USA
Email: legal@vizelo.ai

This document is provided in good faith and reflects the standard terms of Vizelo, Inc. as of the effective date above. It is not legal advice. Enterprise customers may negotiate a separate master agreement that supersedes these Terms.

---

## /glossary.html

### // Glossary

# The AI search vocabulary, plain English.

Five terms you need to argue intelligently about discovery in the answer-engine era. No buzzwords, no filler, no consultant-speak.

### // Entries

## Start here.

#### Generative Engine Optimization (GEO)
Making your brand citable inside ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, and Bing Copilot — not just ranking on Google.
[Read →](what-is-geo.html)

#### Answer Engine Optimization (AEO)
The older, narrower term for optimizing toward direct-answer surfaces like featured snippets, voice assistants, and AI Overviews. GEO's predecessor.
[Read →](what-is-aeo.html)

#### Google AI Overviews
Google's AI-generated answer summaries that sit above the blue links, citing sources inline. The single biggest reason organic CTR cratered in 2025.
[Read →](what-are-ai-overviews.html)

#### Share of Voice (SoV)
The percentage of tracked prompts in your category where an AI engine names or cites your brand. The KPI that replaces keyword rank.
[Read →](what-is-share-of-voice.html)

#### llms.txt
A robots.txt-style plain-text file that points AI engines at your canonical content. Early standard, real adoption, useful even before universal support.
[Read →](what-is-llms-txt.html)

### // Why this exists

## Search didn't die. It got translated.

Every term on this page describes a piece of the same shift: query-and-rank gave way to ask-and-answer. The vocabulary is new because the surface is new. If you're going to operate in it, you should be able to define it in one breath.

## See where you stand in AI search.

---

## /what-is-geo.html

### // Concept

# What is Generative Engine Optimization (GEO)?

GEO is the practice of making your brand citable inside generative answer engines — ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, Gemini — rather than just ranking on Google's blue-link results page.

### // Why it exists

## Why GEO exists.

Roughly 60% of Google searches now end without a click. AI Overviews answer the query directly; ChatGPT and Perplexity answer it before the user ever opens a tab. The traditional SEO funnel — rank, click, convert — has been quietly amputated. What survives is the citation: the moment an engine names your brand inside its answer. GEO is the discipline of earning that mention reliably, across every engine, across every relevant prompt.

### // Difference

## How GEO differs from SEO.

SEO and GEO share infrastructure but optimize for different outcomes. The shift looks like this:

| Dimension | SEO | GEO |
|---|---|---|
| Goal | Rank position | Citation share |
| Unit of measurement | Keyword rank | Prompt-level mentions |
| Content lever | Keyword density & topical depth | Entity clarity & citable claims |
| Technical lever | Crawlability, Core Web Vitals | Schema, JSON-LD, llms.txt |
| Reporting cadence | Weekly / monthly | Hourly per engine |
| Primary competitors | Top 10 SERP | Whoever the engine names |

### // Shape

## What good GEO looks like.

- **Schema markup, everywhere it matters.** Product, FAQ, HowTo, Organization, Article, DefinedTerm. Engines reward sites that hand them structure; they punish sites that hide it.
- **An llms.txt and llms-full.txt.** A canonical map of the content you want ingested, in the format ingestion pipelines actually prefer.
- **Entity completeness.** Your brand, products, founders, and categories defined consistently across your site, Wikipedia, Wikidata, Crunchbase, and LinkedIn so the engine's entity graph resolves cleanly.
- **A monitored citation graph.** You know which engines cite you, for which prompts, against which competitors — and you watch the deltas weekly.

### // Pitfalls

## Common GEO mistakes.

- **Treating it like SEO with new keywords.** Stuffing prompts into H1s doesn't move citation share. Engines extract entities and claims, not phrases.
- **Optimizing for one engine.** The brand that wins ChatGPT often loses Perplexity. A real program tracks all six.
- **Ignoring the off-site graph.** Engines read your Wikipedia, your G2 page, your founder's LinkedIn. If those disagree with your site, the engine picks the wrong one.

### // Vizelo

## How Vizelo operationalizes GEO.

Vizelo measures your brand's share of voice across every major answer engine, finds the prompts where your competitors are winning, ships the schema and content changes that move citations, and re-measures hourly. It is GEO as a working system rather than a quarterly slide deck. Start free to see your current footprint in under a minute.

### // Related

## Keep reading.

- What is AEO?
- What are Google AI Overviews?
- What is share of voice in AI search?
- What is llms.txt?
- Full glossary →

### FAQ

## Common questions.

**How is GEO different from SEO?**
SEO optimizes for rank position on a results page. GEO optimizes for citation inside an AI-generated answer. SEO measures clicks and impressions; GEO measures whether your brand is named, linked, or summarized when the engine answers a buying-intent prompt.

**Do I still need to do SEO?**
Yes. AI engines crawl, rank, and re-summarize the same web. Strong technical SEO — fast pages, clean schema, internal linking — is a prerequisite for GEO, not a replacement for it. GEO is what you do on top once the SEO basics are healthy.

**Which engines does GEO target?**
The six that matter today: ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, and Google Gemini. Each weighs sources differently. A GEO program tracks citation share across all six and surfaces where you're winning and losing.

**Can you do GEO without changing your website?**
Not really. You can monitor without changing anything, but lifting citations almost always requires schema additions, content rewrites, entity-clarification work, and an llms.txt. The site is where the change lands.

**How long does GEO take to show results?**
First citation lifts usually appear within 2–6 weeks of shipping schema and llms.txt work. Compounding gains — moving from sporadic to consistent recommendations across multiple prompts — take a quarter. AI engines reindex at different cadences, so changes show up unevenly.

## Stop guessing whether the engines mention you.

---

## /what-is-aeo.html

### // Concept

# What is Answer Engine Optimization (AEO)?

AEO is the older, narrower discipline of optimizing for direct-answer surfaces — featured snippets, voice assistants, and AI Overviews. GEO is its successor and superset.

### // AEO vs GEO

## AEO vs GEO: which one are you actually doing?

AEO came out of the 2017–2022 era of Google answer boxes: featured snippets, People Also Ask, knowledge panels, Alexa and Google Assistant. It assumed one engine (Google), one playbook (FAQ + HowTo schema, concise definitional copy), and one surface (the SERP). GEO assumes six engines, multi-turn conversation, and citations rather than answer boxes. If you are still talking about featured snippets without also tracking ChatGPT and Perplexity, you are doing AEO. If you are tracking citation share across every major generative engine, you are doing GEO. The right framing in 2026 is to treat AEO as one workstream inside a GEO program, not a competing discipline.

### // Surface

## What AEO covers.

- **Featured snippets.** The boxed paragraph or list Google promotes above organic results for definitional and instructional queries.
- **People Also Ask.** The expanding question stack on Google's results page.
- **Voice assistant answers.** Whatever Alexa, Google Assistant, and Siri read out loud when asked a question.
- **Knowledge panels.** The entity card on the right rail; populated from your structured data, Wikipedia, and Wikidata.
- **Google AI Overviews source cards.** The cited-source row beneath the AI-generated summary. Same playbook, new surface.

### // Blind spot

## What AEO misses.

AEO frameworks were written for one engine. They have nothing to say about how Perplexity weighs source authority, how ChatGPT decides which three brands to name in a recommendation prompt, how Claude handles conflicting sources, or how the citation graph compounds across multi-turn conversations. The schema work AEO recommends still helps. The strategy it implies (rank for the snippet, win the answer) no longer describes the problem.

### // Verdict

## Should you still optimize for AEO?

Yes — but rename it. The schema markup, the concise definitions, the FAQ blocks, the HowTo structure all feed generative engines too. Keep the tactics. Drop the framing. Move your reporting from "do we own the snippet?" to "do the engines name us in answers?" That's GEO with the AEO tactics still inside it. Vizelo tracks both layers in one place.

### // Related

## Keep reading.

- What is GEO?
- What are Google AI Overviews?
- What is share of voice in AI search?
- What is llms.txt?
- Full glossary →

### FAQ

## Common questions.

**Is AEO the same as GEO?**
No. AEO predates the generative-engine era and targets specific Google answer surfaces. GEO is broader: it covers AEO surfaces plus citation behavior across multi-turn AI engines like ChatGPT, Perplexity, and Claude. AEO is a subset of GEO.

**Should you still optimize for AEO in 2026?**
Yes, but think of it as one workstream inside GEO rather than a separate program. The FAQ schema, HowTo schema, and concise question-answer copy that lift AEO performance also feed the generative engines.

**What does AEO actually cover?**
Featured snippets, People Also Ask, voice assistant answers, knowledge panel population, and the source-card layer of Google AI Overviews. Anything where the engine returns a direct answer with a credited source.

**What does AEO miss?**
Cross-engine citation behavior. AEO frameworks were built around Google. They have nothing to say about how Perplexity weighs sources or how ChatGPT chooses which three brands to name when a user asks for recommendations.

## Whatever you call it, measure it.

---

## /what-are-ai-overviews.html

### // Concept

# What are Google AI Overviews?

AI Overviews are Google's AI-generated answer summaries that appear above the traditional search results, citing sources inline.

### // Mechanics

## How AI Overviews work.

When a user submits a query Google judges suitable, the search stack runs the query through a generative model that synthesizes an answer from a small set of retrieved web sources. The result is a paragraph or bulleted summary, displayed at the very top of the results page, with a row of source cards beneath it. The model picks the sources; the user sees the answer first and the citations second — if they look at them at all. Coverage expanded sharply through 2024 and 2025; today AI Overviews appear on a majority of informational queries in supported markets.

### // Impact

## Why they cratered organic CTR.

The blue-link economy assumed the user had to click to get the answer. AI Overviews remove that requirement on a huge fraction of informational queries. Industry CTR studies from 2025 consistently showed organic clicks on AI-Overview-bearing queries down 30–60% versus the same query without one. The pages didn't lose rank; they lost the click. The asymmetry is what makes this a strategic problem rather than a tactical one: even ranking #1 no longer guarantees traffic on the query you used to own.

### // Selection

## How citations are chosen.

Google hasn't published the full ranking signal. From observed behavior, citation selection appears to weight:

- **Entity authority for the topic.** Sites the engine already trusts as authorities in the relevant entity cluster are cited disproportionately.
- **Direct topical match.** Pages that answer the specific sub-question, not just the broad keyword.
- **Clear structure.** Schema markup, semantic HTML, and discrete citable claims are easier for the model to extract.
- **Recency where it matters.** Time-sensitive queries reward freshly updated pages; evergreen queries don't.
- **E-E-A-T signals.** Author bylines, organizational identity, citations to primary sources.

### // Playbook

## How to optimize for AI Overviews.

- **Answer the question in the first 60 words.** Models prefer extractable, self-contained answers near the top of the page.
- **Ship the schema.** Article, FAQ, HowTo, Product, DefinedTerm. Structure is a citation accelerant.
- **Define your entities cleanly.** One canonical name, consistent across your site, Wikipedia, and the open knowledge graph.
- **Publish citable claims.** Specific, attributable, verifiable. Vague marketing copy doesn't get cited; precise data does.
- **Monitor by query, not by keyword.** Track which prompts trigger an AI Overview in your category and which sources Google chose.

### // Related

## Keep reading.

- What is GEO?
- What is AEO?
- What is share of voice in AI search?
- What is llms.txt?
- Full glossary →

### FAQ

## Common questions.

**What are AI Overviews on Google?**
AI Overviews are Google's AI-generated answer summaries that appear above the traditional ten blue links. They synthesize information from multiple web sources and cite those sources inline with linked source cards.

**Did AI Overviews kill organic traffic?**
They didn't kill it, but they meaningfully compressed it. Click-through rates on informational queries dropped sharply through 2024–2025 because users no longer needed to click to get the answer. Buying-intent and high-consideration queries are less affected, but no category is untouched.

**How does Google choose which sources to cite in an AI Overview?**
Google has not published the full ranking, but observed behavior suggests strong weight on entity authority, structured data, direct topical match, recency on time-sensitive queries, and the same E-E-A-T signals that drive organic ranking. Sites with clean schema, clear entity definitions, and citable claims are cited disproportionately often.

**Can you opt out of being used by AI Overviews?**
Partially. The nosnippet meta tag and Google-Extended user agent rules limit some use, but if your page is indexed for normal search, fragments can still appear. The realistic strategy is to optimize for inclusion with attribution rather than opt out.

**Do AI Overviews appear for every query?**
No. They appear most often on informational, definitional, comparison, and how-to queries. They are rarer on navigational queries, on transactional queries where Google prefers shopping units, and on highly local queries dominated by the map pack.

## See which AI Overviews already mention you.

---

## /what-is-share-of-voice.html

### // Concept

# What is Share of Voice in AI search?

Share of voice (SoV) in AI search is the percentage of tracked prompts in your category where an AI engine recommends or cites your brand vs. competitors.

### // Replacement

## Why SoV replaces rank.

Keyword rank measures one position on one page for one query. That worked when users clicked. In an answer-engine world, rank can stay flat while citations vanish: the engine simply paraphrases your competitor and never names you. SoV measures the thing that now drives buyer awareness — whether the machine mentions you when somebody asks it for a recommendation. It rolls many prompts into one number, normalizes across engines, and compares directly against the brands you actually lose deals to. Rank tells you whether your page is reachable. SoV tells you whether your brand is being chosen.

### // Measurement

## How SoV is measured.

- **Per engine.** ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, Gemini each get an independent score. They diverge more than people expect.
- **Per prompt set.** A curated list of 50–500 prompts that represent how real buyers ask about your category. Quality of the prompt set is the whole game.
- **Mention vs citation.** A mention is your brand named in the answer text; a citation is a linked source card. Most useful dashboards track both.
- **Normalized share.** Your mention rate divided by the total brand mentions on the prompt set. That's your percentage of the conversation.
- **Position weighting.** First-mentioned brands compound; being named eighth in a list is worth less than being named first. Weighted SoV captures that.

### // Reading

## Reading a SoV chart.

A useful SoV view shows three things at once: your trendline, your top three competitors' trendlines, and the engine breakdown. Watch the relative shape, not just the absolute number. A flat 22% while two competitors are climbing means you are quietly losing share even though the headline didn't change. A spike on one engine and a flat line on the others usually means a single high-traffic source updated and the rest of the engines haven't recrawled yet — informative, but not yet structural. The signals that matter are sustained, multi-engine moves.

### // Levers

## Lifting SoV: the four levers.

- **Schema.** Structured data the engines can extract without ambiguity. The cheapest lever and usually the fastest to move the needle.
- **Citation-worthy content.** Specific claims, primary data, original frameworks. Engines cite what stands out, not what restates the consensus.
- **Entity completeness.** One canonical brand identity across your site, Wikipedia, Wikidata, Crunchbase, LinkedIn, G2, and the analyst graphs. Disagreement confuses the engine.
- **PR and earned mentions.** Third-party citations on authoritative sites still feed the engines disproportionately. Press hits are still GEO infrastructure.

Vizelo measures all four and ships the changes that lift the score. GEO is the program; SoV is the scoreboard.

### // Related

## Keep reading.

- What is GEO?
- What is AEO?
- What are Google AI Overviews?
- What is llms.txt?
- Full glossary →

### FAQ

## Common questions.

**What is share of voice in AI search?**
Share of voice is the percentage of prompts in a defined category where an AI engine mentions or cites your brand. It is measured per engine, per prompt set, and normalized so it can be compared across categories and competitors.

**How is share of voice different from keyword rank?**
Rank measures position on one results page for one query. Share of voice measures presence inside answers across many prompts and many engines. Rank can stay #1 while SoV drops to zero if the engine summarizes around you instead of citing you.

**What is a good share of voice score?**
It depends on category concentration. In a category with three real players, 25–35% is healthy and 40%+ is leadership. In a fragmented category, 10–15% can already mean you are top three. The score matters less than the trendline against your direct competitors.

**How often should you check share of voice?**
Weekly for normal monitoring, daily during launches or campaigns, hourly when you ship a major content change and want to see how fast each engine reflects it. Engines reindex on different cadences, so any single check can mislead.

**Can you fake share of voice?**
No. AI engines synthesize across many sources; you cannot bid your way in. You can earn share of voice through schema, entity completeness, citation-worthy content, and PR, but you cannot pay for it directly the way you can pay for an ad.

## See your share of voice in under a minute.

---

## /what-is-llms-txt.html

### // Reference

# What is llms.txt?

llms.txt is an emerging plain-text convention, analogous to robots.txt, that tells AI engines which canonical content on your site they should ingest and how.

### // Format

## How llms.txt is structured.

llms.txt lives at the root of your domain and is served as text/plain. It is written in Markdown, intentionally simple, and assumes an LLM is the primary reader. A typical file opens with an H1 of your site or product name, a short summary paragraph, and then a sequence of H2 sections grouping links to canonical pages: documentation, glossary entries, pricing, comparisons, policies. Each link gets a short label. The whole point is to hand the model a hand-curated map instead of letting it guess. Vizelo's own file is at /llms.txt if you want a working example.

### // Variants

## llms.txt vs llms-full.txt.

Two files, two jobs.

- **llms.txt** is the index. Short. Scannable. Links to your most important canonical pages with one-line descriptions. Treat it like a sitemap for LLMs.
- **llms-full.txt** is the bundle. It concatenates the full text of those pages into a single file an LLM can ingest in one read — useful for ingestion pipelines that prefer not to crawl many URLs.

Vizelo publishes both: /llms.txt and /llms-full.txt. Most sites should ship the index first and add the full bundle once the canonical pages stabilize.

### // Contents

## What to put in yours.

- **Identity.** Your brand name, one-line description, and canonical URL. Resolve the entity before you list anything else.
- **Core docs.** Product overview, pricing, comparisons, how the thing works. The pages an evaluator would actually need.
- **Definitional content.** Your glossary, your category-defining pages, your category FAQs. The stuff engines reach for when asked "what is X."
- **Policies.** Privacy and terms, so an engine summarizing your trust posture has the right source.
- **Skip.** Login pages, paginated archives, marketing experiments, anything you wouldn't link a senior buyer to.

### // Reality check

## How AI engines actually use it (today).

Honest read: adoption is early and uneven. Developer-facing ingestion pipelines and several smaller crawlers already read llms.txt. The largest consumer-facing engines have not formally committed to a spec, and their behavior is inconsistent. The reason to ship one anyway is that the cost is near zero, the file improves at least one downstream surface today (developer tools, agents, anyone consuming your docs through an LLM), and the directional bet is obvious: as crawling gets more expensive and ingestion gets more structured, a hand-curated content map gets more valuable, not less. Ship it now, update it quarterly, and treat full-engine support as upside rather than the reason to do it. Vizelo generates and maintains both files automatically as part of your GEO program.

### // Related

## Keep reading.

- What is GEO?
- What is AEO?
- What are Google AI Overviews?
- What is share of voice in AI search?
- Full glossary →

### FAQ

## Common questions.

**What is llms.txt?**
llms.txt is a plain-text file placed at the root of your site that points AI engines and ingestion pipelines at the canonical content you want them to use. It is conceptually similar to robots.txt and sitemap.xml, but written in human-readable Markdown for LLM consumption.

**What's the difference between llms.txt and llms-full.txt?**
llms.txt is the lightweight index — short, scannable, with links to your most important pages. llms-full.txt is the long-form version, containing the actual text of those pages bundled into one file an LLM can ingest in a single read.

**Do AI engines actually read llms.txt today?**
Adoption is early and uneven. Some ingestion pipelines and developer-facing crawlers read it; the largest consumer-facing engines have not formally committed. The file is still worth shipping because the cost is near zero, it improves at least one downstream path today, and adoption is heading the right way.

**Where should llms.txt live?**
At the root of your domain — https://example.com/llms.txt — served as text/plain. Same convention as robots.txt. The llms-full.txt sibling sits next to it.

**Does llms.txt block AI engines from training on my site?**
No. llms.txt is descriptive, not restrictive. It tells engines what you want them to use. For opting out of training, you need user-agent rules in robots.txt and platform-specific controls like Google-Extended, OAI-SearchBot, and equivalents.

## Ship llms.txt without writing it by hand.

---

## /roadmap.html

### // Roadmap

# What we're shipping next.

An honest snapshot of where we're spending our time. Now, Next, and Later — refreshed at least every quarter. Aspirational, not contractual.

### // Q2 2026 · Now

## Now — what we're building this quarter.

Foundational work. We're holding the surface area steady and going deep on accuracy, latency, and the controls enterprise buyers ask about on the first call.

- **SOC 2 Type II.** Audit underway. Targeting completion this quarter so we can stop saying "in progress" on the front page.
- **Citation accuracy v2.** Tightening the probing pipeline for ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, and Gemini. Goal: cut the manual-audit delta to under 2% per engine.
- **Brief Generator quality.** Better entity coverage, fewer false-positive cannibalization flags, and FAQ blocks that actually make it through to publication.
- **Workspace primitives.** Per-client roles, audit log, and white-label export polish for agencies on the Scale plan.

### // Q3 2026 · Next

## Next — what we plan to start.

Committed near-term work. Anything here that doesn't ship in the quarter slides to Later with a note explaining why.

- **Outreach module.** The sixth capability on the homepage. Finds the publications, podcasts, and aggregators the answer engines cite for your category, and helps you pitch them. Templated and personalized; reply tracking included.
- **Engine coverage expansion.** Onboarding additional answer engines as adoption justifies the probe cost. Candidates we're watching: Mistral Le Chat, DeepSeek, and the Brave Search API surfaces.
- **API + webhooks v1.** Pull share-of-voice data and citation snapshots into your own warehouse on a schedule. Subscribe to drop/spike events for any tracked prompt.
- **Public llms.txt builder.** A free tool that produces a starter `llms.txt` and `llms-full.txt` for any domain, with an embedded validator. Pairs with our public glossary as a category-anchor entry point.

### // Later

## Later — directional bets.

Convinced of the direction, not yet committed to the shape. These are the areas where we expect to spend real time over the next year.

- **Vizelo Research.** A microsite with original benchmark data — share-of-voice leaderboards, engine behavior diffs, and quarterly "State of AI Search" reports. Vizelo's answer to the question "where does this data live?"
- **Citation graph explorer.** Interactive viz: pick a prompt, see which domains each engine cites and why. Public for sample prompts, full access for customers.
- **Embeddable visibility badge.** A widget customers can paste into their site (think Trustpilot, for AI citations). Auto-updates from their workspace.
- **Agency tier & marketplace.** A way for vetted Vizelo-trained agencies to list themselves and pick up GEO work from customers who'd rather hire it out than run it in-house.
- **Localization.** Tracked prompts and citations for non-English engines and regional AI products. The category will not stay English-only for long.

### // How we prioritize

## How we decide what ships when.

Three filters, in order. Stage one: **does it move share-of-voice for at least one customer cohort?** If the answer isn't a confident yes with evidence, the feature doesn't enter the queue. Stage two: **is the engine behavior stable enough that we're not building on sand?** AI engines change weekly; some surfaces aren't worth a permanent investment yet. Stage three: **can we ship something measurable in a quarter**, or are we sneaking a multi-quarter project in under a small label? Multi-quarter projects get their own line. Anything that fails all three filters lives in Later until conditions change.

### // Recently shipped

## What landed already.

The changelog is the source of truth for what's in the product today. JSON Feed available for anyone wanting to subscribe machine-readably.

### FAQ

## Common questions about the roadmap.

**Is the roadmap a commitment?**
No. It's an honest snapshot of what we're working on, what we plan to start next, and which directions we believe in. Sequence and timing change as we learn — usually a few times per quarter.

**How can I influence the roadmap?**
Email hello@vizelo.ai with a concrete use case, the workaround you're currently doing, and what would change if we shipped it. Specific beats general — the more grounded the request, the more it weighs in our prioritization.

**Where can I see what already shipped?**
The changelog page lists every meaningful release. The /changelog.json feed is the machine-readable version.

**How often is the roadmap updated?**
We refresh this page at least at the start of every quarter, and mid-quarter when something material changes.

## Want to see this in your workspace?

Free forever tier. Four-minute setup. We start probing the engines within ten.

---

## /badge.html

### // Badge

# Wear it on your site.

A small, embeddable "Tracked by Vizelo.ai" badge. One line of HTML, two colour variants, no JavaScript, no tracking pixel. Just paste it in your footer.

### // Preview

## Two variants. Pick the one that fits.

Dark / default variant and a light variant. Both are SVG badges sized 160×36 with an "Tracked by Vizelo.ai" label that links back to vizelo.ai.

### // Embed

## Copy. Paste. Done.

Drop one of these into your footer, an "as seen in" row, or a `Built with` strip. The link target back to `vizelo.ai` is what makes the badge useful for everyone — please don't strip it.

Dark snippet:
```
<a href="https://vizelo.ai/?ref=badge" rel="noopener">
  <img src="https://vizelo.ai/assets/badge.svg"
       alt="Tracked by Vizelo.ai"
       width="160" height="36" loading="lazy" />
</a>
```

Light snippet:
```
<a href="https://vizelo.ai/?ref=badge" rel="noopener">
  <img src="https://vizelo.ai/assets/badge-light.svg"
       alt="Tracked by Vizelo.ai"
       width="160" height="36" loading="lazy" />
</a>
```

### // Why embed it

## Three reasons people use it.

- **Signal seriousness.** Putting the badge on your site tells visitors (and AI crawlers visiting your page) that you measure your AI-search visibility. In the answer-engine era, that's the equivalent of a Trustpilot or G2 badge ten years ago.
- **Mutual link equity.** Every embed is a backlink to `vizelo.ai` — and the page hosting the badge accumulates entity-association signals with us. Net positive on both sides if you use it where it makes sense.
- **Conversation starter.** Most people clicking the badge end up at our homepage and learn what GEO actually is. If your audience overlaps with ours, you're doing them a favour.

### // Rules of use

## Be cool about it.

- **Keep the link.** The badge has to link back to `vizelo.ai`. Stripping the link or changing the target defeats the point.
- **Don't recolor.** Keep the SVG as-is. If our palette clashes with yours, the light variant works on most backgrounds.
- **Don't imply an endorsement.** The badge means "I track my AI-search visibility with Vizelo." It doesn't mean we vouch for your service.
- **Don't self-host.** Link directly to `https://vizelo.ai/assets/badge.svg` so you always get the latest version when we update.

### FAQ

## Common questions.

**Do I need an account to use the badge?**
No. The badge is a static asset you can embed anywhere. We don't track who embeds it. If you want a customer-only variant later (one that pulls your live share-of-voice number) we'll ship that on the Outreach + API milestone.

**Can I change the colors or size?**
We ship a dark and a light variant. Keep the badge readable: minimum 120px wide for the standard layout. For colors, please don't recolor — recolored variants are off-brand. If you need a different palette, email hello@vizelo.ai.

**Will this slow my page down?**
It's a single SVG, well under 1 KB on the wire after gzip. Loaded via a normal `<img>` tag, it doesn't block render and doesn't ship any JavaScript.

**Is using the badge implying an endorsement?**
It implies that you use Vizelo to track your AI-search visibility. It does not imply a partnership, certification, or that Vizelo endorses your specific service. Don't claim a relationship beyond what's accurate.

## Don't use Vizelo yet?

Sign up free, connect your domain in four minutes, then earn the badge.

---

## /answers.html

### // Answers

# AI search, answered honestly.

The questions every marketing lead, founder, and SEO asks once they realize ChatGPT is eating the funnel. Direct answers. No hedging, no jargon.

### // Questions

## Start here.

#### How do I rank in ChatGPT?
ChatGPT doesn't have a ranking algorithm in the SEO sense. What it has are retrieval and citation patterns — and four levers that actually shift them.
[Read →](how-to-rank-in-chatgpt.html)

#### How does Perplexity decide which sources to cite?
Perplexity is the most citation-transparent engine in the market. Here's what we've learned about its retrieval, ranking, and source-selection signals.
[Read →](how-perplexity-chooses-citations.html)

#### Why aren't my pages cited by ChatGPT?
Five-step diagnostic for brands that suspect they're invisible inside the answer. Most failures are mechanical, not creative.
[Read →](why-am-i-not-cited-by-chatgpt.html)

#### How do I track when AI engines cite my brand?
Why Google Search Console can't see it, why manual checking doesn't scale, and what a real AI-citation tracking pipeline actually measures.
[Read →](how-to-track-ai-citations.html)

#### Do AI engines respect robots.txt?
Mostly yes, with caveats. Which named crawlers honor it, which don't, and what blocking actually accomplishes once your content is already in the training data.
[Read →](do-ai-engines-respect-robots-txt.html)

### // Why this exists

## Ahrefs and Semrush won't save you here.

The questions on this page didn't exist five years ago. The dashboards built to answer the last era's questions can't answer them now. So we wrote down what we've learned from tracking citations across every major engine — in the plainest English we could manage.

## See where you stand in AI search.

---

## /how-to-rank-in-chatgpt.html

### // Answer

# How do I rank in ChatGPT?

You don't — not in the SEO sense. ChatGPT doesn't rank pages; it retrieves, cites, and echoes. Four levers decide whether it names you: schema, llms.txt, entity completeness, and citable content.

### // Premise

## ChatGPT doesn't have a ranking algorithm.

The question conflates two things. There is no ChatGPT SERP, no PageRank-equivalent, no public scoring function that orders results. What there *is* is a generation process — and that process draws on three different sources of facts about your brand. Live retrieval through the browsing tool, which is Bing-backed and queries the open web at request time. In-context retrieval from sources the model pulled into a specific response. And statistical recall from the training corpus, frozen at whatever cutoff the active model version uses. You "rank" in ChatGPT the way a quote ranks in a journalist's article: you're named because something about you made the writer reach for you. The job is to be reachable.

### // Mechanics

## What ChatGPT cites and why.

When ChatGPT browses, it issues a query, ranks candidate URLs (Bing's ranker, mostly), fetches a handful, extracts spans, and feeds them into the prompt. Two things decide whether your page makes that shortlist: how the search engine ranks it, and how legible the page is once fetched. The first is regular technical SEO — crawlability, freshness, link graph, query-intent match. The second is new: schema, headings, claim density, semantic structure. A page that's ranked #4 on Bing but parses cleanly often beats a page ranked #1 that hides its content inside a JavaScript framework. When ChatGPT isn't browsing, it falls back to training-data echo: your brand is named because it appeared often enough, in clearly enough described contexts, that the model learned the association. That part you influence by being everywhere — consistently, with the same name and the same category claim.

### // Levers

## The four levers that actually move the needle.

- **Structured data.** JSON-LD for Organization, WebSite, Article, FAQPage, HowTo, Product, Offer, BreadcrumbList, and DefinedTerm. The engine doesn't guess what your page is about when you've told it.
- **An llms.txt manifest.** A flat, parseable list of your canonical content. Ingestion pipelines prefer it because it's cheaper to crawl than your sitemap and richer than your robots.txt.
- **Entity completeness.** Your brand should resolve as one entity, not three. Same legal name on Crunchbase, Wikidata, LinkedIn, and your site. Same one-sentence category claim on your About page, your G2 listing, and your Wikipedia article.
- **Citable content.** Short, specific, claim-dense sections an LLM can lift into an answer without rewriting. "The five engines that matter are X, Y, Z, A, B" beats "In today's rapidly evolving AI landscape…" every time.

### // Mistakes

## Common mistakes.

- **Stuffing prompts into H1s.** ChatGPT extracts entities and claims, not phrases. "Best CRM for startups 2026" in your H1 doesn't make you the best CRM for startups in 2026.
- **Ignoring schema.** The single largest gap between brands that get cited and brands that don't is JSON-LD coverage. It is unglamorous, mechanical work, and it dominates.
- **No llms.txt.** It costs an afternoon to ship and it's the cheapest legible signal you can send.
- **Optimizing for ChatGPT only.** The brand that wins ChatGPT often loses Perplexity. Operate cross-engine or get blindsided.

### // Measurement

## How to know if it's working.

Search Console can't see this. You need a tracker that runs your category's prompts against ChatGPT — with browsing on and off — logs whether your brand is named, and watches the deltas. Tracking AI citations covers the mechanics. Vizelo runs this hourly across ChatGPT and the five other engines that matter, then surfaces the prompts where your share of voice is moving up, down, or flat. Start free to see your current footprint.

### // Related

## More answers.

- How does Perplexity decide which sources to cite?
- Why aren't my pages cited by ChatGPT?
- How do I track when AI engines cite my brand?
- Do AI engines respect robots.txt?
- All answers →

### FAQ

## Common questions.

**Is there a ChatGPT ranking algorithm I can optimize for?**
No. ChatGPT decides what to say through a mix of training-data recall, retrieval (its browsing tool is Bing-backed), and the in-context sources it pulls into a single response. There is no public PageRank-equivalent. You optimize the inputs — schema, llms.txt, entity graph, citable content — not a ranking function.

**How long until ChatGPT starts citing me after I make changes?**
Browsing-tool retrieval reflects changes within days, sometimes hours. Training-data echo only updates with new model versions, so changes there can take months. Most of the lift you'll measure in the first quarter comes from the browsing path.

**Do I need a Wikipedia page to rank in ChatGPT?**
No, but you need entity completeness — your brand needs to be findable and described consistently somewhere the engine trusts. Wikipedia and Wikidata help, but well-structured Crunchbase, LinkedIn, and G2 pages plus an Organization schema on your own site cover most of the gap.

**What schema types matter most for ChatGPT visibility?**
Organization and WebSite for the site itself; Article, FAQPage, and HowTo on content pages; Product and Offer on commercial pages; DefinedTerm on glossary entries; BreadcrumbList everywhere. The goal is to hand the engine pre-parsed facts so it doesn't have to guess.

**Can I rank in ChatGPT without writing new content?**
Sometimes. Adding schema, fixing entity issues, and shipping an llms.txt can lift citations on existing content. But if your category's winning answers are claim-dense and yours are vague, you'll need to rewrite for citability.

## Find the prompts where ChatGPT isn't naming you.

---

## /how-perplexity-chooses-citations.html

### // Answer

# How does Perplexity decide which sources to cite?

It runs a retrieval-augmented pipeline against multiple search backends, ranks candidates, fetches a shortlist, and cites the spans it actually used. Recency, structural clarity, and citation-graph density move the needle most.

### // Pipeline

## How Perplexity's retrieval works.

Perplexity is the most citation-transparent engine on the market — every answer ships with inline source links, which is a gift to anyone trying to reverse-engineer its behavior. The pipeline is recognizably retrieval-augmented generation. A user query is rewritten into one or more search queries. Those queries hit multiple backends — Perplexity's own crawler index (PerplexityBot) plus syndicated search APIs — and a candidate set is assembled. The candidates are reranked, a shortlist is fetched, spans are extracted, and a language model writes the answer over those spans, attaching citations to the URLs whose content actually contributed. The exact blend between Perplexity's own index and third-party APIs isn't published, but the practical implication is that both being directly indexed by PerplexityBot *and* ranking well on the major engines compound — they feed different paths into the same answer.

### // Signals

## The signals that get you cited.

- **Recency.** For any query with a recency dimension — news, releases, prices, comparisons, "best of 2026" — Perplexity disproportionately favors content updated in the last 90 days. Same URL, fresher date, more citations.
- **Authority.** Domain trust still matters. Pages on established domains get fetched and surfaced more often than equivalent content on new ones. The familiar SEO authority signals (link graph, content depth, brand mentions) carry across.
- **Structural clarity.** Pages that are easy to parse — clean HTML, real headings, FAQ and Article schema, content rendered server-side — convert into citations at a higher rate than equivalent content trapped inside JS-heavy SPAs.
- **Query-intent fit.** Perplexity rewards specificity. A page that answers the exact question wins over a more comprehensive page that buries the answer in section seven.
- **Citation graph density.** Pages that are themselves cited by other trusted sources (G2, Reddit, Wikipedia, established blogs) show up as citations more often. The web that cites itself gets cited again.
- **Claim density.** Content with short, specific, attributable claims is easier for the extractor to lift. "Perplexity surfaces three-to-six citations per answer" is a usable span. "Perplexity has emerged as a major player in the AI search landscape" is not.

### // What we've measured

## What we've measured across the citation graph.

Tracking citations at scale across thousands of category-relevant prompts, a few patterns hold. Recency edges out raw authority on time-sensitive queries — a one-week-old article on a smaller site routinely beats a two-year-old article on a household name. Pages with explicit FAQ or HowTo schema get cited at a higher rate than visually equivalent pages without it. And Perplexity surfaces a wider, longer-tail set of sources per answer than ChatGPT does — you don't need to be in the top three to be cited; the top eight or ten often is enough.

### // Cross-engine

## Optimizing for Perplexity vs cross-engine.

The fundamentals are the same across engines — good GEO is good GEO. But the emphasis tilts. Perplexity over-rewards **recency and crawlable HTML**. ChatGPT over-rewards **training-data presence and entity completeness**. Google AI Overviews lean heavily on the existing SERP. Treat each engine as a separate distribution problem with shared infrastructure, then watch which lever moves which engine for which prompts. Tracking AI citations covers the measurement side. Start free to see how often Perplexity cites you today.

### // Related

## More answers.

- How do I rank in ChatGPT?
- Why aren't my pages cited by ChatGPT?
- How do I track when AI engines cite my brand?
- Do AI engines respect robots.txt?
- All answers →

### FAQ

## Common questions.

**Does Perplexity use its own search index or a third-party one?**
Both. Perplexity operates its own crawler (PerplexityBot) and index, and it also queries third-party search APIs. The exact blend isn't disclosed publicly, but the result is that getting indexed by Perplexity directly and getting ranked on the major search engines are both useful — they feed different paths into the same answer.

**How important is recency for Perplexity citations?**
Very, for time-sensitive queries. Perplexity disproportionately surfaces content published or updated within the last 90 days when the question implies recency (news, releases, prices, comparisons). A stale page on the same URL often loses to a fresher competitor.

**Does schema markup help on Perplexity specifically?**
Yes. Schema doesn't directly trigger a citation, but it makes your page easier and cheaper to parse, which raises the odds your span gets selected when Perplexity extracts content. FAQPage, Article, and Product schema are the highest-leverage.

**Should I optimize for Perplexity differently than ChatGPT?**
Mostly the same fundamentals — schema, claim density, entity completeness — but the emphasis differs. Perplexity rewards recency and crawlable HTML more than ChatGPT. ChatGPT rewards training-data presence more than Perplexity. A real GEO program tracks both and reports the deltas.

**Can I see who Perplexity is citing for a query?**
Yes — Perplexity shows inline citations under every answer, which is the most transparent surface in the AI search market. Vizelo tracks those citations at scale across thousands of prompts so you can see which sources Perplexity prefers in your category over time.

## See who Perplexity cites in your category today.

---

## /why-am-i-not-cited-by-chatgpt.html

### // Answer

# Why aren't my pages cited by ChatGPT?

Almost always one of five mechanical things: you're chasing the wrong KPI, the crawler can't read you, your schema is thin, your entity is ambiguous, or nobody trusted is talking about you yet. Diagnose in that order.

### // Step 1

## Confirm you're trying to be cited, not ranked.

Citation and rank are different objectives. Citation is "the engine named me inside the answer." Rank is "my URL is on a list of links." ChatGPT mostly does the first and only sometimes does the second — and a brand that's great at ranking can be terrible at being cited because it relies on link-bait pages, vague positioning, and JavaScript frameworks. Decide which KPI you're solving for before you start changing things. The fix sets overlap, but they're not identical.

### // Step 2

## Check that crawlers can actually read your page.

The most common silent failure. Open your robots.txt and look for explicit disallows against GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, ClaudeBot, and Google-Extended. Some teams blocked these in 2024 and never went back. Then load a representative page in a browser with JavaScript disabled. If your headline, body copy, and key facts disappear when JS is off, the in-browsing crawler that ChatGPT uses to extract spans can't see them either. Server-side render or use a static build for content pages. Whether AI engines respect robots.txt covers the crawler side in more depth.

### // Step 3

## Check your schema.

If your high-value pages don't emit JSON-LD, you're forcing the engine to guess what they're about. Use a schema validator and confirm each high-stakes page emits the right type: Organization and WebSite at the root, Article on content pages, FAQPage on anything with question-and-answer structure, Product and Offer on commercial pages, DefinedTerm on glossary entries, BreadcrumbList for navigation. The goal isn't schema for SEO's sake. It's handing the model your facts pre-parsed so it doesn't have to extract them under pressure.

### // Step 4

## Check your entity completeness.

Open Wikidata, Crunchbase, LinkedIn, G2, and your About page side by side. Is your legal name the same on all five? Is your category claim the same one sentence in all five places? Are your founders, headquarters, and founding date consistent? Brands that fail this audit usually have the same problem: the engine resolves them as two or three different entities, or as a single entity with conflicting descriptions, and silently demotes them. The fix is consistency, not creativity — same name, same category, same one-line description, same domain across every public surface that describes you.

### // Step 5

## Check your link and citation graph.

If steps 2–4 are clean and you're still not being cited, the bottleneck is almost always here. The engines you're trying to win lean on the same handful of trust signals the rest of the web does: who links to you, who reviews you, who writes about you on G2, Reddit, Hacker News, Wikipedia, and established trade press. If you're a category newcomer with zero of those, no amount of schema will rescue you in the short term. Earn the citations off-site, then watch them feed back into the on-engine ones. Tracking AI citations is how you tell whether the inputs are converting into outputs. Start free to see your current footprint.

### // Related

## More answers.

- How do I rank in ChatGPT?
- How does Perplexity decide which sources to cite?
- How do I track when AI engines cite my brand?
- Do AI engines respect robots.txt?
- All answers →

### FAQ

## Common questions.

**How do I know if ChatGPT can even crawl my site?**
Check your robots.txt for explicit blocks against GPTBot, ChatGPT-User, and OAI-SearchBot. Then load a representative page with JavaScript disabled — if your main content disappears, ChatGPT's parsing path can't see it either, even when browsing is on.

**Is being missing in ChatGPT the same as not ranking on Google?**
No, though they correlate. You can rank on Google and still not be cited by ChatGPT — the engine extracts and rewrites rather than linking, and it weighs schema, entity clarity, and content structure differently. The fix set overlaps but isn't identical.

**How much schema is enough?**
Organization and WebSite at the site level. Article on every content page. FAQPage on pages with Q&A. Product and Offer on commercial pages. BreadcrumbList everywhere. If your highest-stakes pages have none of those, schema is your first fix, not your last.

**Why does my brand resolve as the wrong thing?**
Usually entity collision — another company with a similar name, or your old name still cached, or inconsistent category claims across listings. The fix is consistency: same legal name, same one-line category, same domain in your Crunchbase, LinkedIn, Wikidata, and Organization schema. Force the engine to disambiguate in your favor.

**How long after I fix things should I expect citations to appear?**
Browsing-path citations can shift within days. Training-data citations only refresh on new model versions. Most teams see meaningful movement in 2–6 weeks for browsing-tool answers and across a quarter for steady-state visibility.

## Run the diagnostic against your real footprint.

---

## /how-to-track-ai-citations.html

### // Answer

# How do I track when AI engines cite my brand?

Not by Googling. AI answers are sessioned, personalized, and ephemeral — you need a clean-room pipeline that runs your prompt set against every engine on a fixed cadence and aggregates what it finds.

### // Why it's hard

## Why you can't just Google it.

AI engines don't behave like a SERP. The answer you see when you ask is shaped by your session, your location, your prior conversation, your account's personalization, and the random sampling that makes generation interesting. Two people can ask the same question and get different brands cited. The same person can ask twice in the same hour and get different answers. Search Console doesn't see any of this. Ahrefs doesn't see any of this. The surface is real, the impact on demand is real, and the only way to measure it is to build — or buy — a pipeline that re-runs your prompts under controlled conditions and aggregates over enough samples to be meaningful.

### // Manual

## Manual tracking and why it doesn't scale.

The first move every team makes is logging into ChatGPT once a week and typing "best CRM for early-stage startups." This will work for a month. It will not work at scale. You can't cover six engines, hundreds of buyer-intent prompts, three languages, and weekly cadence by hand. You can't reproduce results. You can't aggregate. And you can't catch a competitor pulling ahead in week three because you only checked twelve of your three hundred prompts. Manual is fine for spot-checks. It is not a measurement program.

### // What to measure

## What a real tracking pipeline measures.

- **Share of voice.** The percentage of tracked prompts in your category where an engine names or cites you. The single most useful headline number.
- **Citation count and rank.** When you're cited, where in the answer? First citation versus seventh matters more than it should.
- **Sentiment toward your brand.** Being named neutrally is fine. Being named as the cautionary tale is not. A real tracker labels the polarity.
- **Sources cited in your place.** The most actionable number nobody else gives you: which competitors and which third-party sites win the citations you should be winning?
- **Cross-engine deltas.** Where Perplexity loves you but ChatGPT doesn't, you have a known asymmetry to investigate.
- **Time series.** The point of measurement is movement. A snapshot is decoration; a trend line is operations.

### // Buying checklist

## What to look for in a tracking tool.

- **Engine coverage.** ChatGPT, Perplexity, Google AI Overviews, Bing Copilot, Claude, Gemini. If a tool covers three of those, you'll learn a third of the answer.
- **Prompt density.** Tracking thirty prompts is theater. Tracking hundreds across the buyer journey is operating.
- **Citation graph visibility.** The tool should tell you not just whether you were cited but who was cited instead.
- **Accuracy validation.** Does the tool periodically verify its extractions against the actual engine output? AI engines change formats. Trackers that don't validate drift.
- **Cadence.** Daily at minimum on high-stakes prompts. Weekly is the floor for the long tail.

### // Vizelo

## Vizelo's approach.

Vizelo runs your category prompt set against every major answer engine on an hourly cadence, normalizes the citation data, and surfaces share of voice, the sources cited in your place, and the deltas that matter week over week. It's GEO measurement built to operate from rather than report on. Start free to see your current footprint in under a minute.

### // Related

## More answers.

- How do I rank in ChatGPT?
- How does Perplexity decide which sources to cite?
- Why aren't my pages cited by ChatGPT?
- Do AI engines respect robots.txt?
- All answers →

### FAQ

## Common questions.

**Can Google Search Console show me ChatGPT citations?**
No. Search Console reports on Google Search and Google Discover. It has nothing to say about ChatGPT, Perplexity, Claude, or any non-Google engine. Some Search Console reporting on AI Overviews exists but it's limited to the Google surface.

**Why doesn't manual checking work?**
Answers are personalized to your session, location, and prior conversation. Two people asking the same question get different answers. You can't generalize from a single laptop. You need a clean-room prompt run that's reproducible, repeated, and aggregated across hundreds or thousands of prompts.

**What's the difference between a citation and a mention?**
A citation is a linked source under the answer (most explicit on Perplexity and AI Overviews). A mention is your brand named inside the answer text, with or without a link. Both matter. A good tracker reports both and labels them clearly.

**How many prompts should I be tracking?**
Enough to be statistically meaningful and to cover the buyer journey: category-defining queries, comparison queries, jobs-to-be-done queries, and brand queries. For most B2B categories that lands between 100 and 1,000 prompts per language.

**How often should the prompt set re-run?**
Daily at minimum for high-stakes prompts, weekly for the long tail. AI engines change fast enough that monthly cadence is too slow to catch movement, and quarterly is decorative.

## Track citations across every engine that matters.

---

## /do-ai-engines-respect-robots-txt.html

### // Answer

# Do AI engines respect robots.txt?

Mostly yes. The named crawlers from OpenAI, Anthropic, Perplexity, Google, and Microsoft honor it. The caveats are third-party scrapers, the persistence of training data already collected, and the difference between blocking a crawl and being absent from an answer.

### // Honors robots.txt

## Which crawlers honor it.

Every major vendor with a public AI product publishes the user agents it crawls under and commits to honoring robots.txt. The list as of 2026: OpenAI ships **GPTBot** (training-data crawler), **ChatGPT-User** (live browsing from a ChatGPT session), and **OAI-SearchBot** (indexing for ChatGPT search). Perplexity ships **PerplexityBot** (indexing) and **Perplexity-User** (live retrieval). Anthropic ships **ClaudeBot** and, separately, **anthropic-ai** for various data-collection paths. Google ships **Google-Extended** to give publishers a way to opt out of Gemini training while still being indexed by regular Googlebot. Microsoft uses **Bingbot**; the AI surfaces on Bing inherit Bingbot's rules. ByteDance, Apple, and Meta all maintain their own AI-related agents. In practice these named crawlers do what they say they'll do — the headers identify correctly and the disallow directives stick.

### // Doesn't honor it

## Which ones might not.

The honest answer: anyone who decides not to. Robots.txt is a convention, not a fence. The biggest practical exposures are third-party scrapers that feed open dataset aggregators — the corpora that get reused as training inputs across many models — and smaller commercial scrapers that crawl on behalf of analytics products. Common Crawl (**CCBot**) does honor robots.txt, and its archives are a frequent ingredient in foundation-model training, but content that escaped into derivative datasets before you blocked it can persist in places you can't reach. There's also a steady supply of unbranded scrapers that ignore robots entirely; those are the ones that pay no attention regardless of what your file says, and the only defense against them is server-level rate limiting, auth, or accepting the risk.

### // What blocking does

## What allow / disallow means in practice.

Three things to keep separate. First, disallowing a training-time crawler (GPTBot, Google-Extended, ClaudeBot in its training role) keeps you out of *future* training data. It does nothing to content already in earlier model versions. Second, disallowing a query-time crawler (ChatGPT-User, OAI-SearchBot, Perplexity-User) keeps you out of *live answers* — you become invisible at the moment the engine tries to fetch and cite you. Third, none of this affects what the model has memorized statistically from past training. A model can still echo your brand by name based on training-data exposure even when every active crawler is blocked. Blocking is a forward-looking control, not a reset button.

### // Recommended setup

## The right setup for most sites.

If your goal is to be cited — the goal for almost every commercial site — allow the query-time bots. GPTBot in its retrieval role, ChatGPT-User, OAI-SearchBot, PerplexityBot, Perplexity-User, ClaudeBot, Google-Extended. Each one of those is a path into an answer. Disallowing them is choosing invisibility. Make a conscious, separate decision about training-time inclusion: if you write content you don't want repurposed wholesale, you can disallow training-only crawlers without giving up live citation. Pair the robots.txt with an llms.txt that points engines at your canonical content; the combination is what we recommend, and it's what we run on vizelo.ai itself. Start free to see how your robots and llms configuration affects what engines actually do with you.

### // Related

## More answers.

- How do I rank in ChatGPT?
- How does Perplexity decide which sources to cite?
- Why aren't my pages cited by ChatGPT?
- How do I track when AI engines cite my brand?
- All answers →

### FAQ

## Common questions.

**What's the difference between GPTBot and ChatGPT-User?**
GPTBot is OpenAI's training-data crawler. ChatGPT-User is the user agent ChatGPT uses when a user's session triggers a live browsing fetch. OAI-SearchBot powers the indexing behind ChatGPT's search features. Blocking each one has a different consequence: blocking GPTBot keeps your content out of future training; blocking ChatGPT-User and OAI-SearchBot blocks live citation in real answers.

**If I disallow GPTBot, will my brand still appear in ChatGPT?**
Maybe. Content already in the training corpus before you disallowed it can still be echoed. Live browsing via ChatGPT-User is a separate channel — if you allow that bot, the model can still fetch you at query time. Most brands shouldn't block both unless they have a specific reason to be invisible.

**Do Common Crawl and other scrapers honor my robots.txt?**
Common Crawl (CCBot) honors robots.txt, and its corpus is a frequent ingredient in foundation-model training. But many smaller scrapers that aggregate or repackage web data have historically been less consistent, and content that escapes into derivative datasets can persist in places you can't unwind.

**Does blocking AI crawlers protect me from being copied?**
It reduces but doesn't eliminate the risk. Robots.txt is a polite signal, not a security perimeter. If you have content that genuinely can't be public, putting it behind authentication is the right control. Robots.txt is for shaping legitimate crawler behavior.

**What's a sensible default robots.txt setup for an AI-aware site?**
Allow the query-time bots (GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, Perplexity-User, ClaudeBot, Google-Extended) because being citable is the goal. Optionally disallow training-time-only crawlers on content you don't want repurposed wholesale, and use server-level rate limits or auth for anything sensitive. Then ship an llms.txt to point engines at your canonical content.

## Make sure your robots config isn't the reason you're invisible.

---

## Metadata

- Last reviewed: 2026-05-26
- Source: https://vizelo.ai/
- Generated for: AI ingestion (ChatGPT, Perplexity, Claude, Gemini, Copilot)
- License: All rights reserved, Vizelo Inc. May be quoted with attribution.