AI Traffic Analytics. Ask how people found you.
Every visit, from Google, ChatGPT or a link, and what it did next. Ask anything: each answer links to its report.
I followed 76,367 visits in 30 days: 64% from Google search, 2.5% from AI.
Sample · seomator.com · 30 daysCame from
- Google search43,895
- AI assistants1,619
- Direct20,160
- Other sources1,431
Landed on
- SEO audit tool18,145
- Domain authority checker16,252
- Sitemap finder8,040
- Home page4,891
- Other pages19,777
Then
- Left after one page50,901
- Went to another page14,482
- Reached the waitlist1,722
seomator.com's own analytics, 16 Sept – 15 Oct 2026: the 67,105 visits with a recorded landing page. "Left after one page" applies each page's bounce rate to its landings.
Every visit, not just the AI ones.
Google, direct visits, AI assistants, referrals, email and social sit in one report, credited the same way, so AI traffic is measured against everything else.
These are seomator.com's own numbers from the app, 16 Sept – 15 Oct 2026. One script collects them, with no analytics cookies and no raw IP address stored.
Where seomator.com's visits came from
16 Sept – 15 Oct 2026
| Channel | Visits | Share |
|---|---|---|
| Organic search | 48,769 | 63.9% |
| Direct | 23,963 | 31.4% |
| AI assistants | 1,903 | 2.5% |
| Internal | 1,257 | 1.6% |
| Referral | 319 | 0.4% |
| Social, email and other | 156 | 0.2% |
seomator.com, 16 Sept – 15 Oct 2026: 76,367 visits, up 72% on the 30 days before.
What AI sends you, and what happens next.
Each AI visit is credited to the assistant it came from, then followed like any other: where it landed, where it went, whether it reached your goal. Ours includes the number we'd rather were higher.
AI visits to seomator.com
16 Sept – 15 Oct 2026
By assistant
- ChatGPT1,58583.1%
- Gemini24512.8%
- Perplexity653.4%
- Claude110.6%
- DeepSeek, Qwen20.1%
Where they landed
- /free-domain-authority-checker642
- /free-seo-audit-tool280
- /google-serp-rank-checker110
- /free-keyword-research-tool91
- /find-competitor-keywords86
Reached the waitlist
- All visits1,722 of 76,3672.3%
- Google search1,086 of 48,7692.2%
- AI assistants35 of 1,9081.8%
- ChatGPT27 of 1,5851.7%
seomator.com, 16 Sept – 15 Oct 2026: 1,908 visits credited to an AI assistant, up 74% on the 30 days before (all visits: up 72%). The channel view above files 1,903 under AI; landing pages count the 1,619 with a recorded landing page.
Who isn't a person.
Bots are caught by six detection layers and counted apart, so they never inflate your visits.
AI crawlers are named and sorted by purpose: training, search, or an agent fetching a page because someone asked.
Kept out of seomator.com's visits
16 Sept – 15 Oct 2026
45,365bot requests: 4.0% of every event the script recorded.
AI crawlers that ran the script
- Meta-ExternalAgent4,020
- Manus142
- Cursor47
- OAI-SearchBot4
By purpose
- Training3,916
- Agent (someone asked)189
- Search4
What flagged them
- Browser automation flags31,421
- A crawler's own user agent27,465
- Headers no real browser leaves out17,135
- Crawl-shaped bursts6,554
A request can trip more than one.
What no script seesGPTBot · ClaudeBot · PerplexityBot
GPTBot, ClaudeBot and PerplexityBot fetch pages without running JavaScript, so they never reach a script. Counting them takes your server logs.
And a crawl isn't a citation: it shows a page was fetched, not that an answer quoted it.
seomator.com, 16 Sept – 15 Oct 2026. Detection is best effort: a bot that hides every signal can still count as a visit.
Everything in the app.
One script, every report, and an AI that answers from them.
Where people came from and what they did.
- Dashboard and realtimeSix headline numbers, and who's on the site right now.
- Pages, sessions, users, eventsEvery visit's timeline, every event with its properties.
- JourneysThe paths people take, up to six steps deep.
- Funnels and goalsWhere a sequence of steps loses people.
- Retention and cohortsWho comes back, grouped by when they started.
- AcquisitionWhere each user first came from, by channel, source and campaign.
- Search ConsoleYour queries and pages, beside your visits.
- HeatmapsClicks, rage clicks and scroll depth, without recording.
- Session replayOff by default, inputs masked, kept 30 days.
What AI sends you, and what keeps watch.
- AI trafficVisits, trend, conversions and revenue per assistant.
- AI crawlersNamed, sorted by purpose, kept out of your visits.
- Ask AIAnswers that link to their report; changes wait for your approval.
- SQL in plain EnglishDescribe the question; it writes the query.
- AlertsWhen a number moves, by email, Slack, Discord or a webhook.
- WorkflowsActions that run when an event happens.
- Scheduled reportsA summary by email, with an AI-written note each week.
- DashboardsYour own, shared publicly or embedded in your site.
What visits are worth, and what breaks.
- RevenueFrom Stripe or your own events, beside the source of each visit.
- Feature flags and A/B testsRoll out to a share of visitors; tests report significance.
- Surveys and NPSTargeted questions, open answers summarised by AI.
- Onboarding checklists and toursGuide new users through your product.
- Core Web VitalsLCP, INP and CLS from real visitors.
- JavaScript errors and uptimeErrors from real visits; your site checked on a schedule.
- ImportsHistory from Google Analytics 4, Plausible, Umami or Simple Analytics.
- PrivacyNo analytics cookies, no raw IP stored, a script under 6.5 KB.
What happens after you close this tab?
The agent follows every journey through the night. When visitors keep stopping at the same step, it finds the page, drafts the next step that's missing, and waits for your OK.
A morning in the app
Sample- 06:00Read yesterday's journeys from every source.
- 06:02Domain authority checker: 0.7% of visits reach the waitlist.
- 06:03Drafted a next step under the result. It waits for your approval.
It asks before it changes anything.
The agent drafts the change on your page and waits. Nothing reaches your site until you approve it, and afterwards it checks whether the step works.
Next step drafted for the domain authority checker
Sample
Nothing is sent. This is a sample.
Every plan includes every report.
Plans differ only in credits and support. Every feature on this page is on every plan, Free included, and unused credits on a paid plan roll over.
| Plan | Price | Credits a month |
|---|---|---|
| Free | $0 | 500 |
| Standard | $49/mo | 10,000 |
| Expert | $250/mo | 50,000 |
| Enterprise | Custom | Custom |
AI traffic analytics questions
Does it count GPTBot, ClaudeBot or PerplexityBot?
No. They fetch pages without running JavaScript, so they never reach the script; counting them takes your server logs. Crawlers that do run it are named and counted apart from your visits.
What counts as AI traffic?
A person who clicked a link in an AI assistant's answer, credited to the assistant they came from. An answer that cites you without a click isn't a visit; the AI visibility tracker shows those.
Does it use cookies?
No analytics cookies, and no raw IP address is stored: visitors are counted with a one-way ID made on the server. Whether you need a consent banner still depends on your setup and where you operate.
What can Ask AI change?
It answers from the same reports you see and links each answer to its report. When it proposes a change, such as a goal, a funnel or a dashboard, nothing happens until you approve it.
Can I bring my old analytics?
Yes. Import your history from Google Analytics 4, Plausible, Umami or Simple Analytics and keep reporting without starting over.
Is session replay on by default?
No. Replay stays off until you turn it on. Inputs are always masked, and visits are sampled and kept 30 days.
Will the script slow my site down?
It's one script under 6.5 KB gzipped, and it can run through your own domain as a first-party proxy.