About this plugin
Trakkr Crawler Tracking records requests whose User-Agent matches a known AI crawler pattern. It runs on the server after WordPress finishes the request, so it can record the final status code without adding a script, pixel, cookie, or public credit to your site.
The plugin is designed for site owners who use the Trakkr service. After you connect WordPress to Trakkr with a WordPress Application Password, Trakkr can retrieve recent crawler records through authenticated REST endpoints and acknowledge the rows it has received.
What it does
- Matches known AI crawler and AI assistant User-Agents, including GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Agent, and others.
- Stores the crawler name, User-Agent, requested URL, request method, referring URL, response status, IP address, country code, and timestamp.
- Removes query strings and fragments from requested and referring URLs before storage.
- Supports common proxy headers from Cloudflare, Sucuri, and other reverse proxies. These IP values are informational and are never used for access control.
- Exposes records only through capability-protected WordPress REST endpoints.
- Adds a dedicated Trakkr Crawler Sync role that can retrieve and acknowledge crawler rows but cannot publish content, edit posts, upload media, change site options, or write files.
- Lets an authenticated site administrator publish approved robots.txt, llms.txt, llms-full.txt, sitemap redirect, structured data, and supported SEO metadata changes from Trakkr.
- Deletes synced local rows after 30 days and unsynced local rows after 90 days.
The plugin does not contact Trakkr or any other external server by itself. It does not load remote code, remote fonts, tracking pixels, or third-party scripts. It does not include a custom updater.
org supplies plugin updates for the directory release.
External Service
This plugin works with Trakkr, an AI visibility service operated by Trakkr. A Trakkr account is required to view the collected crawler records in the Trakkr dashboard or use Trakkr’s connected-site publishing features.
The plugin does not initiate outbound requests. When an authorized user explicitly connects the site in Trakkr, the Trakkr service sends authenticated HTTPS requests to this site’s WordPress REST API. WordPress Application Password authentication and WordPress capabilities control access.
Crawler-only connections can use a dedicated user with the Trakkr Crawler Sync role. Existing administrator connections remain supported.
For crawler syncing, the response can contain the crawler User-Agent, crawler name and type, requested URL, request method, referring URL, IP address, country code, response status, and timestamp. Query strings and fragments are removed from both URLs. Trakkr uses this data to show crawler activity for the connected site.
Trakkr also sends the IDs it received back to WordPress so those local rows can be marked as synced.
If the administrator uses connected-site publishing, Trakkr can read or update only the allow-listed WordPress options, files, post metadata, and publish-operation markers exposed by this plugin. These actions occur only after the administrator connects the site and requests or approves the related action in Trakkr.
- Trakkr service: https://trakkr.ai
- Terms of Service: https://trakkr.ai/terms
- Privacy Policy: https://trakkr.ai/privacy
Privacy
The plugin writes a local database row only when a request’s User-Agent matches one of its known AI crawler patterns. User-Agent strings can be imitated, so site owners should still treat the stored IP address and URL paths as potentially personal data.
To reduce collection, query strings and fragments are removed from requested and referring URLs before storage. The plugin does not set cookies and does not add front-end JavaScript.
Synced rows are deleted from the WordPress database after 30 days. Rows that have not been synced are deleted after 90 days. Deleting the plugin removes its database table, scheduled cleanup event, and stored options.
Trakkr keeps connected-site data according to its Privacy Policy. Site owners should review that policy and add the suggested Trakkr text from Settings > Privacy to their own privacy policy where applicable.