Image SEO – AI-Driven Image SEO Optimizer

Changelog

3.2.16 – 25.08.2026

• Fix: image generation silently skipped every image on sites where a CDN or performance plugin appends a cache-busting query string (e.g. photo.webp?ver=123) to attachment URLs — the file extension is now derived from the URL path only. This affected automatic alt text on upload AND the manual Optimize button.
• The on-upload extension rejection now logs a line to the PHP error log instead of failing silently.

3.2.15 – 18.08.2026

• Fix: the “Visit website” link in the settings screen pointed at a domain that no longer exists; it now opens imageseo.io.

3.2.14 – 14.08.2026

• Improvement: the “update available” notice now appears on every admin screen, not only the ImageSEO pages, so a pending update is not missed.
• Fix: the plugin reported its own version as 3.2.12 while running 3.2.13, which made version checks and support diagnostics show the wrong version.

3.2.13 – 14.08.2026

• Fix: a bulk optimization that could no longer resume no longer reports itself as a stuck run forever. A run left marked “running” by an interrupted or very old optimization now clears itself, instead of repeatedly reporting a stall that no longer exists. Genuinely stalled runs are still detected and reported as before.

3.2.12 – 14.08.2026

• Fix: an uploaded image could be sent for optimization twice, consuming two credits for one upload. This happened for large images (whose thumbnails are generated in a second pass) and will be the default for every upload under WordPress 7.1’s client-side media processing. Uploads are now processed once.
• Compatibility: tested with WordPress 7.1, including its client-side media processing and iframed post editor.
• Fix: the post edit screen no longer emits a PHP warning on sites that never configured social media post types.

3.2.11 – 13.07.2026

• Reliability: a stalled bulk optimization is now detected and reported on any wp-admin page load (previously only when you reopened the ImageSEO screen), so a stuck run on a locked-down or dead-cron host surfaces instead of failing silently.
• New: a Health tab with at-a-glance install diagnostics (API connection, plugin version, recent activity).
• New: an in-plugin banner prompts you to update when a newer version is available, and update hints are added to error messages.
• Fix: a few default settings could be missed on a brand-new install until the first save, due to a key-conversion bug in three more places (same class as the 3.2.10 fix).

3.2.10 – 10.07.2026

• Fix: the API key was stored under two different option names read by different features, so long-lived installs could end up with working credits/validation but failing generation (or vice versa). All features now fall back to the other stored key, and a request that succeeds with the alternate key re-saves it under both names (self-healing).
• Fix: saving any setting could silently corrupt other stored options (including the API key) due to a key-conversion bug in the settings save path. Saves no longer drop the original option names.
• Improvement: alt-text generation errors in the editor and media library now explain what actually went wrong (e.g. an unsupported file type such as SVG/GIF, the exact API error, or “your server could not reach the ImageSEO API”) instead of the unhelpful “ImageSEO Error: error”.
• Fix: the filename-optimization error path returned a boolean instead of the failure details.

3.2.9 – 05.07.2026

• Fix: an empty batch (all images filtered/unsupported) now advances instead of leaving the run stuck at ‘running’.
• Fix: batch re-checks are capped (~10 min) so a batch that never resolves can’t loop forever.
• Fix: a run stuck with no progress for >15 min is treated as stale and can be restarted (dead WP-Cron recovery).
• New: the plugin now pings the API when it detects a stuck run, so support can spot dead-cron stalls.

3.2.8 – 05.07.2026

• Fix: bulk optimizer no longer wedges at “Batch ID not found” when the API returns a 2xx response without a usable batch ID. The run now stops cleanly with a clear error and can be restarted.

3.2.7 – 12.06.2026

Fixed: Bulk optimization no longer stalls when the API returns an error; the real error is surfaced and the run stops cleanly instead of failing with a “Batch ID not found” message
Fixed: Images with uppercase file extensions (e.g. .JPG, .PNG) are now optimized correctly instead of being skipped, which previously could leave a bulk run stuck
Fixed: Clicking “Optimize” (or “Try again”) while a bulk run is already in progress no longer restarts it from the beginning and re-charges credits for already-optimized images

3.2.6 – 05.06.2026

Fixed: Bulk optimization no longer shows a false “limit reached” message when the API is temporarily unreachable; the real error is surfaced instead

3.2.5 – 20.05.2026

Changed: Marked compatibility with WordPress 7.0

3.2.2 – 09.12.2025

Fixed: Issue preventing settings to be displayed

3.2.1 – 18.03.2025

Fixed: Issue with optimization on image upload and gutenberg editor

3.2.0 – 31.01.2025

Added: Gutenberg functionality

3.1.4 – 29.11.2024

Fixed: Bug with alt text

3.1.3 – 22.11.2024

Added: Support for WebP images

3.1.2 – 19.07.2024

Added: Optimize image title
Added: Optimize image caption
Changed: UI Changes and wording
Fixed: Vulnerability issue

3.1.1 – 8.07.2024

Added: Filter to know when api key is validated

3.1.0 – 14.03.2024

Changed: Refactored code to integrate new API
Changed: Updated UI for better user experience ( still needs improvements )

3.0.2 – 28.02.2024

Fixed: File Path update

3.0.1 – 14.02.2024

Changed: Code cleaning

You can read the complete changelog here