Publishing is part of the program.

AutoSEOPilot does not stop at a draft. Publishing is connector-specific: use a configured ordinary-write path — WordPress, Ghost, Webflow, Shopify, signed webhook, or Markdown/HTML/JSON export — when that path's proof requirements are complete.

Ordinary-write paths

These are the ordinary-write destinations in the current runtime. Native CMS connectors are enabled individually after connector-specific credentialed write/read-back proof; webhook and export paths follow their own delivery requirements.

  • WordPress

    Native connector; usable for ordinary publishing after its connector-specific configuration and credentialed proof are complete.

  • Ghost

    Native connector; usable for ordinary publishing after its connector-specific configuration and credentialed proof are complete.

  • Webflow

    Native connector; usable for ordinary publishing after its connector-specific configuration and credentialed proof are complete.

  • Shopify

    Native connector; usable for ordinary publishing after its connector-specific configuration and credentialed proof are complete.

  • Signed webhook

    HMAC-signed delivery to a stack that can receive and verify the request.

  • Markdown / HTML / JSON export

    Export the finished draft bundle for the publishing workflow your stack already uses.

Not available for ordinary publishing

These destinations are not available for ordinary publishing yet.

  • Wix

    Beta (coming soon); unavailable for ordinary publishing.

  • Notion

    Beta (coming soon); unavailable for ordinary publishing.

  • Framer — beta

    Beta (coming soon); unavailable for ordinary publishing.

  • VibeCMS

    VibeCMS is activation-gated and unavailable for ordinary publishing.

Need a custom API path or a publishing setup that does not fit this list? Email [email protected].