Neve stores nearly every customizer choice inside theme_mods_neve: header builder rows with their items, footer rows, color palettes, typography, container widths, and blog layout settings. Neve Pro adds the neve_custom_layouts custom post type for hooked layouts, headers, footers, and 404 pages, plus extras like the Custom Layouts builder, the white label module, and module-specific options. Generic chatbots see none of that, so a question about the off-canvas drawer or a custom layout hooked into the sidebar comes back as a guess.

SleekAI maps theme mods and the neve_custom_layouts posts into the chat system message at request time. Display conditions scope each bot by post type, taxonomy term, user role, logged-in state, or URL pattern, so a member bot stays behind login while a marketing bot greets the homepage. Conversation logs include model, token usage, and origin URL inside WordPress on every message.

Most Neve sites pair with WooCommerce or with Otter Blocks. SleekAI reads those sources from the same chatbot, so a single widget answers about both header builder rows and live shop inventory without separate integrations.

Neve is a popular pick for sites that want a builder-style header and footer without the overhead of a page builder. The theme exposes a deep header builder, palette and typography options, and a Custom Layouts post type for Pro users that handles hooks, alternative headers, 404 pages, and conditional blocks. None of that is visible to a generic chatbot.

So a visitor asks what changes on mobile or what that strip above the footer is and the bot guesses. That is a poor experience for the visitor and a missed opportunity for the merchant. SleekAI maps theme_mods_neve and the neve_custom_layouts post type into the chat system message at request time.

The bot now answers from real builder rows and real Custom Layouts rather than vague layout intuition. Add WooCommerce, Otter Blocks, or any other plugin to the same data source list and one widget covers both layout and content questions accurately. The site owner brings their own provider key, owns the conversation logs in WordPress, and picks the model that fits the workload best.

That is the right way to add AI to a Neve site today.