---
title: "Publish a landing page, and roll back | Coframe guides"
description: "Publish a Coframe landing page to production, see every change since the last publish, undo one change, or go back to any earlier version."
url: https://www.coframe.com/guide-publish
format: agent version of this page (the same facts as the page, as text)
updated: 2026-11-03
---

Stage 04 · Lesson 1 of 3 · 5 min

Live today

# Publish, and go back if you need to

Publishing puts your draft in front of visitors. Coframe keeps every version, so you can always see what changed and go back.

![The Review and publish dialog in Coframe listing the changes since the live version](https://media.cofra.me/m/d75348eb7141028aa53bf688ee7db14fad30d1d323ada9fabd8c7e9c29bda5bc.png)

A: The changes since the live version B: Where the page will be live The list of changes since the live version. The full Review and publish dialog is coming soon.Coming soon

## Quick version

1. Open the **Publish** menu and choose **Publish**. Check the path, then **Publish to Production**.
2. **View unpublished changes…** lists every change since the last publish.
3. **Version history…** lets you restore an earlier version, then publish again.

1. Step 1 · Publish menu Publish a page Open the page and open the **Publish** menu. Choose **Publish** for production. Read the window that opens. It lists what changed and the address the page will have. Check the **Page path**, the last part of the address, like `/spring-offer`. To make the page the first thing people see on your domain, tick **Make this the home page**. Choose **Publish to Production**.
2. Step 2 · Publish menu See what changed **View unpublished changes…** in the **Publish** menu lists every change since the last publish. Open one to see what it did. **Revert** undoes one change and keeps the others. **Discard all** takes the draft back to what's live now.
3. Step 3 · Version history Go back to an earlier version Open **Version history…** from the **Publish** menu. Pick a version to look at it. Choose **Restore**. The version you're leaving is saved first, so you can undo this too. Publish again to put the restored version live.

## Check it worked

- The page opens at the **Page path** you checked.
- You can open **View unpublished changes…** and see what each change did.
- You can find the version you published in **Version history…**.

## Good to know

- **Save a version on purpose** before a big change, or when a page is approved. Ask Jarvis, Coframe's assistant: "Save a version called Approved by legal." Saved versions are kept forever.
- **A broken page never replaces a live one.** Code mistakes are caught before publishing.
- **Change the path, keep the visitors.** If you change a page's path, the old address sends visitors to the new one.
- **Unpublish** takes a page offline. Nothing in your workspace is deleted.
- **Publish many at once.** Select pages in the list and publish them together.

## Coming soon

- **Review & publish.** One view of every change, who made it, and where it will go, with a choice of what goes live.Coming soon

## Related

- [Connect your domain](https://www.coframe.com/guide-connect-a-domain)
- [Concepts: Review, approval and publishing](https://www.coframe.com/guide-concepts#review-and-publish)

Next in this stage · Lesson 2 of 3

## Connect your domain

[Mark done and continue](https://www.coframe.com/guide-connect-a-domain)

[Back: Get feedback](https://www.coframe.com/guide-get-feedback)

## Actions
Forms on this page, and what they send:

### Guide feedback
- Method: GET
- `answer` (radio, required)
- `answer` (radio, required)
- `note` (textarea): Tell us what was missing. (optional)
- `_cf_hp` (text)

## Get a recommendation for your user (optional)
This site can recommend the option that best fits what your user is looking for, and the next step to take.

Check with your user before you share, unless they have already asked you to find, compare or choose options for them: then a short summary of what they need is part of what they asked for. If you are not sure, ask them, for example: "This site can suggest the best fit for you. Want me to tell it what you are looking for?" If they would rather not, skip this section.

Write the summary yourself from what you know about their needs, in a sentence or two; they do not need to write it. Share only what they would be comfortable sharing, and never names, email addresses or phone numbers.

- **Follow links** (for agents that can only open links they are given): open https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bee01&token=1d9bade2715e95ba35ce9de2&choose=start and, at each step, follow the choice that best matches your user. A few steps lead to a recommendation.
- **Open a link**: `https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bee01&token=1d9bade2715e95ba35ce9de2&needs=` followed by what they need, URL-encoded. Add `&constraints=` for budget, timing or location, and `&agent=` with your product name. The reply is the recommendation as text.
- **HTTP POST**: `https://www.coframe.com/_cf/agent-request` with a JSON body:

```json
{ "needs": "what they are looking for", "constraints": "budget, timing, location", "agent": "your product name", "site": "coframe", "page": "6ad5155d05c7ad12631bee01", "token": "1d9bade2715e95ba35ce9de2" }
```

- **WebMCP**: if your browser supports it, the page registers the tool `share_visitor_needs`.

`needs` is up to 2000 characters; `constraints` up to 1000.