SearchSeal is Live

SearchSeal is live again, but it is not the product first described at this URL, and it has changed once since then too. The original version polled AI assistants with prompts and turned their answers into brand visibility reports. It had no users, and that product has been retired.

What SearchSeal is now

SearchSeal is privacy-friendly website analytics with AI visibility built in. It shows pageviews, privacy-safe daily visitors and sessions, acquisition sources, goals, revenue, and human AI referrals: visits from ChatGPT, Claude, Perplexity, Gemini, and other AI products.

SearchSeal also keeps a separate AI crawler evidence module: which crawlers hit a site, which pages they request, and the HTTP outcome. Human analytics and crawler evidence stay separate because they measure different things.

The product truth rule

Unknown is never presented as zero. A human referral is evidence of a visit, not proof that crawling caused it. An observed crawler request does not prove that a page was indexed, used in an answer, or cited. When evidence is unavailable, SearchSeal reports unknown instead of guessing.

What the product does not claim

SearchSeal does not grade chatbot answers, calculate a visibility score, or infer recommendation share from a prompt pool. It also does not treat every AI system as one crawler, and it does not claim that a crawler request or a referral proves a citation or a conversion.

Current access

The dashboard, API, and MCP services are in early access at app.searchseal.com, api.searchseal.com, and mcp.searchseal.com. The marketing site remains at searchseal.com. Pricing is published on the pricing page, with a free tier under 1,000 monthly pageviews on a single site and a 14-day trial on every paid plan.

This article remains as a record of the launch, corrected twice now: first to describe the crawler-only product that replaced the original prompt-polling tool, and again to describe the combined analytics and crawler evidence product that is actually live today.

Why this correction is public

The old launch article earned a stable URL and became part of the product record. Deleting the history would hide the change, while leaving either earlier description in place would mislead readers and crawlers.

Keeping the URL with corrected copy makes the transition explicit: the name remains, the earlier single-purpose descriptions do not, and every current feature claim must match the live product.