First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3662677,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3662677,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3662677,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3662677,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3662687,"resolution":"1","location":"assets","locale":"","width":1486,"height":638},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3662687,"resolution":"2","location":"assets","locale":"","width":1516,"height":3446}},"screenshots":{"1":"The dashboard: daily volume, who is crawling you, and which posts they want.","2":"Settings, with crawlers grouped by what they are actually for.","3":"The per-post control in the editor sidebar.","4":"A preview of the robots.txt rules and the generated llms.txt."}},"plugin_section":[],"plugin_tags":[277167,246479,232,274092,12753],"plugin_category":[36],"plugin_contributors":[272568],"plugin_business_model":[],"class_list":["post-353367","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-access","plugin_tags-ai-crawlers","plugin_tags-analytics","plugin_tags-bot-traffic","plugin_tags-robots-txt","plugin_category-analytics","plugin_contributors-globaldevitus","plugin_committers-globaldevitus"],"banners":{"banner":"https:\/\/ps.w.org\/globaldev-ai-traffic-control\/assets\/banner-772x250.png?rev=3662677","banner_2x":"https:\/\/ps.w.org\/globaldev-ai-traffic-control\/assets\/banner-1544x500.png?rev=3662677","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/globaldev-ai-traffic-control\/assets\/icon-128x128.png?rev=3662677","icon_2x":"https:\/\/ps.w.org\/globaldev-ai-traffic-control\/assets\/icon-256x256.png?rev=3662677","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/globaldev-ai-traffic-control\/assets\/screenshot-1.png?rev=3662687","caption":"The dashboard: daily volume, who is crawling you, and which posts they want."},{"src":"https:\/\/ps.w.org\/globaldev-ai-traffic-control\/assets\/screenshot-2.png?rev=3662687","caption":"Settings, with crawlers grouped by what they are actually for."}],"raw_content":"\n
GlobalDev AI Traffic Control is primarily an AI crawler traffic monitoring and access-control plugin<\/strong>. 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.<\/p>\n\n Monitor identifiable AI crawler traffic.<\/strong> 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.<\/p>\n\n Create a policy hierarchy.<\/strong> 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.<\/p>\n\n Choose the enforcement level.<\/strong> You can record policy violations only, send Publish matching robots.txt rules.<\/strong> 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.<\/p>\n\n Keep an audit trail.<\/strong> Crawler requests and policy decisions are stored locally in a dedicated WordPress database table, with configurable retention and automatic cleanup.<\/p>\n\n Optionally publish llms.txt.<\/strong> llms.txt support is an additional feature and is disabled by default. If enabled, the plugin can publish a Markdown summary at The plugin combines four functions in one policy workflow:<\/p>\n\n The optional llms.txt output is generated from that policy rather than being the main purpose of the plugin.<\/p>\n\n 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.<\/p>\n\n The plugin therefore manages crawlers that identify themselves through supported User-Agent tokens and provides enforcement for requests that WordPress actually receives.<\/p>\n\n 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.<\/p>\n\n\n 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.<\/p>\n\n\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n Yes. Developers can use the X-Robots-Tag: noai, noimageai<\/code>, or return HTTP 403 for recognized crawler requests that are not allowed.<\/p>\n\n\/llms.txt<\/code>, omit content you have excluded, and include your own description and usage terms.<\/p>\n\nWhat makes this different<\/h4>\n\n
\n
What this plugin does not claim<\/h4>\n\n
External services<\/h3>\n\n
\n
\/wp-content\/plugins\/<\/code>, or install the zip through Plugins > Add New > Upload.<\/li>\n\n
Will this hurt my Google rankings?<\/h3><\/dt>\n
Should I block everything?<\/h3><\/dt>\n
I already have a robots.txt file<\/h3><\/dt>\n
Does this work with caching plugins?<\/h3><\/dt>\n
Does it slow the site down?<\/h3><\/dt>\n
Can I add a crawler you have not included?<\/h3><\/dt>\n
gdatc_bot_registry<\/code> filter to add or modify crawler definitions. gdatc_policy_decision<\/code> and gdatc_llms_txt<\/code> are also available.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n
\n