Title: GlobalDev AI Traffic Control
Author: Globaldev
Published: <strong>August 24, 2026</strong>
Last modified: August 24, 2026

---

Search plugins

![](https://ps.w.org/globaldev-ai-traffic-control/assets/banner-772x250.png?rev=
3662677)

![](https://ps.w.org/globaldev-ai-traffic-control/assets/icon-256x256.png?rev=3662677)

# GlobalDev AI Traffic Control

 By [Globaldev](https://profiles.wordpress.org/globaldevitus/)

[Download](https://downloads.wordpress.org/plugin/globaldev-ai-traffic-control.1.0.0.zip)

 * [Details](https://wordpress.org/plugins/globaldev-ai-traffic-control/#description)
 * [Reviews](https://wordpress.org/plugins/globaldev-ai-traffic-control/#reviews)
 *  [Installation](https://wordpress.org/plugins/globaldev-ai-traffic-control/#installation)
 * [Development](https://wordpress.org/plugins/globaldev-ai-traffic-control/#developers)

 [Support](https://wordpress.org/support/plugin/globaldev-ai-traffic-control/)

## Description

GlobalDev AI Traffic Control is primarily an **AI crawler traffic monitoring and
access-control plugin**. It is not an llms.txt generator with a few extra settings:
its core job is to identify known AI crawler requests, record what they request,
evaluate those requests against your policy, and optionally enforce that policy.

**Monitor identifiable AI crawler traffic.** The dashboard records requests from
supported AI crawler user agents, including which crawler requested which URL, when
it happened, and whether the request matched or violated your configured policy.
Ordinary visitors are not logged. Raw IP addresses are not stored; when an identifier
is needed, the plugin stores a one-way hash.

**Create a policy hierarchy.** Set a site-wide default, override it for a specific
crawler, and override that again for an individual post or page. This lets you block
model-training crawlers while still allowing AI search crawlers or live assistant
fetchers, or exclude only selected content.

**Choose the enforcement level.** You can record policy violations only, send `X-
Robots-Tag: noai, noimageai`, or return HTTP 403 for recognized crawler requests
that are not allowed.

**Publish matching robots.txt rules.** The plugin adds AI crawler directives to 
WordPress’ virtual robots.txt and can include URL-specific exclusions. A preview
screen shows the rules that would be published.

**Keep an audit trail.** Crawler requests and policy decisions are stored locally
in a dedicated WordPress database table, with configurable retention and automatic
cleanup.

**Optionally publish llms.txt.** llms.txt support is an additional feature and is
disabled by default. If enabled, the plugin can publish a Markdown summary at `/
llms.txt`, omit content you have excluded, and include your own description and 
usage terms.

#### What makes this different

The plugin combines four functions in one policy workflow:

 * request-level analytics for identifiable AI crawlers;
 * site-wide, per-crawler, and per-content access decisions;
 * active enforcement through headers or HTTP 403 responses; and
 * robots.txt output derived from the same policy.

The optional llms.txt output is generated from that policy rather than being the
main purpose of the plugin.

#### What this plugin does not claim

User-Agent identification is not a firewall. A scraper that disguises itself as 
an ordinary browser cannot be reliably identified by this plugin. robots.txt is 
also advisory and depends on crawler cooperation.

The plugin therefore manages crawlers that identify themselves through supported
User-Agent tokens and provides enforcement for requests that WordPress actually 
receives.

### External services

This plugin does not connect to, depend on, or send data to any third-party service.
AI crawler identification is performed locally using User-Agent strings included
with incoming requests. The plugin does not call crawler-provider APIs, load remote
scripts, or send analytics to GlobalDev.

## Screenshots

[⌊The dashboard: daily volume, who is crawling you, and which posts they want.⌉⌊
The dashboard: daily volume, who is crawling you, and which posts they want.⌉[

The dashboard: daily volume, who is crawling you, and which posts they want.

[⌊Settings, with crawlers grouped by what they are actually for.⌉⌊Settings, with
crawlers grouped by what they are actually for.⌉[

Settings, with crawlers grouped by what they are actually for.

## Installation

 1. Upload the plugin folder to `/wp-content/plugins/`, or install the zip through 
    Plugins > Add New > Upload.
 2. Activate it.
 3. Open **AI Traffic** in the admin menu.
 4. Configure your crawler policy and enforcement level. Enable llms.txt only if you
    want to publish it.

The plugin ships with an allow-by-default access policy. llms.txt publishing is 
disabled by default, so activation does not publish that file unless you explicitly
enable it.

## FAQ

### Will this hurt my Google rankings?

No. Googlebot is not in the crawler list and is never affected. Google-Extended 
is a separate token covering Gemini training and grounding only, and blocking it
has no effect on Search.

### Should I block everything?

Probably not. Blocking training crawlers costs you nothing. Blocking search crawlers
takes you out of AI answers, which is where a growing share of referral traffic 
comes from. Blocking assistant fetchers breaks the page for a person who asked an
assistant about your site a second ago. Start with training only and watch what 
happens.

### I already have a robots.txt file

Then your web server serves that file directly and WordPress never gets asked. The
Published files screen detects this and shows you the rules to paste in by hand.

### Does this work with caching plugins?

The log and the header mode work through most page caches. The 403 refusal mode 
may not, because a cache can answer before WordPress runs. Test with a page you 
have excluded from caching.

### Does it slow the site down?

A database write happens only when a known AI crawler visits, which on most sites
is a small fraction of requests. Ordinary visitors do nothing but a string comparison
against the user agent.

### Can I add a crawler you have not included?

Yes. Developers can use the `gdatc_bot_registry` filter to add or modify crawler
definitions. `gdatc_policy_decision` and `gdatc_llms_txt` are also available.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“GlobalDev AI Traffic Control” is open source software. The following people have
contributed to this plugin.

Contributors

 *   [ Globaldev ](https://profiles.wordpress.org/globaldevitus/)

[Translate “GlobalDev AI Traffic Control” into your language.](https://translate.wordpress.org/projects/wp-plugins/globaldev-ai-traffic-control)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/globaldev-ai-traffic-control/),
check out the [SVN repository](https://plugins.svn.wordpress.org/globaldev-ai-traffic-control/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/globaldev-ai-traffic-control/)
by [RSS](https://plugins.trac.wordpress.org/log/globaldev-ai-traffic-control/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.0

 * First release.
 * Visit logging for 26 known AI crawlers, with a 30 day dashboard.
 * Site-wide, per-crawler, and per-post access rules.
 * Automatic robots.txt directives, including individual excluded URLs.
 * llms.txt generation with a custom description and usage terms.
 * Three enforcement levels: record, header, refuse.
 * Configurable log retention with daily cleanup.

## Meta

 *  Version **1.0.0**
 *  Last updated **2 days ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.2 or higher **
 *  Tested up to **7.0.4**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [AI Crawlers](https://wordpress.org/plugins/tags/ai-crawlers/)[analytics](https://wordpress.org/plugins/tags/analytics/)
   [bot traffic](https://wordpress.org/plugins/tags/bot-traffic/)[robots.txt](https://wordpress.org/plugins/tags/robots-txt/)
 *  [Advanced View](https://wordpress.org/plugins/globaldev-ai-traffic-control/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/globaldev-ai-traffic-control/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/globaldev-ai-traffic-control/reviews/)

## Contributors

 *   [ Globaldev ](https://profiles.wordpress.org/globaldevitus/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/globaldev-ai-traffic-control/)