Manage SiteOrigin Widgets with AI

What we learned testing it

Behavior the ability descriptions do not mention.

• SiteOrigin's tools change widgets on draft and pending pages only and refuse published ones. Reading works on any page. Make changes to a live page in the block editor.
• These tools see SiteOrigin widget blocks in the block editor, including inside Group and Columns blocks. Widgets inside synced patterns are not reached through the page, and widgets inside a Page Builder by SiteOrigin layout are not widget blocks, so they are not seen (see <a href="/works-with/siteorigin-panels/">Page Builder by SiteOrigin</a>).
• Changing any field re-saves the whole widget. A rich-text box saved from the visual editor is then cleaned again as if newly typed: in our test, changing only an Editor widget's title removed a Google Maps embed from its text and stopped a gallery shortcode working. The recipes look for embeds, scripts, forms and shortcodes first and leave such widgets to you.
• Lists inside a widget (features, plans, FAQ panels, testimonials) are changed by position. An empty item or an empty list sent by mistake clears it, so the recipes address items by number and clear a list only to rewrite it.
• Text the AI writes is cleaned as post content whatever your role, and shortcodes in it are turned off (SiteOrigin stores the brackets as full-width brackets).
• A widget type switched off under Plugins, SiteOrigin Widgets cannot be changed until it is switched on again; these tools never switch widgets on.
• Changes run without WPVibe's approval page. The recipes show you each change and wait for your yes, and when revisions are on every change saves a revision of the page.