Skip to content

WordPress for publishers

Private beta

Your distribution desk, inside WordPress.

Give editors one place to decide what travels, how it is packaged, when it publishes, and what happened next.

Request WordPress accessSee publisher use cases

The working loop

Install with us. Keep control with your team.

The current product is an assisted private beta. We work alongside a WordPress administrator to validate compatibility and configure the first distribution strategy.

  1. 01

    Install & provision

    A WordPress administrator installs the connector and provisions a private Content Pulse workspace.

  2. 02

    Map the source

    Confirm brand settings and map the categories and tags that define eligible content.

  3. 03

    Connect channels

    Connect the owned social profiles that should receive approved distribution.

  4. 04

    Set the strategy

    Choose cadence, formats, language, timing, and approval behaviour for each content stream.

  5. 05

    Package stories

    Content Pulse turns eligible articles into channel-native creative packages.

  6. 06

    Review or automate

    Approve each package or use a defined hold period before scheduled release.

  7. 07

    Publish in language

    Distribute approved posts with multilingual output where the strategy requires it.

  8. 08

    Read performance

    Review post and profile performance inside the WordPress control centre.

What is ready

A real control centre—not another publishing tab.

  • Self-provisioned workspace
  • Brand and business settings
  • Category and tag mapping
  • Per-site channel connections
  • Strategies and approval rules
  • Scheduled publishing
  • Multilingual output
  • Post and profile reporting

Private-beta notes

Release discipline before public download.

We are validating production compatibility, security, billing, and support before offering a public plugin download. Until those gates are complete, access is assisted and the marketing site will never send you to a broken or unverified package.

Best current fit: editorial teams with a WordPress administrator, an established article taxonomy, and owned social channels ready to connect.

Next signal

Bring one publication into the private beta.

We will review your WordPress setup, editorial workflow, content volume, and target channels before proposing an install plan.

Request WordPress access