Edit with chat and the visual editor
Change your page by asking in plain words or by editing it directly. Every change is versioned, and nothing goes live until you publish.
Updated October 14, 2026
On this page
Ask for changes in chat
Type what you want changed in the chat, in your own words. Without a selection, a request can touch the whole page. To keep it focused, first select a section, a call to action (CTA) or a form in the preview: the chat shows what the request is scoped to, and the AI changes only that part.
Each request runs as an AI job. You see a credit estimate first, the job reports its progress, and the result is saved as a new version of the page. Sections keep their IDs through edits, so you can follow a section’s analytics from one version to the next.
Example requests
“Make this more premium”, with the hero selected, refines its typography, spacing, imagery and tone.
“Change the form to a quiz” turns a lead form into a short multi-step quiz that ends by asking for contact details, so it still produces leads.
“Make the mobile CTA sticky” keeps the call to action on screen on phones, placed so it never covers the form.
“Create a TikTok Ads variant” drafts a version of the page for a cold TikTok audience, which you can review and then test against the original.
Specific requests work best: “shorten the form to name and phone” gets a better result than “improve the form”. The AI also keeps to the product’s rules, so a countdown needs a real deadline, a stock notice needs a real inventory source, and reviews have to come from you.
Edit by hand
When it’s quicker to make a change yourself, edit the page directly in the preview:
Click any text to edit it in place, or replace an image.
Reorder sections.
Adjust the basic layout, colors and typography of a section.
Change the design tokens the whole page uses: colors, type, spacing, corner radius and motion.
Add a CRO widget from the trusted library, such as a sticky CTA, an FAQ accordion, a multi-step form or a countdown tied to a real expiry date.
Widgets come from CVRLanding’s library of tested components, each with its own settings, accessibility checks and analytics events. The editor doesn’t insert free-form HTML or scripts into a page.
Chat and editor share one page
A CVRLanding page isn’t a blob of generated code. It’s a structured page schema of sections, components, forms, design tokens and tracking settings, rendered by the trusted block library. The chat and the visual editor both change that same schema.
So you can switch freely: fix a headline by hand, then ask the AI to rework the section around it, and neither change is lost. There is one editor, not a separate drag-and-drop builder to keep in sync.
Versions, undo and history
Autosave saves changes as you work, and an indicator shows when something hasn’t been saved yet.
Undo and redo step backward and forward through your recent changes.
History lists every version with who made it, when, and whether it came from the AI, a manual edit, a restore or an experiment. Open a version to see a diff of what changed.
Restore brings back an earlier version as a new version, so the history itself never changes.
Named snapshots mark a version you may want to come back to, such as the page before a pricing change.
Share a read-only preview
To get feedback from a client or a colleague, share a read-only preview. Choose the version and when the link expires. Anyone with the link can view that version of the page, but can’t edit it or see anything else in your workspace.
Unsaved changes aren’t part of a shared preview, so let autosave finish before you share.
Preview sizes and test mode
Switch the preview between desktop, tablet and mobile widths. The preview uses the same components as the published page, so the mobile view shows what a visitor from an ad sees on their phone.
Forms, booking requests and orders work in the preview, so you can try the whole flow. Anything submitted there runs in test mode: it isn’t counted as a production conversion, and preview visits don’t affect running experiments.
When two people edit at once
Every edit, whether it comes from you, a teammate or the AI, is applied to the version it started from. If the page has changed in the meantime, CVRLanding doesn’t silently overwrite anyone’s work. You get a conflict to resolve or a separate branch of the page instead, and neither edit is lost.
Nothing goes live until you publish
Your draft and your live page are separate. Chat edits, manual edits and the CRO agent’s proposals change the draft or a staged variant. Visitors keep seeing the published version until you publish again, after the pre-publish checks.
AI edits never reach a live page on their own. Publish and connect a custom domain describes the checks that run before a page goes live, and how to roll back.