Free vs Pro
Every setting, side by side.
Free is a complete plugin, not a demo. Pro adds the parts that need more server work or are made for busy and professional sites. Search below, or show only what Pro adds.
What the plans add on top of Pro
Every paid plan has every Pro feature. These are the differences between them.
| Free | Personal | Business | Agency | |
|---|---|---|---|---|
| Sites | Any | 1 / 3 | 5 / 10 | 25 / 50 / 100 |
| All Pro features | – | |||
| Automatic updates | – | |||
| Log history | 30 days | Unlimited | Unlimited | Unlimited |
| Bans shared between your sites | – | – | ||
| Health of all sites in your account | – | – | ||
| Monthly PDF report per site | – | – | ||
| Keel Agency Hub plugin | – | – | – | |
| White-label client reports | – | – | – | |
| Support answer time | Docs | 2 working days | 1 working day | Priority |
Every area, every setting
| Setting | Free | Pro |
|---|---|---|
| Setup | ||
| Welcome tourA guided 3-5 minute walk through everything the plugin can do. Choose which sections this site uses; the rest are switched off but stay visible. | ||
| Quick setupAnswer three questions and the plugin configures itself. You can change anything afterwards. | ||
| PresetsReady-made combinations of settings. Each one shows exactly what it would change before you apply it; settings it does not mention stay as they are. | – | |
| NotificationsWhere the plugin sends its emails: the weekly summary, security alerts and file-check warnings. | ||
| Send reports and alerts to | ||
| Import & exportSave all settings to a file and load them on another site, so every new project starts with your setup. | – | |
| LicenseYour Keel Pro key, and what Keel Pro adds. | ||
| Speed | ||
| Lazy loadingImages and videos further down the page only load when the visitor scrolls near them, so the top of the page appears sooner. | ||
| Lazy load images | ||
| Lazy load videos and embeds | ||
| Images at the top that load immediately | ||
| Never lazy load images with these classes | ||
| Load the main image first | ||
| Video previews instead of players | – | |
| Fonts & connectionsServe Google Fonts from your own site and open connections to other sites early. | – | |
| Host Google Fonts on this site | – | |
| Connect early to the sites a page uses | – | |
| Always connect early to | – | |
| WebP imagesWebP is a modern image format, usually 25-35% smaller than JPEG or PNG at the same quality. | – | |
| Convert new uploads to WebP | – | |
| Quality | – | |
| Keep the original files when converting the library | – | |
| Shrink uploads larger than (pixels) | – | |
| Remove hidden photo data on upload | – | |
| Instant clicksStarts loading a page the moment a visitor hovers over a link, so by the time they click it is often already there. | – | |
| Load pages on hover | – | |
| Never preload addresses starting with | – | |
| Delay scriptsAnalytics, chat widgets, pixels and heatmaps wait until the visitor first scrolls, taps or moves the mouse, so they no longer slow down the first view. | – | |
| Delay third-party scripts | – | |
| Delay scripts containing | – | |
| Run them anyway after (seconds) | – | |
| Minify & combineMake the page's code smaller and send fewer files: comments and extra spaces are removed, and many small CSS and JS files are joined into a few. | – | |
| Minify HTML | – | |
| Minify CSS | – | |
| Combine CSS files | – | |
| Minify JavaScript | – | |
| Combine JavaScript files | – | |
| Leave these files alone | – | |
| Database cleanupWordPress keeps old revisions, drafts, spam and temporary data forever. Removing it keeps the database small and fast. | ||
| Clean up every week | – | |
| What to remove | ||
| Background activityReduce the work WordPress does behind the scenes while people edit. | ||
| Heartbeat | ||
| Revisions to keep per page | ||
| Caching | ||
| Page cacheSaves each page as ready-made HTML, so the server can answer in a few milliseconds instead of building the page from the database every time. | ||
| Cache pages | ||
| Keep pages for (hours) | ||
| Never cache addresses starting with | ||
| Rebuild the cache in the background | – | |
| Pages per minute | ||
| Browser cacheTells browsers to keep images, styles and scripts so returning visitors do not download them again, and compresses files on the way out. | ||
| Browser caching and compression | ||
| Object cache (Redis)Keeps database results in memory so wp-admin and pages that cannot be page-cached load faster. Needs a Redis server on your hosting. | – | |
| Use Redis | – | |
| Redis server | – | |
| Port | – | |
| Password | – | |
| Database number | – | |
| REST API cacheSaves REST API answers so a headless front end, app or widget gets content in milliseconds. | – | |
| Cache REST API answers | – | |
| Keep answers for (minutes) | – | |
| Never cache routes starting with | – | |
| SEO | ||
| Site identityYour logo, the default title, description and share image, and the contact details Google can show about your business. Pages without their own SEO data use these. | ||
| Logo | ||
| Default title | ||
| Default description | ||
| Default share image | ||
| Contact email | ||
| Phone | ||
| Address | ||
| Social profiles | ||
| SEO statusChecks that search engines can find and understand the site. | ||
| Search appearanceThe page title, description and share image that Google, Facebook, LinkedIn and others show. | ||
| Add SEO tags to every page | ||
| Hide author and date archives from Google | ||
| SitemapA list of every page for search engines, at /sitemap.xml. | – | |
| Create /sitemap.xml | – | |
| Include categories and tags | – | |
| Bulk editorEdit the SEO title and description of many pages at once, in one table, without opening each page. | – | |
| Instant indexingTell search engines the moment a page is published, updated or removed, instead of waiting for them to crawl the site. | – | |
| Use IndexNow | – | |
| BreadcrumbsThe "Home › Services › Web design" trail: shown in Google results instead of the raw address, and optionally on the page itself. | ||
| Tell Google the page's place in the site | ||
| Name of the first link | ||
| Separator | ||
| AI & LLMsDecide which AI companies may read the site, and give AI assistants a summary of it. | ||
| AI crawlers | ||
| Block these crawlers | ||
| Also refuse their requests | ||
| Create /llms.txt | – | |
| Extra introduction | ||
| Content to list | ||
| Page checkA Google-style preview of every published page, with missing or too-long titles and descriptions flagged. | – | |
| API & Headless | ||
| Headless modeMakes sure no security feature gets in the way of a front end that reads content through the REST API. | – | |
| This site is headless | – | |
| Front end address | – | |
| REST API accessThe REST API (/wp-json/) lets apps and scripts read site content. By default anyone can use it. | ||
| Limit the REST API for visitors | ||
| Parts that stay open | ||
| Login & accounts | ||
| Login pageWhere and how people log in. | ||
| Move the login page to a secret address | ||
| Login address | ||
| Show your logo on the login page | ||
| Don't reveal which part of the login was wrong | ||
| Two-factor loginAfter the password, users also enter a 6-digit code sent by email or shown in an authenticator app. A stolen password alone is no longer enough. | ||
| Turn on two-factor login | ||
| Who needs it | – | |
| Offer an authenticator app after an email login | – | |
| PasswordsRules checked whenever someone sets or changes a password. | ||
| Minimum length | ||
| Refuse passwords that have leaked online | ||
| Passwords must contain | ||
| No names, usernames or emails inside passwords | ||
| Apply these rules to | ||
| Ask for a new password every | – | |
| Do not allow reusing the last | – | |
| Login alertsEmails that tell people when something unusual happens to an account. | ||
| Tell users about logins from new devices | ||
| Tell all administrators about new administrators | ||
| Bot checkStops automated scripts on the login, lost password and registration forms. | ||
| Invisible bot trap | ||
| Cloudflare Turnstile check | – | |
| Turnstile site key | ||
| Turnstile secret key | ||
| Login linksLog in with a one-time link sent by email: no password needed, and it works even while an attack has paused the account. | – | |
| Offer "Email me a login link" on the login page | – | |
| Links work for | – | |
| Only for these roles | – | |
| Trusted devicesOnly devices you confirmed can change plugins, themes, users and settings, and stolen login cookies stop working. | – | |
| Use trusted devices | – | |
| For these roles | – | |
| Limit new devices until they are confirmed | – | |
| End sessions used from another device | – | |
| User securityEvery account at a glance (two-factor, last login, password age, devices) with actions for many accounts at once. | – | |
| SessionsLog out people who walked away, see every account's recent logins, and ask accounts for a new password. | – | |
| Log out after this long without activity | – | |
| Only for these roles | – | |
| Firewall | ||
| Blocked IPsWho is blocked for now, who is banned for good, who is always allowed, and the banned list shared by all your sites. | ||
| Share permanent bans with all my sites | ||
| Stop banned addresses in .htaccess | – | |
| Visitor IPEvery block depends on knowing the visitor's real IP address. | ||
| Read the visitor IP from | ||
| Failed logins & bansToo many failed logins block an address for a while; an address that keeps getting blocked is banned for good. | ||
| Block addresses after failed logins | ||
| Failed logins allowed | ||
| Counted within | ||
| Then block the address for | ||
| Ban for good anyone who tries to log in on wp-login.php | ||
| Block it from the whole website | ||
| Ban repeat offenders for good | ||
| Ban for good after | ||
| Blocks counted within | ||
| Block anyone trying fake usernames | ||
| Fake usernames | ||
| Pause an account after | ||
| Block anyone who tries a username that does not exist | ||
| Email me about each block | ||
| File scanningBots look for leftover files such as backups, .env or phpMyAdmin. Asking for several of them is a clear sign of an attack. | ||
| Block addresses that scan for files | ||
| Suspicious requests allowed | ||
| Counted within | ||
| Then | ||
| Block length | ||
| Count every "page not found" | ||
| Bots & attacksCheck each request for hacking tools and attack code. Logged-in administrators and whitelisted IPs are never filtered. | ||
| Block hacking tools | ||
| Block requests without a browser name | ||
| Also block browser names containing | ||
| Attack code in web addresses | – | |
| Block addresses that send too many requests | – | |
| Requests allowed | ||
| Then block it for | ||
| Count password guessing through XML-RPC and the REST API | – | |
| Form protectionStops bots and spam on every form of the site: comments, WooCommerce, Contact Form 7, WPForms, Gravity, Elementor, Fluent, Formidable and any other form. | ||
| Protect forms | ||
| Which forms | – | |
| Refuse forms sent faster than | ||
| Require a real visit | ||
| Captcha | – | |
| reCAPTCHA site key | ||
| reCAPTCHA secret key | ||
| reCAPTCHA v3: lowest human score | ||
| hCaptcha site key | ||
| hCaptcha secret key | ||
| Refuse messages with more than | – | |
| Refuse messages containing | – | |
| Refuse messages written in | – | |
| Refuse the same message sent 3 times in a day | – | |
| Refuse fake email addresses | – | |
| Block the sender after | ||
| Block length | ||
| Share spam with your other sites (Hub) | ||
| CountriesBlock countries you never get real visitors from, or allow only your own. | – | |
| Country rule | – | |
| Countries | – | |
| Where it applies | – | |
| Allow & block listsAddresses that are always trusted or always blocked. One per line, single IPs or ranges like 198.51.100.0/24; IPv6 works too. Text after # is a note. | ||
| Always allow | ||
| Always block | ||
| Public blocklistsLists of known attacker addresses maintained by security organisations. They download once a day in the background and checking a visitor takes a fraction of a millisecond. | – | |
| Block visitors listed on | – | |
| Hardening | ||
| Security healthA checklist of the most important security basics for this site. | ||
| Security toolsOne-click fixes: change user ID 1, the database prefix and the WordPress salts, and check file permissions. | ||
| WordPressTurn off WordPress features attackers like to use. | ||
| Turn off XML-RPC | ||
| Hide usernames | ||
| Turn off the code editor in wp-admin | ||
| Turn off the Customizer | ||
| Turn off "Additional CSS" | ||
| Turn off the Site Editor (block themes) | ||
| Hide the WordPress version | ||
| Turn off application passwords | ||
| Allow safe SVG uploads for administrators | ||
| Lock plugin and theme installs | ||
| Browser protectionInstructions sent with every page that tell browsers to apply extra protections. | ||
| Send security headers | ||
| Always use HTTPS (HSTS) | ||
| Server rulesRules for the web server itself, written to .htaccess on Apache and LiteSpeed. On nginx the lines to add are shown above the settings. | – | |
| Never run PHP in the uploads folder | – | |
| Block access to sensitive files | – | |
| Block hidden files and folders | – | |
| Don't list folder contents | – | |
| Monitoring | ||
| Threat scanChecks WordPress, plugins and themes for known security holes four times a day (hourly in Keel Pro), and whether Google lists the site as dangerous. | ||
| Scan automatically | ||
| Email me when something new is found | ||
| Google Safe Browsing API key | ||
| File checkFinds WordPress files that were changed or added, the typical sign of a hack. | – | |
| Check files every day | – | |
| Folders and files to skip | – | |
| Updates & vulnerabilitiesPlugins, themes and WordPress itself, with updates waiting and known security problems. | ||
| Show outdated software | ||
| Allow updates from the Keel Hub | ||
| WPScan API token | – | |
| Activity logWho changed what in wp-admin, and when. | ||
| Record admin activity | ||
| Also record logins, content, media, menus and comments | – | |
| Logs & privacyHow long logs are kept, and when visitor IP addresses in them are anonymised. Matters for GDPR: IP addresses are personal data. | ||
| Delete log entries after (days) | – | |
| Anonymise IP addresses after (days) | ||
| Security logLogins, failed attempts, blocks, attack attempts and two-factor events. The last 200 are kept. | ||
| Errors & email problemsHear about crashed pages and failing emails straight away. | ||
| Email me when a page crashes with a PHP error | ||
| Warn me when emails start failing | – | |
| Broken linksFinds links and images on your pages that lead nowhere. | – | |
| Check every week | – | |
| Weekly emailA short security summary in your inbox every Monday morning. | ||
| Send the weekly summary | ||
| Send to | ||
| Site tools | ||
| Email deliverySend WordPress emails (password resets, login codes, form messages) through a real mail service so they arrive instead of landing in spam. | ||
| Send email through SMTP | – | |
| Mail service | ||
| Google client ID | ||
| Google client secret | ||
| SMTP server | ||
| Port | ||
| Encryption | ||
| Username | ||
| Password or API key | ||
| Send from address | ||
| Send from name | ||
| Keep an email log | ||
| Keep the email content | ||
| Duplicate pagesCopy any page, post or custom content with one click, including all custom fields, as a new draft. | ||
| Show "Duplicate" links | ||
| Redirects & 404sSend visitors from old addresses to new ones, and see which missing pages people are landing on. | ||
| Use redirects | ||
| Create redirects automatically | – | |
| Keep a "page not found" log | ||
| Maintenance modeShow visitors a "back soon" page while you work. Logged-in editors keep seeing the real site. | ||
| Turn on maintenance mode | ||
| Heading | ||
| Message | ||
| Let "Always allow" IPs see the site | ||
| BackupsCopies of the database and files, made on a schedule and before every update, kept here and optionally in your own cloud storage. | ||
| Make backups on a schedule | – | |
| Database every | ||
| Files every | ||
| Include uploaded images and files | ||
| Keep the newest | ||
| Back up before every update | – | |
| Also send backups to cloud storage | – | |
| Storage address | ||
| Region | ||
| Bucket | ||
| Folder in the bucket | ||
| Access key ID | ||
| Secret access key | ||
| CommentsMost business sites never use comments, but WordPress keeps them switched on everywhere. | ||
| Turn off comments completely | ||
| Cleanup | ||
| WebsiteExtra code WordPress adds to every page. Removing it makes pages lighter. | ||
| Remove block editor styles | ||
| Remove the emoji script | ||
| Remove unused links from the page header | ||
| Remove jQuery Migrate | ||
| Turn off speculative preloading | ||
| Hide the admin bar on the website | ||
| wp-adminA simpler dashboard for you and your clients. | ||
| Use the classic editor | ||
| Tidy up the dashboard | ||
| Hide the Comments menu | ||
| Hide the Tools menu | ||
Five minutes from now
Give your site a keel.
Steady when traffic spikes, calm when attacks come, found when people search. Start free; go Pro when a site needs more.