Manage Page Builder by SiteOrigin with AI

What we learned testing it

Behavior the ability descriptions do not mention.

• Page Builder's abilities read and write a page's whole layout at once; there is no edit for one widget. The AI sends the full layout back with only your changes, and on a published page visitors see them at once. The recipes show you each change first, and the placeholder recipe works on a draft copy when you want one.
• Every AI save cleans every widget on the page, not only the ones it changed, and removes iframes, scripts, styles, forms, SVG and onclick-style attributes. In our test a YouTube embed and a booking script in a widget the AI never touched disappeared. Page Builder 2.38.0 tries to keep unchanged widgets as stored, but the Widgets Bundle stores numbers such as 85.0 that come back as 85 through an AI connection, so in our test no widget counted as unchanged. The recipes stop on pages with embed code in any widget and send you to the editor.
• Close the page in Page Builder or the WordPress editor before the AI changes it. By Page Builder's code, an editor opened before the change still holds the old layout and saves it over the AI's change when someone clicks Update.
• Undo in the same chat, not from the page's Revisions screen. Page Builder copies the layout into a revision only for saves made in wp-admin, so the revision an AI change creates has no layout, and restoring it removed the page's layout in our test. Restoring the revision from your last editor save brought the old layout back.
• Sending a layout with no widgets and no rows deletes the page's layout and reports success; with Page Builder's copy content setting on (the default) the page then shows a static HTML copy of its last version. Writing a layout to a page that was not built with Page Builder replaced that page's content in our test. The recipes check that the page has a Page Builder layout first and treat a cleared layout as an error.
• Each widget re-saves its own settings, as it does in the editor, so a few values come back in a new form (1.3 becomes 1.3em). Text, rows and the number of widgets stay as sent.
• In the block editor, a page can hold several Layout Blocks, and the AI has to say which one to change: without it the write is refused rather than guessed. On a page with both a classic layout and Layout Blocks, a write without it goes to the classic layout. A Layout Block inside a Group or Columns block cannot be reached at all.
• A larger page's layout can pass WPVibe's 50,000-character limit on ability results (a 14-widget prebuilt page came back at 54,000 characters), and the read ability cannot return part of it. The recipes read layouts through Page Builder's own read-only route, which returned the same layout whole, and stop on pages over 11 widgets, the size our write tests reached.
• A Google Maps widget keeps its pin's coordinates next to the address and uses them first, so by the widget's code a new address alone leaves the pin where it was. The recipes clear the coordinates when the address changes.
• Prebuilt layouts load their photos from layouts.siteorigin.com and demo.siteorigin.com and come with sample testimonials, made-up statistics and buttons that link nowhere. The recipes list them for you and never write testimonials or numbers of their own.
• Page Builder does not mark the layout update as destructive, so WPVibe's approval step never shows for it. The recipes ask for your yes in the chat instead.