AEOmeter
Get started

Product

Engines

Resources

How it works

How AEOmeter collects AI answers in your browser

AEOmeter asks ChatGPT, Claude, Perplexity and Google your prompts from your own Chrome, signed in as you, then reads the finished answers and turns them into reports. Here is every step, including what can stop a check.

Track your first brandTake the product tour
AEOmeter web app
Your brand, prompts and daily schedule. Queues checks.
queued checks
Your Chrome
The extension, signed in to your AI accounts. Runs checks in background tabs.
types each prompt

AI engines

  • ChatGPT
  • Claude
  • Perplexity
  • Google AI Overviews
answer + sources
Reports
Mentions, citations and share of voice, each linked to its answer.

Step by step

From a queued check to a number you can trust

  1. 1

    Set up in the web app

    Add your brand, competitors and prompts, pick the engines for each prompt and set a daily schedule in your timezone. A schedule queues checks. It does not run them by itself.

    Example data

    Brand & competitors

    Acme Analytics your brand

    Aliases
    Acmeacme.io
    Domains
    acme.iodocs.acme.io

    Competitors

    MixpanelPostHogAmplitude
    Starter prompts suggested8 ready to review
    Example data for the fictional Acme Analytics.
  2. 2

    The extension connects

    Install the AEOmeter BETA Chrome extension and click Connect. Sign in to ChatGPT, Claude and Perplexity in that same Chrome, as you normally would. Monitoring shows which engine sessions are ready.

    Example data

    Monitoring

    Chrome connectedMacBook · Chrome
    ChatGPTReady
    ClaudeReady
    PerplexitySign-in needed
    Google AI OverviewsReady
    Next scheduled
    Today, 09:00 Europe/Berlin
    Last capture
    Yesterday, 18:42
    Example data for the fictional Acme Analytics.
  3. 3

    Checks run in background tabs

    Queued checks open in background tabs grouped as "AEOmeter". Each prompt goes to all its selected engines at once, and the next prompt starts when all of them finish. Chrome shows a "started debugging this browser" banner while this happens.

    Example data
    AEOmeterChatGPTClaudePerplexity
    "AEOmeter" started debugging this browserCancel
    AEOmeter BETARunning

    Prompt 3 of 24

    Waiting for ChatGPT, Claude and Perplexity to finish

    PauseSkipOpen app
    Example data for the fictional Acme Analytics.
  4. 4

    Private mode where available

    Before asking, the extension turns on each engine's private mode: temporary chat in ChatGPT, incognito in Claude and Perplexity, and non-personalized results on Google. This is best effort, because engines move these settings around.

    Private mode, per engine

    • ChatGPTTemporary chat
    • ClaudeIncognito
    • PerplexityIncognito
    • Google AI OverviewsNon-personalized
  5. 5

    Real input, finished answers

    The prompt is typed into the engine's own chat box, the same way you would. The extension waits until the engine shows the answer is finished, up to 10 minutes, then reads it as Markdown with its cited sources. For Perplexity, sources come from the thread data.

    Example data
    Claude

    Mixpanel alternatives with a generous free tier

    Typed into Claude's own chat boxSend
    FinishedRead as Markdown · 3 sources · 48 s
    Example data for the fictional Acme Analytics.
  6. 6

    Upload the answer, nothing else

    Only the answer text, its sources and run diagnostics are uploaded. The page itself, your cookies and your account tokens stay in your browser.

    Uploaded

    • Answer text
    • Cited sources
    • Run diagnostics

    Stays in your browser

    • Cookies
    • Account tokens
    • The page itself
  7. 7

    Reports with the math shown

    Mentions are matched against your aliases and citations against your domains. Visibility, owned citation rate and share of voice are calculated with explicit denominators, and every number links to its answer.

    Example data

    Visibility

    +6.4 pp

    42%

    18 of 43 answers mention Acme Analytics

    Cited

    19%

    8 of 43 answers cite acme.io

    Example data for the fictional Acme Analytics.

When an engine wants a human

What pauses a check

Sometimes an engine wants a human. When that happens, AEOmeter stops and tells you instead of guessing.

Login wall
You were signed out of an engine. Sign back in in that Chrome and resume.
Verification or CAPTCHA
The engine asked you to prove you are human. You solve it yourself. AEOmeter never bypasses a CAPTCHA.
Rate limit
The engine asked you to slow down. The check waits until you resume it.

A paused check shows a red "!" badge on the extension icon. Open the toolbar popup to pause, resume or skip. A prompt is never sent twice, and a failed or skipped check never counts as a miss in your numbers.

Example data
AEOmeter BETAPaused

Perplexity needs you

A verification check appeared. Solve it in the Perplexity tab, then resume.

ResumeSkipOpen app
Example: the extension popup when Perplexity asks for verification.

The approach

Why collect from a browser

The answers your buyers see

Your buyers use the ChatGPT, Claude and Perplexity apps and Google search, not a developer API. AEOmeter reads answers from those same consumer apps.

Signed in like a real person

Checks run in a normal Chrome session with your own accounts, the way a buyer would ask.

Low collection cost

The work happens on your machine, so collecting answers costs very little to run.

Other tools also collect from web interfaces. What AEOmeter adds is that it runs in your own browser and shows you the raw evidence.

The trade-off: your Chrome has to be open

Checks run only while Chrome is open, connected and signed in to each engine. If your laptop stays closed for a week, nothing is collected that week. AEOmeter shows the next scheduled time and the last actual capture side by side, so a gap in your data is visible instead of hidden behind zeros.

Privacy

Privacy

  • The extension never captures provider cookies or account tokens.
  • It uploads the latest answer and its sources, not the page.
  • Your prompts go only to the AI engines you selected for them.
  • Site analytics load only after you consent and exclude prompts, answers and brand identifiers.
Privacy policy

FAQ

Questions

Can I keep working while checks run?
Yes. Checks run in background tabs in their own "AEOmeter" tab group. You can use Chrome as normal, though closing those tabs or signing out of an engine can interrupt a check.
Which browser do I need?
Google Chrome on a computer. The extension is called AEOmeter BETA and is not yet searchable in the Chrome Web Store, so the app walks you through installing it after sign-up.
How long does a check take?
As long as the engine takes to finish its answer. The extension waits for each engine's finished state and gives up after 10 minutes.
Will a prompt ever be sent twice?
No. AEOmeter never sends the same prompt twice for one check. If the answer cannot be read, the check shows as failed and stays out of your numbers.
Why does Chrome show a debugging banner?
The extension uses Chrome's debugger API to type into each engine's chat box like a person would. Chrome shows the banner whenever an extension uses that API.
What if an engine changes its page?
Engines redesign often, so the adapters are experimental. When one breaks, checks for that engine fail visibly and we fix the adapter. See troubleshooting.

Keep reading

See what AI tells your buyers about you.

Add your brand, a few competitors and the questions your buyers ask. Your first answers arrive as soon as the extension is connected.

Track your first brandNeeds Chrome and your own AI accounts.