Changelog
Every release, what changed, how it was tested, and what it does not do yet. Versions follow semantic versioning.
0.10.0, 2026-11-17
Commerce. Built together with the Ironhelm Portal 0.2.0 at my.ironhelmsuite.com (license-server/, its own changelog): accounts, Paddle subscriptions and one API key per site.
Changed
- One API key per site. A site connects with its own key from the Ironhelm account (Sites and API keys). Plans set how many keys exist at once: Solo 1, Studio 10, Agency 50. The key binds to the first site that uses it; the same key also works on that site's development copies (localhost, private addresses,
.local,.test, staging. and dev. subdomains) without using a slot. Licence server moved tomy.ironhelmsuite.com(protocol v2,docs/LICENSING-API.md). - Features need a working key. Without one, Ironhelm pauses: a new site runs only its own screens until connected; a site whose key stops working (removed, subscription ended, moved, or no answer from the licence server for 30 days) keeps its security protections running (firewall, login protection, two-step login, passkeys, hardening, security headers, spam protection, safe SVG) with frozen settings and pauses the rest. Pausing removes drop-ins, cache files, schedules and server rules through each feature's own switch-off; settings and data are never deleted, and everything resumes when a key works again. Changes are refused on the screens, through REST and in WP-CLI while paused (the licence screen always works; kept security features still allow their actions, such as unblocking an address).
- Instant lock. The licence server rings a new public doorbell route (
ironhelm/v1/license/ping, no data, 10-second throttle, a follow-up check when rung twice) when a key or subscription changes; the site checks in at once. Twice-daily checks cover sites the server cannot reach; wp-admin also checks when the last answer is over 12 hours old. - Licence screen renamed "API key and updates": key, connected site, plan, keys in use, renewal date, Check now, Open your account, Disconnect this site, and "use a different key" after a removal.
- Brand: the Ironhelm helm (from the new logo) as the mark, on a blued-steel plate that reads on light and dark themes; a new single-colour menu icon drawn from the helm and its V visor; icons on WordPress's Updates screen.
- Every email Ironhelm sends from a site (two-step login codes, unlock links, the new login address, alerts, the delivery test, client reports) uses one premium design: dark header with the lockup embedded inline, the temper line, a plain-text part; reports keep a light, data-friendly body. White-label replaces the name, logo and colour and hides the Ironhelm marks.
Added
- Paused notice on every wp-admin screen for administrators ("Add the API key", "Get a key"), a banner with the key field on every Ironhelm screen, and a "Connect this site" card in place of the setup assistant.
wp ironhelm license statusshows whether features run and where the key is connected.
Tested
- 29 end-to-end checks between a real site and a local portal: fresh site paused, wrong key, connect, features and page-cache drop-in back, removal in the portal pausing the site in 3 to 7 seconds with security kept, kept-security actions allowed and settings refused, a new key resuming everything, subscription ended and renewed through the doorbell, 30 days without an answer, doorbell throttle, disconnect stopping everything and freeing the key.
- Firewall corpus (42 ordinary inputs, 31 attacks), MMDB and WebAuthn suites unchanged and passing. All PHP files lint on PHP 8.2.
Known limits
- A ping cannot reach sites behind private addresses or strict firewalls; those pause at their next scheduled check (twice a day).
- Pausing is a business rule in GPL code: someone who edits the plugin can remove it. What a key protects is updates, support and the account; that is what customers pay for.
0.9.0, 2026-11-17
Launch readiness. Built together with the first version of the licence server for ironhelmsuite.com (license-server/, its own changelog).
Added
- Network mode (multisite): features that work on things every site shares (firewall, page cache, object cache, file integrity, vulnerability check, hardening, hotlink and SVG rules, the licence) have one switch and one set of settings for the network, stored network-wide and managed by network administrators on the main site. Sub-sites show them as "Whole network" with a link to the main site; their background jobs (scans, log imports) run once, on the main site; their health checks appear only on the main site. Everything else stays per site.
- Network admin screen: every site's health score, setup status and features at a glance; the shared features with their state; the network licence; and "new sites start with the settings of" a chosen site (copied as a template: business details, tracking IDs, email sender and page code left out, secrets never copied). New sites get their tables when they are created.
- Network licence: one activation covers the whole network and identifies it by the network's main address.
- Settings files on a network: shared features are only applied by a network administrator on the main site; elsewhere they are skipped and listed. Restore points record the real state of shared features.
- AI crawler log on a network: each site logs to its own file; crawls of cached pages are logged with their host and handed to the right site by the main site.
- Privacy tools: suggested privacy-policy text (Settings, Privacy, Policy guide) written only for the features that are on: visitor statistics, speed measurements, cookie choices, tracking tools, security logging, sign-in protection, two-step login and passkeys, activity log, email log, CAPTCHA provider. WordPress's "Export personal data" includes Ironhelm's activity log entries, emails sent to the person and their passkeys; "Erase personal data" removes the email log entries and passkeys and keeps the tamper-evident activity log (with the reason and its deletion date).
- Licence: a site whose slot was freed (removed from the customer's account, or silent for a long time) explains why and offers "Activate again".
Fixed
- Apache rules written from WP-CLI: switching features on from WP-CLI (common on hosts) did not write their
.htaccessrules, because the command line has no web server to detect. On a real Apache test, PHP files in uploads ran anddebug.logwas readable until settings were saved in the dashboard. Ironhelm now remembers the web server and its PHP mode from dashboard visits (with "an .htaccess file means Apache" as the fallback), and Hardening puts missing rules back automatically, checked at most once an hour. - "Start the firewall before WordPress" from WP-CLI: refused as "unsupported" for the same reason; it now uses the remembered web PHP mode and retries from the dashboard if it was refused.
- Redis outages: pages kept working, but WordPress's transients lived only in Redis, so cached reports and API answers were rebuilt on every page while Redis was down (dashboard: 6 to 7 seconds per load on the test machine). During an outage transients now go to the database, as without an object cache (about 1 second).
- Contradictory robots tag: on a site hidden from search (for example staging), noindexed pages said
noindex, nofollow, follow. They now saynoindex, nofollow; public sites still getnoindex, follow. - Nginx instructions: the rules shown for Nginx hosts now say they must go above the block that passes
.phpfiles to PHP. Tested: placed below it, PHP in uploads still runs. - Network uninstall: WordPress runs
uninstall.phpfrom inside a function, so the network-wide cleanup lost access to the database and stopped with a fatal error after the per-site cleanup. Fixed and verified: 0 tables, 0 site and network options, runtime and cache folders removed.
Tested on real servers (all on this machine)
- Apache 2.4.58 with mod_php 8.2, multisite (subdirectories): hardening rules (PHP in uploads,
wp-config.php,readme.html,debug.log, directory listing, XML-RPC), hotlink protection, page cache (miss then hit), security headers, firewall started before WordPress through.htaccess(SQL injection, script injection, path traversal and Log4Shell probes refused; normal pages and a harmless "union of workers" search allowed). - Nginx 1.30.6 with PHP 8.2 over FastCGI: server and PHP mode detected; firewall started before WordPress through
.user.ini(attacks refused in about 9 ms, before WordPress loads); page cache; Ironhelm's Nginx rules accepted bynginx -tand effective when placed as instructed. - Redis 5.0.14: dashboard database queries from 84 to 3 per load; outage (Redis stopped) with pages still served; recovery with a fresh namespace; flush.
- SEO importer against the real plugins: Yoast SEO 28.8, Rank Math 1.0.282, All in One SEO 5.0.5.1, SEOPress 10.4, The SEO Framework 5.2.1 and Redirection 5.10.1 wrote data through their own code; titles, descriptions, noindex, canonical addresses, home-page settings and redirects came across, checked on the live pages.
- One-click update end to end: a release built from this code and signed with a test key was published on a local licence server and installed through WordPress's updater on a network (not a linked copy); the same file altered by one byte on the server was refused, logged, and left the installed plugin untouched.
Known limits
- Not tested: LiteSpeed (no server available), PHP-FPM on Linux (FastCGI on Windows was the closest), passkeys on real phones and laptops, and Search Console, Bing and Chrome UX Report against real accounts. These remain on the 1.0.0 list.
- On Windows, php-cgi runs a single worker, so the first Nginx request that started WordPress's background tasks took about 40 seconds. That is a property of the test setup, not of Nginx hosting.
- A network counts as one site for the licence. If you would rather count each sub-site, the server's site limit is the place to change it; tell me before 1.0.0.
0.8.0, 2026-11-17
Added: Control
- Setup assistant (C4): opens once after activation (and from a dashboard banner until it is finished or dismissed), re-runnable any time from Settings, Setup and transfer. Five questions: kind of site (business, blog or news, online store, members or courses), who runs it (organisation, local business with address and business type, or a person), the email sender, protection level (standard or strict) with two-step login for administrators, and the page cache (left off automatically when the host or another plugin already caches pages). Step six lists every change in plain words before anything is saved; afterwards the whole setup can be undone in one click. Focus mode hides the WordPress menu; on phones the step rail becomes a progress bar. The questions reuse the regular settings fields, so labels and validation are identical. Admins only.
- Presets: each answer maps to a small, specific set of settings (strict: 3 failed logins, 60-minute pause, alerts, two-step login for editors and shop managers too, application passwords off, sessions capped at a day, idle logout after an hour, HSTS on HTTPS sites; members sites count logged-in visitors and keep author archives out of search; shops switch on WooCommerce SEO and speed). A preset only touches what its questions are about.
- Settings files (C6): download Ironhelm's settings as JSON from Settings, Setup and transfer, choosing the areas. Keys, passwords and tokens are never included. A "template" also leaves out what belongs to one site only (business details, tracking and verification IDs, the email sender and server, page code, Search Console, site mode), so a copy for another client can never send their visitors to the wrong analytics account. "Full copy" keeps those for backups and staging-to-live. Whether a site is live or in maintenance is never copied. Loading a file shows every change first; values go through the same validation as the settings screens; settings that do not fit this site are skipped and listed; one restore point covers the whole import.
- One path for bulk changes: the setup assistant, presets, file imports and WP-CLI all apply settings through
Core\Blueprint: field validation, each module's own checks, side effects (drop-ins, config files, cache clearing) in the right order, a restore point first, and an activity-log entry. Undo restores the screen-visible settings and switches only; tokens and internal state that changed since are left alone. - Team access (C7): per role and per area (dashboard, SEO & AI, analytics, performance, security, toolkit), choose no access, view or manage. View-only areas show every setting and report, with inputs disabled and actions hidden. The Settings area and the dashboard's manage level stay administrator-only. Enforced on screens, menus and every REST route.
- White-label (C7): short and full name, logo (or a plain monogram when no logo is set), accent colour with a matching dark-mode tone, help link in the top bar, author, website and description in the Plugins list, and the agency colour on emails and the sitemap page. Removes the small "Ironhelm" HTML comments from page source. It renames; it does not hide: the plugin stays listed in Plugins. Technical names (file paths,
wp ironhelm,X-Ironhelm-Cache,IRONHELM_*constants, REST routes) stay as they are. - Licence and updates (C6): activate, check and remove a licence; status, plan, renewal date and site count. Every feature works without a licence. Updates arrive through WordPress's own update screens and auto-updates (the plugin header's
Update URIkeeps wordpress.org out of it), and every package is verified before WordPress unpacks it: SHA-256 plus an Ed25519 signature over slug, version and hash, checked against release keys built into the plugin (works without the sodium extension, through WordPress's bundled sodium_compat). Damaged, altered, forged or relabelled files are refused and logged. Without a licence the update check sends only version numbers. Licence key and token are stored encrypted. A server outage never removes an active licence. Protocol:docs/LICENSING-API.md. - Release signing:
build/keygen.mjscreates the release key outside the project;build/build.shsigns each ZIP withbuild/sign.mjs(<zip>.sig.json). - WP-CLI (C6):
wp ironhelm settings get|set(same validation as the screens, secrets masked, clear errors for unknown keys and options),export(template or full, chosen areas, to a file),import(preview,--dry-run,--yes, reads stdin),preset,undo,cache flush,firewall status|block|allow|unblock,scan files|vulnerabilities,health --format=json,license status|activate|deactivate|check|updates, andenable/disabletaking several features at once. Tested with WP-CLI 2.12.
Changed
wp ironhelm exportnow writes a settings file without keys, passwords or tokens. Before 0.8.0 it printed every stored setting, including encrypted secrets.- Saving settings from the screens and from WP-CLI now shares one function (
Rest::save_values). - The sitemap page tells visitors "this site" instead of naming the plugin.
- New extension points:
ironhelm/brand/name,ironhelm/brand/full_name,ironhelm/brand/mark,ironhelm/brand/menu_icon,ironhelm/brand/comment_name,ironhelm/brand/accent,ironhelm/brand/band,ironhelm/brand/author,ironhelm/topbar/after,ironhelm/cache_flushed,ironhelm/license/api.
Fixed
- Deleting the plugin with "delete all data" on left five tables behind (firewall, file check, audit, links, passkeys), never removed the runtime folder (it read the setting after deleting it), and used
GLOB_BRACE, which some hosts lack. Uninstall now removes all 15 tables, options, site transients, user and post data, the runtime folder (including GeoIP data, quarantine and checksum cache), cached pages and minified scripts, without following links out of those folders. Verified on the test site. - File check: a large plugin's official checksum list (WooCommerce: about 10,000 files) was too big for MySQL's default 1 MB packet, so it never cached and was downloaded again on every background step; on a slow connection a step could pass PHP's 30-second limit. Lists are now cached as compressed files (WooCommerce: 265 KB), steps are shorter, and background steps get up to 120 seconds where the host allows.
- Read-only screens: WordPress's own disabled-checkbox style showed a native tick on top of Ironhelm's switches, radios and chips.
Known limits
- The licence server does not exist yet. The plugin talks to
https://ironhelmsuite.com/wp-json/ironhelm-license/v1/as specified indocs/LICENSING-API.md; everything was tested against a local stand-in. Until the server is live, activating a licence fails with a clear message, the update check fails quietly and retries every three hours, and every feature keeps working. The readme links to terms and privacy pages on ironhelmsuite.com that must exist before selling. - A real one-click update was not installed end to end. The test site's plugin folder links to the source folder, and WordPress deletes the old folder during an update. Download verification was tested directly (genuine accepted; tampered, forged and relabelled refused); unpacking and replacing is WordPress core's standard upgrader.
- White-label cannot rename the "View details" changelog text, which comes from the licence server, or the technical names listed above.
- Multisite: settings, setup and licence are per site; no network-wide screens yet.
- Presets are opinionated defaults. The review step shows every change, but check strict mode's "application passwords off" against any app or integration that signs in with one.
0.7.0, 2026-11-17
Added: Security depth
- Firewall (D9): stops SQL injection, script injection (XSS), server-file reading, command injection (including Log4Shell), PHP code and object injection, hunts for secret files (
.env, config backups, web shells, PHPUnit), PHP files run from uploads, and 24 known attack tools. Runs before other plugins through a must-use loader, before cached pages are served (the page-cache drop-in calls it first), and optionally before WordPress itself (auto_prepend_filevia.user.inior.htaccess, with a self-check). Logged-in editors who legitimately post code are recognised by WordPress before anything is blocked; requests that bypass WordPress get no such benefit of the doubt. Repeat attackers (5 blocks in 10 minutes) are shut out for 24 hours, page hunters (30 "not found" hits in 2 minutes) for an hour. "Only record it" mode, address allow and block lists with ranges, paths to skip, a lockout guard that refuses settings that would block you, an emergency off switch (wp-content/ironhelm/firewall-off), and a CSV export of the 30-day log. Values are URL-decoded up to three times to defeat stacked encoding. On by default; switches itself off when Wordfence, All-In-One Security, Shield, NinjaFirewall, Solid Security, MalCare or BBQ Firewall is active. - Crawler verification (D10): visitors claiming to be Googlebot, Bingbot, Applebot, GPTBot, OAI-SearchBot, ChatGPT-User or PerplexityBot are checked against the address lists those companies publish (refreshed daily, about 940 ranges); impostors are blocked, real crawlers never are, and a missing or stale list never blocks anyone. Optionally enforces the AI crawler choices from Crawlers and AI at the door instead of only asking in robots.txt.
- Country and address rules (D11): block chosen countries, or allow only chosen countries, for the whole site or just the login and admin area. Country data from Cloudflare when the site really sits behind it (the header is trusted only from Cloudflare's own addresses), otherwise from the free DB-IP Lite database read by a built-in MaxMind DB reader (about 0.3 ms per lookup, no PHP extension needed). Verified crawlers are never blocked by country; unknown locations are never blocked on a guess.
- File integrity and malware check (D4): nightly, in background steps so large sites never time out: WordPress core against WordPress.org checksums, plugins from WordPress.org against their published checksums, Ironhelm against the checksum manifest its release build now ships (
checksums.json), unknown PHP files in core folders and the site root, PHP files and dangerous server rules in uploads, PHP hidden in recent images, and conservative malware signatures for anything already suspect plus themes and plugins from elsewhere. One-click restore of altered core files (downloaded from WordPress.org and verified before writing), quarantine with put-back, "expected" marking that resets if the file changes again, and alerts through Notifications. - Vulnerability check (D3): WordPress, every plugin and theme checked twice a day against WPVulnerability (which gathers CVE, Wordfence and WPScan reports; only names and versions are sent, never Ironhelm's own name) with severity, fixed-in version and CVE; plugins closed on WordPress.org and plugins abandoned for 2+ years. Security fixes install automatically when an available update fixes a known hole; nothing else changes your update settings.
- Passkeys (D12): sign in with Face ID, Touch ID, Windows Hello, an Android phone, a password manager or a security key. Login-page button plus browser autofill suggestions, passkey management on each profile, and passkeys as the second step after a password (they also satisfy the "two-factor required" rule). Server-side WebAuthn verification written to the W3C spec: ES256, RS256 and (where PHP has sodium) EdDSA; origin, challenge, site and user-verification checks; clone detection through signature counters; single-use challenges; rate-limited sign-in.
Added: SEO depth
- SEO importer (S1): titles, descriptions, noindex/nofollow, canonical addresses, social images, archive settings, site settings (separator, home title and description, organisation, social profiles) and redirects from Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework and Redirection. Title variables are translated, ones with no equivalent are dropped cleanly, "fill empty only" or "import and replace", resumable on large sites, and the other plugin's data is never changed.
- SEO audit and internal links (S9, S10): every public page scored on its real title and description (as Ironhelm outputs them), content depth, headings, image alt text, sharing image and links; a site-wide internal link map that finds orphan pages, broken links (confirmed by a real request) and links through redirects; menus and block-theme navigation count as links; shop, cart and blog index pages are judged fairly; pages kept out of search are listed last. Suggestions both ways: pages that mention a page but don't link to it, and, in the editor's search box, pages this one mentions without linking. Pages are re-checked when saved.
- WooCommerce SEO (S14): one complete Product description per product (WooCommerce's own JSON-LD is switched off): price or price range, currency, stock, offer validity (sale end date), return policy, brand (WooCommerce Brands and common brand plugins), GTIN, SKU, gallery images, ratings and up to five reviews, seller linked to your organisation; product Open Graph tags; Home > Shop > category path > product breadcrumbs; carts, checkout, accounts, sorted and filtered listings and hidden products kept out of search and the sitemap.
Added: Performance
- Object cache (P9): Redis persistent object cache with a built-in client (no PHP extension needed) and support for
WP_REDIS_*settings hosts already define. Instant full flush through key generations; group flush; per-site key prefixes; a maximum entry age so the cache can't grow forever; never replaces another plugin's object cache. If Redis goes away, the site carries on with WordPress' normal cache, a circuit breaker skips Redis for 30 seconds instead of slowing every visitor, and the next successful connection starts a fresh namespace so nothing stale is served. Test site: 40 database queries per page down to 1.
Changed
- Author is now "Ironhelm".
- Extension points for add-ons and modules:
ironhelm/seo/noindex,ironhelm/seo/canonical,ironhelm/seo/og,ironhelm/breadcrumbs,ironhelm/sitemaps/exclude,ironhelm/2fa/skip,ironhelm/seobox/after. - "Test after turning on" notes can now be specific to each feature.
- Searchable pick lists (used for countries) for long option lists.
Fixed
- The plugin core now registers itself before booting modules, so a module that checks another module while starting can no longer trigger endless recursion (found when WooCommerce SEO met WooCommerce).
Known limits
- Object cache was tested against a Redis protocol test double, not a real Redis server; test it on the host before relying on it.
- Passkeys were tested with Edge's virtual authenticator (ES256), plus signature tests for ES256 and RS256. Try one real phone and one real laptop before rolling out to clients.
- WooCommerce SEO was tested with WooCommerce 11.3.0 on a small test catalogue. The SEO importer was tested against each plugin's documented storage format, not by running those plugins.
- "Start before WordPress" was verified on PHP's built-in server for files called directly; its
.user.iniand.htaccessinstallers still need a pass on real Apache, LiteSpeed and PHP-FPM hosts.
0.6.1, 2026-11-17
Fixed
- Dashboard: when the health card shares the row with "Fix next" (laptop widths around 1280–1440 px), the area meters ran past the card edge and hid the scores. The card now places the readouts beside the dial only when they fit, and stacks them under it otherwise.
- Dashboard: the dial's guilloché rings stay centred on the dial in both layouts.
0.6.0, 2026-11-17
Added: Analytics pillar
- Visitor statistics (A1, A6): cookieless page views and visitors with a daily-rotating anonymous id (no IP addresses or cookies stored); sources grouped into search, social, AI assistants, referral, email, paid and direct, with UTM campaigns; top pages; devices; country when the site is behind Cloudflare; actions counted automatically (form submissions, phone and email link taps, downloads, outbound clicks) plus WooCommerce orders. A 1.3 KB (gzipped) deferred beacon posts to a lightweight collector that loads only WordPress' database layer (test site: about 60–90 ms per beacon, versus about 1.4 s through the REST API it falls back to). Raw hits are summarised nightly and deleted after two days; daily totals kept 25 months by default. 7/30/90-day views with change against the previous period, a trend chart with a table view.
- AI visibility (A3): which AI and search crawlers read which pages, logged with no database write per crawl (append-only file, imported hourly), including crawls served from the page cache; separate counts for AI answer bots, training bots and search engines; visitors arriving from ChatGPT, Perplexity, Claude, Gemini, Copilot and other assistants.
- Real-user speed (A7): Core Web Vitals (LCP, INP, CLS, plus first paint and server response) measured in a sample of real visitors' browsers; 75th percentile with Google's good / needs work / poor thresholds and the share of visits in each; phones and larger screens separately; slowest pages; daily trend; health checks when phones fall below "good"; optional Chrome UX Report API key to show Google's own 28-day numbers side by side.
- Search performance (A2): Google Search Console clicks, impressions, click rate and average position with change against the previous period, daily clicks, top searches and top pages; Bing Webmaster Tools clicks, impressions and top searches. Google connects through a read-only service account (scope
webmasters.readonly, RS256-signed token, key stored encrypted) straight to Google with no middleman server; "Find my property" detects the right property; results cached for six hours. - Tracking tags (A4): Google Analytics 4, Tag Manager, Google Ads, Meta Pixel, Microsoft Clarity, LinkedIn Insight and TikTok Pixel by ID, with validated IDs and Google Consent Mode v2 defaults (EEA/UK/Switzerland or everyone).
- Consent banner (A5): bar or corner box, light or dark, own button colour and wording; "Reject all" exactly as prominent as "Accept all"; per-category choices (statistics, advertising); scripts held back until consent and released in order; Google Consent Mode v2 updates; Global Privacy Control honoured; optional Europe-only display by time zone; a button and
#cookie-settingslinks to change the choice later; ask again after a set time or on demand; anonymous consent records (no IP or name) with CSV export. Google tags wait for consent by default; Consent Mode "advanced" is an explicit opt-in. - Email reports (A8): weekly or monthly HTML email built for phones: health score with the top things to fix, visitors and sources, Google and Bing search, phone speed, AI crawlers, password lockouts and email delivery; live preview in the dashboard; send now.
Fixed
- Speed beacons with no usable number are no longer stored as empty rows.
- A visitor who changes their consent choice within a minute now has the new choice recorded (only exact repeats are skipped).
- The consent panel scrolls on short phone screens instead of pushing "Save" out of reach.
- Plate headers and period switches wrap cleanly on phones; chart tables and the Google comparison table keep their labels when stacked on phones.
Known limits
- Search Console, Bing and Chrome UX Report connections were tested against recorded API responses, not live accounts. The signing and request formats are verified; confirm on a real property before relying on them for a client.
- Consent records prove what was chosen, not legal compliance. The banner is not an IAB TCF certified platform, which Google requires for AdSense and Ad Manager ads shown in the EEA and UK.
0.5.0, 2026-11-17
Added: Performance pillar
- Shared HTML pipeline: every front-end optimisation runs in one output buffer, in a fixed order, and a failing step can never break the page; partial (early-flushed) pages are left untouched. "Preview speed changes" in Settings applies all of it to administrators only;
?ihs-nooptimizeshows any page without optimisations for comparison. - Page cache (P1): stand-alone
advanced-cache.phpdrop-in that serves stored pages before WordPress loads (test site: 477 ms → 22 ms), precompressed gzip copies, 304 responses, security headers included on cached copies, ignored marketing parameters (utm_, gclid, fbclid…), separate phone copies (optional), automatic exclusions for logged-in users, carts, checkout, account pages and personalised responses; clears the page, home, blog, archives and author page on every edit; full clear on theme, menu, widget, plugin and permalink changes; background preload; admin-bar "Clear cache"; host-aware: on WP Engine, Kinsta, SiteGround, Pantheon, Pressable, WordPress.com, GoDaddy, Cloudways and Flywheel, or next to another caching plugin, it adds no second cache and clears theirs (WP Engine, SiteGround, Pantheon, LiteSpeed Cache, Nginx Helper, Breeze). Never overwrites another plugin's drop-in; wp-config.php edits are marked and backed up. - Scripts and styles (P3): asks WordPress 6.3+'s own loading-strategy system to defer every eligible script, so scripts that inline code or blocking scripts depend on stay blocking automatically; jQuery excluded unless chosen; holds back chat widgets, pixels and heatmaps (25 services by default) until the first interaction or an optional timeout, preserving order where it matters; HTML, CSS and JavaScript minification that only removes comments and spacing (strings, template literals and regular expressions untouched; JavaScript keeps line breaks), CSS relative URLs rewritten for the minified copy. No file combining, by design.
- Asset manager (P2): scans any page as a logged-out visitor, lists every stylesheet and script with its plugin, size and what depends on it, and switches each off on that page, that content type, everywhere, or everywhere except that page.
- Images and media (P4, P8): WebP copies created next to originals on upload and in background batches (kept only when smaller), swapped into
src/srcsetwhen pages are sent, so existing content needs no edits and switching off reverts instantly; compression quality; resize-on-upload limit; lossless removal of EXIF/GPS/IPTC from JPEGs (colour profiles kept); featured-image preload withfetchpriority="high"; number of images loaded eagerly; click-to-load YouTube (privacy-enhanced domain) and Vimeo players; speculative loading control (WordPress 6.8+); preconnect hints. - Fonts (P5): Google Fonts stylesheets and WOFF2 files downloaded in the background and served from the site, with
font-display: swap; Google preconnects removed once everything is local. - WordPress clean-up (P6): emoji script, embed discovery, dashicons for visitors, per-block CSS loading, jQuery Migrate (optional), self-pingbacks, heartbeat control, revision limit, autosave interval, server-timer mode for scheduled tasks with a stalled-cron warning.
- Database care (P7): one-click clean-up of old revisions, abandoned drafts, old trash, spam, expired transients, orphaned metadata and embed caches; weekly automatic clean-up; the 15 largest settings loaded on every page, with "load only when needed".
- CDN and Cloudflare (P10): static file URL rewriting for pull-zone CDNs with exclusions; Cloudflare API token + zone for automatic cache clearing (changed pages or everything), connection check.
- WooCommerce speed (P11): shop scripts and styles only on shop pages (shortcodes and blocks detected), cart-fragment requests off outside the shop, optional WooCommerce Admin switch-off.
Fixed
- Ctrl/Cmd+K no longer also opens WordPress 6.9's own command palette on Ironhelm screens.
- Automatic redirects keep the permalink's trailing slash (one hop instead of two).
0.4.0, 2026-11-17
Added: SEO & AI pillar
- Titles and descriptions (S3, S8): title patterns per page type with variables, custom title and description per page, post and category, automatic descriptions from the content, canonical URLs (custom or automatic, pagination-aware), noindex rules for search results, date archives, author pages, tag pages and empty archives, per-page noindex/nofollow, attachment pages redirected to the file or parent, Open Graph and X cards with a per-page image, featured image or site default, verification tags for Google, Bing, Yandex, Pinterest and Baidu (paste the code or the whole tag).
- Live search preview in the block and classic editors, with length guidance measured the way Google truncates.
- Structured data (S7, S11, S13, S15): one connected schema.org graph: Organization, LocalBusiness (19 business types, address, coordinates, opening hours, price range) or Person; WebSite; WebPage (About, Contact, Collection, Profile); Article/BlogPosting/NewsArticle with author, publisher, image, section and keywords; Service pages; BreadcrumbList. Official profiles (sameAs) connect the site to the same entity elsewhere. Author profiles gain job title, qualifications, areas of expertise and profile links (E-E-A-T). Per-page "what this page is" override.
- Breadcrumbs: Ironhelm Breadcrumbs block and
[ironhelm_breadcrumbs]shortcode. - Sitemaps (S4): replaces the WordPress sitemap; leaves out noindexed and excluded content; lists each page's main image; accurate last-modified dates; categories and optional authors; cached until content changes; styled browser view; old /wp-sitemap.xml redirects; added to robots.txt; switched off automatically on staging.
- Crawlers and AI (S5, S6, S12): robots.txt managed in the dashboard (warns when a physical file overrides it); AI answer bots (ChatGPT search, Perplexity, Claude…) and AI training bots (GPTBot, ClaudeBot, Google-Extended, CCBot…) controlled separately; internal search kept out of crawls; IndexNow notifications on publish, update and unpublish (live site only, rate-limited, with a log); llms.txt generated from your pages and posts.
- Redirects and broken links (S2): 301/302/307/410 redirects, pattern (regex) redirects, automatic redirects when a published page's address changes (with loop protection and re-pointing of older redirects), CSV import and export, pause/resume, hit counts; 404 monitor with referrers, ignore patterns for bot probing, one-click "Redirect" from a broken address, retention. Exact redirects cost one array lookup per request.
0.3.0, 2026-11-17
Added: Toolkit pillar
- Email delivery (U1–U3): send through Brevo, SendGrid (US/EU), Mailgun (US/EU), Postmark, Amazon SES (signed with AWS Signature V4, verified against Amazon's test vectors), Microsoft 365 via the Graph API (password SMTP is retired there), or any SMTP server; HTTP APIs used wherever possible. Sender address can be enforced for every email while keeping other plugins' Reply-To. Automatic fallback to server mail when a service fails (SMTP and API). Email log with status, error, provider and message preview (HTML shown in a locked-down sandbox), one-click resend, retention limit, test email, failure alerts. Deliverability check for SPF (including whether it covers your service), DKIM and DMARC, with plain-language fixes.
- Site mode (U5): Live, Coming soon (200 + noindex, optional countdown), Maintenance (503 + Retry-After so rankings are kept) and Private (401 until login or a visitor password). REST API, payment-gateway callbacks, cron and logins keep working. Bypass by role or IP, a 7-day client preview link that can be revoked, scheduled go-live, admin-bar indicator, and one-tap mode switching on the dashboard.
- Staging guard (U4): detects staging, development and cloned copies (WordPress environment type, staging host names, or a different address from the recorded live site); hides them from search engines without touching the live setting; redirects or holds back their email (Cc/Bcc dropped); pauses Ironhelm's outbound pings; amber "Staging" badge.
- Activity log (U6): logins (failed logins rate-limited per address), account, role, password and email changes, application passwords, publishing, updates, trash and deletes, media, plugin and theme installs/updates/activations, WordPress core updates, key settings with before/after values, exports, Ironhelm and security events. Every entry is SHA-256 hash-chained; "Verify history" pinpoints edited or deleted entries. Filters, search, paging, CSV export (formula-safe), nightly retention.
- Header and footer code (U7): site-wide head, body-open and footer code plus per-page code; only for accounts allowed unfiltered HTML; option to skip logged-in visitors; no PHP execution by design.
- Notifications (U8): alerts by email, Slack, Microsoft Teams (Workflows webhooks) and generic JSON webhooks, with a minimum level and per-alert throttling; test button reports delivery per channel.
Fixed
- Two-factor login: an empty backup-code list was counted as one code, which skipped creating backup codes on first setup.
- Embedded panels no longer paint a background on the profile screen.
0.2.0, 2026-11-17
Added: Security pillar
- Login protection (D2): pauses logins from an address after repeated failures (5 in 15 minutes by default), with 4× escalation for repeat offenders up to 24 hours; instant lockout for bot usernames (admin, root, test…) that don't exist; one generic error message for wrong username or password, including WooCommerce; allowlist with CIDR ranges; failed application-password logins counted; skips the password hash check entirely while locked.
- Private login address: serves the login page at a custom address; wp-login.php, /wp-admin, /login and /dashboard show the theme's 404 to logged-out visitors; password-reset emails, logout and lost-password links follow the new address; the new address is emailed to the site admin.
- Lockout recovery (D7): "Locked out of your own site?" sends a 15-minute unlock link bound to the requester's network;
define( 'IRONHELM_RECOVERY', true );pauses all security modules;wp ironhelm unlockandwp ironhelm 2fa-reset <user>. - Two-factor login (D1): authenticator apps (RFC 6238, verified against the RFC test vectors), emailed codes, 10 single-use backup codes, trusted devices (7/30/90 days, revoked when two-factor changes), per-role enforcement with a grace period, admin reset from the user's profile, XML-RPC blocked for accounts that use two-factor, five wrong codes end the attempt and count as a failed login. QR codes are generated on the site (no third-party QR service).
- Hardening (D6 + "hide WP indicators"): hides the WordPress version (generator tag, core asset versions), removes header clutter and the pingback header, optional REST link removal, turns off XML-RPC (Jetpack-aware), blocks username discovery (?author=, REST users list, users sitemap, oEmbed author), turns off the dashboard code editor, optional application-password switch, strong-password policy (length, common passwords, no username/email/site name) for WordPress and WooCommerce, maximum session length, idle logout, "log out everywhere else", dormant-administrator check.
- Server rules: .htaccess blocks for sensitive files, folder listings and PHP in uploads, each written as a marked block with a backup; Ironhelm checks the site still loads and restores the previous file if the server rejects a rule. Nginx sites get copy-ready rules.
- Security headers (D5): nosniff, frame protection, referrer policy, permissions policy, HSTS (age, subdomains, preload), cross-origin opener policy, Content Security Policy with a report-only mode that lists what would be blocked, and a "check what browsers receive" button.
- Spam shield (D8 + CAPTCHA): hidden honeypot on logins, sign-ups, lost password, comments and forms; comments sent in under 3 seconds or without JavaScript go to spam; Cloudflare Turnstile, hCaptcha or reCAPTCHA v2 on login (every time or after a failed try), registration, lost password, comments, WooCommerce checkout, Contact Form 7, WPForms, Gravity Forms and Elementor forms; fails open (with a dashboard warning) if the CAPTCHA keys are wrong or the service is down, so nobody is locked out; "turn off comments" everywhere or per content type.
- Hotlink protection: Apache rules that always allow search engines, social previews and chat apps; Nginx rules to copy.
- Safe SVG uploads (D13): per-role SVG uploads, cleaned with an allowlist (scripts, event handlers, javascript: links, external references, entity tricks removed; DOCTYPE/entity documents rejected); SVGs in uploads also get a no-script header on Apache.
- Last-login tracking for every account.
Fixed
- Dashboard: brand and area links no longer inherit the link colour.
- Phone layout: breadcrumb separator hidden, "Always on" header no longer boxed.
0.1.0, 2026-11-17
Added
- Module system: every feature is a module that loads no code when switched off.
- Settings framework driven by a field schema (toggles, choices, numbers, lists, code, secrets, images), with server-side sanitizing and encrypted secrets.
- Settings history: the previous version of a feature's settings is kept on every save and can be restored.
- Admin REST API (
ironhelm/v1) with capability checks per area. - Site health score across Security, Search & AI, Speed and Email, with a prioritised "Fix next" list.
- Conflict detection for 80+ overlapping plugins; overlapping features start switched off.
- Environment detection: visitor IP (Cloudflare-aware, spoof-resistant), web server, managed hosts with their own cache, staging hostnames.
- Database tables for upcoming modules (activity, redirects, 404s, email log, analytics, lockouts, consent, web vitals).
- Admin interface: dashboard with the helm dial, area overviews, feature screens, command palette (Ctrl/Cmd + K or /), light, dark and match-device themes, phone-friendly layout.
- WP-CLI:
wp ironhelm modules|enable|disable|export|health. - Uninstall cleanup that only runs when the owner opts in.