Choose the destination before importing
AI output can range from simple HTML to a complete application with external libraries and services. Those are not interchangeable inputs. IM-Press does not promise that every website or application can become editable WordPress blocks.
Swipe or scroll the table to see every column →
| What you need | Approach | What to check |
|---|---|---|
| Ordinary editable content | Supported block conversion | Structure, skipped content, editor behavior and layout fidelity. |
| A design that relies on its code | Trusted styled HTML / Safe Deploy | CSS scope, scripts, external assets, template choice and responsive output. |
| An existing builder page | Supported targeted conversion helpers | Actual supported builder path and converted versus retained content. Not universal migration. |
Use Import Sessions to prepare a draft
The shipped Import Session workflow supports session creation, preflight, draft import, and preview issuance/revocation. Use those stages to inspect the source and resulting draft. They are not a universal, completed approve/publish/rollback transaction.
- Keep the original design and a backup of the destination.
- Check image, stylesheet, script and font references. A file that worked on a designer's machine may point to missing local assets.
- Use preflight results to choose a supported import path. Do not ignore an unsupported-content warning.
- Inspect the imported draft and preview. Verify headings, navigation, forms and any code-dependent behavior.
- Publish through the appropriate WordPress workflow only after review. Check the actual public page afterward.
What Safe Deploy does—and doesn't do
Safe Deploy preserves trusted HTML, CSS, JavaScript and SVG that ordinary WordPress content filtering may strip. It records deployment history and provides revision restore paths.
Save the existing page or site before replacement. Deployment history does not establish that every overwritten state was captured first, or that a restore safely handles newer edits.
Only deploy executable markup you trust and have reviewed. A successful API response is not evidence that a script is safe, a form delivers, or a page looks right.
After importing
- Test desktop and mobile, keyboard focus and readable contrast.
- Open every important link and confirm required assets exist.
- Confirm the intended template, header/footer and SEO owner.
- Test relevant interactions without sending real customer data during QA.
- Retain the original source so future changes have a clear starting point.