Zluck AI Traffic Insights
by Maulik Vora 0 (0 reviews)

Zluck AI Traffic Insights

See which visitors came from AI assistants such as ChatGPT and Perplexity, and how they behave compared with everyone else.

Zluck AI Traffic Insights ranks #72,668 among WordPress.org plugins with 0+ active installations, is #1,670 of 2,168 in the Analytics category, and was last updated Oct 16, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v1.0.0 Current Version v1.0.0
Updated 2 weeks ago Last Update on 16 Oct, 2026
Refreshed 3 days ago Last Refreshed on
#1,670 of 2,168 in Analytics Downloads -48.8% this week Actively maintained
View on WordPress.org
Rank
#72,668
— No change
Active Installs
0+
— No change
KW Avg Position
N/A
— No change
Downloads
244
+10 today
Support Resolved
0%
— No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 10

Total Progress 0%
0+ 10+
45,100
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 10 more installs to reach 10+

Rank Changes

64,680 66,408 68,137 69,865 71,593 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
60,195 63,191 66,187 69,182 72,178 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
Current #72,668
Change
Best #

Upgrade to Pro

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

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
0 10 20 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026
Downloads
Growth
Peak

Upgrade to Pro

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

Upgrade Now

Reviews & Ratings

0.0
0 reviews
Overall 0%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Zluck AI Traffic Insights

Three common reasons. The site has had few visitors from assistants yet, which the empty state on each screen says plainly. The scheduled jobs have not run yet; they run about once an hour when the site has visitors, so on a quiet site the first numbers take two to three hours to appear after the first visit, and the Settings screen has a "Process now" button if you do not want to wait. Or the tracking script is not reaching the plugin; see the next question.
A visit is Likely AI when two things are true together: a first-time visitor arrived with no referrer and landed straight on an inner page, and a verified AI crawler had read that same page within the past 7 days (a filter can change the window). Either one alone is not enough: a bookmarked inner page, or a direct visit to a home page that crawlers read all the time, stays "everyone else". It is an estimate, so the plugin classifies down when unsure and never adds Likely into the Confirmed number. Where a total appears it is a range, for example "12 to 19 sessions". The working target is that fewer than 2 in 100 visits that really came from a search engine would be called Likely. To see why a particular visit was called Likely, export the sessions file from the Overview screen; its "Reason" column reads, for example, "Landed deep on a page ChatGPT-User read 2 days earlier, with no referrer". On WooCommerce the "AI traffic" panel on an order shows the same reason. Every report screen also has a small help icon beside "Likely AI" and a "Help" tab at the top right with this explanation.
Something between the visitor's browser and the plugin. The usual causes: a caching or optimisation plugin that delays or strips inline scripts; a security plugin that blocks the REST API for visitors who are not logged in; a theme that does not call wp_footer(); Cloudflare bot protection challenging POST requests; or a consent tool set to block unknown inline scripts. The plugin cannot fix any of these from its side, but the settings screen tells you the last time a page view arrived so you can tell whether a change helped.
The plugin relies on the WordPress scheduler (WP-Cron) for three small jobs: turning page views into sessions, writing the daily totals the screens read, and deleting old rows. The built-in scheduler only runs when someone visits the site, and some hosts and security plugins block it. The notice names the job and what it means. To fix it, ask your host to call wp-cron.php every 15 minutes (most hosts have a setting for this), or install a plugin such as WP Crontrol to see the plugin's aitraf_ events and run one by hand. The "Process now" button on the Settings screen runs the session and daily-totals jobs immediately, which is the quickest way to confirm the fix worked.
No. On the server it adds under 1 ms to building a page, and nothing at all when a page cache serves the page. In the browser it adds one script under 3 KB that loads nothing else and sends one small request to your own site when the visitor leaves. There is no database write while the page is built, and nothing about your site or your visitors is sent anywhere. The only outside downloads are the public crawler lists described under Privacy, fetched in the background, never while a page is built. The full numbers, and how they were measured, are under Performance in the description.
Usually not. The script is part of the cached page and already carries the attributes that WP Rocket, LiteSpeed Cache, Autoptimize and Cloudflare Rocket Loader use to leave a script alone. Two things to know: if a "delay JavaScript until interaction" feature is on and the numbers look low, add aitraf-beacon to its exclusion list; and after switching cookieless mode on or off, clear the page cache so cached pages pick up the change.
Administrators are never tracked, so that a site owner previewing the site does not pollute the numbers. To test order attribution, place the order in a private browser window where you are not logged in.
A hit is "verified" when the visitor's address is on the list the crawler's operator publishes. If your site sits behind a proxy or CDN that does not pass the real visitor address through, every hit is checked against the proxy's own address and shows as claimed only. Your host can usually pass the real address through; a developer can also supply it with the aitraf_client_ip filter.
An AI lookup is one verified request from an assistant's live answer bot: ChatGPT-User, Claude-User or Perplexity-User. These bots fetch a page while the assistant is answering a person's question, so a lookup means the assistant read your page to help with an answer. It is not a citation. The plugin can see that the page was read; it cannot see the question, the answer, or whether the answer mentioned or linked to your site. Search-index bots such as OAI-SearchBot and training bots such as GPTBot are not lookups; they appear in the crawler table instead. Requests that could not be verified against the operator's published addresses are never counted as lookups.
Administrators always. On the settings screen you can tick other roles; a ticked role can open the report screens and export CSV files, but not change settings.

Sign In / Register

You need to sign in or register to use this feature.