AzEvent SEO Content Creator WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA

Create and rewrite SEO content through reviewable AI workflows, background jobs, GEO prompts, image generation and Rank Math metadata.

Description

AzEvent SEO Content Creator provides Content Studio, SEO Workflow Lab and a checkpoint-based Background Queue. Generated content is always saved as a draft for human review.

Highlights:

• Create-new and existing-post rewrite workflows.
• Mandatory old/new comparison before SEO for rewrites.
• Optional second-pass outline validation.
• Quality Gate with a configurable minimum score and administrator-only override reason.
• Pause, resume, cancel, retry backoff, retention and worker health for batch jobs.
• Authenticated Server CRON trigger with WP-Cron and loopback fallback.
• Explicit HTML sanitization before AI-generated content is stored.
• Server-side constants supported for API secrets.

Installation

1. Upload the plugin directory to /wp-content/plugins/ or install the release ZIP.
2. Activate the plugin.
3. Open AzEvent SEO > Settings and configure the required provider.
4. Open Background Queue and copy the recommended Server CRON command into the server crontab.
5. Keep WordPress Cron and loopback requests working as fallback mechanisms.

Frequently Asked Questions

Does the plugin publish automatically?

No. Final content is saved as a WordPress draft and must be reviewed before publishing.

What happens to data when the plugin is removed?

Deactivation clears scheduled workers and transient locks but preserves settings, drafts, media and queue history. The plugin intentionally does not delete editorial data automatically on uninstall. Completed, cancelled and failed queue rows are cleaned according to the configured retention period while the plugin is active.

Can API keys be stored outside the database?

Yes. Define the relevant constant in wp-config.php: AZEVENT_CLIAPI_API_KEY, AZEVENT_REMOTE_API_KEY, AZEVENT_LOCAL_API_KEY, AZEVENT_CKEY_API_KEY, AZEVENT_DEEPSEEK_API_KEY, AZEVENT_OPENAI_API_KEY, AZEVENT_ANTHROPIC_API_KEY, AZEVENT_SERPAPI_KEY, or AZEVENT_SEO_CRON_KEY.

Changelog

1.8.4

• Add a key-authenticated Server CRON REST endpoint for reliable Queue wake-ups.
• Keep sequential checkpoint processing, the global worker lock, WP-Cron and loopback fallback.
• Add Server CRON health, stale warnings, copyable crontab command and administrator-only key rotation.
• Keep Rewrite review checkpoints and Workflow Lab human approval unchanged.

1.8.3

• Add a direct DeepSeek text provider using the official Chat Completions API.
• Add secure API key storage, wp-config.php constant support and a connection test.
• Add DeepSeek V4 Flash and V4 Pro to per-step model routing.
• Keep AzEvent API as the default provider for existing websites.

1.8.2

• Open active Content Studio jobs directly inside the Background Queue modal.
• Stop sending Rewrite resume actions through the WordPress Edit Post screen.
• Preserve the selected Rewrite checkpoint through its queue job ID.

1.8.1

• Remove the BDDevLab Text API provider, client, settings card and model routing.
• Migrate websites using BDDevLab back to the default AzEvent text provider.
• Delete saved BDDevLab credentials and obsolete per-step model references during upgrade.

1.8.0

• Modernize Content Studio, Workflow Lab and Queue with a shared professional design foundation.
• Add searchable existing-post selection to standalone Rewrite workflows.
• Add section-level old/new comparison in both Content Studio and Workflow Lab.
• Require signed human approval before Rewrite can continue to SEO or Finalize.
• Preserve the full original article snapshot, create a WordPress revision and record a Rewrite audit trail.
• Stop finalization when the source article changed after the Rewrite session started.

1.7.49

• Harden Background Queue control, retry, pagination, retention and health reporting.
• Enforce Workflow Lab Quality Gate with audited administrator overrides.
• Sanitize generated HTML in Content Studio and Workflow Lab.
• Stop rendering stored API secrets into settings HTML.
• Add compatibility metadata and hardening regression coverage.