Most of the work you hand the Divi AI Agent will not be a blank page - it will be a section, a page, or a whole site someone already built that just needs a new look, a new order, or new words.

Redesigning is a different job from building from nothing: you're not just describing an outcome, you're also protecting everything you don't want touched.

This article walks through that job end to end, using a small example: bringing an old Services page up to date.

The habit that makes this go well is to work small before you work big. Scope a request to one section, check the result, then widen it - rather than describing the whole redesign in one message and hoping the Agent guesses right everywhere at once.

Before you change anything on a page you didn't build yourself, or haven't touched in a while, switch the AI Agent's mode toggle to Ask.

This isn't a formality - Ask mode is genuinely unable to change your page. It runs on a version of the Agent that was never given the tools that add, edit, move, or delete anything, so there's nothing to accidentally trigger, and a final check blocks any change that somehow got through anyway. "Look before you touch it" is real advice here, not a suggestion you can skip.

Check the answer against what you actually see in the builder. If the summary is off, that's worth knowing now - it means your next request needs to be more specific about what "the hero" or "the pricing table" actually refers to.

Once you know the page, don't ask for the whole redesign in one go.

Pick the first section you want to change and point the Agent at it directly - pin it as context from the AI Agent's chat, or lock the whole conversation to it - rather than describing it in a sentence and hoping the wording is unambiguous.

The less the Agent has to guess about which section, card, or button you mean, the closer the first attempt lands to what you pictured.

Switch to Build mode once you've confirmed what you're looking at, then start with the smallest piece that represents the redesign - a card row, a hero, one panel - rather than the whole page.

With one section pinned, ask for the specific look you want, and say what to leave alone.

The Agent updates several modules' settings in one pass and reports back per card, so if one card has a slightly different structure than the other two, you'll see which ones actually changed rather than assuming all three landed the same way.

Check the result against what you asked for before moving on. If it's close but not right, correct it in the same conversation rather than starting a wider request on top of a section you haven't confirmed.

Once the styling on that first section holds up, widen to structure. Moving things around is where an unscoped request does the most damage, so keep naming the pieces explicitly.

Reordering rows, columns, or whole sections works the same way for a full-page rearrange as it does for one card inside a row - name the pieces, name the destination, and say what stays put.

Copy usually needs to change alongside the look, and it's worth its own pass instead of folding it into a styling request.

A single instruction to "update the wording" across a whole page tends to rewrite things you'd rather it left alone, like a legal disclaimer or a client's approved tagline - so scope content passes the same way you scope styling ones.

Once a handful of sections look right individually, that's the point to widen out and clean up anything repeated across the whole page in one pass, instead of visiting every section by hand.

For a known value that needs to change everywhere it appears, ask for a straight swap rather than describing every location:

This kind of request doesn't require you to know which setting or which modules hold the color - the Agent can scope a find-and-replace to the page, to one section, or to a single module, and it works the same way the Find and Replace panel does when you use it by hand from a field's right-click menu, just applied across many modules from one request.

A redesign that looks right on desktop can fall apart at narrower widths, especially after a rearrange. Switch to Ask mode again for this check, so nothing changes while you're still deciding what needs fixing.

Work through what comes back one issue at a time, rather than asking for a blanket "make it responsive" pass. For more details regarding the responsive design, check the Making Your Divi 5 Website Fully Responsive article.

Every message you send carries its own restore option.

Click it and confirm in the Restore to This Point dialog, and the page in the builder goes back to exactly how it looked right before the Agent acted on that message, undoing whatever it changed afterward.

This is why working in small, checkable steps pays off twice over: restoring after a scoped section-level change costs you one card row, not the whole redesign. For more details, check the How to Manage Conversations in the Divi AI Agent article.

If a request from this session is one you'll run again on the next site - the card restyle, the color sweep, the responsive check - save it as a custom command instead of retyping it. For more details, check the How to Use Commands in the Divi AI Agent article.