AI Visibility (GEO)

GEO (Generative Engine Optimization) is about whether AI assistants such as ChatGPT, Perplexity and Google AI Overviews can reach your site, understand what you offer, and quote you. ASEOKA checks your site against a fixed list of these signals and reports the result as your AI Visibility score.

Your AI Visibility score

After every scan, ASEOKA recalculates a score from 0 to 100. Each signal carries a fixed number of points, and your score is the share of points your site earns. Higher is better. The score is a readiness check: it tells you whether AI assistants can read and quote your site, not whether they currently do.

Only measured checks count. If a check could not run for your site, it is left out of the score entirely instead of counting against you, so the score is a percentage of what was actually measured.

What ASEOKA evaluates

Signals are grouped into five categories. The points show how much each category can contribute to a perfect score of 100.

CategoryPointsWhat it checks
AI Crawler Access29AI search crawlers (such as GPTBot, ClaudeBot and PerplexityBot) are not blocked; content is in the server-rendered HTML; training-only scrapers are blocked
Entity Clarity26Organization and Product schema, a clear site description, a clear value proposition
Structured Answers20Clear heading structure, a quick-answer block, tables and lists
Topic Authority14Publication dates, content updated within the last year, comparison pages, use-case pages
AI-Friendly Content11Citable content, and content that extracts cleanly from the page

Advisory signals (not scored)

Some things are still detected and reported but carry zero points, either because current evidence says they do not help AI visibility or because they cannot be measured reliably yet: FAQ and HowTo schema, llms.txt, IndexNow, author credentials, readability and mobile-friendliness. They appear under "Advisory, not scored" in your dashboard.

Why server-rendered content matters

ASEOKA detects pages that ship an empty client-side rendering shell, where the content only appears after JavaScript runs. The common industry understanding is that most AI crawlers do not run JavaScript, so content that is only rendered client-side may never be seen by them. This check is worth 12 points.

Where to see it in your dashboard

  • Home: the AI Visibility card shows your current score. Once there is a week of data it also shows how many points it has moved and since when.
  • See details (on Home): a trend chart of the score over time, and a breakdown of how many points each signal earned or missed, including the signals that were not measured and the advisory ones.

Fixes for AI Visibility issues

For some gaps ASEOKA generates the code change itself, and the fix appears on your Review page. See reviewing and approving fixes. Examples:

  • Blocked AI crawlers: a rule-based update to your robots.txt (or a Next.js robots.ts).
  • Missing Organization or Product schema: structured data added to your pages.

Advisory signals, such as FAQ schema or llms.txt, are reported only; ASEOKA does not open pull requests for them.