Build with Thrive Architect
Create and refine a native Architect landing-page draft.

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.
- Thrive Architect 11.0 or later, documented test on 11.0.0.1.
- 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 Thrive Architect under 1. Standalone builder. Choose Save changes. A Not detected card lists missing requirements.
In WordPress, open EMCP Tools, then Page Builders. Under Standalone builder, select Thrive Architect and choose Save changes. If the card says Not detected, check its listed requirements first. Gutenberg can stay available beside this builder.
Step 02
Enable the actions and reconnect
Open Setup → Tools → Thrive Architect. Inspect read and write switches; enable the actions needed for this practice task, then Save changes and reconnect your AI app.
Open Tools and select the Thrive Architect tab. Turn on the read tools and editing actions this lesson needs. On a new installation these Pro tools start switched off. Choose Save changes, then reconnect your AI app so it sees the updated list.
Step 03
Inspect before building
Ask the AI to read Thrive Architect'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
Read the native page
Inspect current content, styles, and the controls for the elements you need.
Architect stores its content differently from other builders. The AI should read the native elements and current version before writing.
Step 05
Build a small draft
Create a draft with basic sections, columns, text, an image, and a contact button.
Keep the example within the supported basic elements. Cloud landing templates, shared-symbol edits, and forms are separate tasks.
Step 06
Revise without replacing styles
Ask for one text or spacing change while preserving unrelated page CSS and settings.
A targeted change should keep the rest of the design intact. Check image sizing and anchors again after saving.
Step 07
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 Thrive Architect 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.
A brief becomes a real page.