• 3.6.0 3cf187303e

    v3.6.0 Stable

    javier released this 2026-11-04 13:42:22 +00:00 | 1 commits to main since this release

    3.6.0

    Release date: 2026-11-03

    Highlights

    • Modern robots directives (TODO #5): notranslate, max-snippet, max-image-preview, max-video-preview and unavailable_after join 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 /effective endpoint and WP-CLI (name=value tokens).
    • Conditional auto-noindex rules (TODO #11): apply noindex automatically 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 +0000 in 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_meta with 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), and list reports the configured value (max-snippet:-1) or off.
    • notranslate as 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 as source: auto_rule in /effective and are excluded from the pages sitemap. The rules read plain post meta, so no ACF installation is required.
    • A notranslate SVG directive icon, plus badge support for value directives in the Robots columns (max-snippet:-1 tokens).

    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. The wp_robots integration 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/unset default (no directive arguments) now enables/disables the six boolean directives; value directives always require explicit name=value tokens (a value on a boolean, or an invalid/missing value, is rejected with a descriptive error). Datetime values need quoting or a T separator 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 through sanitize_text_field(); sitemap rule clauses use WP_Query's meta_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