by imedes 1 (0 reviews)

Imedes AI Bot Verify

Name: Imedes AI Bot Verify
Author: imedes

Verify supported AI bot identities, allow legitimate agents, and block spoofed claims.

Imedes AI Bot Verify ranks #63,733 among WordPress.org plugins with 1+ active installations, is #2,854 of 5,058 in the Security category, a 1/5 rating from 0 reviews, and was last updated Sep 7, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v1.0.0 Current Version v1.0.0

Updated 2 months ago Last Update on 07 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#2,854 of 5,058 in Security

View on WordPress.org

Rank

#63,733

— No change

Active Installs

-50%

KW Avg Position

N/A

— No change

Downloads

314

+5 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

50,796

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 8 more installs to reach 10+

Rank Changes

Current #63,733

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

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

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

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Sep 07, 2026
Requires WP: 6.2+
Tested Up To: 7.1
PHP Version: 8.1 or higher
Author: imedes

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

AI bots crawler security verification

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

Akismet Anti-spam: Spam Protection

5M+ installs

Wordfence Security – Firewall, Malware Scan, and Login Security

5M+ installs

#11

Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)

Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention

View all Security-and-spam-protection plugins

Frequently Asked Questions

Common questions about Imedes AI Bot Verify

No. A supported AI bot request that verifies successfully is allowed to continue normally. ABV blocks requests that claim a supported AI bot identity but fail the corresponding verification.

Blocking all AI bots is a valid policy if a site does not want AI access. ABV is for sites that want to distinguish legitimate AI traffic from impersonation. This makes it possible to allow genuine supported AI agents without automatically trusting every request that uses their names.

Yes. A User-Agent can be changed freely and is not proof of identity. A scraper can send a request using a known AI bot User-Agent. ABV verifies supported claims instead of trusting that string by itself.

An identity claim is only worth faking if it is worth something. Someone impersonating an AI bot picks the identity most likely to grant the desired treatment — meaning the most recognized and most trusted names, not obscure or low-traffic crawlers. ABV therefore focuses verification on the AI bot identities most likely to be impersonated, rather than attempting to cover every crawler that claims to be AI-related.

Yes. That is one reason to verify identity before applying access rules. A site may choose to allow a verified AI agent where generic crawlers or scraping tools are restricted. Without verification, a scraper could attempt to obtain the same treatment simply by copying the AI bot's User-Agent. ABV itself does not grant special content permissions. It only verifies the supported identity claim. The site's own rules still decide what a verified agent may access.

Yes, depending on configuration. The presence of QUIC.cloud does not by itself make a site incompatible with ABV. Using QUIC.cloud for asset caching or other services that still allow relevant main document requests to reach the origin does not prevent ABV from operating. The incompatible case is QUIC.cloud CDN caching of the main document. ABV's requirement test checks the public main document for the QUIC.cloud cache header. If that cache layer is active for the main document, the requirement is blocked because the request can be answered before WordPress and ABV receive it. The issue is main-document caching before the origin, not QUIC.cloud itself.

The same principle applies. Cloudflare or another CDN is not inherently incompatible with ABV. Asset caching, DNS, security features and other proxy services can be used normally as long as the relevant main document requests still reach the origin. If an upstream cache is active for the main document, ABV cannot reliably guarantee that every supported AI request reaches the verification gate. The requirement test therefore checks for main-document cache indicators rather than treating CDN presence alone as a failure.

No. ABV verifies the main request handled by WordPress/PHP. Cached CSS, JavaScript, fonts, images and other static assets do not need to pass through ABV and do not interfere with identity verification.

The underlying issue is the same: ABV cannot verify a request that is answered from page cache before the verification gate runs. ABV therefore installs origin-side compatibility rules for supported AI bot claims and the supported OpenAI Signature-Agent. LiteSpeed/LSCache receives a native no-cache flag. Apache rewrite-based page caches are bypassed by routing matching main-document requests to WordPress before their static cache rules can serve HTML. This covers the rewrite-cache modes used by WP Rocket, WP Super Cache Expert mode, W3 Total Cache Disk: Enhanced and WP Fastest Cache, in addition to LiteSpeed/LSCache. If ABV blocks a request, the 403 response is also sent with no-cache headers. An upstream CDN cache is a separate layer. ABV cannot control an edge cache in the same way, so main-document caching at that layer must be configured so that requests requiring verification still reach the origin.

Yes. Spoofed AI bot requests can target valid pages as well as outdated, random or non-existent URLs. When those requests reach PHP and WordPress, they can still trigger WordPress processing even if the final result is only a 404 response. ABV blocks failed supported identity claims at its early verification gate before the normal WordPress request continues. This can avoid unnecessary WordPress execution for those fake AI bot requests. Requests that are answered by the web server, CDN or another upstream layer before they reach WordPress are outside ABV's request path.