Navigation

Asking for a Change

Describe what a section should become, then compare before and after.

Some changes are not edits to words. You want three columns instead of four, the testimonial moved above the pricing, the whole section reframed around a different objection.

Edit on a section's hover toolbar is for those. You describe what it should become, Webby rebuilds it, and you compare the two before deciding.

Steps

Open the section's editor

Hover the section and press Edit. A panel opens with an instruction box and some optional extras.

Write the instruction

Describe the outcome, not the mechanism. Webby has the section's current layout in front of it, so you are asking for a change from where it is now.

Three things make an instruction work. Say what should be true when it is finished rather than what to do. Give the reason where it helps, because it resolves the dozens of small choices you did not mention. And be specific about scope — which part of the section you mean.

Compare: make this better gives Webby nothing. Our buyers are sceptical about switching costs, so lead this section with the migration support and move the feature list underneath gives it a brief.

Weak instructions name a feeling. Strong instructions name a reader and what should change for them.

Leave Enhance my prompt on

Enhance my prompt is on by default and worth leaving on. It expands a short instruction into a fuller brief before the work begins, filling in the specifics you did not state.

Turn it off when your instruction is already precise and you want it followed literally — particularly when you have tried once and are narrowing in on a specific fix.

Attach references if they help

Reference Images let you show rather than describe: a screenshot of a layout you want, a sketch, a competitor's section. This is the fastest way to communicate something visual.

HTML Reference takes markup directly, for when you have an exact structure in mind.

Both are optional, and an image is usually worth several sentences of description.

Compare before and after

When the rebuild is ready you get a comparison with a Before and After toggle, rendered properly rather than as code.

Use it. Switch back and forth and check the things you did not ask about as well as the thing you did — a section rebuilt for one reason can lose a detail you cared about.

Accept Changes keeps the new version. Declining costs you the generation but leaves the page untouched.

The old version is kept in the page's history whatever you decide, so accepting is not a one-way door.

Rewriting the whole page at once

Rewrite in the main toolbar applies one instruction to every block on the page. It keeps each block's layout — the grids, cards and animations — and swaps the content.

This is the tool for repointing a page: the same structure aimed at a different audience or a different offering. It is priced per block, so the cost scales with the page, and the estimate is shown before it runs.

For anything smaller, edit the one section instead.

Important: Asking for a change is a charged action and the cost is shown before it runs. Editing text by hand is free. If what you want is different words, type them.

Result

A section rebuilt to your instruction, with the previous version recoverable from the page's history.

Continue Reading

Was this article helpful?

NotebookLM Overviews