Page Builder Support

Page Builder Support

Respira understands 19 WordPress page builders at the module level, plus the native Site Editor. AI can update specific sections, buttons, or text blocks without affecting the rest of your page.

As of 9.2.6 the coverage line is 19 page builders plus the native Site Editor.

Supported Builders

Plus the native WordPress Site Editor:

Divi counts once and covers Divi 4 and Divi 5; Oxygen counts once and covers Oxygen Classic and Oxygen 6. That makes 19 builders, read and written, except Thrive Architect (text edits) and SeedProd. SeedProd is audit-only (agents read and report on landing pages). Brizy and Visual Composer moved from read to write in Respira 7.4.0 "Clearing". The native Site Editor became a first-class target in Respira 8.0 "Canopy" and is counted separately from the 19 builders. YOOtheme Pro joined in 9.2.0, Avada in 9.2.6.

New in 8.0 "Canopy": the native Site Editor

Block themes used to be a partial read. In 8.0 the Site Editor is addressable: block templates and template parts with hierarchy and source discovery, synced and unsynced patterns, block navigation edited by exact block path, and Gutenberg design tokens.

Structural writes to those site-level objects are off by default; the site owner turns them on per site. Read-only discovery works everywhere. See Site Editor (Full Site Editing).

New in v6.0: Flatsome UX Builder

Flatsome is the most popular WooCommerce theme on ThemeForest (200,000+ sales). Respira 6.0 adds full support:

• Shortcode-based storage (section > row > col > elements), same architecture as Divi 4
• 55 element definitions with attributes, nesting rules, and responsive patterns
• 6 pre-built page patterns for AI agents
• Theme-based detection (not plugin), with mixed-builder site support
• WooCommerce shortcodes preserved through round-trip editing

See the full Flatsome documentation for element reference and nesting rules.

TagDiv / Newspaper detection

Sites running the Newspaper or Newsmag theme with TagDiv Composer are detected as "WPBakery (TagDiv)" and handled through the WPBakery builder class.

How It Works

1. Extract: Respira reads your page and parses the builder's data format
2. Identify: AI finds the specific module you want to change
3. Update: Changes are applied to just that module
4. Preserve: All other content, styling, and settings remain intact

Key Tools

• respira_get_builder_info — detect active builder, version, module count
• respira_extract_builder_content — view full page structure
• respira_find_element — search by text, CSS class, type, or ID
• respira_update_element — update a single element's settings or content
• respira_build_page — create a complete page from declarative JSON
• respira_inject_builder_content — replace full page structure

Example Workflow

You: "What page builder is my site using?"
AI: Uses respira_get_builder_info → "Your site uses Flatsome UX Builder"

You: "Show me the structure of the homepage"
AI: Uses respira_extract_builder_content → Shows sections, rows, columns, elements

You: "Update the hero banner heading to 'Welcome to Our Store'"
AI: Uses respira_find_element → Finds the text_box inside ux_banner
AI: Uses respira_update_element → Updates just that text

Context-Aware Tool Filtering

The MCP server filters the tool list based on your site's detected builder, so a site only sees the tools that apply to it. The current totals, on any WordPress site and with the WooCommerce add-on, are on the live tools catalog. Builder-specific tools (for example the Bricks and Elementor deep tools) only register when that builder is present. Less noise, faster AI responses.

Best Practice: Use Admin Labels

Set descriptive admin labels on important modules. This makes them easy to target:

• "Hero CTA Button"
• "Footer Contact Form"
• "Pricing Table Section"

Then: "Update the module labeled 'Hero CTA Button' to say 'Contact Us'"

FAQ

Which page builder has the best Respira support?

All 19 supported builders have module-level editing, with Thrive Architect limited to text edits and SeedProd to audits. Divi and Elementor have the most comprehensive intelligence packages. Bricks has 25 dedicated tools, listed only on Bricks sites. Flatsome has a 55-element intelligence package with nesting rules and page patterns, and YOOtheme Pro reads its elements live from the running theme and has 4 tools for its site templates. Avada has 11 tools for its design system, Layouts and Library, listed only on Avada sites. The native Site Editor is covered separately on the Site Editor page.

Can Respira edit Global Modules in Divi?

Yes, through the library item. A page stores a global module as a reference to its Divi Library item, and Respira reads and writes it as that reference, so a page edit never turns it into a local copy. To change a global module, edit the library item: the change shows on every page that uses it.

Does Respira work with custom builder modules?

Core modules from all 19 builders are fully supported. Third-party add-on modules have varying support depending on how they store data. Most text-based custom modules work well.

What happens to my styling when Respira updates a module?

Respira preserves all existing styling, settings, and structure. Only the specific content you ask to change is modified. Colors, fonts, spacing, animations, and responsive settings remain intact.

Can I undo changes made by Respira?

Yes. Every write operation creates a before/after snapshot. Use the Changes page in WordPress admin to review, diff, and restore any previous state.