Blue Editoria : Content workflow helps WordPress teams analyze existing content, prepare SEO and GEO-friendly content workflows, manage internal linking, edit content faster, and automate editorial tasks from a guided WordPress admin interface.
The plugin is designed for site owners, agencies, editors and SEO teams who need a simple workflow without turning WordPress into a complex page builder. It guides the user through setup, content scanning, analyzed content review, spreadsheet-style editing, internal linking, content campaigns, metadata suggestions, schema preparation, and AI-assisted content generation.
Blue Editoria : Content workflow uses WordPress post types, fields, taxonomies and content APIs. It does not create new fields automatically and does not replace your theme. The plugin is meant to help you analyze, organize and improve content while keeping control inside WordPress.
Some features connect to the Blue Editoria : Content workflow service hosted on webmaster-wordpress.com.
Service name:
The service is used for:
A service account is not required to install, activate or use the local WordPress features of the plugin. A configured service key is required only when the user deliberately triggers connected remote features such as AI generation, credit balance, usage history or account-backed generation requests.
Service endpoint:
Data sent to the service may include:
Data received from the service may include:
No third-party AI provider key is exposed in the browser by the plugin. AI requests are routed through the documented service endpoint when the user triggers an AI feature.
You can disable outgoing AI service calls with the aiscb_allow_external_saas_calls filter. AI generation features will not work while service calls are disabled.
Service terms and privacy information:
Blue Editoria : Content workflow stores plugin settings, scan state, generated suggestions, logs, local usage history and model data in the WordPress database.
When connected AI features are used, the plugin sends the minimum data needed for the selected action to the service endpoint listed above. Administrators should review the provider terms and privacy information and inform site users according to their own privacy obligations.
Useful filters include:
aiscb_detected_fieldsaiscb_available_componentsaiscb_generation_payloadaiscb_generated_htmlaiscb_generated_cssaiscb_activation_rulesaiscb_allow_external_saas_callsGenerated frontend CSS is scoped with the aiscb- prefix to reduce theme conflicts. The plugin should not load admin assets globally outside its own screens.