Aprašymas
Understand how AI tools reach your WordPress site.
Which AI crawlers are reaching your content? Which pages receive visits referred by ChatGPT, Claude, Perplexity, Gemini, Microsoft Copilot, and other supported AI tools?
Readable brings these signals into a seven-day dashboard in WordPress, giving marketers a clear view of AI activity around their content.
See what is happening
- View recognised AI crawler requests and AI referral visits separately.
- Find the top AI sources and pages receiving activity.
- Follow daily trends over the past seven days.
- Review recent activity in one place.
Supported AI referral sources include ChatGPT, Claude, Perplexity, Gemini, and Microsoft Copilot. The dashboard recognises supported AI and search crawler signatures.
Find the content getting noticed
See which pages AI tools explore and where AI referrals land. Use these insights to guide your next content review and keep track of AI activity over time.
Set up your site
Install the plugin, create or sign in to a free Readable account, and verify your WordPress site. Add the Site ID and WordPress analytics key shown by Readable, then explicitly choose to enable analytics collection. Collection stays off until a site administrator enables it. Your WordPress Address must use HTTPS, and its exact hostname must be enabled for analytics in Readable.
Matching completed requests are placed in a durable local queue and sent to Readable in the background. Your visitor response does not wait for Readable. Dashboard reads are cached locally for five minutes and can be refreshed by an administrator.
What the plugin sends
For matching visits only, the plugin sends:
- The configured Readable Site ID.
- HTTPS hostname and path, without query strings or fragments.
- A recognized AI agent user agent, or a fixed generic value for an AI-referred person.
- A normalized AI referral source, never the raw referral URL.
- Request time, response status, content type, duration, and random event identity.
The plugin does not send IP addresses, cookies, request or response bodies, authorization values, arbitrary headers, raw query strings, raw referral URLs, or full browser user agents for AI-referred people.
External service
This plugin sends the limited analytics data described above to Readable’s ingestion service at https://ingest.sonicadn.com/v1.0/traffic/data/wordpress. This service is required for the plugin’s analytics functionality. Data is sent only after a valid Readable Site ID and WordPress analytics key have been configured and a site administrator explicitly enables analytics collection.
The plugin also requests the site’s aggregated analytics from https://www.tryreadable.ai/api/external-agentic/integrations/wordpress/analytics when an administrator opens or refreshes the plugin settings page. The saved WordPress analytics key is sent in the HTTPS authorization header. The service derives the Readable site from that key and returns only the site’s bounded seven-day WordPress analytics; it does not accept a site ID from the browser for this read.
Readable privacy policy: https://www.tryreadable.ai/privacy
Readable terms: https://www.tryreadable.ai/terms
Product and setup information: https://www.tryreadable.ai/integrations/wordpress
Support
For setup and product guidance, visit https://www.tryreadable.ai/integrations/wordpress. For bug reports and support questions, use the Support tab on this plugin’s WordPress.org page. Do not post Site IDs, API keys, or visitor data in the public support forum.
Ekrano nuotraukos
Diegimas
- Install and activate Readable – AI Agent Analytics.
- In WordPress, open Settings Readable Agent Analytics.
- Visit https://www.tryreadable.ai/integrations/wordpress and create or sign in to a free Readable account.
- Start WordPress setup, paste the short-lived ownership challenge into the plugin’s verification section, and return to Readable to verify the site.
- Copy the one-time Site ID and WordPress analytics key into the plugin.
- Review the privacy boundary, check Enable analytics collection, and save.
Your WordPress Address must use HTTPS, and its exact hostname must be enabled for analytics in Readable.
DUK
-
Does this slow down my website?
-
Readable is never called while generating the visitor’s page response. Matching completed requests are first written to a local WordPress database queue. WP-Cron sends bounded batches later.
-
Does it collect every visitor?
-
No. The plugin queues only recognized AI agents and visits whose referrer hostname belongs to a supported AI assistant.
-
Does the dashboard show unique visitors?
-
No. The dashboard counts detected requests and AI referral visits. A crawler fetching a page is different from a person opening a link from an AI tool, and repeated requests can be counted more than once. The figures do not identify unique people.
-
Will it record requests served entirely by a page cache or CDN?
-
Not always. The plugin records requests that reach WordPress and run PHP. A full-page cache or CDN can serve a response before WordPress runs, so those cache hits are outside the plugin’s coverage. Sites that need edge-wide coverage should use analytics from their CDN or reverse proxy as well.
-
Does recognition prove which company operated an agent?
-
No. Recognition is based on request user-agent, referral-host, and supported agent-signature signals. Those values can be spoofed, so the dashboard is useful traffic evidence, not cryptographic identity verification.
-
Does it track conversions or citations in AI answers?
-
No. The plugin does not prove sales, leads, or other conversions, and it does not show whether your brand or page was mentioned or cited in an AI answer. It reports supported crawler requests and visits referred from supported AI tools that reach WordPress.
-
Will installing the plugin improve my search or AI rankings?
-
No. The plugin provides analytics evidence for your content reviews. It does not change your content or guarantee search rankings, AI visibility, mentions, or citations.
-
Does it collect personal data?
-
The plugin is designed to exclude IP addresses, cookies, bodies, query strings, raw referral URLs, and browser fingerprints for referred people. Site owners remain responsible for describing their use of analytics in their own privacy notice where required.
-
Events remain in the local queue and are retried with bounded exponential backoff. Unsent rows expire after 30 days. Rejected events are moved aside so they cannot block newer traffic and expire after 14 days. Cleanup removes at most 1,000 expired rows per run. The queue is capped at 50,000 rows; when it is full, recent retryable events are preserved and the plugin visibly reports new events that could not be stored.
-
How do I get a Site ID and key?
-
Visit https://www.tryreadable.ai/integrations/wordpress and choose Set up free connection. A free account can verify one WordPress site through a short-lived challenge visible only after a WordPress administrator saves it. Each site has one active key bound to its Readable WordPress integration. Replacing the key revokes the previous one.
Atsiliepimai
Įskiepis neturi atsiliepimų.
Programuotojai ir komandos nariai
“Readable – AI Agent Analytics” yra atviro kodo programa. Prie jos sukūrimo prisidėję žmonės surašyti toliau.
Autoriai
Išverskite “Readable – AI Agent Analytics” į savo kalbą.
Domina programavimas?
Peržiūrėkite kodą, naršykite SVN repozitorijoje, arba užsiprenumeruokite kodo pakeitimų žurnalą per RSS.
Pakeitimų istorija
1.1.0
- Added a seven-day AI audience dashboard inside WordPress.
- Added bounded top-source, top-page, daily activity, and recent-activity views.
- Added a separate read permission to WordPress integration keys; ingestion remains on SonicADN.
- Added explicit opt-in, WordPress Privacy Policy helper text, bounded retention, visible queue limits, and daily cleanup.
- Added free self-service setup with a short-lived WordPress-admin ownership challenge and one-time site key reveal.
1.0.0
- Initial public release.
- Durable, asynchronous delivery to Readable’s dedicated WordPress ingestion edge.
- Privacy-safe AI agent and AI referral classification.
- Exact acknowledgement validation, retry backoff, and rejected-event quarantine.