Deploying Your Site

Editing content does not change your live site by itself. Deploying is the step that pushes your current pages, posts, docs, navigation, and templates to the edge, where visitors see them. Deploys are fast — a few seconds — and safe, with a preview before anything goes live.

How deploying works

When you deploy, SpiderPublish publishes your site to Cloudflare's global edge. Your pages are served from Liquid templates close to your visitors, so the site is fast everywhere. There is no per-site build step, which is why a deploy completes in roughly two to five seconds.

Preview, then confirm

A deploy is a two-step, safe action:

  1. Preview — SpiderPublish builds a preview and gives you a link plus a summary of what is changing. Inspect it.

  2. Confirm — when it looks right, confirm, and the changes go to production.

This means you always see exactly what will go live before it does — whether you are clicking in the dashboard or letting an agent do it.

Ways to deploy

  • Dashboard — deploy from the content area; you get a preview screen and a confirm button.

  • CLI — spideriq content deploy previews, shows a diff, and prompts before going to production. For automation, pass a confirmation token from a prior preview, or use the non-interactive flags.

  • MCP / agents — the deploy tools (content_deploy_site and the preview/production pair) let an agent deploy with the same preview-and-confirm protection. Check the last deploy's status with content_deploy_status.

Publish vs deploy

Two distinct steps often happen together:

  • Publishing a page or post changes its state from draft to published in your content.

  • Deploying pushes the current published content to the live edge.

A typical flow is: edit → publish the page → deploy the site.

Tips

  • Deploy after a batch of edits. You do not need to deploy after every small change; publish your edits, then deploy once.

  • Use the preview link. Open it and click through before confirming, especially after big changes.

  • Automate carefully. Deploys are scriptable; keep the final confirm gated for anything customer-facing.

Next steps