Website changes at once
On a site in code (the Allsite CMS), a change you ask for is made on the code at once: Echo writes it, your site's build makes a preview, and you publish it with one click. No task to wait for.
Ask for a change
- Open Website → Canvas and the page you want to change.
- In the box at the bottom, pick Ask AI to change and write what you'd like, for example "make the hero button orange".
- The change appears under Changes with its status. A minute or two later its preview is ready.
You can also ask in Ask Echo, in Slack or Microsoft Teams ("@Echo change …"), or in your own Claude, ChatGPT or Cursor through the connector. Asking needs the Design website right.
Check and iterate
On the canvas, pick Ask AI to change on the toolbar, point at the part of the page you mean (a button, a card, a heading, the navbar or a whole section lights up) and click it. Write what should change in the box that opens, with the model and reasoning you want.
Click a change to open it. The canvas goes to where it was asked. Every prompt makes a new version with a short title. The version that goes live sits on top in the orange box; it's Live until you pick another. Each version has Show (the canvas shows it), Iterate (a new version from it), Remove and Info (the full prompt, the AI's answer, the model, credits and times). On the version you're looking at, Take it picks it; Keep on Live goes back.
Turn a comment into a change with Make this change on the Comments tab.
The release
Each site has one release: the changes waiting for a reviewer, from everyone together. Once a version is taken:
- Without the Publish right you see Add to release. The orange button in the header says Add to release too: tick your changes and add them. What you add joins what others added; nothing is replaced. The reviewers get an Inbox message, and an email at most every 30 minutes.
- A change in the release is locked (greyed out). To change it again, open it and click Remove from release, then add it back when it's ready.
- A reviewer can Send back a change with a note. It leaves the release, and whoever added it sees the note on the change and in their Inbox.
Publish from Claude, ChatGPT or Cursor
You don't have to open Echo to publish. After a change, your AI asks once:
- With staging: "Publish now: staging and live, staging only, or not yet?"
- On a demo address (live only): "Publish now, or not yet?"
Answer in the chat, or say it in your request ("make the hero button orange and publish it right away"). A change still building goes out by itself once its build is done. Reload your site a minute or two later to see it. Publishing needs the Publish right; without it, your AI adds the change to the release and a reviewer publishes it. Undo is in Website → Versions.
Staging and live
People with the Publish right are the reviewers. Their orange Publish opens a menu with two tabs, like Framer's:
- Staging: the release and your own ready changes, plus your text and CMS edits, each with a checkbox. Hover a row to see when it changed and View change. Publish to staging builds them on your staging address.
- Live: what staging has. Deploy latest puts exactly that live; when live already has it, the button says Latest deployed.
Each tab shows its address (click to open it) and the last publish, like "22 hours ago by Ben". Your staging address is staging. before your domain (for example staging.yourcompany.com). Allsite sets it up for you, and only people in your Echo workspace can open it. A site still on its demo address (yourname.allsite.pro) has Live only: Publish goes straight live.
Undo on a live change makes a new version with the old files back; nothing is rewritten. Every change that goes live is kept in Actions as done, with who asked, what changed and the before and after.
Rights and credits
- Design lets someone ask AI for changes (it includes Content). Publish makes someone a reviewer: they publish to staging and deploy to live. Set them in Settings → Users.
- Changes made by Echo's AI use Website credits. With your own Anthropic or OpenAI key, or from your own Claude, ChatGPT or Cursor, they use none. See AI credits.
Sites on Framer, Webflow or WordPress
These changes need a site in code. On Framer, Webflow and WordPress you get every AEO feature, with drafts and fixes sent to your builder.
Something wrong or out of date? Write to hello@echo-aeo.com and we'll fix it.