SiteOrigin Page Builder stores page layouts as JSON in the panels_data postmeta field, with rows, columns, and widgets each represented as objects with type and content. SleekAI's Wizard reads panels_data as structured data, so the chatbot's system message receives an ordered list of widgets per page with their text content extracted, instead of trying to make sense of the rendered HTML.

That keeps the bot grounded in the page's real structure. When a visitor asks about a service in a SiteOrigin Editor widget, the model has the widget's heading and body in the prompt. When a question maps to a button widget, the bot can quote the button text and the linked URL. Edits show up automatically because the data source reads panels_data at request time, so an editor's change is live in chat on the next message.

Multibot lets you scope a different chatbot per template or page family, with display conditions for post type, URL pattern, taxonomy term, and user role. For larger sites, push extracted widget text into an OpenAI Files vector store of up to one gigabyte per file. Conversation logs save inside WordPress, so the team can audit how visitors phrase questions and where the page copy falls short.

SiteOrigin Page Builder has been around long enough that many sites carry years of pages built with it. The plugin's quiet strength is that it stores layouts as structured JSON in panels_data rather than baking them into the rendered HTML. That makes life much easier for anything that wants to read the page later, including a chatbot.

The data source can walk the rows and widgets directly, ignore presentation, and surface only the text content the model needs. Reading the rendered HTML, by contrast, would force the bot to guess at section boundaries, mix widget output with theme decoration, and lose the natural structure the editor sees. The result on the conversation side is a bot that quotes the right widget rather than the headline of the wrong row.

The result on the editing side is that any improvement to the page copy reaches the chat immediately, because the data layer that powers the page also powers the bot. That is a quiet but consistent reason to keep using SiteOrigin on sites where this matters.