-
v3.7.0 Stable
released this
2026-11-04 13:43:39 +00:00 | 0 commits to main since this release3.7.0
Release date: 2026-11-03
Highlights
- Import from other SEO plugins (spec section 5): on-demand migration of the noindex / nofollow flags stored by Yoast SEO, Rank Math, SEOPress and All in One SEO into noindex SEO per-post and per-term overrides — detected from data presence (the source plugin does not need to be installed), user-confirmed, and never overwriting content that already has its own override.
- Virtual robots.txt management (spec section 7): block (
Disallow: /) or allow (Allow: /) individual crawlers, appended to the robots.txt WordPress generates virtually — never replacing it — with one-click presets for the well-known AI and search-engine crawlers. Inactive by default.
Added
- Import from other plugins. A new section on the Import / Export tab lists every supported source plugin together with how many posts and terms carry its robots flags, and imports the checked ones on explicit confirmation. The runner converts source flags into granular overrides (
_noindex_seo_override=1plus noindex / nofollow), skips and reports content that already carries a noindex SEO override row (an explicit "off" counts as data), re-verifies LIKE-based matches (Rank Math's serialized arrays) per post so false positives are dropped, and whitelists source slugs server-side. Sources are data-driven and filterable (noindex_seo_import_sources) so third parties can register or correct one. - Robots.txt tab. A fourth settings tab manages up to 30 bot rules (User-agent token + block/allow policy;
*wildcard supported, duplicates collapse, agents stripped to the robots.txt-legal charset). The rules are appended through core'srobots_txtfilter only while the feature is enabled, a live preview shows the exact block appended, and preset buttons add the well-known AI crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot, Bytespider… — filterable vianoindex_seo_ai_bots) or the main search engine crawlers (noindex_seo_search_bots) as blocked rules. The core output — and a physical robots.txt or "Discourage search engines" — always takes precedence. - The robots.txt settings ride the consolidated option and the JSON export/import.
Changed
- The settings page gained a fourth tab (General / SEO Settings / Import-Export / Robots.txt); the rule-table JavaScript is now shared between the conditional rules and the robots.txt tables, scoped per container.
Fixed
- Block editor granular overrides now save on custom post types registered without
custom-fieldssupport (a very common CPT registration). Without that support the REST API exposes nometafield for the post type, so the editor sidebar's saves were silently dropped with an HTTP 200 — the override checkbox appeared to do nothing. The plugin now addscustom-fieldssupport for exactly the post types it registers meta on (while per-post granular control is enabled).
Security
- No new attack surface: the import handler is
manage_options+ nonce gated with whitelisted sources, writes only through the meta API after re-reading each source flag, and skips content with existing override data; robots.txt agents are charset-stripped (no newline or comment injection into the file) and policies are whitelisted; the tab form rides the existing nonce + capability path. PHPCS/PHPStan/composer audit clean.
Compatibility
- WordPress: 7.0 - 7.2
- PHP: 8.3 - 8.6
Tests
- PHPUnit: 9.6.38 (230 tests, 1152 assertions, all passing) on the WordPress 7.2-beta3 test library, run under PHP 8.3, 8.4, 8.5 and 8.6.0RC3 — including the new robots.txt sanitization/output/filter/form suites and the import detection/conversion/never-overwrite/false-positive/handler suites.
- PHPCompatibility: 0 errors on the declared range 8.3-8.6 and on the full review range 5.6-8.6.
- PHPCS (WordPress-Core, -Docs, -Extra) and PHPStan level 9: 0 errors.
- Translations: Catalan and Spanish catalogs regenerated and 100% complete (209 strings each).
Downloads
-
v3.6.0 Stable
released this
2026-11-04 13:42:22 +00:00 | 1 commits to main since this release3.6.0
Release date: 2026-11-03
Highlights
- Modern robots directives (TODO #5):
notranslate,max-snippet,max-image-preview,max-video-previewandunavailable_afterjoin the five existing booleans — on every surface: the global context grid, per-post and per-term granular overrides, Quick Edit, the block editor sidebar, the REST/effectiveendpoint and WP-CLI (name=valuetokens). - Conditional auto-noindex rules (TODO #11): apply
noindexautomatically to any post whose custom field (for example an ACF field) exactly matches a value; matched posts also drop out of the core XML sitemap. - Multisite behavior documented (TODO #9, docs variant): per-site by design, with an export/import-based rollout recipe.
Added
- Value directives everywhere. Boolean directives are flags; value directives carry a value and render as
name:value(max-snippet:-1,max-image-preview:large,unavailable_after: Tue, 01 Jan 2030 09:00:00 +0000in site time with a numeric UTC offset). They are configured with typed inputs (number, size select,datetime-local) on the settings grid, the post meta box, Quick Edit, the term panel and the Gutenberg sidebar; stored in the consolidated option (contexts) and in_noindex_seo_{directive}post/term meta; registered with the REST API (register_post_meta/register_term_metawith per-type sanitization); exported/imported with normalization; and supported by WP-CLI —wp noindex-seo set archive max-snippet=-1 max-image-preview=large,wp noindex-seo unset archive max-snippet(plain name clears the value), andlistreports the configured value (max-snippet:-1) oroff. notranslateas the sixth boolean directive, including a matching SVG icon in the plugin's icon registry and membership in the "Apply Recommended Defaults" set (which enables the six booleans; value directives stay untouched — "enabling" them without a value is meaningless).- Conditional rules (TODO #11). A "Conditional rules" card on the SEO Settings tab manages up to 20 exact-match rules (custom field name + value; rows with empty field/value are ignored, and the plugin's own
_noindex_seo_meta keys are rejected). Rules run on the front-end below an explicit per-post override and above per-CPT/global defaults; matched posts surface assource: auto_rulein/effectiveand are excluded from the pages sitemap. The rules read plain post meta, so no ACF installation is required. - A
notranslateSVG directive icon, plus badge support for value directives in the Robots columns (max-snippet:-1tokens).
Changed
noindex_seo_metarobots()now takes a directive map (name => true|value); a flat list of boolean names (the pre-3.6.0 third-party calling convention) is still accepted and normalized. Thewp_robotsintegration passes directive values through to core ($robots['max-snippet'] = '-1').noindex_seo_get_setting()returns the normalized string value for value directives ('' = off) instead of coercing everything to 0/1; the hourly transient cache stores values the same way.- The WP-CLI
set/unsetdefault (no directive arguments) now enables/disables the six boolean directives; value directives always require explicitname=valuetokens (a value on a boolean, or an invalid/missing value, is rejected with a descriptive error). Datetime values need quoting or aTseparator because of the space:unavailable_after=2030-01-01T09:00. - Block editor sidebar labels dropped their emoji prefixes (matching the 3.5.0 admin UI icon direction), and the sidebar gained controls for all five new directives.
Fixed
- Nothing.
Security
- No new attack surface: rules and value directives ride the existing nonce + capability paths (settings form:
manage_options+check_admin_referer; meta box/Quick Edit:edit_post; term panel:manage_categories); every value normalizes through a single whitelist-driven normalizer (integers ≥ -1, a none/standard/large enum, a parse-validated datetime); rule fields strip everything but[A-Za-z0-9_-]and values go throughsanitize_text_field(); sitemap rule clauses use WP_Query'smeta_query(prepared by core). PHPCS/PHPStan/composer audit clean.
Compatibility
- WordPress: 7.0 - 7.2
- PHP: 8.3 - 8.6
Tests
- PHPUnit: 9.6.38 (216 tests, 1107 assertions, all passing) on the WordPress 7.2-beta3 test library, run under PHP 8.3, 8.4, 8.5 and 8.6.0RC3 — including the new registry/normalization, settings-merge, form-roundtrip, front-end value output, granular value overrides, REST formatted tokens, CLI name=value, rules sanitization/matching/precedence/sitemap/auto_rule suites.
- PHPCompatibility: 0 errors on the declared range 8.3-8.6 and on the full review range 5.6-8.6.
- PHPCS (WordPress-Core, -Docs, -Extra) and PHPStan level 9: 0 errors.
- Translations: Catalan and Spanish catalogs regenerated and 100% complete (188/187 strings), including the previously untranslated strings found during the merge.
Downloads
- Modern robots directives (TODO #5):
-
v3.5.0 Stable
released this
2026-11-03 17:07:02 +00:00 | 2 commits to main since this release3.5.0
Release date: 2026-11-03
Highlights
- WooCommerce special-page contexts (TODO #8): dedicated directives for the WooCommerce Cart, Checkout and My Account pages, detected through the page-ID options (no WooCommerce code needed), recommended by default, and mirrored across the front-end, the REST
/effectiveendpoint and the core XML sitemaps. - Compatibility window narrowed to WordPress 7.0 - 7.2 and PHP 8.3 - 8.6:
Requires at leastraised from 4.7 to 7.0,Requires PHPraised from 5.6 to 8.3,Tested up toset to WordPress 7.2 (verified on 7.2-beta3) and PHP support documented through 8.6 (verified on 8.6.0RC3). - Fixed
wp noindex-seo list, which fatalled on every real WP-CLI invocation since 3.4.0 (nonexistent static API call;--contextfilter renamed to--onlyto avoid WP-CLI 2.11+'s reserved global flag). - Directive icons modernized for the SVG era: on WordPress 7.2+ the five directive icons render through the core Icons API — the same system WordPress 7.2 uses for its own admin chrome — while WordPress 7.0 - 7.1 keep the legacy emoji glyphs as a retrocompatible fallback.
Added
- WooCommerce contexts (
woo_cart,woo_checkout,woo_myaccount): the Cart, Checkout and My Account pages are regular pages that conventionally deserve noindex but previously fell into the genericpagebucket. Each now has its own context with all five directives, a "WooCommerce" section on the SEO Settings tab (rendered only when the store pages are configured), and Recommended badges — the three contexts also joined the "Apply Recommended Defaults" set (now 15 contexts). - Detection is option-driven (
woocommerce_cart_page_id,woocommerce_checkout_page_id,woocommerce_myaccount_page_id): no WooCommerce class or function dependency; without WooCommerce the contexts are inert. My Account endpoints (order history, addresses) and the checkout order-pay / order-received endpoints share their parent page's ID, so they are covered automatically. - Precedence: the dedicated contexts run before the generic
pagecontext on the front-end and in/wp-json/noindex-seo/v1/effective, so a Woo page with directives gets them instead of the page-level ones; with no dedicated directives the page context still applies. - Sitemap: special pages whose context has
noindex=1drop out of the pages sitemap even when thepagecontext is not noindexed. - SVG directive icons (retrocompatible). The five robots-directive icons render as color-adaptive 16px SVGs through the WordPress Icons API (
wp_register_icon()/wp_get_icon()), registered in a privatenoindex-seoicon collection — everywhere they appear: the settings grid, the post meta box, Quick Edit, and the post and taxonomy list-table Robots columns. The SVG path is gated to WordPress 7.2+, whose icon sanitizer understands the stroke-based designs (rect/circle,stroke*attributes) and whose registry supports private collections; on WordPress 7.0 - 7.1 the legacy emoji glyphs remain (7.1's narrower sanitizer would strip the SVGs to unstyled fragments), so rendering stays correct on every supported version — and consistent on every OS, unlike the emoji (which each platform draws differently). Follows the core direction of replacing admin dashicons with SVG (wordpress-develop#12270, landed in WP 7.2's admin chrome). The Quick Edit label strings dropped their emoji prefix; the plain directive names were already in the translation catalogs, so no translations were lost.
Changed
- Compatibility window: WordPress 7.0 - 7.2 (was 4.7 - 7.2), PHP 8.3 - 8.6 (was 5.6 - 8.5). The full-range PHPCompatibility scan (PHP 5.6 - 8.6) still passes clean — the code keeps its PHP 5.6-parseable syntax — but the declared and supported window is now 7.0 / 8.3 and up, per the product support policy. The runtime guards for WordPress APIs older than 7.0 remain in place as harmless no-ops and may be removed in 4.0.
- Tooling aligned with the new window:
phpcs.xmltestVersion8.3-8.6 andminimum_supported_wp_version7.0,phpstan.neonphpVersion80300,bin/preflight.shgates scanning the declared range,composer.jsonPHP constraint>=8.3, and the obsoleteWPCompat.*PHPStan ignores removed (every guarded hook exists since 7.0). - Development dependencies refreshed via
composer update: PHPUnit 9.6.38, PHPStan 2.3.5, wordpress-stubs 7.1.2 (no CVEs;composer auditclean). - The "Apply Recommended Defaults" set grew from 12 to 15 contexts (button title and description updated; existing configurations are untouched — the button is opt-in).
Fixed
wp noindex-seo listwas broken on real WP-CLI installs since 3.4.0: the output call went toWP_CLI\Utils::format_items()(a static method that does not exist — the real API is the namespacedWP_CLI\Utils\format_items()function), and the--contextfilter parameter collided with the--contextglobal flag reserved by WP-CLI 2.11+, so the value never reached the handler. The filter is now--only=<context>and the command renders through the real function API. The unit-test stub was aligned with the real WP-CLI surface (namespaced function, not a Utils class), and everywp noindex-seocommand was smoke-tested against the real WP-CLI 2.12 phar.
Security
- No security changes; the new contexts reuse the consolidated settings storage and existing sanitization paths, and PHPCS/PHPStan/composer audit stay clean.
Compatibility
- WordPress: 7.0 - 7.2
- PHP: 8.3 - 8.6
Tests
- PHPUnit: 9.6.38 (198 tests, 817 assertions, all passing) on the WordPress 7.2-beta3 test library, run under PHP 8.3, 8.4, 8.5 and 8.6.0RC3 — including the icon registration, SVG rendering, emoji fallback and admin-markup tests.
- PHPCompatibility: 0 errors on the declared range 8.3-8.6 and on the full review range 5.6-8.6.
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra) and PHPStan level 9: 0 errors.
Downloads
- WooCommerce special-page contexts (TODO #8): dedicated directives for the WooCommerce Cart, Checkout and My Account pages, detected through the page-ID options (no WooCommerce code needed), recommended by default, and mirrored across the front-end, the REST
-
v3.4.0 Stable
released this
2026-11-03 17:05:54 +00:00 | 3 commits to main since this release3.4.0
Release date: 2026-09-19
Highlights
- WP-CLI support (TODO #7): a
wp noindex-seocommand namespace with list, set, unset, export, import and bulk per-post overrides — automation-friendly and scaling past the ~200-post ceiling of the bulk UI.
Added
- WP-CLI commands.
wp noindex-seo list [--context=] [--format=table|csv|json|yaml](every context × directive pair with its status),wp noindex-seo set <context> [<directive>...]/wp noindex-seo unset <context> [<directive>...](default: all five directives; saving clears the transient cache),wp noindex-seo export [<file>](JSON payload to STDOUT or a file, same as the tools tab),wp noindex-seo import <file> [--dry-run](same validation and sanitization as the import form;--dry-runreports the number of values that would change), andwp noindex-seo override <post_id>... [--off](bulk per-post granular overrides without the UI's selection limit;--offclears the override and directive meta). The commands enforce the same rules as the settings page: unknown contexts/directives are rejected and the attachment context refuses to enable while the implementation method is meta-only. stubs/wp-cli-stubs.php: minimal WP-CLI signatures for PHPStan and a recording stub for the test suite (never shipped; excluded from the release ZIP and from PHPCS).- The undefined "migrate-attachments" command from the original TODO was replaced by the general-purpose
overridebulk command, which covers the same need for every post type.
Changed
- Nothing.
Fixed
- Nothing.
Security
- No security changes; the CLI handlers reuse the existing validated/sanitized helpers, operator-supplied file paths are checked with
is_readable()before reading, and PHPCS/PHPStan/composer audit stay clean.
Compatibility
- WordPress: 4.7 - 7.2
- PHP: 5.6 - 8.5
Tests
- PHPUnit: 9.6.36 (185 tests, all passing): command registration, set/unset round-trips (including transient invalidation and defaults), unknown context/directive rejection, the attachment header-only invariant, list rows and filtering, export to STDOUT and file, import dry-run/apply/rejection, and override enable/disable/skip-missing.
Downloads
- WP-CLI support (TODO #7): a
-
v3.3.0 Stable
released this
2026-11-03 17:04:35 +00:00 | 4 commits to main since this release3.3.0
Release date: 2026-09-19
Highlights
- The settings page is reorganized with the native WordPress tab navigation (General / SEO Settings / Import-Export) and titled sections, built exclusively on core
nav-tabclasses with URL-based switching — no proprietary tab CSS or JavaScript.
Added
- Native WordPress tab navigation on the settings page (
nav-tab-wrapper/nav-tab, the same pattern as the core Updates and Plugins screens): General (implementation method and configuration options), SEO Settings (the directive grid), and Import / Export (the JSON tools). Tabs switch through thetabquery parameter and the active panel renders server-side, so they work without JavaScript and are bookmarkable. - Titled sections inside the tabs: "Recommended settings" (one-click defaults), "Overview" (the number cards) and "Page contexts" (the directive grid) on SEO Settings; "Export settings" and "Import settings" headers on the Import / Export tab. Spacing added between the tab bar and the content below.
Changed
noindex_seo_process_form()is now tab-scoped: saving from the General tab updates only the configuration and preserves the directive grid, saving from SEO Settings updates only the directives and preserves the configuration — hidden tabs can no longer reset each other's values. The form carries anoindex_seo_form_scopemarker and the redirect returns to the tab the user saved from.- The header-only restriction for the attachment context now follows the saved implementation method (the method select lives on the General tab), and switching the method to meta/HTML-only from General zeroes the attachment directives to keep the invariant consistent.
- The apply-suggestions redirect and the import success/error redirects return to their source tabs (
tab=settings,tab=tools). - Removed the dead custom tab machinery: the
.noindex-seo-tab*CSS rules, theinitTabs()JavaScript with its localStorage persistence, and the unused.noindex-seo-apply-noteclass (previously flagged as dead code by the 3.1.6 deploy audit).
Fixed
- Nothing.
Security
- No security changes; the tab parameter is strictly safelisted server-side (
sanitize_key+ allow list) and PHPCS/PHPStan/composer audit stay clean.
Compatibility
- WordPress: 4.7 - 7.2
- PHP: 5.6 - 8.5
Tests
- PHPUnit: 9.6.36 (172 tests, all passing): tab markup (three tabs, active class, unknown-tab fallback), per-tab rendering isolation, scope-aware saving (config-only / grid-only / preserve-other-side / attachment invariant / tab-aware redirect), and section ordering.
Downloads
- The settings page is reorganized with the native WordPress tab navigation (General / SEO Settings / Import-Export) and titled sections, built exclusively on core
-
v3.2.0 Stable
released this
2026-11-03 17:03:27 +00:00 | 5 commits to main since this release3.2.0
Release date: 2026-09-18
Highlights
- Two roadmap features: JSON export/import of the settings (#6) and runtime conflict verification against the
wp_robotsAPI (#10).
Added
- Export / Import of settings (JSON). Two new controls on the settings page: "Export settings" downloads the consolidated settings as a JSON file (
noindex-seo-settings-{date}.json), and "Import settings" restores the global settings from a previously exported file. Imports are strictly validated and sanitized: plugin marker check, 1 MB size limit,is_uploaded_file()verification, the upload is never persisted to the uploads directory, every directive is normalized to 0/1, config values go through the same safelists as the settings form, and contexts that do not exist on the importing site (e.g. custom post types from another install) are dropped. Per-post and per-term granular overrides are content data and are never touched by an import. Both actions requiremanage_optionsand a nonce; success and error notices survive the redirect. - Runtime conflict verification (TODO #10). When no known SEO plugin conflicts,
noindex_seo_detect_conflicts()now also inspects the callbacks actually registered on thewp_robotsfilter (WordPress 5.7+): anything that is not a core callback or one of ours — a foreign function, a class method, or a closure from a theme or unknown plugin — produces a dismissible admin notice naming the detected callback. The core callback safelist is filterable vianoindex_seo_core_robots_callbacks. The notice honours the existing "disable compatibility warnings" opt-out.
Changed
- Nothing.
Fixed
- Nothing.
Security
- No security changes; the new endpoints follow the canonical checklist (capability + nonce on both actions, strict input validation, safelisted config values, no persistence of uploads) and PHPCS/PHPStan/composer audit stay clean.
Compatibility
- WordPress: 4.7 - 7.2
- PHP: 5.6 - 8.5
Tests
- PHPUnit: 9.6.36 (165 tests, all passing): export payload shape and JSON round-trip, import sanitizer (happy path, normalization, unknown-context dropping, malformed-payload rejection), handler guards, foreign-callback detection (functions, class methods, closures, own-prefix skipping, filterable safelist) and the runtime notice.
Downloads
- Two roadmap features: JSON export/import of the settings (#6) and runtime conflict verification against the
-
v3.1.6 Stable
released this
2026-11-03 17:02:11 +00:00 | 6 commits to main since this release3.1.6
Release date: 2026-09-18
Highlights
- Admin UI modernization: all inline styles removed in favour of WordPress admin color-scheme-aware, RTL-ready classes (audit finding M7), plus the two minor items deferred from the 3.1.5 deploy audit (stale wp_die message, unreachable REST fallbacks).
Added
- Regression tests locking in the new UI conventions: the settings page and meta box render without any
style="..."attribute, and the stylesheet is verified to load on the post-list / post-edit / term-edit screens (gated by the granular flags) while staying off everything else.
Changed
- All 61 inline
style="..."attributes removed from the settings page, post meta box, term edit panel, Quick Edit, and the post/term list "Robots" columns. Styling now lives inassets/css/admin.cssunder semantic class names. - Admin styling now follows the WordPress admin color scheme: accents use
var(--wp-admin-theme-color, #2271b1), status boxes and badges use the core admin palette, and neutral grays match wp-admin. The UI adapts to Light / Blue / Midnight / Coffee / Ocean / etc. instead of hardcoded Material-Design colors. - RTL support: layout uses logical CSS properties (
margin-inline-start,border-inline-start) and the toggle switch mirrors under[dir="rtl"]. - Dynamic visibility (override toggles in the meta box and term panel) uses the core
.hiddenclass withclassList.toggle()instead of inlinedisplaymanipulation. assets/css/admin.cssalso enqueues on the admin screens where the plugin renders UI (post list, post editor, term editor), gated by the granular-control flags; the interactive JavaScript remains settings-page-only.- Admin stylesheet cleanup: duplicate
.noindex-seo-view-linkrule block removed; keyframe names prefixed to avoid collisions.
Fixed
- Stale
wp_die()message in the two form handlers: after the 3.1.5 nonce split only the capability path is reachable there, so the message is now "Permission denied." instead of "Permission denied or invalid nonce." (deploy-audit finding I2). Catalan and Spanish translations and the.pottemplate updated;.mofiles recompiled. - Unreachable
function_exists( 'rest_authorization_required_code' )ternaries removed from both REST permission callbacks — the function exists on every supported WordPress version (deploy-audit finding I5).
Security
- No security changes; the full canonical checklist (
AGENTS-security.md), PHPCS security sniffs andcomposer auditremain clean.
Compatibility
- WordPress: 4.7 - 7.2
- PHP: 5.6 - 8.5
Tests
- PHPUnit: 9.6.36 (150 tests, all passing). Coverage maintained above the 80% floor.
Downloads
-
v3.1.5 Stable
released this
2026-11-03 17:01:05 +00:00 | 7 commits to main since this release3.1.5
Release date: 2026-09-18
Highlights
- Maintenance review: composer update, code review, security review and compatibility review (WordPress 4.7 - 7.2, PHP 5.6 - 8.5). Declared WordPress floor corrected to the real tested minimum (4.7). Test suite expanded to 147 tests with 94.78% line coverage, meeting the 80% AGENTS target.
Added
- 76 new PHPUnit tests: front-end output (
noindex_seo_metarobots, all majornoindex_seo_showcontexts, overrides, CPT defaults, transient shortcut), admin surface (settings page, meta boxes, Quick Edit, bulk actions, columns, filters, enqueues, conflict detection, helpers), sitemap per-term exclusion, and uninstall cleanup.
Changed
- Minimum WordPress requirement raised from 4.0 to 4.7 in the plugin header,
readme.txtandphpcs.xml(minimum_supported_wp_version). Version 4.7 is the oldest release in the tested range and the first with the complete REST API, so every advertised feature (including the/wp-json/noindex-seo/v1/endpoints) is available on all supported versions. Newer-API integrations keep degrading gracefully above the floor (wp_robots5.7+, sitemaps 5.5+, block editor 5.0+,register_post_meta, term meta). - Tested up to WordPress 7.2 in
readme.txt. - Removed three now-obsolete
WPCompatPHPStan ignores (rest_api_initaction,WP_REST_Request::get_param()× 2): with the 4.7 floor those APIs always exist, and PHPStan reports unmatched ignores as errors. - Dev dependencies updated via
composer update(phpstan/phpstan2.2.8 → 2.2.14,nikic/php-parser5.8.0 → 5.9.0,php-stubs/wordpress-stubs6.9.4 → 7.1.0,szepeviktor/phpstan-wordpress2.0.3 → 2.0.4,wp-hooks/wordpress-core1.12.0 → 1.13.0). No production code ships these packages. - Coverage regression floor in
bin/preflight.shraised from 25% to 80% now that the suite meets the AGENTS target.
Fixed
- Dead nonce check in
noindex_seo_process_form()andnoindex_seo_process_apply_suggestions():! check_admin_referer()with a specific action can never be true (the function exits on failure instead of returning false), so the||branch was dead code flagged by PHPStan level 9 with the updated WordPress stubs. Both handlers now checkcurrent_user_can( 'manage_options' )first and callcheck_admin_referer()separately, which dies on an invalid nonce. No behavior change for valid requests.
Security
- Full canonical checklist (
AGENTS-security.md) reviewed against the release diff: no findings. Input validation (safelist + strict types), sanitization (sanitize_text_field,absint,sanitize_key), late output escaping, nonces on every state-changing action, capability checks in UI and execution logic,$wpdb->prepare()on all custom SQL, no dangerous functions, RESTpermission_callbacks intact, no secrets in code.composer auditclean. - The nonce-handler fix above is hardening only: the previous code was still safe in practice because
check_admin_referer()dies on failure.
Compatibility
- WordPress: 4.7 - 7.2
- PHP: 5.6 - 8.5
Tests
- PHP Coding Standards: 3.13.6
- WordPress Coding Standards: 3.4.1
- PHPUnit: 9.6.36 (147 tests, 569 assertions — all passing on WordPress 7.1.1 test library; staging site runs WordPress 7.2-alpha, PHP 8.5.10, MariaDB 11.8.9)
- PHPCompatibility 5.6-8.5 scan: clean (declared PHP floor 5.6 confirmed)
- PHPStan level 9: clean;
bin/preflight.sh: full PASS (coverage 94.78%, above the 80% AGENTS target and floor)
Downloads
-
v3.1.3 Stable
released this
2026-08-17 20:04:32 +00:00 | 8 commits to main since this release3.1.3
Release date: 2026-08-17
Highlights
- Compatibility release: WordPress 4.0+ and PHP 5.6+ supported again (declared floors now match the real compatibility of the code), and branding moved to robotstxt.software.
Added
- Classic
<meta name="robots">output onwp_headfor WordPress versions older than 5.7, restoring the pre-wp_robotsfallback so the declared WordPress 4.0 floor is real. On WordPress 5.7+ the directives keep flowing through the corewp_robotsAPI. noindex_seo_get_cpt_label()helper returning a safe display label for custom post types on the settings page.
Changed
- Minimum requirements lowered back to WordPress 4.0 and PHP 5.6 in the plugin header,
readme.txt,composer.jsonandphpcs.xml, verified with a full-range PHPCompatibility 5.6-8.5 scan (clean) and the WP-Compat report. - Plugin URI and Author URI now point to robotstxt.software.
register_setting()calls use the two-argument form: the$argsarray parameter requires WordPress 4.7+, and all sanitization already happens in the admin-post form handler.
Fixed
- Potential fatal errors on older WordPress versions:
is_privacy_policy()(WP 5.2+),is_customize_preview(),get_term_meta()(WP 4.4+),register_post_meta(),register_term_meta(),wp_set_script_translations()(WP 5.0+) andWP_Screen::is_block_editor(WP 5.0+) are now guarded; the features that depend on them degrade gracefully instead of crashing. - Removed PHP 7-only syntax (strict types, scalar type hints, return type declarations, null coalescing operator) so the code parses and runs on PHP 5.6 as declared.
- Restored the repository governance files (
CLAUDE.md,.claude/settings.json) that were accidentally dropped from the repository during the 3.1.2 release cleanup. - Bundled translations (Catalan and Spanish) regenerated against the current source: 9 strings added in 3.0.2–3.1.0 are now translated, 7 fuzzy entries reviewed, 149 messages complete per locale with 0 untranslated and 0 fuzzy.
Security
- No security changes; the 5.6-8.5 PHPCompatibility scan, the dependency audit and the WordPress Coding Standards security sniffs are clean.
Compatibility
- WordPress: 4.0 - 7.1
- PHP: 5.6 - 8.5
Tests
- PHP Coding Standards: 3.13.6
- WordPress Coding Standards: 3.4.1
- PHPUnit: 9.6.36 (71 tests, 385 assertions)
Downloads
-
v3.1.2 Stable
released this
2026-08-10 19:07:46 +00:00 | 9 commits to main since this release3.1.2 [2026-08-10]
Audit-driven maintenance release.
Security
- Fixed the composer-audit gate in
bin/preflight.sh. The previous version grepped for "security vulnerability advisory" (singular), which never matched Composer's actual output "security vulnerability advisories" (plural) — the y→i pluralization change silently disabled CVE detection, green-lighting every release regardless of known vulnerabilities. The gate now uses Composer's bitmask exit code (bit 0 = security), which is immune to wording changes. - Bumped
squizlabs/php_codesnifferto ^3.13.6 andwp-coding-standards/wpcsto ^3.4.1, fixing CVE-2026-67434 (OS command injection) and CVE-2026-45293 (arbitrary code execution) in the development tooling. These are dev-only dependencies and were never shipped in the release ZIP.
Fixed
- Nested
<form>elements on the settings page. The "Apply Recommended Defaults" form was physically nested inside the main settings form — HTML5 forbids this, and the stray</form>could close the main form early, orphaning the "Save Changes" button and all directive checkboxes. The apply-suggestions form is now a standalone sibling rendered before the main form. - Meta-box "Effective Directives" reference panel now reads from the consolidated
noindex_seo_settingsoption vianoindex_seo_get_setting()instead of the stale legacy individual options that may diverge after a settings save.
Added
load_plugin_textdomain('noindex-seo')hooked oninit. The plugin ships.mofiles for Catalan and Spanish (es_ES) inlanguages/, but without this call WordPress only loaded translations fromwp-content/languages/plugins/— the bundled translations were effectively dead code.- PHPUnit coverage measurement in
bin/preflight.sh(requires Xdebug). Enforces a 25% regression floor against the current 26.64% baseline; the AGENTS target remains 80%. <coverage>configuration inphpunit.xmlso--coverage-textproduces a report.README.mdfor developer and contributor onboarding.tests/wp-tests-config.sample.phptemplate. The realtests/wp-tests-config.phpis now gitignored and reads from environment variables.
Changed
- Pinned all remaining wildcard
"*"dev dependencies to caret constraints incomposer.json(phpcsutils^1.2,php-compatibility^9.3,dealerdirect/phpcodesniffer-composer-installer^1.2). Unpinned ranges were how the CVE-affected versions were resolved. - Lowered
phpstan.neonphpVersionfrom 80500 (PHP 8.5) to 80200 (PHP 8.2) so PHPStan flags any accidental use of PHP 8.3+ syntax that would break on the development floor. - Refreshed
CLAUDE.mdto reflect 3.1.x reality (version, line count, v3 consolidated storage model, four-priority output logic, current 8-file test suite). Documented the uninstall direct-DB exception. - Updated
TODO.mdto mark shipped items (#1–#4).
Compatibility
- WordPress: 5.7 - 7.1
- PHP: 7.2 - 8.5
Tests
- 71 tests, 385 assertions — all passing. Coverage measured at 26.64% (471/1768 lines).
Downloads
- Fixed the composer-audit gate in