Agent Experiences

Agent Visualizer

A score tells you how you did. This shows you what happened: where an agent arrives on your page, where it reads, where it stops, and everything after that it never reaches.

An actual walk

Scored 97 of 100

A real scan of our own blog index, taken on October 3, 2026. Two steps come back short, and both are ours to fix.

  1. 1Arrive

    Nothing in the way

    Fetch the page and be allowed to keep it.

    Title
    Blog | Agent Experiences
    Language
    en

    The page is fetched and kept. Everything after this is possible because this worked.

  2. 2Read

    Nothing in the way

    Get the words out of the markup, without running a browser.

    Readable words
    923 in the page
    Inside <main>
    862 words

    The words come out of the markup without running a browser, so every agent gets the same text a person would.

  3. 3Separate

    Nothing in the way

    Tell the content apart from the navigation and the chrome.

    Landmarks
    <main>, 17 <article>, <nav>
    Outline
    h1 AXO Blog · h2 Why an Agent That Works 80% of the Time Finishes a Third of the Job · h2 The Same Agent, the Same Page, 34 Points Apart · h2 Muse and Dots Both Drive a Browser · h2 GEO, AEO, LLMO: What Do You Actually Call This? · h2 Atlas Is Dead, Agentic Browsing Isn't

    Your content is distinguishable from the navigation and the footer, so a quote comes from the article rather than from a menu.

  4. 4Understand

    Gets through, with gaps

    Work out what this page is and what question it answers.

    Declared types
    Organization, ImageObject, Person, EducationalOccupationalCredential, WebSite, Blog, BlogPosting
    Headline
    AXO Blog

    What is missing: The markup and the visible page disagree, so a machine holds two versions of the facts and may repeat the wrong one.

    What this costs you: The agent has to guess the subject from the text. It matches your page to the wrong questions and misses the right ones, which shows up as being absent from answers you should be the obvious source for.

  5. 5Attribute

    Gets through, with gaps

    Find out who wrote it, when, and on what basis.

    Author
    Alan Weibel
    Dates
    none found

    What is missing: Claims stand on their own with nothing behind them, so neither a reader nor a model can check where they came from.

    What this costs you: The agent has a claim it cannot attribute. Systems that cite sources tend to prefer one they can name, so your material gets used without credit or passed over for a weaker page that says who wrote it and when.

  6. 6Explore

    Nothing in the way

    Find the rest of the site, and tell what has changed.

    Links out of here
    55 internal, 3 external
    Within the content
    35 of those are inside the main region

    The rest of the site is reachable from here, and changes are visible, so one good page leads to the others.

  7. 7Act

    Nothing in the way

    Do something here rather than only read: a form, a tool, an API.

    Form submits to
    POST /api/subscribe
    Form fields
    email:email required

    There is something here to do, named clearly enough that an agent can do it on someone’s behalf.

An agent gets all the way through, losing something at each marked step.

What you are watching

Seven steps, in the order an agent meets them: it arrives, reads the words out of the markup, separates your content from the navigation, works out what the page is, finds who wrote it, looks for the rest of the site, and finally tries to do something other than read.

Each step is impossible until the one before it works. That is the part a number hides. A page can have immaculate structured data and a perfect author block and still be a dead end, because the agent stopped two steps earlier and never saw any of it.

So anything after a stop is drawn as unreached rather than passing. It did not succeed; it was never tried.

The same idea, for software

This walks a page. An agent working inside an application walks 7 steps of its own — discovering what the software can do, proving it is acting for someone, attempting the task, and getting back out with something the person can check.

The agent journey map for software →