How it works

The mechanism, in the open. What a fix can move — and what it can't.

The short version is on the home page. Here's the long one: how AI engines actually read your app, the loop that proves the gain, and how we keep you found and safe over time.

The Found read, in depth · how AI visibility actually works

There are two kinds of AI. We're honest about both.

Most "get cited by AI" tools blur a real line — and over-promise across it. Here it is, plainly, so you can tell us apart from the slop: what a website fix can move, and what it genuinely can't.

No vanity scores. No faked AI rankings. The number is your AI-readability on a 9-signal engine — and we're plain about what a website fix can and can't move.

Search-groundedmoves in days

They read your page live.

Perplexity, Google AI / Gemini, ChatGPT-with-search — they fetch and read your live page at the moment they answer.

  • Better foundations change what they retrieve — and what they cite — fast.
  • This is where the loop is real: fix, re-measure, watch the citation move.
  • It's also where our perception-delta study is measured.
A site fix can move this — and we prove it.
Training-bakeduntil the next retrain

They answer from memory.

ChatGPT and Claude answering from what they learned in training — no live fetch. Their "knowledge" is frozen until the model is retrained.

  • No website tweak rewrites a model's training weights. Full stop.
  • What you ship today reaches them only when they next retrain on the web.
  • Anyone promising to change this on demand is selling you slop.
A site fix can't rewrite this — so we don't pretend it does.

So here's exactly what getAdvantage does: we fix the foundations every AI reads — instantly, across all engines. We move your citations in the search-grounded engines (ChatGPT, Perplexity & Gemini) and prove the change. And we will never tell you a website edit rewrites a model's training. That last honesty is the whole reason to trust the first two.

Receipts · what the engines said

Don't take our word for it — here's what the engines said when we asked.

We asked the assistants, plainly, to name a tool for getting found by AI. Read what they actually answered — it tells you everything about how invisible this whole category still is to AI today.

ChatGPTanswered from training
we asked

What tool helps founders optimize their website for AI search discovery?

it answered

Recommended SEMrush, Moz, Ahrefs and Google Search Console — every name a generic legacy-SEO tool. Not one AI-visibility / AEO-native tool among them.

It reached for the old SEO playbook — the category we work in didn't surface at all.
Claudeanswered from training
we asked

Best AEO tool for indie founders who built on Lovable or Bolt?

it answered

“I don't have confident recommendations for AEO tools specifically designed or optimized for apps built with Lovable or Bolt. These are relatively newer/niche platforms…”

It named nothing — and was honest that, from training, it doesn't know this category yet. See the Lovable AI-visibility study →

So what does this mean for you? Today's AI either defaults to old-school SEO or admits it doesn't know the AEO category yet — the whole space is still invisible to AI. The opening isn't to game a training-baked answer (a site fix can't rewrite training). It's the engines that read your page live (ChatGPT, Perplexity & Gemini, ChatGPT-with-search) — fix the foundations they read and you win the gap before everyone else notices it exists. That's exactly what we do.

real API responses · June 2026 Actual answers from live API calls, captured June 20 2026 — reproducible, but AI responses vary, so your results may differ.

The closed loop · across all three reads

Everyone measures. Only we close the loop.

Measurement-only tools — Profound, Peec — hand you a score and stop. We keep going, on every read: show you the fix, apply the DOM-safe ones, re-check, and prove it moved — whether the gap was being found, converting a first visit, or an exposure to close before you ship. Then we do it again, daily. That whole loop, drawn end to end, is the moat nobody else has.

  1. 01inputdone
    Your app
    Point us at the URL you shipped.
    https://your-app.com
  2. 02readdone
    Read the page
    Fetch the live HTML the way an AI crawler does.
    page content + extracted facts
  3. 03scoredone
    Score AI-readability
    Grade 9 signals models actually read — title, JSON-LD, llms.txt…
    Advantage Score 41 / F
  4. 04perceivedone
    How AI sees you
    Ask the assistants what they say — and who they name instead.
    not named — rivals named instead
  5. 05fixdone
    Generate paste-ready fixes
    Build the exact artifacts from your own content — nothing to write.
    llms.txt · JSON-LD · meta · FAQ
  6. 06applydone
    Apply via one-line embed
    The DOM-safe fixes go live from one line of code — no redeploy.
    live in the DOM — no publish
  7. 07proveproven
    Re-measure · prove it moved
    Re-scan and show the number climb — proven, not promised.
    Advantage Score 92 / A · ▲ +51

illustrative sample run The 41 / F → 92 / A at the ends are our own real Advantage Score — getadvantage.app, scored by the same engine, daily. The per-app outputs are a sample for a generic app. We query ChatGPT, Perplexity & Gemini live; the embed applies only DOM-safe fixes (9-signal scan).

Why you stay · drift watch

A scan is a photo. Your app is a film.

Here's the part scan-and-score tools can't sell you: getting found once is easy to undo. Your next deploy can silently wipe the fixes you applied — and you'd never notice until the AI traffic quietly dries up. We watch for it, every day, and tell you the moment it regresses.

What silently breaks your visibility
A deploy strips the JSON-LD
your next push overwrites <head> and the schema the embed applied silently vanishes
Meta / canonical regress
a template change drops the description or points canonical at the wrong URL
llms.txt or robots breaks
the file you placed gets clobbered, or robots starts blocking AI crawlers again
A new exposure ships
a leaked key, public .env, or missing header appears in a release you forgot about
What lands in your inbox illustrative sample
Regression detected · getadvantage.app
Advantage Score 92 / A78 / B

Your 11:42 deploy removed the JSON-LD the embed applied. The fix is queued — re-apply from one line and we'll re-measure to confirm it's back.

And when nothing breaks, you hear nothing. We re-scan daily across ChatGPT, Perplexity & Gemini and only interrupt you when something actually moves — signal, never noise.

Why the loop is the moat

A score is a snapshot. The loop is an asset.

Anyone can sell you a number. The compounding, timestamped record of how your standing actually moves — that's the thing a one-shot scan can never hand you, and the thing you lose the day you switch tools.

We close it

We close it (today).

Measurement-only tools stop at the number. We apply the DOM-safe fix, re-measure across ChatGPT, Perplexity & Gemini, and prove the move — daily, on our own real 41 / F → 92 / A.

It compounds

It compounds (today).

Every re-check is timestamped and kept. The longer you stay, the more we know how your standing drifts as models retrain — a trajectory a one-shot scan can't reconstruct. Switching tools resets it to zero.

Why now

Why now.

AI became a real distribution channel in 2025–26 — and they re-rank constantly. Being named once is worthless if you silently drop out. The job is staying named.

Where this goes · roadmap, not shipped

As thousands of these loops run, the aggregate of what actually moves AI standing becomes a dataset no measurement-only tool can assemble. We're not claiming that corpus today — we're building the loops that produce it.

The third read · Safe to ship

Found and converting is moot if it's leaking on the way out.

Apps built with AI leak secrets and ship wide open more often than not. So the same scan reads a third thing: we run getAdvantage's own Ship Verified engine over your app and check for the exposures that slip into vibe-coded builds — leaked keys, a public .env, missing headers, open CORS. We tell you exactly what we found, hand you the paste-ready fix, and watch for new ones as you ship. (We check what's exposed on your page — we don't claim your app is "secure".)

Leaked API keys & secrets
OpenAI / Stripe / AWS / GitHub keys shipped in your client bundle
Public .env / .git
the files that hand over every secret and your whole source history
Missing security headers
CSP, HSTS, X-Frame-Options, nosniff, Referrer-Policy
CORS & HTTPS gaps
wide-open cross-origin access and unenforced transport security
Exposed source maps
production .map files that de-minify your app back to source
Exposed backend config
Supabase / Firebase config reachable without row-level rules on
Check your app's safety — free

Paste one link. The Ship Verified engine runs the same checks live and tells you exactly what it found — free, no signup.

We watch how AI reads you and whether your app is exposed — so you stay focused on what matters: your business.

Two buyers · one engine

Run it for your app — or resell it to your clients.

The same scan-fix-prove loop serves both. Solo founders keep one app named by AI. Agencies turn AI visibility into a new, high-margin line of business across a whole client roster.

For founders & solo builders

Get your own app found — without learning AEO.

  • Paste one line; the DOM-safe fixes apply themselves.
  • See exactly how ChatGPT, Perplexity and Gemini read your app today.
  • Re-scanned daily — you hear from us only when something moves.
  • Start free, no card. Upgrade only when you want it auto-applied.
  • Built on Lovable or Bolt? Read the Lovable AI-visibility study.
Scan your app — free →
For agencies & consultants

Sell “get found by AI” as a service line.

  • One Agency seat covers unlimited client apps — your margin is the spread.
  • Hand each client a real before → after they can see, not a vague promise.
  • Daily monitoring across every app, so a client deploy can't quietly undo your work.
  • API + MCP access to wire the loop into how you already deliver.
See the Agency plan →

Said plainly:the Agency tier is the same product on an unlimited-apps plan — it's “high-margin” because one seat resells across a whole portfolio, not because we add per-client white-label (team seats are on the roadmap). You charge the retainer; we run the engine.

Seen enough? Check your app.

Free, in under a minute — see how AI reads you, get the fix, prove the gain.