Skip to main content
AI PublishMulti-site SEO Operations Platform

CMS Integration

WordPress Integration

Self-hosted WordPress connects through a root connector: no theme changes, no plugins, no database alterations. The platform only creates or updates real posts after you confirm the task.

How it connects

WordPress uses the root connector (currently version 1.6.2): download one PHP file from the platform, upload it to your site root, and the platform can verify the site, read categories and publish articles.

  • Works with standard self-hosted WordPress with root-directory access and HTTPS.
  • Themes and front-end structure stay untouched; publishing uses WordPress' own wp_insert_post, identical to publishing from the admin console.
  • The connector is not interchangeable with the Emlog, PbootCMS or other CMS files; each site installs exactly one.

Four steps to connect

  1. Download the WordPress connector under "Sites > CMS connector files" — you get aiseo-connector.php.
  2. Upload it to your WordPress root (beside wp-load.php); the final URL is https://your-domain.com/aiseo-connector.php.
  3. Add and verify the site in the platform: signing is activated automatically and the CMS version, site name and all categories are read.
  4. Pick target categories, sync the mapping, then import titles, generate and publish articles.

Your server needs PHP JSON and cURL support; image localization requires a writable media directory. Opening the connector in a browser returns METHOD_NOT_ALLOWED — that is expected (the platform uses POST).

Publishing behavior

  • Categories: real categories (including parent-child relations) are read and applied via real term IDs; the platform never creates or deletes categories in your WordPress.
  • Tags: task-specified tags are written; tag failures only record a warning and never block publishing.
  • Images: remote mode references remote images directly; localize mode downloads them into the media library, sets the featured image and rewrites the in-content URL. Up to 5 candidates are tried in order — if all fail, the article still publishes with a recorded warning.
  • Updates: republishing the same platform article updates the original post instead of duplicating it.

Security and boundaries

The connector enforces the shared security protocol (see the Security Center): only POST requests from the platform egress are accepted; every request carries an HMAC-SHA256 signature, timestamp and single-use nonce; request bodies are capped at 2 MiB.

The connector offers no remote category editing, article deletion, arbitrary file writes or arbitrary PHP execution. To disconnect, delete aiseo-connector.php and its companion state files from your site root.

Troubleshooting

  • WORDPRESS_BOOTSTRAP_NOT_FOUND: the file is not beside wp-load.php — check the upload location.
  • PLATFORM_SOURCE_NOT_ALLOWED (403): the request did not originate from the platform egress, usually a CDN or proxy rewriting the source address; contact us to align the egress IP configuration.
  • All images failing: check that image URLs are valid HTTPS direct links without redirects and under 10 MiB.
  • Duplicate articles: confirm the WordPress article markers were not removed manually — the platform identifies existing posts through the idempotency marker.

WordPress Integration

Self-hosted WordPress connects through a root connector: no theme changes, no plugins, no database alterations. The platform only creates or updates real posts after you confirm the task.