AI Kansoku Lab Tracker vs Crawler Record

Crawler Record shows when Google, ChatGPT, Claude, and other top bots last visited pages on your website, so you can be confident your pages are being crawled. This is the first step in ensuring these platforms index your website so they can serve it to visitors. The data covers several top user-agents, including: Google Bing ChatGPT (OpenAI) Claude (Anthropic) Perplexity Meta Apple Amazon DuckDuckGo Common Crawl Administrators with manage_options can view this information: Admin page: a grouped list of all crawlers, with last seen time, last page, and robots.txt status for the crawler. Recent Pages: From the admin page, you can select a crawler and see its latest visited pages, the response status WordPress observed, and a destination when WordPress exposes one for a retained 3xx response. Crawler Activity Overview: Review 28-day visit totals, response-code health, crawler mix, a daily activity timeline, and crawler staleness. URL reports use up to the 50 most recent recorded visits per crawler. Crawler Status Overview: Filter the main dashboard and crawler table by crawlers that visited within 28 days, have become stale, or have never visited. The unfiltered dashboard includes the stale-crawler age distribution alongside current activity; the Stale view focuses on that distribution, latest-visit details, and Recent Pages links instead of empty or potentially misleading historical metrics. Header Codes for User-Agents: Did a user-agent successfully visit a page (2xx), receive a 3xx response, or land on a page that was missing or inaccessible (4xx)? Crawler Record will show you. The 3xx report includes every retained 3xx status, including 304 Not Modified; only responses with an observable redirect destination show where the request was sent. Admin Bar (front-end): quick-glance status for all user-agent visits. Per Page/Post: From the edit screen on any page or post, you can see the last time each crawler visited that page. Administrators can also open the main dashboard or an individual crawler’s Recent Pages report from this box. Robots-aware: The plugin checks your robots.txt and evaluates Allow/Disallow rules for a given path. WordPress’s “Discourage search engines” preference is reported separately because it asks compliant search engines to avoid indexing. Response-aware: Recent visits include the final HTTP status WordPress can observe, including ordinary WordPress 404 pages and 3xx responses that occur after tracking begins. The 3xx report groups all retained 3xx statuses together; 304 Not Modified does not redirect and therefore has no destination. Other 3xx rows show a destination only when WordPress/PHP exposes one. Responses served by a CDN, web server, static cache, or security layer before WordPress runs cannot be recorded. Identification note: Crawler identification is based on the supplied user-agent string. User-agent strings can be spoofed, and this plugin does not verify IPs. Learn how to use this plugin. Highlights Supports common user-agent variants for Google, Bing, OpenAI (ChatGPT), Anthropic (Claude), Perplexity, Meta, Apple, Amazon, DuckDuckGo, and Common Crawl. robots.txt status computed from a local physical or WordPress virtual source without outbound requests. Known limitations Can only track crawlers from the time the plugin is installed—it cannot reconstruct earlier visits. Per-post “last seen” timestamp and user-agent metadata update at most once every 10 minutes by default. Separately, rapid same-crawler, same-URL, same-status visits are suppressed for 30 seconds, and a high emergency ceiling retains up to 50 visits per crawler per minute. Concurrent requests matching the same crawler are not coordinated. One database write may replace another, causing a visit to be absent from recent history or daily totals, or causing the latest-visit fields to reflect whichever write finished last. Dashboard totals are therefore approximate retained activity rather than an exact raw access log because of throttling, retention limits, and possible concurrent writes. Response codes are available only for requests that reach WordPress. Responses served earlier by a CDN, web server, static cache, or security layer are outside the plugin’s visibility. The 3xx report includes all retained 3xx statuses, including 304 Not Modified. Redirect destinations are available only when WordPress/PHP exposes a Location header. Redirects issued before WordPress runs cannot be recorded, and a followed destination is retained as a separate visit if it reaches WordPress. Stored source and redirect URLs include scheme, validated host, optional port, and path. Query strings are omitted to avoid retaining sensitive tokens, personal data, and high-cardinality tracking parameters. Reverse-proxy configuration can affect the scheme WordPress observes. URLs up to 114 characters are stored normally. URLs from 115 through 1,028 characters retain the visit with a 100-character prefix and an excessive-length marker; they are displayed with an ellipsis and are not linked. URLs longer than 1,028 characters are omitted from URL-level reports. Sitewide tracking for such requests is subject to the 30-second suppression window, while applicable per-post metadata uses its separate 10-minute throttle. Privacy This plugin stores: – Timestamps of crawler visits (float, with microseconds) – Exact matched crawler user-agent strings, bounded to 512 characters – Last URL and a bounded 50-visit recent history per crawler – Final HTTP response status observable by WordPress for recent crawler visits – Observable redirect destination, when PHP exposes one for a retained 3xx response other than 304 Not Modified – Last post ID per crawler (for admin performance) Stored source and redirect URLs omit query strings. Incoming hosts are validated and used only for reporting; they are never used for redirects, filesystem access, or outbound requests. Existing URL length limits apply independently to redirect sources and destinations. The plugin stores requests matching configured crawler patterns, but user-agent strings can be spoofed. It performs no IP verification and transmits no data to third parties. Crawler reports, the front-end admin-bar menu, and the post/page meta box require manage_options. Source URLs with hosts outside the configured WordPress home/site hosts are displayed as non-clickable diagnostic text. Uninstall removes all current and legacy Crawler Record options, transients, and post metadata from each site in a multisite network; WordPress removes the plugin files themselves. License GPLv2 or later. See LICENSE file.

AI Kansoku Lab Tracker detects visits from AI-related crawlers such as GPTBot, ChatGPT-User, ClaudeBot, and PerplexityBot using PHP server-side detection. AI crawlers often do not execute JavaScript, so JavaScript-based analytics tools such as GA4 may not record these visits as normal pageviews. This plugin helps site owners observe AI crawler activity at the server level. Detected crawler visits are stored in your WordPress database. Optional external tracking is available only when you explicitly enable it in the settings page. Features 34 AI-related crawler patterns from 20+ companies – GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, Anthropic-AI, PerplexityBot, Perplexity-User, Google-Extended, Google-NotebookLM, Google-Agent, ByteSpider, Meta-ExternalAgent, Meta-ExternalFetcher, AppleBot, AppleBot-Extended, DeepSeek, Grok, xAI-SearchBot, CopilotBot, Bingbot, AmazonBot, YandexBot, YouBot, Diffbot, ShapBot, TavilyBot, DuckAssistBot, Cohere-AI, Timpibot, FirecrawlAgent, and related access patterns Training vs. user-triggered classification – Crawler visits are classified as either “Autonomous AI (training/patrol)” or “Human-triggered AI reference,” showing whether your content is being collected for AI training or actually being looked up because someone asked an AI about it Local crawler logging – Detected visits are stored in your WordPress database 30-day trend analysis – Dashboard with 30-day / 7-day period switching AI Exposure Score – Visibility score based on crawler activity Crawler breakdown – See which AI-related services visit your site most Top pages – Identify which pages AI crawlers focus on Explicit opt-in for external tracking – External transmission only activates when you enable it via checkbox Minimal performance impact – Optional external requests use non-blocking POST requests Front-end only – Does not fire on admin, cron, AJAX, or REST API requests WordPress standards – Uses wp_remote_post, register_setting, nonce verification, and proper escaping throughout 日本語の説明 AI Kansoku Lab Tracker は、GPTBot・ChatGPT-User・ClaudeBot・PerplexityBot などの AI 関連クローラーがあなたのサイトを訪問した記録を、WordPress 上で検知・可視化するプラグインです。 AI クローラーは JavaScript を実行しないことが多いため、GA4 などの JavaScript ベースのアクセス解析では通常のページビューとして記録されない場合があります。本プラグインは PHP によるサーバーサイド検知を採用し、AI クローラーの訪問をサーバーレベルで観測できるようにします。 検知したクローラーのログは WordPress のローカルデータベースに保存されます。外部トラッキングを有効にした場合のみ、AI観測ラボへデータを送信します。 主な機能: 20社以上・34種類のAI関連クローラーパターンを検知 「学習・巡回AI」と「人間起点のAI参照」を区別して表示 — サイトがAIの学習データとして収集されているだけなのか、それとも誰かが実際にAIに質問した結果として読まれているのかが一目でわかります 検知ログを WordPress のローカルDBに保存 30日間のトレンド分析（7日間表示への切り替え対応） AI露出スコアによる可視化 クローラー種別の内訳表示 よく見られているページの可視化 外部トラッキングは明示的なオプトイン方式 管理画面・AJAX・REST API・WP-Cron では実行しない設計 開発・運営: AI観測ラボ How It Works When a front-end page is requested, the plugin checks the User-Agent string against known AI-related crawler patterns. If a match is found, the detected visit is stored in your WordPress database. If you have explicitly enabled external tracking and configured a Site ID, the plugin also sends an asynchronous POST request to the AI Kansoku Lab API. This optional external request uses a non-blocking request so that the site visitor experiences no delay. External Services This plugin may connect to the following external service: AI Kansoku Lab https://www.ai-kansoku.com External tracking is opt-in only. Data is only transmitted after you explicitly enable external tracking in the plugin settings page. When an AI-related crawler is detected and external tracking is enabled, the following data is sent to the AI Kansoku Lab API: User-Agent string of the detected crawler URL path of the visited page HTTP referer header, if present HTTP status code of the page, such as 200 or 404 Site ID configured in the plugin settings No personally identifiable information is collected. This plugin does not collect cookies, account credentials, form contents, or visitor IP addresses. Service URL: https://www.ai-kansoku.com Privacy Policy: https://www.ai-kansoku.com/privacy Terms of Service: https://www.blog.ai-kansoku.com/terms Requirements WordPress 6.0 or higher PHP 7.4 or higher A free AI Kansoku Lab account is optional and only required if you want to use the external dashboard integration. Privacy Policy This plugin stores detected crawler visits in your WordPress database. This plugin can also connect to an external service to log AI-related crawler visits in the AI Kansoku Lab dashboard. External tracking is opt-in only and only activates after explicit user consent via the settings page. Data transmitted to AI Kansoku Lab when external tracking is enabled: User-Agent string of the detected crawler URL path of the visited page HTTP referer header, if present HTTP status code of the page, such as 200 or 404 Site ID configured in plugin settings No personally identifiable information is collected. This plugin does not collect cookies, account credentials, form contents, or visitor IP addresses. Full privacy policy: https://www.ai-kansoku.com/privacy