What exactly is AiVIS Cite Ledger?

AiVIS Cite Ledger is an evidence-backed AI citation audit and remediation system. It measures how AI models, ChatGPT, Perplexity, Claude, and Google AI, interpret, trust, and cite your web content. The result is a 0–100 CITE LEDGER score across ten weighted families (avs-v3), with BRAG evidence-linked findings and prioritized fixes.

How is this different from Semrush, Ahrefs, or Clearscope?

Traditional SEO tools optimize for keyword ranking in traditional search results. AiVIS Cite Ledger audits citation readiness, the specific signals that determine whether AI answer engines retrieve and cite your content. A page can rank #1 on Google and be completely invisible to AI answer synthesis.

What is BRAG and how does it make findings trustworthy?

BRAG stands for Based-Retrieval-Auditable-Grading. It ties every audit finding to a real, traceable element on your page, a specific heading, schema block, meta tag, or content section, each carrying a unique evidence ID. You can open the element, verify the finding, and recheck it after a fix. No black boxes.

Is the free tier genuinely useful, or just a teaser?

The Observer (free) plan gives you a full composite CITE LEDGER score and all ten family scores (avs-v3), so you can see exactly where you stand and which categories are hurting you. BRAG evidence IDs and prioritized fix packs require a paid plan. Three audits per month, no credit card.

JavaScript Rendering Blocks AI Crawlers | AiVIS Cite Ledger

AI crawlers fetch HTML and leave. They don't run your JavaScript bundles, wait for API calls, or hydrate your React components. If your content depends on JavaScript, it's invisible.

How AI Crawlers Process Pages

AI crawlers (GPTBot, ClaudeBot, PerplexityBot) operate like wget or curl, they download the HTML response and parse it. No browser engine, no JavaScript execution.

This means dynamic content loaded via API calls, client-side routing, and JavaScript-rendered components simply don't exist from the crawler's perspective.

Which Frameworks Are Affected

React (Create React App, Vite): fully client-rendered by default. All content invisible to AI crawlers.

Vue (standard SPA mode): same issue as React. Content rendered in the browser only.

Angular: client-side rendering by default. Angular Universal (SSR) solves it but adds significant complexity.

Next.js, Nuxt, SvelteKit: safe by default IF you use SSR or SSG. But client-only components within these frameworks still have the problem.

How to Fix It

Migrate to a framework with SSR/SSG support (Next.js, Nuxt, SvelteKit, Astro). This is the most robust long-term solution.

Use a prerendering service that serves static HTML to crawler user-agents. This works as a stopgap but adds latency and cost.

At minimum, ensure critical content (headings, body text, meta tags) is in the initial HTML response, even if interactive elements load later.

Frequently Asked Questions

Does Google render JavaScript for AI answers?: Google's traditional indexing can render JavaScript, but AI-specific crawlers (GPTBot, ClaudeBot) typically do not. Don't assume Google's behavior applies to all AI models.
Can I check if my JavaScript content is visible to AI?: Yes, run an AI visibility audit. It crawls your page without JavaScript execution and shows exactly what AI models see.
Is server-side rendering required for AI visibility?: Not strictly, SSG (static site generation) works too. The key requirement is that the HTML response contains your content without JavaScript execution.