Agencies + AI-Assisted WordPress Work

IM-Press supports reusable page workflows, white labeling, migrations, permissioned agent access, and a source-defined Agency license limit of up to 50 sites—without pretending that a license key is a remote fleet-management system.

On this page

White Label Templates + Deployment Multi-Site Reality Connect Agents Migration Scope Safety Model Licensing

🏷️ White Label

Agency branding inside WordPress

The Agency tier can change the plugin name, description, author identity, icon, support/documentation links, visibility, and custom admin styling. Treat white labeling as a WordPress-admin presentation feature—not a claim that every user-facing email or external service is automatically rebranded.

🚀 Templates + Deployment

Reusable page assets with explicit targets

✅Export/import IM-Press pages and reusable templates

✅Generate and deploy page templates through permissioned routes

✅CSV-driven rank-and-rent page generation within one connected WordPress installation, bounded to 10 pages per AI bulk-deploy request

✅Safe Deploy history and restore for advanced styled pages

Cross-site rollout requires each destination to be separately connected and authorized. Backups, previews, validation, and approval still apply.

🌐 What “Up to 50 Sites” Means

A licensing limit, not automatic central control

The 5.2.3 Agency tier encodes a 50-site license limit. It does not, by itself, discover sites, share credentials, or create a central remote-management dashboard. Each WordPress installation remains its own security and rollback boundary.

🤖 Connect Compatible Agents

REST, OpenAPI, and MCP-adapter workflows

The Connect AI Agent screen can generate a one-time WordPress Application Password and copy-ready configuration for Claude Desktop, Claude Code, Codex, Cursor, and custom clients. MCP access additionally requires the optional IM-Press agent-layer flag, compatible Abilities functions, an active WordPress MCP Adapter, and client configuration.

🔐WordPress capability checks and per-site credentials

📘OpenAPI discovery plus route-specific safety notes

🧭Content, SEO, media, health, import, and deploy workflows

🛑No claim that any MCP client works with zero setup

🔄 Migration Scope

Beaver Builder and Elementor conversion helpers

The current migrator scans and converts Beaver Builder legacy data and Elementor data into a new IM-Press page, reporting converted and skipped modules/widgets. Divi and WPBakery are not advertised as automatic migrations in 5.2.3. For other sources, use reviewed HTML import or rebuild with blocks; expect manual styling checks.

🛡️ Agency Safety Model

One target, one rollback, one approval boundary

1️⃣Inspect the destination and capability surface first

2️⃣Back up content and metadata before mutation

3️⃣Prefer drafts/previews for substantial layouts

4️⃣Use Safe Deploy only when raw styled content needs preservation

5️⃣Verify stored HTML, public rendering, links, and console output

6️⃣Keep cPanel, SSH, DNS, and server recovery outside Core; Hosting Manager is a proposed separate companion, not a shipped 5.2.3 layer

💳 Agency Licensing Reference

Agency — $149/year in declared 5.2.3 tier metadata

The 5.2.3 tier metadata declares Pro modules plus white label, Agency workflows, AI endpoints, templates, migration tools, priority support, and a license limit of up to 50 sites. All 80 live-runtime blocks currently register across tiers.

For provisioning or commercial questions, email AI Robot Build support. The documentation no longer links to a removed product-page pricing section.

Start with the exact 5.2.3 package.

Review the feature map first, then connect and authorize each WordPress target separately.

Download 5.2.3 Verified Features