Drafts, publishing and scheduling
Statuses, publishing, when the updated date changes, scheduling, bulk actions, changing an address, version history, and editing alongside Willo.
On this page
Every content item has a status, and only one action changes what visitors see: publishing.
The four statuses
| Status | What it means | On the live site? |
|---|---|---|
| Draft | New, never published. | No |
| Scheduled | Set to publish at a future time. | Not yet |
| Published | Live, and what visitors see matches the editor. | Yes |
| Published + edits | Live, with saved edits that are not live yet. | The previous version is |
Edits wait for you
Edits save on the item, not on the site. A published post keeps its live version until you publish again, so you can make many small edits without rebuilding the site after each one. When you are done, Publish changes sends them all at once.
Drafts always save, even if a field holds a value the site can't use. The check happens when you publish.
Publishing
Publishing writes the item into your site's code and rebuilds the site. It runs in the background, and the item shows "Publishing…" until it is live, usually within a few minutes.
If your business is drafting (changes collect on a private draft until someone publishes the site), publishing an item still puts it live by itself. Only that item goes out. Every other change waiting on the site draft stays there until someone publishes the site, and the draft preview shows the item too.
The exception: when Willo can't confirm the item can go out on its own, it is staged on the draft instead and goes live with the next site Publish. For example, the site draft holds its own unpublished change to that item's file or to how the site's content is set up, or the change also edits a page outside your content. Unpublishing and deleting follow the same rule. Its chip in the Content tab says On site draft, and the tooltip says why. The chip clears when the site is published.
Publishing from chat always asks you to confirm first, because it changes your public site.
When a post's updated date changes
A blog post shows two dates to search engines and AI assistants: when it was first published, and when it was last updated. The publish date is set once, the first time the post goes live.
The updated date moves only when you publish a real change:
- at least 50 words of the text change, or at least 5% of them; or
- the title changes.
A smaller change, such as a typo fix, and changes to the description, tags, author or address publish as normal and keep the updated date as it was. Moving paragraphs or sections around doesn't count as a change. New sites show "Updated" with the date under the publish date when the two differ. To show it on an existing site, ask Willo: "show the updated date on blog posts". A post copied in from your previous site keeps the dates it had there.
Field checks before publishing
One invalid value in one item could break the whole site's build, so publishing checks every field against the collection's rules first. If something is wrong, publishing is refused with "Fix these fields before publishing." and the problems appear on the fields themselves, for example "This field is required." Fix them in the editor, or ask Willo to, and publish again.
Scheduling
You can schedule an item to publish at a future time, from the Publish dialog in the Content tab (Schedule for…) or in chat: "publish the autumn menu post on 1 November at 9am". The Content tab shows the item as Scheduled with its time, and Willo publishes it within a few minutes of that time. Setting the schedule counts as your confirmation, so nothing asks again when it fires. Drafting does not hold it back: the item goes live on time by itself, with the same exception as publishing by hand.
If the item's fields stop passing the checks before then (for example because the collection's fields changed), or your site cannot take the change, it is held, still scheduled, and the chip says why. Willo keeps trying for 24 hours after the scheduled time; after that the item leaves the schedule, returns to its previous status and is marked Not published on schedule with the reason. Cancel schedule on the item's row returns it to its previous status at any time. Schedule a post has the steps.
Finding items and acting on several at once
The list in the Content tab searches the whole collection by title, address and description, filters by status with the All / Draft / Scheduled / Published chips, and sorts by newest, recently updated, title, status or most viewed. Long collections load 100 items at a time; Load more brings the next hundred.
Tick items to get a selection bar with Publish, Unpublish and Delete for the selection, up to 100 items at a time. Each item is checked exactly as if you had acted on it alone, and the whole selection goes in one site rebuild. If some can't go ahead, nothing changes and a dialog names each one with the reason: choose Cancel and fix to keep just those selected, or Publish 37 now (or Unpublish, Delete) to go ahead with the rest while they stay selected for fixing. Bulk Publish offers the same Publish now or Schedule for… choice, and while your business is drafting the selection goes live by itself, as a single publish does. Bulk Unpublish and Delete treat each address the way removing that item alone would.
Changing an item's address
A post's address comes from its first title: "Autumn opening hours" publishes at /blog/autumn-opening-hours. Editing the title later never changes the address. To change the address, edit it directly under the title in the editor; the preview shows the full address as you type. Addresses use lowercase letters, numbers and hyphens, and each one is unique within its collection.
On a draft, the new address simply applies when you first publish. On a published item, the page moves when you next publish, and from then on the old address redirects to the new one, so links and search results keep working. The redirect takes effect within a few minutes of the publish going live. Renaming twice before anyone visits leaves one redirect per old address, each pointing at the address that replaced it.
An entry copied from your previous site keeps the address it had there; its address is not editable.
Version history
History in the item editor lists the item's saved versions, newest first, with who saved each one (you or a teammate in the dashboard, Willo, the Growth Engine, an outside agent, or a schedule), when, and which fields changed. Pick a version to see its body changes, or compare it with what is in the editor now. Hide formatting-only changes leaves out lines that differ only in how the Markdown is written (for example * and - bullets), which is useful after the first edit in Write tidies a body.
What is kept:
- every publish, for as long as the item exists;
- every restore, for as long as the item exists;
- every version replaced with Keep mine (see below), for as long as the item exists;
- the last 20 dashboard saves and, separately, the last 20 agent edits. While you type, one version is kept about every ten minutes. Before Willo or an outside agent edits the item, and before a restore, the version it replaces is kept as one of the saves, so a run of agent edits never pushes out yours.
Restore this version puts its title, body and fields back in the editor. The version it replaces stays in History, so a restore can itself be undone. A restore never publishes: a live item shows "Published + edits" until you publish. If the version had a different address, the address changes back too where it can (a message says why when it cannot), and on a live item the current address redirects to it after you publish. Deleting an item deletes its history.
Editing at the same time
When Willo, a teammate or another browser window changes an item you have open, the editor updates in place within a few seconds, and your cursor stays where it was. If you are typing at that moment and the other change touched different fields, or different paragraphs of the body, both changes are kept and a message says so.
If the same field was changed both ways, or the same paragraph of the body, or the same or a neighbouring list item or table row, saving pauses and a notice above the editor names the field and asks which version to keep:
- Keep mine saves your version of those fields. For the body, only the parts you both changed take your version; the other side's edits elsewhere in the body are kept. The other version stays in History as Kept on conflict.
- Use Willo's version (or Use their version) keeps the saved version of those fields. For the body, only the parts you both changed take their version. Your changes to any other field, and to the rest of the body, still save.
- Compare shows both versions first, with the body as a line-by-line diff.
Publishing that item waits until you choose. If you leave the item before choosing, the saved version of those fields is kept, your changes to any other field are saved, and a message names what was not saved.
Unpublishing and deleting
- Unpublish takes the item off the live site and keeps it in the Content tab as a draft.
- Delete removes the item for good. A published item is taken off the site first. There is no undo.
Either way, the confirm dialog says what happens to the item's address. On most sites the old address redirects to the collection's main page (for example /blog/); the dialog has an "Also redirect old address to" field if you would rather send visitors to a specific page, such as the post that replaces it. The redirect takes effect within a few minutes of the change going live. Publishing the item again puts the page back at its address and the redirect stops.
Some collections behave differently, and the dialog says so: an entry copied from your previous site may keep its page up without the entry, and an item in a page-less collection simply disappears from wherever the site showed it. A site without a redirect host is told that the old address will return "not found".
Related: Who publishes content, Schedule a post.