Skip to content

AI analytics

Find out which AIs read your site, and which ones are lying.

Know whether ChatGPT, Claude and Perplexity can cite you, which pages they skip, and how many AI crawlers are really scrapers in disguise. No script to install.

Your analytics can't see the visitors that matter most now.

Most AI crawlers don't run JavaScript, so Google Analytics and every script-based tool report nothing while they fetch your pages. You can't fix what you can't see, and you can't be cited from a page an AI never read.

What it shows

Real figures from hatamoto.dev. This site, last 30 days.

AI fetches
46,191 from 16 of 19 known agents
spoofed fetches
3,301 fake user agents, left out of the totals
error responses
11,456 served to AI crawlers, with paths
pages no AI has fetched
863 published, not yet read

What you get

  • Know if you can be cited at all

    See every published page no AI agent has fetched yet. A page an answer engine never read can't be quoted.

    Never-fetched pages
  • Stop counting the fakes

    Bots that claim to be ClaudeBot or GPTBot are checked against the operator's published IP ranges and reverse DNS, flagged, and kept out of your totals.

    Verification
  • Fix what AI sees broken

    Error responses served to AI crawlers are listed with their paths, so you fix the pages that cost you citations first.

    Errors report
  • Tell training from live readers

    Training crawls, search indexers and live answer fetches are kept apart. A live fetch is the closest you get to a real reader.

    Purpose per agent
  • See it while you write

    The editor shows which agents fetched the page you are working on, and when.

    Editor sidebar
  • Measure the traffic AI sends back

    Visits from ChatGPT, Perplexity, Gemini, Claude and other assistants, counted per assistant.

    AI referrals

Under the hood

  • Server-side logging

    Every crawler fetch is logged on the server, in the background.

  • Known agents, grouped by purpose

    A registry of AI and search agents, each with an operator and a purpose.

  • Verified against the operator

    Published IP ranges or forward-confirmed reverse DNS.

  • Allow or block per purpose

    Choose which kinds of crawler may read the site, from the same screen.

  • No cookies for visitors

    Human visits are counted without cookies, and the path, referrer, IP and user agent are discarded.

Questions people ask

Does this replace Google Analytics?

No. Keep Google Analytics for human visitors if you use it. Hatamoto covers what script-based tools can't see: crawlers that never run JavaScript.

Does it slow my pages down?

No. Crawler fetches are logged on the server in the background and in batches, so the response is not held up.

Is any visitor data stored?

Human visits are counted without cookies. Crawler hits are kept per fetch so they can be verified, then IP addresses are truncated and old rows are dropped.

Read next

  • Grow

    Search and AI answers

    One record feeds the page, JSON-LD, sitemap and llms.txt.

    Read more
  • Build

    AI agents and MCP

    Let agents draft and publish under your rules.

    Read more

See who is reading your site

Install Hatamoto and the first crawler fetch shows up in AI analytics.

Install Hatamoto