Analytics for the AI-search era.
WebmasterID is a lightweight, first-party analytics and AI visibility platform built for SEO ecosystems, publishers, AI-native websites, and indie founders. No fingerprinting. No third-party cookies. No bloat.
<script defer src="https://webmasterid.com/tracker.iife.min.js" data-wmid="wm_xxxxxxxxxxxxxxxx" data-endpoint="https://webmasterid-ingest-api.vercel.app/api/events" ></script>
Core shows what happened. Agent tells you what to do next.
WebmasterID Core measures traffic, AI visibility, and bot activity. WebmasterID Agent reads those signals and prioritises the work. Claude helps prepare the change. You approve, deploy, and verify — every change runs through human review.
1 · Core
Privacy-first analytics. AI-crawler visibility. AI referrals.
2 · Agent
Daily brief, recommendations, repo mappings — and an MCP surface Claude can read.
3 · Claude
Reads Agent data, prepares the code change, hands the diff back for review.
4 · You
Approve, deploy, verify. The Agent never deploys on its own.
An AI-native webmaster operations platform
Detect → prioritise → execute → verify → remember. WebmasterID is not just analytics — it is the operator loop that turns AI-search signals into deterministic, review-first work.
The WebmasterID Agent
Review-first execution layer. Daily brief, deterministic recommendations, Claude Code prompts — never autonomous.
SEO operations loop
One queue per operator. Work packages, not dashboards.
Bot intelligence
Categorise AI crawlers, search bots, and automation traffic — deterministic, never invented.
AI referrals
Attribute traffic from ChatGPT, Claude, Perplexity, Gemini, and AI Overviews.
See pricing or compare against Plausible and Google Analytics.
One product, six clear stories.
WebmasterID is small on purpose. Each surface below explains one part of the system — read in any order.
- Product philosophy
Search infrastructure observability, not adtech surveillance. Built for SEO ecosystems and the AI-search era.
- AI visibility
See which AI assistants and crawlers read your site — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and more.
- Privacy-first analytics
No cookies, no fingerprinting, no third-party identifiers. First-party events with text/plain transport.
- Architecture
A small browser tracker, a typed ingest API, Postgres, and a server-rendered dashboard. No magic, no bloat.
- Use cases
Indie founders, SEO ecosystems, publishers, AI-native sites, programmatic SEO, and content networks.
- BuildDesignHub case study
First real-site integration — the install, the verified browser path, the AI crawler observability story.
Privacy-first by architecture, not by toggle.
No third-party cookies. No localStorage tracking. Source IPs are anonymized at the ingestion edge — raw IPs never reach storage. DNT and GPC are respected unconditionally.
No fingerprinting
We don't read canvas, fonts, or device entropy.
No third-party cookies
We don't set cookies, period.
IP anonymization
IPv4 last octet zeroed; IPv6 truncated to /48.
DNT / GPC respected
Opted-out browsers send nothing to the server.
Read the full breakdown on the privacy-first analytics page.
Pick the part of WebmasterID that matters to you.
Each link below is a focused read on one observability surface — useful for evaluators, operators, and editorial teams investigating the AI-search era.
- AI visibility analyticsAI crawlers + AI-assistant referrals, joined on one timeline.
- AI search analyticsPer-assistant detection for ChatGPT, Claude, Perplexity, Gemini.
- Attribution analyticsDirectional attribution with per-row confidence labels.
- Event ExplorerThe investigation surface for ad-hoc questions and incident response.
- MCP analyticsRead WebmasterID through Claude Desktop, Claude Code, or VS Code — through MCP.
- Website observabilityTraffic, bots, attribution, AI visibility — one fabric.
Honest, in-progress, infrastructure-first.
Today is the foundation: tracker, ingest, dashboard, and the first real-site integration. From here, scale and intelligence.
The full roadmap lives at /roadmap. The implementation case study for BuildDesignHub lives at /case-studies/builddesignhub.