What Is This Issue?
When generating Content Genius articles through the MCP (Model Context Protocol) integration, some customers have reported that articles are automatically published live to an incorrect or unintended WordPress site — even when auto-publish settings are expected to prevent this.
This behaviour appears to be specific to the MCP integration. Manual publishing and article generation through other methods do not reproduce the same problem.
Is This Affecting You?
You are likely experiencing this issue if:
- You generated a Content Genius article using MCP.
- The article published automatically to a WordPress site you did not intend.
- Your auto-publish settings are configured to prevent automatic publishing.
Immediate Steps to Take
This is a known bug affecting Content Genius article generation via MCP. While the root cause is within the MCP integration itself, you can take the following steps to limit impact and help resolve the issue:
- Pause MCP-based article generation for any projects connected to WordPress sites until the issue is resolved. This is the most effective way to prevent additional unintended publishing while the bug is being investigated.
- Unpublish or delete the incorrectly published article directly from your WordPress site's admin dashboard (Pages or Posts > find the article > set to Draft or Trash) to remove it from public view immediately.
- Review your connected WordPress sites in your Search Atlas account settings to confirm which site is set as the default publish destination for your MCP workflow, and correct it if it is pointing to the wrong site.
- Check your auto-publish settings in Content Genius and ensure that auto-publish is explicitly disabled for any sites you do not want articles pushed to automatically.
- Document the incident — note the WordPress site the article was published to, the site it should have been published to, the approximate date and time, your auto-publish settings, and any MCP workflow or prompt details you used. This will be needed if the steps above do not prevent recurrence.
If unintended publishing continues after taking the steps above, our support team can investigate your account configuration directly. Please contact us and include the details you documented in step 5 so we can assist you as quickly as possible.
How to Contact Support
Reach out to our support team and include the following details to speed up the investigation:
- The WordPress site the article was published to, and the site it should have been published to.
- The approximate date and time the unintended publishing occurred.
- Your current auto-publish settings.
- Any MCP workflow or prompt details you used when the incorrect publishing occurred.
Our team is actively investigating this issue. If you are experiencing unexpected publishing behaviour through the MCP integration that persists after following the steps above, please contact our support team so we can assist you directly.