Terradium logoTerradium

AI Visibility

AI Visibility shows you where — and how often — AI engines cite your brand when people ask them questions. Instead of guessing whether ChatGPT or Perplexity mentions you, Terradium samples real prompts and reports the answer as a trend over time.

What prompt-sampling is

Search rank is a single number for a single query at a single moment. AI answers don't work that way: the same prompt can produce different sources on different runs, and small wording changes shift who gets quoted.

So Terradium uses prompt-sampling. For a set of prompts relevant to your brand and topics, it asks the AI engines those prompts repeatedly over time and records what comes back — whether you appeared, whether you were cited as a source, and who else showed up alongside you.

Why it's a trend, not a fixed rank

Because answers vary run to run, a single sample isn't meaningful — but the rate across many samples is. AI Visibility metrics are therefore directional trends, not guaranteed placements. You'll watch a line move up and to the right as your content gets picked up more often; you won't see a brittle "position #1" that flips every refresh.

The metrics

Across your sampled prompts, Terradium reports:

  • Appearance rate — the share of sampled prompts where your brand shows up at all (mentioned or cited).
  • Citation share — how often you're the named source the engine links or attributes its answer to.
  • Share of voice — your slice of the cited sources versus the competitors who appear for the same prompts.
  • Average position — where you tend to land among the cited sources when you do appear.

Each is shown as a current value plus its trend, so you can tell whether your GEO work is compounding.

The four engines

Terradium samples the four AI surfaces that matter most:

  • ChatGPT
  • Perplexity
  • Google AI Overviews
  • Gemini

Metrics are available per engine and rolled up across all four, so you can spot where you're strong and where you have room to grow.

Sample-run quota

Sampling AI engines costs real compute, so each billing period includes a fixed quota of sample runs. A run refreshes your metrics across your prompt set; the quota resets at the start of each billing period. You can see how many runs you've used on the AI Visibility screen.

Getting cited more

To improve these numbers, publish content that's easy for engines to quote — clear, well-structured answers to real questions. The Terradium content pipeline is built to write exactly that, and Search Console tells you which questions to target.

Make your content AI-readable (GEO)

Measuring citations is only half of GEO — the other half is making sure AI crawlers can actually read your published content. This matters because most AI crawlers don't run JavaScript: if your blog renders client-side, a crawler sees an empty shell and there's nothing to cite.

Terradium does the hard part for you (it builds clean markdown and a JSON-LD entity graph for every post), but those signals have to be served on your site. Aim for:

  • Content in the raw HTML — server-render or pre-render your blog so the article text is in the initial response, not injected after load.
  • JSON-LD in the page <head> — render each post's seoMetadata.jsonLd (the Organization + author + Article graph) as a <script type="application/ld+json">. Fill your project's Brand & entity fields so that graph is rich.
  • llms.txt and llms-full.txt at your site root — a clean, link-first index and a full-markdown corpus for crawlers. Terradium serves ready-made versions you can mirror at build time.
  • A markdown alternate per post (/blog/{slug}.md + <link rel="alternate" type="text/markdown">) — the most token-efficient way for an engine to read you.
  • robots.txt that welcomes AI bots (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) and references your sitemap.

The onboarding "install" step gives you a copy-paste prompt that sets all of this up; you can re-run it against your AI coding agent any time.

GEO readiness check

On the AI Visibility screen, Run readiness check fetches your live site and grades it across four groups:

  • Setup — website URL, brand/entity fields, Search Console, tracked prompts, sampling, and whether you have published content.
  • Published page — is a real post reachable, is its content in the raw HTML, is the JSON-LD present, are title/description/canonical set.
  • Discoverability files — robots.txt, sitemap.xml, llms.txt, llms-full.txt.
  • Crawler access — can an AI bot (e.g. GPTBot) fetch the page, and does it see the same content a browser does (no cloaking).

Every failing check explains what's wrong, links here, and gives a copy-paste fix prompt you can hand to your AI coding agent. Run it after you deploy changes to confirm crawlers can read everything.

← Search ConsoleEmbed SDK →