Better Robots.txt – AI-Ready Crawl Control & Bot Governance
Better Robots.txt replaces the default WordPress robots.txt workflow with a smarter, structured version you can configure and preview before publishing. Instead of a blank textarea, you get a guided wizard with presets, plain-language explanations, and a final Review & Save step so you can inspect the generated robots.txt before it goes live. Built for beginners and advanced users alike, Better Robots.txt helps you control how search engines, AI crawlers, SEO tools, archive bots, bad bots, social preview bots, and other automated agents interact with your site. Trusted by thousands of WordPress sites, Better Robots.txt is designed for the AI era without resorting to hype, vague promises, or hidden rules. Better Robots.txt is available in Free, Pro, and Premium editions. The free plugin covers the guided workflow and essential crawl control features, while Pro and Premium unlock additional governance, protection, and AI-ready modules. Some screenshots on the plugin page show features from all three editions. A quick overview Why Better Robots.txt is different Most robots.txt plugins fall into one of three categories: Simple text editor Virtual robots.txt manager Single-purpose AI or policy add-on Better Robots.txt goes further. It gives you a complete, guided crawl control workflow so you can: Choose a preset that matches your goals Control major crawler categories without writing everything by hand Keep core WordPress protection rules visible and editable Clean up low-value crawl paths that waste crawl budget Generate a cleaner robots.txt output Preview the final result before saving What you can control Better Robots.txt helps you manage: Search engine visibility AI and LLM crawler behavior AI usage signals such as search, ai-input, and ai-train preferences SEO tool crawlers Bad bots and abusive crawlers Archive and Wayback access Feed crawlers and crawl traps WooCommerce crawl cleanup CSS, JavaScript, and image crawling rules Social media preview crawlers ads.txt and app-ads.txt allowance llms.txt generation Advanced directives such as crawl-delay and custom rules Final review before publishing Editions Better Robots.txt is available in three editions: Free – Includes the guided setup, the Essential preset, core crawl control features, and the final Review & Save workflow. Pro – Adds more advanced governance and protection modules, including additional AI, crawler, and cleanup controls. Premium – Unlocks the most restrictive and advanced protection options, including the Fortress preset and additional high-control modules. Some options shown in the interface are marked Free, Pro, or Premium so users can immediately understand which modules belong to each edition. AI crawler controls by edition The Free edition lets site owners choose a basic global policy for AI search and discovery crawlers: allow or block. AI training crawlers remain separated from AI search crawlers, so a site can block training use while still allowing AI-powered search and answer discovery. The Pro and Premium editions add advanced controls, including per-bot AI crawler rules, custom user agents, AI usage signals, llms.txt, and additional machine-readable governance files. Better Robots.txt separates AI-related agents into three practical families: AI training crawlers, such as GPTBot, Google-Extended, and ClaudeBot. AI search and discovery crawlers, such as OAI-SearchBot, PerplexityBot, and Claude-SearchBot. User-action fetchers, such as ChatGPT-User, Perplexity-User, and Claude-User. User-action fetchers are triggered by user requests. Depending on the provider, robots.txt may not apply to those fetches in the same way as it applies to automated crawlers. For stronger enforcement, combine robots.txt with server logs, WAF rules, provider verification, or IP-based controls where available. Presets Setup starts with four modes: Essential – A clean, practical configuration for most websites that want a better robots.txt without complexity. AI-First – For publishers and content sites that want AI-ready governance without shutting down discovery. Fortress – For websites that want stronger protection against scraping, archive capture, and unnecessary crawl activity. Custom – For users who prefer to configure each module manually. For many sites, one preset plus a quick review is enough. Built for beginners and experts Beginners get: A guided setup instead of a raw robots.txt box Preset-based configuration Plain-language explanations for important choices A safer workflow with a final preview step Advanced users get: Editable core WordPress protection rules Fine-grained crawler controls by category WooCommerce-oriented cleanup options Consolidated output options Advanced directives and custom rules A final output they can inspect before publishing AI-ready, without hype Better Robots.txt includes features for modern AI-related crawl governance, including: AI crawler handling Optional llms.txt support AI usage signals for compliant systems Optional machine-readable governance signals for advanced use cases These features help you express how you want automated systems to use your content. However, Better Robots.txt does not claim to control AI by force. Like robots.txt itself, these signals are most useful with compliant systems and good-faith crawlers. What Better Robots.txt is Better Robots.txt is: A robots.txt governance plugin for WordPress A guided configuration workflow instead of a raw text editor A crawl control layer to reduce wasteful crawling A practical bridge between SEO, crawl hygiene, and AI-era policy signaling A way to keep your crawl policy clearer for humans and machines Technical reference for advanced users: Better Robots.txt also maintains a public GitHub repository with product definition, governance notes, and machine-readable artefacts. What Better Robots.txt is not Better Robots.txt is not: A firewall or Web Application Firewall (WAF) An anti-scraping enforcement engine A legal compliance engine A guarantee that every bot will obey your rules A replacement for server-level security or access control It helps you publish a clearer crawl policy. It does not replace infrastructure-level protection. Typical use cases Use Better Robots.txt if you want to: Clean up a weak or noisy default robots.txt Reduce crawl waste on WordPress or WooCommerce Keep major search engines allowed while restricting other bots Control whether archive bots can snapshot your site Publish AI usage preferences more clearly Keep social preview bots allowed while limiting scrapers Review the final file before making it live Key Features Guided step-by-step wizard Preset-based setup: Essential, AI-First, Fortress, Custom Search engine visibility controls AI and LLM crawler governance AI usage signals support SEO tool crawler controls Bad bot and abusive crawler options Archive and Wayback access controls Spam, feed, and crawl trap cleanup WooCommerce crawl cleanup options CSS, JavaScript, and image crawling rules Social media preview crawler controls ads.txt and app-ads.txt allowance Optional llms.txt generation Consolidated output option Core WordPress protection rules remain visible and editable Final Review & Save preview screen About the publisher Better Robots.txt is developed and maintained by Pagup, a digital readability firm based in Quebec, Canada. Pagup helps organizations become correctly understood by search engines, generative AI systems, and autonomous agents. The robots.txt file is the first surface that AI crawlers read when they discover a site. A well-structured robots.txt that references governance files such as llms.txt, ai-manifest.json, and interpretation policies helps AI systems understand your site faster and more accurately. Better Robots.txt is one component of a broader digital readability practice that includes semantic content architecture, AI governance and machine readability, and interpretive SEO. Part of the Pagup ecosystem pagup.com — Digital readability firm. Diagnostic, semantic architecture, AI governance. gautierdorval.com — Doctrine, canonical definitions, interpretive governance research. interpretive-governance.org — Formal versioned standard for interpretive governance. better-robots.com — Documentation and resources for Better Robots.txt.
Top keywords
- txt43×3.53%
- robots34×2.79%
- robots txt34×2.79%
- ai25×2.05%
- better21×1.73%
- better robots21×1.73%
- better robots txt21×1.73%
- crawl16×1.31%
- governance14×1.15%
- crawlers13×1.07%
- crawler11×0.90%
- rules11×0.90%
BitFire Security – Firewall, Malware Scanner, Bot Blocker, Login Protection
Your Site Deserves Real Protection You built your WordPress site to grow your business, share your ideas, or connect with your community. You shouldn’t have to become a security expert to keep it safe. BitFire stops hackers, bots, and malware automatically so you can focus on what matters: running your site. And when you have a question, a real person on our US-based support team is here to help, 12 hours a day. How BitFire Keeps You Safe Most security plugins wait until something goes wrong and then try to clean up the mess. BitFire works the other way around: it stops threats before they ever reach your site. Think of it like a lock on your front door versus a camera that records a break-in. BitFire is the lock. Our AI-powered scanner watches your files and traffic in real time, catching new threats that other plugins miss because they are still waiting for someone to write a rule for it. “Traditional firewalls allow everything by default and react to known threats. BitFire flips that: it verifies traffic first and only lets the good stuff through.” Key Features What BitFire Does For You (Free) Stops Bots Automatically Spam bots, scrapers, and scanners get blocked before they waste your server resources or fill your forms with junk. No CAPTCHAs, no puzzles for your visitors. Scans for Malware BitFire checks every file on your site against a database of over 20 million known-good files. If something does not belong, you will know about it. Shows You Who is Visiting See every request to your site in real time: where visitors are from, what browser they are using, and whether they are a real person or a bot. No more guessing. Protects Your Login Page Brute-force attacks, password stuffing, and login bots are stopped cold. Your admin area stays locked down. Tells Real People from Fake Browsers BitFire verifies visitors with 99.7% accuracy, 50 times faster than Cloudflare’s challenge pages. Real visitors never notice. Bots get stopped instantly. Blocks Known Bad Actors Over 300,000 known malicious IPs are blocked before they can even connect to your site. What You Get with BitFire Pro Everything in Free, plus the protections that stop even zero-day attacks on vulnerable plugins and themes: Runtime Protection (RASP) BitFire is the only WordPress security plugin with Runtime Application Self Protection. It watches what your plugins and themes are actually doing and stops anything suspicious: A plugin tries to create a secret admin account? Blocked. Malware tries to edit your PHP files? Blocked. A hacked plugin tries to phone home to a malware server? Blocked. Code tries to redirect your visitors to a scam site? Blocked. BitFire has blocked 100% of critical WordPress zero-day vulnerabilities since 2022, with zero new rules required. A+ Rated Web Application Firewall Independent testing by Cloudbric rated BitFire’s WAF at 94% (A+). See how that compares: BitFire [PRO]: 94% (A+) Ninja Firewall [PRO]: 67% (D) WordFence [PRO]: 41% (D) MalCare [PRO]: 34% (F) iThemes Security: 2% (F) Shield Security [PRO]: 2% (F) SiteGround Security: 2% (F) View the full independent test results at Cloudbric Labs AI-Powered Malware Analysis When the scanner finds something suspicious, BitFire’s AI analyzes it in real time to determine if it is actually malicious or just unusual code. Pro users get results in about 2 minutes. Free users can submit files for batch analysis. Automatic Security Headers BitFire learns which domains your site uses (Google Fonts, your CDN, analytics, etc.) and automatically sets up Content Security Policy headers that earn an A+ rating. This protects your visitors from cross-site scripting and redirect attacks without you having to configure a thing. 30 Days of Traffic History Look back through a full month of traffic data to investigate issues, spot patterns, or just understand how your site is being used. Real Human Support This is what makes BitFire different from the big-name security plugins: when you need help, you talk to a real person. Our US-based support team is available 12 hours a day. No ticket queues that take days. No chatbots. No copy-paste answers. Just experienced people who will make sure your site is secure. Whether you need help with setup, have a question about a block, or want someone to look at a suspicious file, we are here. Pricing Free $0 forever. Bot blocking, malware scanning, login protection, and real-time traffic monitoring. Everything you need to stop the vast majority of automated attacks. Pro – Single Site $60/year. Full RASP protection, A+ rated WAF, AI malware analysis, 30-day logs, and priority human support. Pro – Multi-Site Volume Pricing Managing multiple sites? The more you protect, the less you pay: 2-4 sites: $50/site per year 5-9 sites: $45/site per year 10-24 sites: $35/site per year 25-49 sites: $25/site per year 50+ sites: $20/site per year Volume pricing is perfect for freelancers, agencies, and anyone managing WordPress sites for clients. Contact us for volume licensing. How BitFire Compares BitFire vs WordFence WordFence is a solid product with a large team writing custom rules for known vulnerabilities. But there are two things you should know: Free WordFence delays protection by 30 days. When a new vulnerability is found, paying WordFence customers get the fix immediately. Free users wait a full month. If your site is vulnerable, it will almost certainly be attacked before the free patch arrives. WordFence relies on knowing about attacks in advance. With over 10,000 known WordPress vulnerabilities and fewer than 200 signatures, they simply cannot cover everything. BitFire’s RASP does not need to know about an attack in advance. It watches what code is actually doing and stops anything malicious, even brand-new attacks nobody has seen before. Whatever security solution you use – we strongly recommend only using the paid version for all important work. Read the detailed BitFire vs WordFence comparison Why Do Other Plugins Focus So Much on Cleaning Up Malware? Good question. Notice how much other security plugins charge for malware removal and how much of their marketing is about finding infections? A security plugin that does its job well should not need to clean malware off your site very often. If a plugin spends most of its energy on cleanup, that tells you something about how well it prevents attacks in the first place. BitFire focuses on keeping malware off your site so you do not need to pay someone to remove it. Privacy / Monitoring / Data Collection We take your privacy seriously. Here is exactly what BitFire does with data: Traffic inspection. BitFire inspects web traffic to your site to identify threats. Sensitive data like passwords and credit card numbers is automatically replaced with redacted in logs. You can add additional fields to filter in the settings. Error reporting. If BitFire encounters a software error, it can send a report to our development team so we can fix it in the next release. No visitor data is included in these reports. Malware hash checking. BitFire sends tiny numeric fingerprints (64-bit hashes) of your files to our hash server to check them against our database of known-good files. For example, a file might hash to the number 812612388126487. We never see your actual file contents, and your hashes are never stored on our servers. Local data storage. All log data and configuration files are stored locally on your server in a hidden, randomly-named directory under wp-content/uploads/. This directory is protected by an .htaccess file and is not accessible from the web. =trunk/views/hashes_v2.html= Changelog == 5.1.5 Bots impersonating crawlers (bing, meta, google, etc) are not blocked for simple unrestricted GET requests Added daily fetch data for supplemental crawler dns / cidr lists Improved server IP address detection for allowing local server loop back calls Added plugin inventory hiding to malware detection capabilities Malware detections for plugins missing valid headers / plugin scripts Malware detections for plugins with random identifiers in them Improved logging of xmlrpc requests – now records list of method names – not raw xml Added ability to allow users to delete / restore entire plugins if they are only malware (not official plugins with strong malware signals) Binary files are excluded from malware diffs now Reduced false positives for SQL injection Bot Control panel links to dashboard filter user agents better AI verdict results are now stored for future reference Fix deprecation warning for http response headers on PHP 8.5 Removed dependency on filter_var extension Added expert opinion check allowing admins to request a review of potential malware samples by BitFire staff 5.1.4 Fixed an issue that could allow some admin-ajax requests to recieve a browser challenge for the logged in admin on first install Added additional filtering to cover unknown authorization values, provider keys, and hexadecimal tokens in log storage Added daily updated list of allowed network ranges for core web and AI crawers Improved chaching of DNS lookups for core web bots Added additional bot telemetry gating for bitfire core enable flag 5.1.3 fixed an issue with bot triage recomendations that could generate fatal errors on some host in a background task 5.1.1 Added traffic percent blocking for large sites to sample blocking behavior before fully commiting Increased free AI usage credits from 10 to 12 Improved bot/browser verification compatibility with ModSecurity Added buttons for allowing traffic on the dashboard Fixed an issue that was blocking obviously malicious bots even when bot whitelist setting was not enabled Added reasonable limit for max malware file size to prevent resource exchaustion on servers with very large files Expanded bot source and threat intel data Older versions could label some woocommerce user-agents that were completely random as Improved detection of when to load wordpress vs when to inspect early Bots can be configured directly from the dahboard by clicking on their link to the bot control page False positives can now have execptions added on the dashboard with a single button click AI Malware change for OpenAI compliance – previous versions will no longer support AI analysis Threat hunter content scanner reduced false positiveso Basic harending (size limits, shape constraints) for inputs, moved some requests to POST Expanded learning to support sites that accept POSTs from off site for validated web browsers Bot triage moves from hourly to every 3 hours Expanded runtime protection to ensure environemnt loaded successfull before registering wordpress hooks Improved malware input tainting tracing which detects additional potential malware, reduced false positives Added an exclude list of allowed files in the root for the malware scanner Bots who have been repeat visitors with an AI recomendation different different than current mode now show up on to_review tab 5.1.0 Reduced false positvies for malware scan Improved AI scan results with greatly reduced false positives Implemented quarantine restore for deleted malware files in case of site breakage with Add quarantine restore in case core files are deleted from malware cleanup using new mu-plugin error handler bitfire.php Improved RASP compatibility with fewer exceptions UI improvements Add quick links to wafer firewall scan and securityheaders.com tests Hardening for bot domain verification Improved UI browser and bot icons Support auto-updating BitFire PRO plugin Improved fallbacks for caching Minor refactoring to improve AI analysis of codebase Added special handling for servers with low available memory (< 10MB) Added support for servers that have getmypid() disabled 5.0.9 Add security posture to settings page Improved bot identification Improved loading order decreases block time Multi-Site support! Few bug fixes Fixed an issue with support for PHP 7.4 Links to header and WAF 3rd party verification checks on settings page Display hardening for malformed malware Fix for header signatures on 32bit systems 5.0.0 New AI-powered malware analysis for suspicious files Reduced Pro pricing to $60/year with volume discounts Improved malware scanner performance and accuracy Updated bot and browser fingerprint databases Improved dashboard and settings UI 4.8.3 Fix an issue that could reset the configuration on upgrade 4.8.2 Improvements to the malware scanning UI Fixes for downloading non-PHP files Additional guards to handle corner cases 4.8.0 Improved malware detection and reduced false positives Added 3 new file hash servers in US, DE, and KR Added support for checking for backups and files that could contain sensitive data New daily/weekly status emails Added daily malware scan scheduling Various stability and configuration improvements 4.7.4 Improved dashboard messaging for IP and user-agent blocking Fixed toggle behavior on the exceptions page Fixed deprecation warnings Fixed an issue that could prevent uploading plugins when bot blocking was enabled 4.7.3 Initial WP-CLI support: review logs, check metrics, manage blocks Configuration file reliability improvements PHP 8.3 compatibility fix 4.7.2 Improved traffic monitoring and logging Added “Fake Browser” detection badges Added DoS protection for rate-limited IPs New traffic filter keywords: BLOCKED, RESTRICTED, ADMIN, LOGINS, and more Added email notifications for server health Performance improvements across the board 4.7.0 Added AI verification framework for block accuracy Reduced server communication timeout for faster responses Additional blocking class types for exclusions PHP 8.4 compatibility Updated Google, Bing, and Cloudflare IP lists 4.6.1 Improved dashboard log searching Fixed a rare memory issue with log writing 4.6 Moved configuration and log storage to a more secure location Added .htaccess protection for data directories Resolved several minor PHP warnings 4.5 Fixed filtering on blocked requests Fixed handling of malformed file uploads Added additional browser support 4.4.9 Major quality and performance improvements Daily report emails Complete rewrite of caching and statistics Full support for cached websites (Cloudflare, etc.) Log up to 30 days and 2 million requests per month 4.0.1 Major overhaul of browser and bot detection Added 180+ browsers and 300+ browser icons Switched to high-performance binary log format Added commercial IP reputation database with 300K+ abusive IPs Simplified user interface