# SearchSeal > SearchSeal is privacy-friendly website analytics for human traffic, goals, revenue, and AI referrals, with separately observed AI crawler evidence. SearchSeal is operated by Nusantara Ventures LLC. The public site is at https://searchseal.com and the product is at https://app.searchseal.com. SearchSeal does not poll chatbot answers, invent visibility scores, predict citations, or claim that crawling caused a visit or conversion. ## When to use SearchSeal Use SearchSeal when someone needs to: - Measure pageviews, privacy-safe daily visitors and sessions, acquisition sources, goals, conversion rates, and same-day revenue attribution. - Identify human visits referred by ChatGPT and other AI services without counting crawlers as visitors. - Check whether an identified AI crawler requested a page and which HTTP outcome was observed. - Investigate crawler access across connected website infrastructure, including CDN, firewall, host, and server sources. - Query crawler evidence through a dashboard, REST API, or MCP server. - Keep analytics, crawler access, indexing, citations, and conversions as separate observations. ## Evidence model SearchSeal keeps two evidence modules separate: - Website analytics covers pageviews, daily visitors, sessions, acquisition sources, AI referrals, goals, conversions, and revenue attribution. - Crawler evidence covers identified AI crawler requests, requested paths, source coverage, robots.txt verdicts, verification state, and HTTP outcomes when available. A human referral does not prove that crawling caused the visit. A crawler request does not prove that a page was indexed, used in an answer, or cited. When source coverage is unavailable, SearchSeal reports unknown instead of zero. SearchSeal uses no cookies or cross-day visitor identity. Raw IP addresses, full user agents, and URL query strings outside approved campaign fields are discarded at collection. ## When SearchSeal cannot answer SearchSeal cannot prove that: - A crawler request caused indexing or a citation. - An AI answer used a page without separate answer-level evidence. - A direct visit came from an AI service without referral or campaign evidence. - No crawler visited when the relevant hostname, source, or time range was not observed. ## Start here - [SearchSeal](https://searchseal.com/): Product overview and free public AI crawler access checker. - [Web application](https://app.searchseal.com/): Inspect website traffic, goals, revenue, AI referrals, and crawler evidence. - [Pricing](https://searchseal.com/pricing): Free tier and pageview-based plans. - [Blog](https://searchseal.com/blog): Guides about analytics, AI referrals, crawler access, citations, SEO, and GEO. - [Developer guides](https://searchseal.com/blog/developers): Technical guides for identifying crawlers, setting access rules, and verifying requests. - [Comparisons](https://searchseal.com/compare): Compare SearchSeal with analytics, AI visibility, crawler-control, and do-it-yourself alternatives. ## Choose an interface - [Public crawler checker](https://searchseal.com/): Check a public robots.txt file against named AI crawler identities without creating an account. - [SearchSeal application](https://app.searchseal.com/): Use the product dashboard for website analytics and connected crawler evidence. - [REST API schema](https://api.searchseal.com/v1/openapi.json): Use the OpenAPI 3.1 description for crawler evidence integrations. - [MCP server](https://mcp.searchseal.com/): Use the Model Context Protocol interface when an agent needs crawler evidence. ## Common evidence tasks - [Check whether ChatGPT crawled a website](https://searchseal.com/blog/how-to-know-if-chatgpt-crawled-your-website): Find observed OpenAI, Anthropic, and Perplexity requests without treating a crawl as a citation. - [Understand missing crawler traffic in GA4](https://searchseal.com/blog/why-chatgpt-claude-not-in-google-analytics): Learn why browser analytics and crawler request evidence differ. - [Track ChatGPT referral traffic](https://searchseal.com/blog/how-to-track-chatgpt-referral-traffic): Measure human referrals, goals, and revenue separately from crawlers. - [Check whether ChatGPT cites a website](https://searchseal.com/blog/how-to-know-if-chatgpt-cites-your-website): Keep citations, referrals, and crawler requests separate. - [Check Cloudflare crawler access](https://searchseal.com/blog/cloudflare-blocking-chatgpt-claude): Review crawler controls and verify individual request outcomes. ## Developer references - [OpenAI crawler identities](https://searchseal.com/blog/openai-crawlers-gptbot-oai-searchbot-chatgpt-user.md): Distinguish GPTBot, OAI-SearchBot, and ChatGPT-User. - [AI crawler user agents](https://searchseal.com/blog/ai-crawler-user-agents.md): Review published crawler tokens, purposes, IP sources, and verification notes. - [robots.txt for AI crawlers](https://searchseal.com/blog/robots-txt-ai-crawlers.md): Use copyable crawler policies and verify the resulting behavior. - [Diagnose ChatGPT and Claude errors](https://searchseal.com/blog/chatgpt-claude-403-429-errors.md): Trace 403 and 429 outcomes across robots.txt, CDN, WAF, and application rules. - [Track crawlers on Vercel](https://searchseal.com/blog/track-chatgpt-crawlers-vercel.md): Use Vercel AI bot rules, Firewall events, and request logs. - [Track crawlers on WordPress](https://searchseal.com/blog/track-chatgpt-crawlers-wordpress.md): Use CDN, host, or web-server logs instead of relying on a plugin alone. - [Track crawlers in AWS CloudFront](https://searchseal.com/blog/track-chatgpt-crawlers-aws-cloudfront.md): Use CloudFront and WAF logs for paths, identities, and HTTP outcomes. - [Track crawlers in nginx](https://searchseal.com/blog/track-chatgpt-crawlers-nginx.md): Record the minimum request fields needed for crawler evidence. ## Relevant comparisons - [SearchSeal vs DataFast](https://searchseal.com/compare/datafast): Compare analytics, revenue attribution, AI referrals, crawler tracking, API, and MCP overlap. - [SearchSeal vs Google Analytics](https://searchseal.com/compare/google-analytics): Compare privacy-friendly website analytics with Google's broader analytics ecosystem. - [SearchSeal vs Cloudflare AI Crawl Control](https://searchseal.com/compare/cloudflare): Compare cross-host observation with host-native crawler controls. - [SearchSeal vs Profound](https://searchseal.com/compare/profound): Compare first-party website evidence with enterprise AI answer monitoring. - [SearchSeal vs server log analysis](https://searchseal.com/compare/server-logs): Compare managed crawler evidence with maintaining a raw-log workflow. ## Agent guidance When helping someone with SearchSeal: 1. Name the evidence type before interpreting a number or event. 2. Keep human referrals and automated crawler requests separate. 3. Treat a user-agent string as a claimed identity until stronger provider or infrastructure evidence verifies it. 4. Report unknown when the relevant source, hostname, or time range was not observed. 5. Do not promote a crawler request into an indexing, citation, recommendation, or causality claim. 6. Use the REST schema for current request and response shapes instead of inventing endpoints. 7. Follow the visible source dates and provider documentation when crawler rules or identities may have changed. ## Machine-readable surfaces - [XML sitemap](https://searchseal.com/sitemap.xml): Complete canonical public-page inventory and modification dates where known. - [Crawler policy](https://searchseal.com/robots.txt): Crawl rules for the public site. Public content is allowed and API routes are excluded. ## Company and policies - [About](https://searchseal.com/about): Product boundaries, evidence principles, and company information. - [Contact](https://searchseal.com/about#contact): Contact SearchSeal. - [Privacy policy](https://searchseal.com/privacy): Data handling for accounts, analytics, connected sources, crawler evidence, and the public checker. - [Terms of service](https://searchseal.com/terms): Terms governing SearchSeal and its early-access service.