A brief becomes a real page.Build with Visual Composer
Stage an editable layout together with matching frontend content.
Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- EMCP Pro and a verified AI connection.
- Visual Composer Website Builder 45.16.2–45.16.x.
- A practice site and a draft page.
Let’s do this, step by step.
Step 01
Select and save the builder
Open Setup → Page Builders. Select Visual Composer under 1. Standalone builder. Choose Save changes. A Not detected card lists missing requirements.
Start with the required plugin or theme active. Select this builder and click Save changes. This does not convert existing content.
Step 02
Enable the actions and reconnect
Open Setup → Tools → Visual Composer. Inspect read and write switches; enable the actions needed for this practice task, then Save changes and reconnect your AI app.
Open this integration’s Tools tab. Check both read and write actions; Pro read tools can also start off on a fresh install. Save your choices and reconnect the app so it reads the updated list.
Step 03
Inspect before building
Ask the AI to read Visual Composer's context, supported element controls, and existing design settings.
Ask what this installed version can actually edit. Seeing an element in the catalog does not always mean EMCP can create or change it.
Step 04
Inspect the existing document
Read the native editable layout, rendered HTML, and page CSS.
Visual Composer stores the editable design separately from what visitors see. A complete change needs both to agree.
Step 05
Stage a complete document
Have the AI prepare matching native elements, HTML, and CSS using the installed schemas, then stage all three together.
Do not save only the editable graph and expect the frontend to rebuild itself. The staged document must include all three parts.
Step 06
Reuse and recover carefully
Inspect compatible local templates or restore a complete staged snapshot. Use Discard draft to retain the published document if needed.
Local templates include the saved rendering. Remote Hub downloads and linked template edits are outside this workflow.
Step 07
Publish after editor review
Open the native editor and check a native save, then publish the reviewed staged document explicitly.
Confirm the desktop and phone view match the editable layout before publication. Visual Composer here is a different product from WPBakery.
Step 08
Read back and preview
Read the saved page again. Open the native editor, then inspect the frontend at desktop and phone widths.
Check the saved content, editing controls, images, and links. If a newer edit is detected, read it before trying again. A save response alone does not prove the page looks right.
You’re done when…
The Visual Composer result remains natively editable and the intended save/publication state is verified.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
You only need the guide for the app or builder you use. Ready to build? Try an Elementor draft or use Gutenberg.