Brainwerk SEO Suite

Přehled změn

1.9.0 — 2026-08-05

• New — compare your site to its own past („Eigenvergleich“): a daily local snapshot now builds a history of your on-page-analyzer score, meta-description/alt-text/word-count fail rates, traffic shape and AI-crawler activity, and the dashboard gains four new widgets — analyzer trend, traffic shape (hour of day / day of week), AI-crawler development per family, and headline-number deltas — so you can see how your site is trending week over week and month over month. Works from day one, on every install, whether or not you’ve joined the SEO benchmark network, and nothing here ever leaves the site. Shows an honest „still filling up“ message until enough history has built up. This release creates a new database table (wp_seoforge_history) on update, handled automatically.
• Improved — honest benchmark progress instead of a blank card: until enough sites have joined the SEO benchmark network to compare safely, the dashboard now says plainly how many sites currently participate and how many are needed before industry comparisons switch on, instead of a silent „not available“ gap.
• Security hardening: CSV exports (visits, sessions, 404s, redirects, audit log) are now protected against formula/DDE injection when opened in Excel/LibreOffice/Sheets. The outbound-request safety guard (SSRF protection) now also covers the Search Console sync and GEO-database download Pro modules, and pins the resolved IP for the duration of the request to close a DNS-rebinding window. On Multisite, saving settings on a subsite no longer silently freezes that subsite out of future network-wide setting changes; existing installs with a stale full copy are cleaned up automatically on update.
• Adds automated regression tests covering all of the above (259+ tests total).

1.8.2 — 2026-08-05

• Fix — some admin interface texts could show up blank: on sites using Italian, Spanish or French — and even on some English installs — a bug in the plugin’s translation files could cause a number of admin-screen texts to render blank instead of readable text. Untranslated strings now correctly fall back to the English original instead of an empty string. Italian was affected the most (nearly the entire admin UI); Spanish and French lost around 174 strings each; English installs lost around 238. Recommended for everyone, especially non-English sites. No database changes.

1.8.1 — 2026-08-03

• Security — report files now use unguessable filenames: generated SEO reports (weekly/monthly/custom) were previously saved under a predictable filename that could be reached directly by guessing the address on some server configurations. Report filenames now carry a long random token, and any existing report files are renamed to the new scheme automatically the next time an admin visits wp-admin after updating — no action needed. Users are recommended to update.

1.8.0 — 2026-08-01

• New — signature-verified peer benchmarks: the SEO benchmark network now pulls back an Ed25519-signed feed from the hub as well as sending your own snapshot, so the dashboard can show how your bounce rate, session length and on-page-analyzer checks compare with anonymised peers in your industry. The feed is verified against pinned public keys before anything is trusted; it fails closed (silently ignored, never accepted unverified) if it can’t be verified, is out of date, or looks like a replay of an older feed. A new „Pull feed now“ button sits next to the existing push controls under Tools → SEO network.
• New — AI-crawler and bot-traffic visibility: the dashboard gains a „Bot & AI-crawler traffic“ card showing your declared/suspect/cloaked bot mix and crawl-to-referral ratio, plus (once the peer feed is available) a read-time reputation note when traffic claims to be a known AI crawler but doesn’t behave like one. Nothing here is inferred until the peer feed actually supplies it.
• New — richer, still-anonymous benchmark snapshot: the daily aggregate snapshot now also includes on-page-analyzer score distribution and per-check failure rates, an hour-of-day/day-of-week traffic profile, AI-crawler visibility (banded, never an exact count) with crawl-to-referral, your declared-bot mix, and coarse comparability bands (PHP/WordPress version, site size, traffic volume). All of it is counts, percentages and bands — never a single visitor, IP, URL or raw crawler string.
• Improved — stronger anonymity guarantees: days under 50 pageviews (or under 10 Core Web Vitals samples, or under 5 analysed posts for the analyzer figures) now send no metrics for that figure at all, rather than a low-confidence number. Small-sample countries are dropped from the country breakdown. Versions, site size and traffic are only ever sent as coarse bands, never exact values.
• Corrected — consent wording: earlier release notes and onboarding copy described the SEO benchmark network as „off by default.“ That was wrong — it has been on by default since 1.4.0, with a one-click switch-off in onboarding and under Tools → SEO network. The copy now says this plainly; nothing about the actual default has changed, only the description of it.
• Clarified — external-service disclosures: the External services section below now documents the new inbound feed pull and the Multisite inbound-pull relay route, alongside the existing outbound snapshot.
• Fix — the benchmark network now actually works for everyone, not just our own sites. Self-registration with the hub silently failed for every install that never pasted a token by hand, because no default registration token shipped with the plugin — the opt-in looked „on“ but never connected. A rate-limited, publicly-scoped registration token (isolated to the SEO benchmark channel, no access beyond that) now ships with the plugin, and a failed registration is now shown in the admin card instead of failing silently.
• Adds automated regression tests covering all of the above (152 tests total). No database changes.

1.7.1 — 2026-08-01

• Security — Multisite: sites can no longer see or affect each other. On a Multisite network, an administrator of one site could previously view another site’s analytics via the site selector, change settings for the whole network by saving on their own site, and delete other sites‘ records with the „Clean up now“ tool. All three are now correctly limited to the site the administrator actually manages; the network-wide view and network-wide settings remain available to Super Admins as before. Single-site installations were never affected by any of these.
• Privacy — the analytics beacon now honours „Do Not Track“. The server-side tracker already respected the browser’s Do-Not-Track signal; the JavaScript beacon (time on page, scroll depth, Core Web Vitals, outbound clicks) did not. Both now use the same rule, so a visitor sending DNT is not recorded at all.
• Fix — Search Console sync (Pro) works again. The sync silently did nothing because the license key was never passed through; it now runs, and any failure is reported in the admin instead of failing quietly.
• Adds automated regression tests covering all of the above (78 tests total). No database changes.

1.7.0 — 2026-07-30

• Fix — accurate visitor countries behind a proxy or CDN: sites served through a reverse proxy (e.g. nginx) or a CDN like Cloudflare were attributing most or all visits to a single wrong country (the proxy/edge location). The plugin now detects the real client IP from the standard forwarded headers when the request comes through a trusted local proxy, so country stats are correct again. Manual override via SEOFORGE_TRUSTED_PROXIES still works.
• New — the on-page SEO analyzer now explains every check: alongside the score, each check shows what was measured, whether it passed, and a concrete tip to improve it — in the post editor and as an expandable breakdown in the SEO list.
• New — consistent, clear Pro labelling: every Pro-only feature now carries the same „Pro“ badge and a proper upsell card (region & city geolocation, Search Console & Bing sync, traffic-spike alerts, the network-aggregate dashboard and the full audit log), so it’s always obvious what’s included in your plan.
• Fix — region & city drill-down is now correctly Pro-gated: the country → region/city detail was being returned to Free installs; it is now enforced server-side as the Pro feature it is.
• Change — the overview refreshes in place: switching the date range or site scope now updates just the dashboard widgets instead of reloading the whole page (with a graceful fallback if JavaScript is unavailable).
• New — traffic-source tooltips: Direct, Internal, Search, Referral, Social, Campaign and AI answer engines each have a one-line explanation, so it’s clear what every source means.
• Improved — clearer AI answer engines section: a better explanation of AEO/GEO traffic (visits arriving from ChatGPT, Gemini, Copilot, Perplexity, Claude and others).
• Fix — mobile layout: wide tables and stat grids no longer overflow the screen on phones; tables scroll and grids reflow.
• Improved — German translations completed: 113 previously-English admin strings are now translated for German (de_DE) and Austrian German (de_AT).
• Assorted i18n and licensing-consistency hardening. No database changes.

1.6.0 — 2026-07-30

• Security — Multisite data reset is now per-site: the Tools reset actions (visitor stats and 404 log) now clear only the current site’s rows instead of the shared network-wide tables, so a single-site admin can no longer wipe another site’s analytics on a Multisite network.
• Fix — scheduled reports use the correct time window: the automatic weekly/monthly report crons now compute their date range in UTC (matching how visits are stored), so reports on non-UTC servers no longer drift. The monthly report e-mail is now correctly labelled (was mislabelled „weekly“), and report e-mail subjects are unified under the Brainwerk SEO Suite name.
• Hardening — outbound webhooks & settings import: Pro webhook alerts and imported settings now refuse URLs that resolve to internal/loopback/link-local addresses, closing a server-side request forgery (SSRF) vector.
• Hardening — analytics beacon: the public beacon endpoint now also requires a rotating, site-signed token, on top of the existing origin check and per-IP rate limit.
• Fix — race-free 404 logging: concurrent first hits to the same missing URL are now recorded with a single atomic upsert, so no hit is lost.
• Fix — uninstall respects a per-site „keep data“ choice: on Multisite, the shared data is kept if any site opted to keep it.
• Polished report e-mails: dark-mode-aware colour scheme, hidden preview (preheader) text, accessible logo alt text, a document language attribute, and a „Manage e-mail reports“ footer link.
• European positioning: refreshed EU messaging („the European answer — from the EU, for the EU“) and removed third-party product comparisons from the marketing copy.
• Assorted i18n and defense-in-depth cleanups. No database changes.

1.5.0 — 2026-07-29

• New — settings & action audit log: a new Audit Log tab records who changed what and when (settings saved, redirects created/deleted, license/tier changes, the uninstall data-deletion choice, manual data resets, SEO-network opt-in/opt-out) — a short human-readable summary only, never a raw diff of your data, so the privacy footprint stays small. The free build shows your last 5 entries with a Pro upsell; Pro gets full pagination and CSV export. A new Privacy → Audit log retention setting (default 180 days) keeps it tidy automatically.
• Changed — weekly digest e-mail is now consent-first: on a fresh install, the weekly digest no longer looks „on“ while silently sending nothing — it now defaults to off, matching the daily digest, until you explicitly enable e-mail reports (in onboarding or under Tools → E-mail reports). Existing installs are unaffected.
• Changed — network admins can manage Reports: a network admin without their own admin rights on the active site can now open and use the Reports tab, matching how every other admin screen already behaves on Multisite.
• Fix — Reports tab is now fully translatable: the last hardcoded UI strings on the Reports screen now go through the plugin’s translation files, so nothing falls back to English on a translated site (source strings added to all 5 language catalogs).
• Assorted internal hardening and documentation cleanup; see CHANGELOG.md for the full list.

1.4.0 — 2026-07-20

• New — periodic review reminder: a friendly, dismissible admin notice invites you to rate the plugin, starting 14 days after activation. Snooze it for another 14 days, or dismiss it for good — your choice is remembered.
• Changed — SEO network sensor is on by default on fresh installs: the opt-in benchmark sensor (see External services below) now defaults to enabled for new installs, so benchmark data starts building from day one. It still transmits nothing until the site completes registration, and can be turned off any time under Tools → SEO network. Existing installs keep whatever they already had configured.

1.3.1 — 2026-07-06

This is the first wp.org release since 1.2.0; it delivers everything from 1.3.0 to the public build plus one fix.
* New — true PDF export for reports (Pro): on Pro, both the standard report and the Executive (CEO/CTO) report download as real, server-generated PDF files through a bundled PDF engine — no more relying on the browser’s „Save as PDF“. The free build is unchanged: it keeps the printable HTML report you save as PDF from your browser.
* Fix — bundled translations now load: the plugin again registers its own /languages folder (via load_plugin_textdomain() on init), so the shipped German, Spanish and French catalogs are actually used. Previously the admin stayed in English even on a translated site: wp.org’s slug-based auto-loader only scans the global wp-content/languages/plugins/ folder, never the plugin’s own bundled /languages directory — so the catalogs shipped in the plugin were never picked up. Re-registering the folder is the wp.org-supported way to load bundled translations.
* New — Austrian German (de_AT): adds a de_AT catalog so Austrian-German sites are no longer shown in English (they previously got no German at all, because WordPress does not fall back from de_AT to de_DE).
* Fix — Reports tab is reachable again: the Reports screen and its handlers existed but the tab was never registered in the admin tab list, so its menu entry had no link and ?tab=reports silently fell back to the Dashboard. The tab is now wired into the System group.

1.3.0 — 2026-07-04

• New — true PDF export for reports (Pro): on Pro, both the standard report and the Executive (CEO/CTO) report now download as real, server-generated PDF files through a bundled PDF engine — no more relying on the browser’s „Save as PDF“. The Executive report gains a one-click Download as PDF button. The free build is unchanged: it keeps the printable HTML report you save as PDF from your browser.
• Fix — bundled translations now load: the plugin again registers its own /languages folder, so the shipped German, Spanish and French catalogs are actually used. Previously the admin stayed in English even on a translated site because WordPress‘ just-in-time loader only scans the global translations folder. Adds an Austrian German (de_AT) catalog so de_AT sites are no longer shown in English.

1.2.0 — 2026-07-01

• New — settings survive uninstall & reinstall: your configuration is now kept in a private database backup, so if you delete and later reinstall the plugin, all your settings are restored automatically — no reconfiguring. The backup holds only your settings (never visitor data) and is never placed in a public folder. It even survives the „delete all data on uninstall“ option. A new Privacy → Remember settings for reinstall toggle (on by default) lets you turn it off for a complete wipe.

1.1.0 — 2026-07-01

• New — SEO benchmark network (opt-in): contribute one aggregate snapshot per day (counts, percentages and p75 Core Web Vitals only — never a single visitor, IP or URL) and see how your site compares to anonymised peers in your industry. Strictly opt-in and off by default: a clear consent step in onboarding, plus a one-time invitation on the plugin’s own screens. Available on every tier. Manage or disconnect any time under Tools → SEO network. Fully documented under External services.
• New — pull transport for locked-down servers: sites whose PHP cannot make outbound HTTPS can still take part — the hub fetches the daily snapshot from an authenticated, read-only endpoint instead (the site makes no outbound connections).

1.0.1 — 2026-07-01

• Fix: connecting to the optional „SEO network“ sensor could fail with „missing_register_token“ — the registration token, industry and enable toggle were silently dropped when saving settings. These are now persisted correctly, so connecting works.

1.0.0 — 2026-06-30

• Printable reports, no PDF software required: the report generator now produces a self-contained, branded HTML report that any browser saves as PDF. This removes an external PDF library dependency, so reports work on every install — including locked-down servers.
• Reports now include visitor countries: the report gained a „Top countries“ block (flags + share bars) alongside the KPI grid, trend, sources and devices.
• Onboarding: a new „AI search readiness (GEO/AEO)“ step lets you switch on the llms.txt manifest and FAQ schema right from the setup wizard.
• Accessibility: clearer screen-reader labels on the redirect, 404 and visitor-country controls; decorative icons are now correctly hidden from assistive tech.
• Hardening: database schema migrations now run only in the admin context (never triggered by a public front-end request), with a lock against concurrent runs.
• Pro: opt-in „SEO network“ sensor pushes one aggregate snapshot per day to power an agency fleet overview and anonymous peer benchmarks (counts and percentages only — never per-visitor data). Search Console performance (clicks, impressions, position, top queries) now has its own card.

0.9.0 — 2026-06-29

• Generative Engine Optimization (GEO/AEO) — a new toolkit to get your content surfaced and cited by AI answer engines:
  • AI-crawler controls: one-click allow/block for GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, CCBot and more — written straight into robots.txt.
  • llms.txt manifest: optionally publish /llms.txt (+ /llms-full.txt), a Markdown map of your key pages and posts for AI crawlers — generated automatically and cached.
  • FAQ schema: add question/answer pairs per post/page in the editor; output as FAQPage JSON-LD (plus speakable on articles) for rich results and AI answers.
  • AI-engine traffic: visits arriving from ChatGPT, Gemini, Copilot, Perplexity, Claude and other assistants are now classified as their own „AI answer engines“ source, with a dedicated breakdown on the Sources tab.
• Fix: saving settings on the Meta/Schema tab silently did nothing after a slug rename (the form data was read under the wrong key). Settings now save correctly again.

0.8.0 — 2026-06-29

• Visitor geolocation, now in Free: the Visitors tab gets a „Visitor countries“ breakdown with flags and share-of-traffic bars, and recent visits show a country column. Country resolution runs entirely offline from a compact IP→country database bundled inside the plugin (built from DB-IP Lite, CC BY 4.0) — no external requests, so it works on locked-down/firewalled servers too. Covers both IPv4 and IPv6.
• Pro — region & city drill-down: with a Pro license, click any country to expand its top regions and cities, powered by MaxMind’s GeoLite2 City database (read with a bundled, dependency-free reader). Country-level data stays available on Free.
• Schema: visits and sessions gain region + city columns (DB upgrade to v4, applied automatically).
• Demo data: the demo seeder now emits internally-consistent country/region/city so the new geolocation views look populated out of the box.

0.7.7 — 2026-06-24

• Every e-mail now shares the same polished design: the traffic-spike alert, the scheduled report cover e-mails (auto weekly/monthly and re-sends) and the „send test“ e-mail were plain text or a bare one-liner — they now use the same branded HTML shell as the digests (navy gradient header with logo, status-coloured hero band, clean facts table, call-to-action button and the made-in-EU footer). Consistent look across every notification the plugin sends.
• Richer traffic-spike alert: the anomaly alert now leads with a colour-coded hero (amber for a spike, red for an extreme spike) and a tidy breakdown — hour, human pageviews, z-score, rolling baseline and your alert threshold — plus a one-click button into the live dashboard. Slack/Discord/Teams webhook payloads are unchanged.
• Fix — /favicon.ico no longer counted as a page: favicon requests (and any other static asset that gets routed through WordPress) were recorded as visits and could top the „Top pages“ report. They are now excluded from tracking (via is_favicon() plus a static-file-extension guard), so the report only shows real pages.
• Fix — broken in-app links („Sorry, you are not allowed to access this page“): links that pointed to the old admin.php?page=seoforge slug — the onboarding „Start setup“ button, Site Health fixes, the dashboard widget, report/e-mail buttons and others — led to a permission error because the admin page slug is brainwerk-seo-suite. All ~40 links now use the correct slug.

0.7.6 — 2026-06-21

• E-mail reports — graphical daily & weekly digests: the report e-mails are now beautifully designed HTML (brand header, KPI tiles with period-over-period trend arrows, traffic-source bars, top pages, Core Web Vitals ratings, human-vs-bot split) — everything at a glance. New daily digest in addition to the weekly one; configure recipient + cadence and send a test from Tools → E-mail reports.
• Fix — Core Web Vitals, engagement & new-visitor tracking now actually work: these metrics queried database columns that were never created or populated (they silently returned 0 and logged „unknown column“ errors). The schema now includes lcp_ms/cls_x1000/inp_ms/is_engaged/is_new_visitor (DB upgrade to v3, applied automatically), new-visitor detection runs server-side, engagement + Core Web Vitals (LCP/INP/CLS, real field data) are captured via the front-end beacon (beacon/hybrid tracking mode). Verified on a staging install.
• Hardening & cleanup (from an internal audit): Multisite isolation fix so a subsite admin can no longer delete/toggle another site’s redirect by id; removed a dead „link check“ cron that fired into the void; report crons are now cleared on deactivation; minor robustness fixes.
• AI — Mistral AI support (EU-based) + provider choice: AI suggestions can now run on Mistral AI — an EU-based provider, so your content stays in the EU — in addition to Anthropic (Claude). Choose your provider and model in the AI tab; Mistral is the new default for fresh installs. Still bring-your-own-key, encrypted at rest, fully opt-in.
• Pro — Executive report (CEO / CTO): a one-click, print-ready branded report for leadership. Pick an Executive (CEO), Technical (CTO) or Full/Board preset, choose a period, and present it or save it as PDF from the browser. Includes period-over-period deltas, human-vs-bot split, traffic mix, geographic reach, top/entry/exit pages, Core Web Vitals ratings (overall and by device), new-vs-returning audience and a privacy/compliance summary — rendered entirely from your own first-party data, no external service. The Free build shows a preview/upsell.
• Multisite: the analytics tabs (Dashboard, Visitors, Sources, Pages) and the at-a-glance dashboard widget now scope visitor stats per site. A new site selector lets you switch between this site, the entire network (aggregated), or any single subsite; the choice is remembered per user. Previously every subsite admin saw network-wide totals.
• Multisite: the network Dashboard adds a per-site breakdown table (pageviews / unique visitors / sessions per subsite) with a one-click drill-down into each site.
• Fix: SEOFORGE_VERSION was still reporting 0.7.4; it is now back in sync with the plugin header.

0.7.5 — 2026-06-19

• Security/SQL: every plugin-owned table name that was previously interpolated into a query string is now passed through the $wpdb->prepare() %i identifier placeholder (WordPress 6.2+) instead of string interpolation. Conditional WHERE builders and the breakdown/percentile switches were restructured so each $wpdb->prepare() call receives a string literal with placeholders only — no SQL string is built in a variable. The only remaining interpolation is the dynamic post_type IN (...) list, which uses generated %s placeholders bound through prepare() (an IN() list cannot use %i). Requires at least WordPress 6.2.

0.7.4 — 2026-06-14

• Security: removed the last two cases of a column identifier being interpolated into SQL. The breakdown query (Seoforge_Stats::group_count()) and the Core Web Vitals percentile query (Seoforge_Reports::percentile()) now select a separate, fully literal query string per allowed column — the SQL identifier is never taken from a variable. All values continue to be bound through $wpdb->prepare().

0.7.3 — 2026-06-13

• Enqueue: the Reports tab no longer outputs an inline <script>; its quick-range helper moved into the enqueued assets/js/admin.js.
• i18n: the last seoforge text-domain string now uses brainwerk-seo-suite, matching the plugin slug.
• Security: report admin-post handlers sanitize the nonce with sanitize_text_field( wp_unslash() ) and unslash/sanitize all request values; the post meta box sanitizes its submitted array at input.

0.7.2 — 2026-06-10

• Security: table names passed to the internal table-resolver are now validated against the fixed whitelist of plugin tables before being used in SQL.
• Security: the migration coordinator builds its post-type IN (...) list from dynamically generated %s placeholders via $wpdb->prepare() instead of escaping + interpolation.
• Security: internal report/stats helpers validate metric and group-by column names against fixed whitelists before using them as SQL identifiers.

0.7.1 — 2026-06-03

• Security: Schema.org JSON-LD is now emitted with slash-escaping (no JSON_UNESCAPED_SLASHES), so a value containing </script> can no longer break out of the inline application/ld+json block. \/ and \uXXXX remain valid JSON-LD.

0.7.0 — 2026-05-21

• Rebranded to Brainwerk SEO Suite (was: SEOForge). Display name + text-domain + plugin filename updated.
• Security: nonce verification in the post meta box now goes through sanitize_text_field( wp_unslash() ) (pluggable-function hardening).
• Security: $_COOKIE reads in the tracker now go through sanitize_text_field( wp_unslash() ) in addition to the existing hex-filter.
• Security: SVG sparkline attributes in the dashboard widget now use esc_attr() for chart coordinates.
• Security: WP-CLI export --out=<path> is now restricted to a wp-content/uploads/seoforge/ subdirectory (and writes only the basename) so it cannot clobber arbitrary paths.
• wp.org compliance: removed the Pro-only bearer-key path from the REST permission_callback. The Free REST API is admin-cookie/nonce only. Pro external dashboards stay in the separate Premium build.
• wp.org compliance: removed load_plugin_textdomain() — WordPress 4.6+ auto-loads translations for plugins hosted on wp.org by slug.
• wp.org compliance: weekly digest now uses admin_url() instead of a hard-coded /wp-admin/ path.
• Docs: readme now documents the optional Anthropic (Claude) API integration as an == External services == section, with what is sent, when, how to disable, and links to Anthropic’s Terms / Privacy.

0.6.0 — 2026-05-19

• Freemius integration live-wired end-to-end (real product IDs, SDK in freemius/, is_live=true).
• Paid plans Starter (€59/yr, 1 site) and Agency (€199/yr, 25 sites) with auto-generated pricing table.
• New sanity row in the Tools tab reports SDK / opt-in / license state.
• Premium build script (bin/build-premium.sh) for Freemius Deploy.
• Fix: Seoforge_License::is_pro() now uses is_paying() so Pro modules load in both Free and Premium builds with a valid license.
• uninstall.php logic migrated to Freemius after_uninstall hook (per Freemius Deploy guideline).

0.5.0 — 2026-05-10

• CI alignment with the ShieldForge UX (Hero banner, tab groups, action items, iOS toggles, tooltips, dark mode, mobile, sanity card).
• bin/bump-version.{sh,ps1} + bin/build-free.{sh,ps1} + .distignore.
• Pre-launch sanity check (17 checks across versioning, cron, DB, privacy, tracking, sitemap, coexistence, file hygiene, readme, translations).
• i18n: POT + de_DE PO/MO shipped.
• PHPUnit tests for Seoforge_Crypto + Seoforge_Analyzer.

0.4.0 — 2026-05-07

• Migration wizard for Yoast / RankMath / AIOSEO (metadata + redirects).
• JS-beacon tracking mode with scroll depth + outbound clicks.
• Seoforge_Health setup-health score on the Dashboard.
• UX polish for non-technical site owners.

0.3.0 — 2026-05-07

• Pre-aggregated daily table for O(1) dashboard queries.
• Transient caches with auto-flush on mutations.
• License-key encryption at rest (AES-256-CBC).
• Streamed CSV exports (visits, sessions, 404, redirects).
• Bulk redirect import from CSV.
• WP-CLI commands (wp brainwerk-seo-suite ...).
• Demo seeder + live-visitors widget.
• REST API (/wp-json/seoforge/v1/...).

0.2.0 — 2026-05-07

• Coexistence layer detects Yoast / RankMath / AIOSEO / The SEO Framework / SEOPress and stands down passively.
• License + Pro module foundation.
• Pro stubs: Geo-Lookup, webhooks, anomaly detection, Search Console.
• Marketing landing page (landing/index.html).

0.1.0 — 2026-05-07

• Initial release: tracker, sessions, stats, meta, schema, sitemap, robots, redirects, 404 log, on-page analyzer, weekly digest, onboarding wizard, tools tab.