Blacklight SEO Suite — v1.0.6 Release Notes

By /

Blacklight SEO Suite — v1.0.6 Release Notes

 

This update focuses on bug fixes identified during the initial soft launch. No new features — just things that needed tightening up.

Purchase Flow

  • Claim page was incorrectly set to draft, causing 404 errors for customers after purchase. Now published.
  • Stripe webhook was assigning the wrong plan to new licenses due to incorrect metadata lookup. Fixed to read plan_slug from the product metadata correctly.
  • Plugin ZIP download link added to the claim page after successful license activation.

Echoverse

  • Rebuild Index Now button was doing nothing on a fresh install. Now correctly indexes all published posts and pages before running the TF-IDF calculation.

Pulse

  • Beacon was sending pings via POST but the REST endpoint was registered as GET only. Fixed.
  • blPulseConfig was not being output on the frontend, causing the beacon to exit silently without firing. Fixed.
  • Beacon JS was reading window.blPulseConfig instead of blPulseConfig, causing it to fail inside the IIFE scope. Fixed.
  • Run Pulse Now button was redirecting to Settings instead of running Pulse. Fixed.
  • Pulse cron changed from daily to hourly for more responsive dashboard updates.

Dashboard

  • Stale content recommendations were incorrectly flagging brand new posts as stale. Threshold corrected to 180 days using post_modified_gmt.
  • Stale count in dashboard banner was inconsistent with the recommendations page. Now uses the same logic.
  • Freshness tile now shows separate counts for Posts and Pages.
  • Anomalies tile was showing “Anomalies Detected” even when count was zero. Fixed.
  • Anomalies count in dashboard tile was inconsistent with the Anomalies tab. Now reads from the same data source.
  • Top Posts by Real Visitors tile was not displaying data despite real visitor data existing. Fixed.
  • Run Scan Now in Anomalies tab was returning a permissions error. Fixed.
  • Run Scan Now redirect now correctly returns to the Anomalies tab instead of the Lightcrawl tab.

MetaMaster

  • Canonical URL field was rejecting relative paths due to type="url" HTML5 validation. Changed to type="text".

i18n

  • Emoji and unicode symbols were incorrectly wrapped in translation functions during the i18n pass, causing corrupt characters to appear in the post list and SEO tooltips. Fixed across all affected files.
  • Mojibake sequences (窶・, 窶銑, 笨・) cleaned up across dashboard, diagnostics, MetaMaster and Lightcrawl files.
  • All affected files re-saved as UTF-8 without BOM.
Scroll to Top