Changelog

Intro

This page contains public release notes for ScriZen SEO Page Auditor.

We use the changelog to document meaningful product changes, including new functionality, improvements, fixes, and known issues that may affect your workflow.

How to read this page

Each release entry may include the following sections:

  • New
  • Improved
  • Fixed
  • Known Issues
  • Upgrade Notes

Not every release will include all sections. Minor maintenance builds may only include a short summary.

Current status

The Windows version is the current public platform. The macOS version is in development and will be announced separately when public testing or release begins.

Release history notice


If no public version history is listed below yet, it means the first public changelog entry has not been published on this page. Once public builds are released, this page will be updated with version numbers and release notes in chronological order.

Version: 1.0.0
Release date: October 19, 2026
Known Issues:

Version: 1.1.0
Release date: October 23, 2026
IMPROVEMENTS & FIXES
• Live results view: fixed white bands and lost scrolling; stable across repeated searches.
• Single instance: relaunching the app now activates the running window.
• Fixed a crash when the Store-installed app checked for updates.
• Default search locations updated: added Brasil (Porto Alegre) and India (Delhi).
• Page Audit Text / Content Audit Text: link anchors now show their URL in a hover tooltip.
• Taskbar icon stability fix; spinner and white-flash fixes in Semantic Analysis and Visual Analytics.
• Embedded browser engine updated to Chromium 156.
• Linguistic models: Spanish, Italian, and Polish now use rule-based analysis (replaced non-redistributable model packages); Third-Party Notices updated.
• Security and dependency updates.

Known issues policy

We publish known issues when they may materially affect installation, activation, stability, or expected behavior. The goal is to set accurate expectations, not to hide rough edges.

Bug reporting

If you believe you found a bug, please contact the Support Desk and include:

  • the application version
  • your Windows version
  • the steps to reproduce the issue
  • screenshots or logs if available

Supporting links: