by Airefs 5 (2 reviews)

AI Search Analytics & Tracking

Name: AI Search Analytics & Tracking
Rating: 5.0 (2 reviews)
Author: Airefs

Track AI search impressions and clicks from ChatGPT, Perplexity, Claude & other LLMs and improve your website's visibility across AI search results.

AI Search Analytics & Tracking ranks #21,523 among WordPress.org plugins with 40+ active installations, is #542 of 2,168 in the Analytics category, a 5/5 rating from 2 reviews, and was last updated Oct 14, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.8 (Current: 7.1.4)

v1.2.6 Current Version v1.2.6

Updated 3 weeks ago Last Update on 14 Oct, 2026

Refreshed 1 week ago Last Refreshed on

#542 of 2,168 in Analytics Top 50% by installs Downloads -35.1% this week Actively maintained

View on WordPress.org

Rank

#21,523

— No change

Active Installs

40+

— No change

KW Avg Position

155

3 better

Downloads

3.1K

+9 today

Support Resolved

100%

— No change

Rating

100%

Review 5 out of 5

5 (2 reviews)

Next Milestone 50

Total Progress 70%

40+ 50+

1,513

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 3 more installs to reach 50+

Rank Changes

Current #21,523

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0

2 reviews

Overall 100%

2 (100%)

0 (0%)

Support Threads Overview

Resolved

Unresolved

Total Threads

Resolved

Unresolved

100%

Resolution Rate

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.2.6
Last Updated: Oct 14, 2026
Requires WP: 5.0+
Tested Up To: 7.0.8
PHP Version: 7.4 or higher
Author: Airefs

Support & Rating

Rating: ★ ★ ★ ★ ★ 5
Reviews: 2
Support Threads: 1
Resolved: 100%

Keywords

AI analytics search tracking

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,015

Site Kit by Google – Analytics, Search Console, AdSense, Speed

5M+ installs

MonsterInsights – Google Analytics Dashboard for WordPress (Website Stats Made Easy)

GTM4WP – A Google Tag Manager (GTM) plugin for WordPress

700K+ installs

#83

Header Footer Code Manager

600K+ installs

#105

WP Statistics – Simple, privacy-friendly Google Analytics alternative

500K+ installs

#112

GA Google Analytics – Connect Google Analytics to WordPress

View all Analytics plugins

Frequently Asked Questions

Common questions about AI Search Analytics & Tracking

The plugin sets a first‑party airefs_session_id cookie for session continuity. We do not forward site visitors' existing Cookie headers or authentication headers containing credentials.

The local queue holds visitor IP addresses, User-Agent strings, and session IDs until Airefs confirms delivery. Pending events do not expire and can remain indefinitely during an outage or while tracking is paused. Deactivation preserves them; deleting the plugin through WordPress uninstall removes the local queue. The API anonymizes non-bot IP/User-Agent values before persisting analytics records; bot records may retain them for attribution and validation. Queued page URLs retain origin, path, validated WordPress page IDs, explicitly configured content parameters, and supported UTM parameters. Other query parameters and fragments are removed; URLs containing credentials are rejected. Referrers retain only origin and path.

Valid WordPress p and page_id parameters are preserved automatically, so /?p=123 and /?p=456 identify different pages. IDs must contain 1–20 decimal digits and be greater than zero; leading zeros are removed. For other content selectors, open Settings → Airefs Tracking → Advanced Settings → Content Query Parameters. Enter comma-separated names, such as countries, to distinguish /jobs?countries=201 from /jobs?countries=202. Each WordPress site has its own setting. Up to 16 custom names are allowed, with a letter first and up to 64 letters, numbers, underscores or hyphens. Names are case-sensitive. Only configure values that are safe to send to analytics, never personal data or credentials. Known email, credential, session and tracking names are blocked even if entered, including api_key, access_key, private_key, auth_code and email_address. Content values must be nonempty, contain no control characters and fit within 200 UTF-8 bytes. Duplicate query names are discarded. Retained content parameters are sorted and encoded consistently; a content query exceeding 2,048 encoded bytes is discarded. The five supported UTM parameters remain attribution fields and do not distinguish pages. Fragments are not tracked. The setting is captured with each new event and remains the same through delivery retries, even if you change the setting later. Previously saved events and historical reports cannot recover query values that were already removed.

Impressions are server-side visits from AI crawlers — bots sent by ChatGPT, Perplexity, Claude, and other LLMs to crawl your pages in order to answer user queries or gather training data. Clicks are visits from real human users who saw your site cited in an AI-generated answer and clicked through to your site. Both are tracked automatically once the plugin is installed and connected.

Airefs tracks crawler and click traffic from ChatGPT, Perplexity, Claude, Google Gemini, Microsoft Copilot, Meta AI, Amazon, and other LLMs. Coverage is updated as new AI systems emerge.

The plugin writes events to a local queue instead of contacting the analytics API during page requests. WP-Cron and a protected background runner send queued events in small batches to reduce network requests. Each event still needs its own delivery confirmation; unconfirmed events stay queued. Queue writes, the footer script, and its same-site browser request still use server and browser resources; the plugin does not promise zero overhead.

Clicks data typically appears within 1–2 days of installation. Impressions data appears as AI crawlers visit your site — frequency depends on how often AI systems crawl your content.

Cached HTML can still run the browser tracker if it contains the script and the WordPress REST endpoint is reachable. AI crawler tracking requires the request to reach WordPress: a CDN or static page cache that responds before PHP runs prevents server-side tracking. The plugin includes WP Rocket user-agent exclusions and optional LiteSpeed handling, but cache behavior depends on your cache configuration. Clear page caches after changing plugin settings or updating the plugin, and verify both crawler and browser tracking on your site.

Saved events stay in the local database until Airefs confirms that it has stored them. Temporary failures are retried with increasing delays; retries reuse the same event ID so reports do not count them twice. Events are not removed because they are old, delivery failed, or tracking was disabled. Some errors need attention before delivery can resume. WP-Cron is the normal scheduler. A protected background runner also starts from site requests and continues processing a backlog, so delivery does not rely only on WP-Cron. Both mechanisms can be blocked by hosting restrictions. For low-traffic sites or disabled WP-Cron, ask your host to run WordPress scheduled events at least once a minute and allow loopback requests. If both mechanisms stop, delivery waits safely in the queue; they must recover before it can resume.

Open Settings → Airefs Tracking → Background delivery. It shows pending events, the oldest event, last attempt, last confirmed delivery, blocked events, network storage use, and events that could not be saved. Retry delivery requests background processing; a connection test checks API access and local storage readiness. If local storage setup fails, a persistent red administrator notice states that tracking cannot save new events. Background delivery shows Storage setup: Failed, explains what to ask your host to check, and provides Retry storage setup. This action is available even while tracking is paused. Automatic setup attempts wait 15 minutes after a failure; a manual retry runs immediately. Setup retries preserve existing queued events. Events that could not be saved cannot be recovered later. The API connection test reports local storage readiness separately and cannot show a successful tracking setup when the queue is unavailable. A ready queue and a working connection do not prove delivery: check Last confirmed delivery for that. Queue storage defaults to 64 MiB across the WordPress network, with a 100,000-event safety limit and 32 KiB per-event limit. The airefs_tracking_queue_capacity_bytes filter can adjust the storage budget. A full or unavailable database cannot accept new events: the browser endpoint returns an error and the plugin records a rejection when the database is available. Already saved events are never evicted to make room. A browser response accepting an event into the queue is not yet an Airefs delivery receipt.