Acez SEO AI

Changelog

0.9.9.36

• Every settings screen now verifies the form nonce in its own save handler,
  instead of relying only on the shared dispatcher that calls it.
• Table names in the AIOSEO import and conflict detection are passed through
  $wpdb->prepare()’s %i identifier placeholder rather than being interpolated
  into the query string.
• Structured data is printed through WordPress’s own inline script tag API
  (wp_print_inline_script_tag). The JSON-LD output itself is unchanged.

0.9.9.35

• Form input is now sanitized with core WordPress functions at the point it is
  read, before the plugin’s own template sanitizers run. Percent signs in
  %variable% tokens and percent-encoded URLs are still kept intact.
• Custom schema JSON is sanitized after decoding: HTML tags are removed from
  every value and property name.
• Fixed: sitemap URL exclusions did not work for percent-encoded (non-Latin)
  slugs. Exclusion rules now match regardless of letter case in the encoding
  and also accept the plain, decoded characters.
• Fixed: uninstalling the plugin now also removes the sitemap, onboarding, AI
  bot and AI usage/log settings, and the dismissed-notice state.

0.9.9.34

• Added “Generate with AI” buttons to the llms.txt tab (title, description,
  introduction and footer).

0.9.9.33

• Removed the Custom Code tab (header/body/footer snippet injection), following
  the WordPress.org plugin review — arbitrary code insertion is not allowed in
  plugins hosted in the directory.
• Added site ownership verification fields for Google Search Console, Bing
  Webmaster Tools, Yandex, Pinterest, Baidu and Meta/Facebook to the
  Integrations tab. These cover the legitimate reason most people reached for
  header snippets: pasting a verification meta tag. Each field is validated and
  sanitized, and outputs a single <meta> tag.
• Verification codes entered in the admin are now sanitized at the point the
  form is read, not only when they are stored.

0.9.9.32

Collective entry covering the main changes since 0.9.5, most of them made in
response to the WordPress.org plugin review.

• No feature in the free plugin is gated behind a licence any more. Per-language
  Organization overrides, schema property overrides for a forced node, the
  form-based node builder, and AI translation of meta fields moved to the Pro
  add-on; the llms.txt footer, publication dates and caching, plus AI alt text
  from image analysis, are now permanently free.
• Source strings are English. Polish and Spanish translations are served from
  translate.wordpress.org instead of being bundled with the plugin.
• Removed the anthropic-ai/sdk Composer dependency — all four AI providers now
  talk to their APIs through the WordPress HTTP API. The plugin ships with no
  production dependencies at all.
• Security: AI provider API keys are encrypted with a key derived from
  wp_salt(‘auth’), unique per install; the older key derivation and its
  hard-coded fallback have been removed.
• Security: JSON-LD output is escaped with JSON_HEX_TAG against </script>
  breakout, and user-authored schema nodes now pass through a recursive
  sanitizer after decoding.
• Google Tag Manager and Hotjar snippets are emitted through the WordPress
  script enqueue API instead of raw <script> tags.
• Manual override of the main schema node type per post, AI generation of full
  article content, automatic connection test for the active AI provider, and a
  declared search intent used as AI context.
• Fixed the Hotjar terms and privacy links under “External services” (Hotjar is
  now part of Contentsquare).

0.9.5

• Internal: added a generic AiGenerationService::generate_for_filtered_field()
  entry point for AI fields whose context isn’t a post (used by the Pro
  addon’s new AI redirect-target suggestions) — no user-facing change in
  the free plugin.

0.9.4

• Added “Generuj przez AI” for the focus keyword field (“Fraza kluczowa”),
  in both the Classic meta box and the Gutenberg sidebar — free feature,
  same as the existing title/description generation.

0.9.3

• AI Providers: fixed a bug where a configured-and-tested provider that
  wasn’t (yet) set as the “Aktywny dostawca” disappeared from the tab on
  the next visit, looking like the save had silently failed — a provider
  card now stays visible whenever it has a saved API key, not only when
  it’s the active one.
• Fixed two related markup bugs: a duplicate id=”model” shared by all three
  provider cards, and a duplicate class=”” attribute on the provider “Zapisz”
  button that silently dropped its custom class.

0.9.2

• AI Providers: after a successful “Testuj połączenie” test, the provider
  card now shows up to 10 of the provider’s most recent models to pick from
  — selecting one fills the “Model” field, so both the API key and the
  chosen model are saved together on “Zapisz”.

0.9.1

• AI Providers: added a “Rozłącz i usuń klucz API” (Disconnect & delete API key)
  button per provider card, so a connected provider’s key, model and tested
  status can be fully erased from the database, with a confirmation prompt.

0.8.7

• Current feature set as of this release: Schema.org/meta engine, Location
  Rules, AI generation on your own key, robots.txt/llms.txt editors,
  multilingual support, SEO-data importers, ACF integration, and the optional
  Pro add-on.