Documentation

Getting Started

Everything you need to go from access to your first GEO audit and hallucination sweep.

Quick Start

Get access, run your first GEO audit, and optionally connect your store for catalog-grounded checks.

1

Request access

Discover is not open for self-serve sign-up yet. Use Request beta access on the Discover page. Accepted members get a dashboard account.

Until then, the free AI visibility check and hallucination scanner run on a single URL without an account.

2

Submit your first GEO audit

Go to Discovery, then Audits, paste a product page URL, and click Run Audit. The scorecard appears in your audit list when the scan completes.

3

Connect your store (optional)

A connected catalog lets Discover check AI answers against your real product data and deploy approved schema patches. Skip this step to audit public URLs only.

Shopify. Go to your Shopify Admin, then Settings, then Notifications, then Webhooks. Add a webhook pointing to your VritantAI endpoint:

https://api.vritantai.com/api/v1/integrations/shopify/webhook
HMAC secret: (shown in your VritantAI dashboard → Settings → Integrations)

WooCommerce. Install the VritantAI plugin from the .zip in your dashboard, then connect it with your API key:

  1. Download the VritantAI plugin .zip from your VritantAI dashboard (Settings, then Integrations, then Download WooCommerce plugin).
  2. In your WordPress admin, go to Plugins, then Add New, then Upload Plugin. Click Choose File, select the .zip you just downloaded, then click Install Now.
  3. Click Activate once the install finishes.
  4. In the WordPress sidebar, open WooCommerce, then VritantAI.
  5. Copy your API key from your VritantAI dashboard (Settings, then Integrations), paste it into the API key field, and click Save changes. The plugin verifies the key and subscribes the product webhooks for you.

A one-click install from the WordPress.org plugin directory is on the way and not yet available. Until that listing is published, the .zip upload above is the way to install the plugin.

4

Trigger your first catalog sync

Navigate to Data Hub in your VritantAI dashboard and click Sync Catalog. Product ingestion typically completes in 2 to 5 minutes for stores with fewer than 10,000 SKUs. Hallucination sweeps compare AI answers against this synced catalog.

GEO Optimisation

Read your GEO score, work the issue queue, and approve schema patches. Discover diagnoses and proposes fixes; it does not promise rankings, citations, or traffic.

1

Understand your GEO score

Your GEO score is a weighted composite: Schema Markup (50%), Page Performance (30%), Entity Coverage (20%). Scores above 80 indicate strong structured-data health.

2

Review the issue queue

Each audit surfaces a prioritised list of issues. Critical issues are the largest structured-data gaps and should be addressed first.

3

Add JSON-LD Product schema

VritantAI auto-generates a patch with the correct schema. Here's an example of the Product schema it produces:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Brooks Ghost 16 Wide Running Shoe",
  "description": "DNA LOFT cushioning, engineered mesh upper, 2E width",
  "sku": "GHOST16-2E-BLK-105",
  "brand": {
    "@type": "Brand",
    "name": "Brooks"
  },
  "offers": {
    "@type": "Offer",
    "price": "114.95",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "image": "https://example.com/ghost16-black.jpg"
}
4

Approve, apply, and benchmark

Navigate to Discovery, then Audits, then [audit ID] and click Approve, then apply the approved changes in your store admin (applying them from Discover is on the roadmap). Then run a benchmark under Discovery, then Citations: VritantAI queries Perplexity, OpenAI API, Gemini API, Claude API, and DeepSeek APIand reports mention rates with each provider's evidence mode.

Hallucination Monitor

Detect and address fabricated claims about your brand before they reach customers.

1

Configure your sweep schedule

Go to Discovery, then Hallucination Monitor, then Configure. Set your preferred sweep frequency (daily or weekly) and the LLMs to query. All 5 providers are queried by default.

2

Define your query seeds

Add the product queries most likely to surface your brand. Examples: “best wide running shoes for men”, “[brand name] ingredient list”, “[product name] reviews”.

3

Review events as they arrive

Each sweep generates hallucination events with severity (Critical, Warning, Info), exact extracted claims, and a side-by-side comparison to your catalog ground truth.

4

Resolve or dismiss events

Mark events as Resolved once corrective action has been taken (for example, updated copy, patched schema). Dismiss low-severity events that are not actionable.