McCrossenSEO

Өзгөртүүлөр

3.1.2

• New: mccm_seo_analytics_consent filter for cookie-consent integrations. When an integration answers false, the Google Analytics 4 script is not requested; a small listener loads it once the visitor grants analytics consent, signalled by a mccm-consent document event whose detail.analytics is true. With no consent integration present, GA4 loads exactly as before. Google Tag Manager and Meta Pixel output are unchanged.
• Change: no robots meta tag is emitted while “Discourage search engines from indexing this site” is enabled, so the site-wide noindex set by WordPress is never contradicted.
• Change: automatic error reports are sent only from sites connected to the McCrossen platform. Unconnected installs make no requests unless an administrator clicks Send Diagnostic Report.
• New: deleting the plugin now removes its credentials, sync state, caches, scheduled tasks and the 404 log; settings, SEO fields, redirects, apply history, media log and robots.txt are kept.

3.1.1

• Fixed: FAQ Schema builder was non-functional — the Add Question control did nothing and FAQ pairs could not be entered. The builder’s script now initialises on post and product edit screens.
• Change: the review request now links to the plain reviews page with no pre-filled rating.
• Compatibility: tested up to WordPress 7.1.

3.1.0

• New: WooCommerce product image optimization — an “Optimize with McCrossenSEO” button on the product edit screen renames the featured and gallery images to an SEO slug built from the product title (template-based, default {sitename}-{title}) and converts them to WebP (default, quality 82), AVIF (where the server supports it), or keeps the original format. The rename covers the original file and every generated thumbnail size, rewrites the attachment metadata, and never changes the attachment ID or URL history. The ideal moment to run it is before first publish, when a freshly uploaded image has no external references.
• New: WooCommerce tab in the McCrossenSEO admin housing the image-optimization settings plus the existing out-of-stock sitemap/noindex toggles (moved from the Settings tab).
• New: Media log — a third panel on the Redirects page recording every image rename (original name, new name, conversion, product, source, date) with per-row Rollback. Rollback restores the original file names and metadata and reverses any auto-created redirects.
• New: published-product safety — renaming images on a published product warns first and requires confirmation, then automatically registers 301 redirects from every old file name (original + each size) to its new name. Images used by other posts or products are never renamed silently: choose duplicate-then-rename or skip.
• New: CSV import integration — images downloaded by the WooCommerce product CSV importer are optimized in the background (one job per product, via Action Scheduler). Only newly downloaded images are touched; re-imports never rename images that already existed, and WooCommerce’s image de-duplication meta is preserved so re-imports don’t re-download files.
• New: optional “delete original after conversion” toggle (default OFF). When enabled, the source JPG/PNG files are removed after a successful conversion and the Media log marks the entry redirect-only.
• Change: admin icon glyphs are now rendered from SVG assets bundled with the plugin (Twemoji, CC-BY 4.0) instead of raw emoji characters that WordPress rewrites to images loaded from an external CDN. Plugin admin pages no longer trigger any external asset requests.

3.0.17

• Internal: moved the review-request admin script to an enqueued asset (coding-standards housekeeping). No functional or user-facing changes.

3.0.16

• New: archive SEO rendering — meta titles and descriptions now render on the WooCommerce shop page (read from the shop page’s own SEO fields) and on category, tag, and taxonomy term archives. Previously they only rendered on single posts and pages, so values stored for archives were never output.
• New: term-level SEO — SEO Title and SEO Description fields on the add/edit screens of every public taxonomy, plus WooCommerce product attribute taxonomies. Stored in term meta; the archive pages render them.
• New: Yoast taxonomy term import — the importer now migrates Yoast’s term titles and descriptions. Template variables convert the same way as the post importer; values that can’t be converted are flagged “needs review” and never imported raw. Term imports appear in Apply History and can be rolled back for 30 days, like post imports.
• New: virtual robots.txt ownership — when no physical robots.txt exists, the editor saves a managed ruleset that McCrossenSEO serves through WordPress. A physical file, when present, always bypasses WordPress and wins; the editor says so instead of pretending otherwise.
• Bug fix: “Create Physical File” now seeds the new file from the live virtual robots.txt output — including rules added by other plugins such as WooCommerce — instead of a generic template, and no longer inserts the obsolete wp-includes disallow line.
• Bug fix: when WordPress core or WooCommerce has already marked a page noindex (cart, my account), the plugin no longer emits its own “index, follow” robots tag alongside it. The more restrictive directive now holds structurally instead of by browser-side precedence.
• Bug fix: bare ampersands in meta titles are now emitted as the proper HTML entity; existing entities are left untouched.
• Bug fix: sitemap hygiene — post types with zero published items no longer appear in the sitemap index, WPBakery internal post types are excluded, and sitemap URLs are served directly without a trailing-slash redirect hop.
• Change: titles and descriptions are no longer texturized on output. Product titles like “5.56×45” or a 16-inch measurement written with a straight quote emit exactly as stored instead of being converted to typographic characters. Stored values were never modified — this only changes the rendered output.

3.0.15

• Improvement: the SEO data importer now converts Yoast template variables instead of copying them verbatim. %%title%% and %%sitename%% become their McCrossenSEO equivalents ({title}, {sitename}), %%sep%% becomes the literal separator character configured in Yoast, and %%page%% is dropped (Yoast renders it empty outside paginated views). Literal text — like a brand name written out in the template — always passes through unchanged. Previously these templates were imported as-is, which would have put raw %% text in your page titles.
• Safety: any Yoast value containing a template variable the importer can’t convert is flagged “needs review” and left un-imported — never silently stripped or imported raw. The preview and the final summary both show the needs-review count and affected post IDs.
• New: every field written by the importer is now recorded in Apply History, so individual imported values can be rolled back for 30 days from the History tab. This applies to imports from all four supported plugins (Yoast, RankMath, AIOSEO, SEOPress).

3.0.14

• Bug fix: the redirect manager now rejects redirects that would create a loop — a URL pointing to itself, or a chain that cycles back (A->B->A). Previously these could be saved and would send visitors into an endless redirect. A safeguard at serve time also breaks any self-redirect from rules created in earlier versions.
• Bug fix: editing an existing redirect no longer silently re-enables it. Previously, changing any field (such as the note) on a disabled redirect forced it back to active. Disabled redirects now stay disabled, and you can also create a redirect in the disabled state.
• Improvement: saving on the Settings and Tracking & Verification tabs now shows a “Settings saved” confirmation. Your settings were always saved correctly; this adds the visible confirmation that was missing.
• Accessibility: the Local Business address fields (street, city, state, ZIP, country) now have proper accessible labels for screen readers.

3.0.13

• Compatibility: bumped Tested up to to WordPress 7.0 (released May 20, 2026). No code changes — all features verified to work unchanged on WP 7.0. The Plugin Bridge, 404 Monitor, redirect manager, sitemap generator, schema output, and tracking pixel injection were all sanity-checked against 7.0’s new admin UI and the WP AI Client API surface (which the plugin does not consume).
• Internal: trimmed the 3.0.11 upgrade notice for WordPress.org compliance (the upgrade-notice line is shown on the Plugins update screen and must stay short).

3.0.12

• New: 404 Monitor now suggests redirect targets by matching broken URLs against your published pages and posts. Up to three suggestions per broken URL with one-click redirect creation directly from the suggestions.
• New: Optional WordPress.org review prompt appears after the plugin has been installed for three weeks. Easy to dismiss permanently, snooze for fourteen days, or open the reviews page.
• Internal: top-3 suggestions are stored as a compact JSON list in the existing suggested_url column (no schema change). Legacy single-URL values from earlier versions continue to render as a single button and are rewritten to JSON the next time the suggester runs.
• Internal: added MCCM_SEO_Review_Nudge class. The install-age clock starts on first activation; existing installs upgrading to 3.0.12 receive a fresh 21-day countdown rather than seeing the prompt immediately.

3.0.11

• Bug fix: the McCrossenSEO™ meta box now renders in its canonical position below the content on the post editor for all post types. On some sites it had been appearing in the sidebar due to leftover state from an earlier preview version — that position is now restored automatically.
• All SEO features and platform-connected features (where enabled) continue to work exactly as before; no settings or workflows changed.
• Removed an unused internal background process that was logging PHP debug warnings on sites running with WP_DEBUG enabled. If you saw those warnings in your error log, they will stop after this update.
• Cleanup runs automatically on update: a leftover scheduled task and cached options from the removed layer are cleared with no action required.
• Internal: the McCrossen_SDK and McCrossen_CrossSell classes were removed (neither was wired to any user-facing code path). The 15-minute heartbeat (MCCM_SEO_Heartbeat) is unaffected and remains the sole platform sync channel for connected installs. Connection state is read directly from the stored API key. The sdk_version field was dropped from heartbeat and diagnostic payloads (it was always reporting the 'unknown' fallback). All other payload fields are unchanged.

3.0.10

• Plugin Check: added missing Squiz.PHP.DiscouragedFunctions.Discouraged to the existing phpcs:ignore annotation on class-mccm-seo-admin.php:727 (@set_time_limit( 60 ) in ajax_404_purge_noise). The WordPress.PHP.* rules were already covered; the Squiz-flavor rule was missed when alpha.40 originally annotated this line. The sibling call at line 876 (rollback batch) already had the Squiz rule covered, which is why Plugin Check flagged only one of them. Plugin Check now returns zero ERRORs / zero WARNINGs.

3.0.9

• Hotfix: 3.0.8 contained a parse error in includes/helpers.php introduced when adding the new mccm_seo_custom_head_allowed_html() and mccm_seo_sanitize_custom_head() helpers — the existing if ( ! function_exists( 'mccm_seo_show_in_dev' ) ) : opener was inadvertently removed, leaving a stranded endif; and a fatal syntax error, unexpected token "endif". Restored the opener. Plugin now activates cleanly on a debug-enabled WordPress install. Verified via php -l across all PHP files.

3.0.8

• Bug fix: button labels in the Elementor preview-draft meta box (“Replacing…”, “Replaced ✓”, “Discarding…”, “Discarded ✓”) were displaying their literal escape sequences (e.g. Replacing\u2026) because PHP single-quoted strings do not interpret \u escapes. Replaced with the actual UTF-8 characters.

3.0.7

• WordPress.org review round 2 fixes:
• Replaced broken Google Tag Manager terms URL in readme.txt (marketingplatform.google.com/about/analytics/tag-manager-terms/ → www.google.com/analytics/terms/tag-manager/).
• Removed inline <script> block from the Connect tab; the manual-setup toggle handler is now in the already-enqueued mccm-seo-admin.js.
• Removed inline <script> block from the Replace-Original meta box on Elementor preview drafts; logic moved to a new mccm-seo-preview-draft.js enqueued via admin_enqueue_scripts only on screens that render that meta box.
• Replaced direct ABSPATH references in class-mccm-seo-llms.php and class-mccm-seo-robots.php with get_home_path() so site root path is computed via a WordPress function.
• Replaced direct WP_PLUGIN_DIR reference in class-mccm-seo-migrator.php with a path derived from the plugin’s own location (MCCM_SEO_DIR).
• Replaced raw is_writable() probe in class-mccm-seo-robots.php with the WP_Filesystem API.
• Custom <head> code option (mccm_seo_custom_head) is now escape-on-output via wp_kses with a head-content allowlist, matching the same allowlist applied at save time. Removes reliance on save-time-only sanitization.
• Removed JSON_UNESCAPED_SLASHES flag from JSON-LD output in class-mccm-seo-schema.php. JSON_HEX_TAG is preserved as the security-relevant flag.

3.0.0-alpha.1

• Plugin slug renamed from mccrossen-seo to mccrossenseo to match the McCrossenSEO™ trademark form. Existing installs migrate automatically on activation.
• WordPress.org compliance pass: removed dead watchdog references, removed deprecated Google/Bing sitemap pings (deprecated 2023), fixed sanitization gaps in nonce and content readers, hardened REST endpoint permission_callbacks (action-plan, webpage-draft) so authentication runs in the permission_callback rather than the handler, added JSON_HEX_TAG to JSON-LD output, removed the dead MCCM_PLATFORM_VERSION conditional in the tracking tab.
• Inline <script> and <style> blocks across admin views converted to enqueued assets per WP.org guidelines. Affected pages: Pending Optimizations, Redirects + 404 Monitor, Import, robots.txt editor.
• Frontend tracking pixel injection (GA4, GTM, Facebook Pixel) now uses wp_print_script_tag() and wp_print_inline_script_tag() per WordPress 5.7+ guidelines.
• External Services section in this readme rewritten to accurately disclose all conditionally-loaded third-party scripts.
• Cross-sell module’s inline JS converted to use wp_print_inline_script_tag().
• Diagnostics file-scope filter updated to recognize the renamed plugin folder.

2.1.7

• WordPress.org submission release
• License updated to GPL-2.0-or-later
• Added comprehensive readme.txt with external services documentation
• Added sanitize callbacks to all register_setting calls
• Code compliance review for WordPress.org guidelines

2.1.6

• SDK stale update fix

2.1.5

• Plugin Bridge one-click apply for meta, headings, alt text, and schema
• Bulk editor with post type filtering

2.1.4

• LLMs.txt generator
• Internal link suggestions
• Redirect manager