Deploy your changes

Everything you write or change waits in the dashboard until you deploy (click the Deploy button). Readers see the version you last deployed.

Deploying rebuilds your blog with your latest changes, optimises it for SEO and speed, and puts it online worldwide. For most blogs it takes less than 10 seconds. You can keep working while it runs, or close the dashboard.

Deploy

Click Deploy at the top right of the dashboard.
Wait for the line under the button to change from Deploying to Up to date.

To get an email when a deploy finishes, tick Send email on deploy in Settings > Advanced. It is only sent for deploys that take longer than 15 seconds.

See what is waiting to go live

The line under the Deploy button tells you where your blog stands:

Line	What it means
3 changes	Three things changed since your last deploy. Click it to see which.
Up to date	Your blog matches your dashboard. There is nothing to deploy.
Not live yet	Your blog has never been deployed, so nothing is online yet.
Deploying	A deploy is running. The line counts down the seconds left.

Click the line to see what is waiting, grouped by kind, such as 4 posts updated or 3 categories created, newest first. It covers posts, pages, categories, tags, menu items, redirects, team changes, imports and settings. When more are waiting than the list can show, it ends with and 12 more. Click Deploy now to deploy from the list.

The list of 13 changes not live yet, with the Preview, Close and Deploy now buttons

Deleted items cannot be listed, because they no longer exist. The list says that something was deleted, and deploying removes it from your blog.

To see the changes on your real blog before they go live, click Preview in the same list. See Preview before you deploy.

Deploy once per batch of changes

You do not need to deploy after every edit. Every deploy rebuilds your whole blog, so a deploy with one change takes as long as a deploy with fifty. Make your changes, then deploy once at the end.

If you deploy many times in a short while, Superblog reminds you of this.

If the Deploy button is disabled

The button is turned off when your blog already matches your dashboard.

If you know something changed and the button is still disabled, click the line under it and choose Activate deploy. The button turns back on, and you can deploy.

If a deploy is refused

Message	What to do
A deployment is already in progress	Wait for the current deploy to finish, then deploy again.
Your blog has been deployed a lot in the last day	Wait a little while and deploy again. See Deploy limit.
Your site has reached the deploy limit for trial sites	Upgrade to a paid plan to keep deploying.
Your trial period has expired, or your plan is not renewed	Upgrade, or complete the payment, to deploy again.

Why deploying takes time

When you deploy, your whole blog is rebuilt into small, fast pages, optimised for speed and SEO, and copied to servers around the world. When someone reads your blog, it is served from the location nearest to them. That is what makes the blog fast, and it is why changes go live in a deploy rather than instantly.