How to Redesign Your Lovable Site Without Losing Your Copy

The most common reason teams stop using Lovable is that the second prompt destroys what the first prompt got right. You spend a week tightening the copy on your hero, your features, your testimonials. Then you ask Lovable to "make it look better" and every sentence comes back rewritten — same length, same structure, none of your voice. You roll back. You stay on the bad design. You eventually stop opening the project.

This is fixable. The redesign just needs to be scoped to the visual layer.

Why "make it look better" rewrites copy

Lovable treats the page as a single unit. When you ask for a visual change, the model regenerates components, and components include their text. Unless you explicitly tell it not to touch the strings, it will. The "regeneration ate my copy" problem is not bad behavior — it is the model doing exactly what was asked, applied too broadly.

The scoped redesign workflow

The workflow that preserves copy has three steps.

Step 1 — Lock the copy. Before any redesign prompt, paste this into the chat: *"Do not modify any user-visible text content. Headings, body copy, button labels, testimonials, and pricing copy are locked. Only modify visual properties: tokens, component styling, layout, and spacing."* This single instruction prevents 90% of copy regression.

Step 2 — Change the visual language, not the components. The instinct is to ask for "a redesign." Instead, ask for token-level changes: a new color palette, a different type scale, a different radius and shadow system, a different button shape. The components stay; the visual vocabulary changes.

Step 3 — Use a real design system as the input. The most reliable version of step 2 is to paste in a complete design system pack. The Rottoways design system pack is built for this exact use case: it ships with a "renovate existing site" prompt that explicitly tells Lovable to keep all copy untouched and only swap the visual layer. You paste it in, you run the prompt, and your site comes back with the same words but a different identity.

This is the difference between a redesign that takes an afternoon and one that takes three weeks. The afternoon version preserves all the copy work you have already done; the three-week version restarts from scratch.

What about the motion?

A copy-preserving redesign covers the visual layer. The motion layer is independent and can be swapped the same way. Paste a motion prompt into the project after the design system, and Lovable will add coordinated spring physics, stagger timing, and route transitions on top of the new visual language — again without touching any copy. See add animations to vibe-coded apps for the exact prompt.

Verification step

After the redesign, do a copy diff. Open the previous version of the page in one tab and the new version in another. Read the headlines, body copy, and CTA labels in order. Anything that changed without your approval is a regression — fix it before shipping. With the locking prompt in place, this diff should usually be clean.

Stop being afraid of the redesign prompt

The reason most Lovable users live with a generic-looking site is that they do not trust the redesign prompt to leave their work alone. With the right scope, the prompt does. A locked copy instruction plus a paste-in design system gives you a reliable path from "AI default" to "looks intentional" without touching a single sentence.

Rottoways ships a copy-preserving renovation workflow built for Lovable, Cursor, and Claude. Pair it with UI Motion Prompts for the motion layer. Both paste-ins, both leave your copy alone.