Skip to content
Tutorials Center
My learning

Topics

Lesson 33 of 37 ยท Publishing and Maintenance

Publishing, Staging and Backups

Learn safe publishing in Wix and Webflow: staging, site history, backups and restores, team roles, change control and a release routine, with runnable version and permission stand-ins.

A site is never "done"; it is maintained. Prices change, posts are added, a manager wants a new banner. The risk is not the first publish but the hundredth: someone edits the wrong page, deletes a collection, or pushes half-finished work live. Good habits for publishing, restoring and sharing access make a site safe to change.

Wix and Webflow are hosted and cannot run on this site. Feature names and availability depend on the plan and may change; check each platform's current documentation. The runnable code is stand-in logic for versions, backups and permissions.

Publishing basics

Editing does not change the live site. You work in the editor, and publish to push changes live.

  • Webflow: the Publish button in the Designer lets you choose the domains to publish to (the free webflow.io staging domain, your custom domains, or both). Webflow publishes the whole site, with the exception of things such as CMS items marked as draft. CMS items and ecommerce data can be published separately from the Designer in the Editor.
  • Wix: the Publish button publishes the whole site. Some changes (apps, the store, blog posts, data collections) update live right away in the dashboard, independent of the editor. Check whether a setting is live immediately.

Two habits help everywhere: review the page in Preview (and on a real phone) before publishing, and publish at quiet times.

Staging

A staging site is a private copy for testing before the public sees a change.

  • Webflow gives every site a free yourname.webflow.io staging domain, which you can publish to separately from the custom domain. Use it for review by clients and teammates (hide it from search engines by keeping indexing off on that domain, a setting in the site settings). Newer Webflow features may include branching or similar workflows on higher plans.
  • Wix Studio offers features such as site duplication and, in Studio for agencies, workspaces and collaboration tools. On the classic Wix Editor you can duplicate the site and work on the duplicate. Connecting a custom domain to a copy is a deliberate step.

A staging copy of an ecommerce site has its own orders and data, so decide how to keep content in sync, and never test payment settings with live cards (use test mode and test payments where available).

Version history and restore

Both platforms keep earlier versions.

  • Webflow: Backups are saved automatically when you publish, and you can create manual backups. You can restore a backup (this affects the Designer content; CMS content and ecommerce data have their own considerations, so read the notes on the restore screen before you proceed) and clone a backup into a new site to compare versions without overwriting.
  • Wix: Site History (in the editor's menu) lists saved versions with dates, so you can preview and restore an earlier one. Autosaves happen frequently, and you can name a save.

Restoring replaces current work, so before you restore, back up the present state first.

Your own backup

Platform history is not a substitute for a backup you control. Habits:

  1. Export CMS collections as CSV (both platforms allow exports of CMS or database content).
  2. Export store products and orders to a spreadsheet regularly.
  3. Keep copies of originals of images and brand files.
  4. Keep an "operations document" with plan details, domain registrar, DNS records, integrations, logins' owner, and renewal dates.
  5. Know whether code export exists: Webflow can export the front-end code (HTML, CSS, JS) on eligible plans, but dynamic features (CMS, ecommerce, forms) do not run from the export. Wix does not offer a code export of the site.

Roles and permissions

Give each person the least access needed.

  • Webflow: workspace members and site-level access; roles such as Designer, Editor (content-only, edits text and CMS items in a simpler interface), and ecommerce or billing access. Clients often get Editor access so they cannot break the layout.
  • Wix: site collaborators with roles such as Admin, Designer, Content Manager, and custom roles with permissions you pick (on supported plans).

Use two-factor authentication on the owner account, and keep billing under an account that survives staff changes.

The stand-in below models a permission check so you can see the idea of least privilege.

JS Stand-in: role permissions

Press Run (or Ctrl + Enter) to see the console output here.

No output.

A version log

Teams that publish often keep a short change log. This stand-in records releases and reports which one to restore.

JS Stand-in: release log

Press Run (or Ctrl + Enter) to see the console output here.

No output.

A safe release routine

  1. Make changes (on staging or a duplicate for large work).
  2. Run the checklist (see Accessibility and Launch Checklist): links, forms, mobile, speed.
  3. Create a manual backup or named save.
  4. Publish to staging, review, then publish to production.
  5. Test live pages: home, a form, a purchase, a redirect.
  6. Note the change in your log.
  7. If something breaks: restore the previous version, then repair calmly.

Planned maintenance

  • Monthly: check forms, broken links, payment flows, and that backups exist.
  • Quarterly: audit apps and scripts, remove unused ones, review user access.
  • Yearly: renew domain and plan, review content and SEO, update copyright dates.

Common mistakes

  • Editing the live site's structure during busy hours.
  • Giving clients full designer access.
  • Restoring without taking a fresh backup first.
  • Never exporting CMS or store data.
  • No record of who owns the domain and the payment account.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a staging site allow?

    Staging is a safe copy for review before public release.
  2. 2. What should you do before restoring an old version?

    Restoring overwrites current work, so save the present state first.
  3. 3. A client who edits blog text should usually get which kind of access?

    Least privilege lets them change content without risking the layout or billing.
  4. 4. Is platform version history a replacement for your own exports?

    You control your own backups, which survive account or platform problems.

Summary

  • Editing is not publishing; review in preview and on staging first.
  • Use version history and manual backups, and also keep your own exports.
  • Grant least-privilege roles and secure the owner account.
  • Follow a repeatable release routine and schedule regular maintenance.

Next: Accessibility and Launch Checklist