Begin with the job, not a feature count
IM-Press combines page creation and import with content, search and site tools. Not every capability is active on every installation. Check module configuration, the current license, permissions and required external services.
Swipe or scroll the table to see every column →
| Area | What it provides | Boundary |
|---|---|---|
| Pages and design | Blocks, patterns, import paths and trusted styled-content deployment. | Not lossless conversion of arbitrary applications or universal visual editing. |
| SEO and content | Metadata, structured-data and content/analysis tooling. | Use one deliberate SEO owner. Scores are heuristics; rankings and AI citations are not guaranteed. |
| Site capabilities | Forms/email, products and booking-related tools. | Feature-specific setup and delivery/integration testing remain necessary. |
| Agent access | REST/OpenAPI discovery and optional agent-layer integration. | Requires appropriate authorization; MCP adapter is separate. |
| Custom code | Site-wide and supported page-specific code workflows. | Trusted executable content, permission checks and license-specific access apply. |
Custom Code in this release
Starter includes site-wide CSS and footer JavaScript. Pro and Agency retain head JavaScript, per-page code, safety validation and the dedicated authenticated Custom Code workflow. WordPress capabilities and explicit enable settings still apply. This is a single-site feature distinction—not a promise of a central fleet-control dashboard.
Compatibility is a test, not a slogan
On established sites, check the existing theme, builder, SEO plugin, scripts and integrations on staging. Site-wide hooks can affect output even when page content is not replaced.
Targeted builder conversion helpers are not universal migration. Review what is converted, skipped or retained; do not assume automatic support for every builder.
Not included as shipping products
- The proposed Hosting Companion.
- A central fleet-management console or plugin marketplace.
- A universal approval/publish/rollback transaction for every change.
See the ecosystem boundaries and release notes for context.