Scheduling content

Updated 2 min read

A publish date in the future lets content appear on its own, at the time you set.

Publishing later

A record is visible once its publish date has passed. Set the date in the future and the record stays hidden until that moment, then appears by itself: nothing needs saving when the time comes. Pages, blogs and blog posts, books, units and book pages, FAQ questions and product descriptions can all be scheduled this way.

Use it for an announcement that must not appear early, a launch at a fixed time, or a page you want ready in advance.

Taking content down at a set time

Pages and books can also carry an unpublish date: once it passes, the record is unpublished automatically. The admin has no field for it; a developer sets it through the API. In the admin, take content down by unpublishing it when the time comes.

Time zones

Dates are entered and shown in the time zone set for the site, not your computer's. "9:00" on the site means 9:00 in the site's time zone, wherever you are when you set it. If you work in another time zone, convert before you schedule, and schedule a little early when the exact minute matters.

Scheduling is not a review step

A future publish date is not "someone will check this before it goes live". Nobody will: scheduled content goes live exactly as it stands. Review it before you schedule it.

Keep track of what is pending

Scheduled content is invisible on the site, which makes it easy to forget. Before a launch, look for records with a publish date in the future: the classic failure is a page that was scheduled, then superseded, and goes live anyway saying something no longer true.

Unpublish rather than delete

For anything that might come back, or that someone might link to, unpublishing is the better tool. It can be undone at once, and it keeps the record and its versions.

Was this page helpful?

Your answer goes to the docs team.