Manage site updates

An edit to your storefront never goes live the moment you make it. Whatever method you use to make a change, StoreConnect stages the edit, and a person has to approve and publish that change before your visitors see it.

Use this section to understand that path, and to find the article for whichever end of it you are working on.

Ways to make site changes

• The Website Builder. Edit pages and rearrange content blocks while seeing how the result looks, then submit the change for review. See edit your site with the Website Builder.
• Salesforce records. Edit pages, content blocks, articles, and menus directly on their records. Suited to bulk work and to fields the builder does not expose.
• An AI agent. An agent connected over MCP stages its work as a content change and submits it for you to review. See Connect an AI agent to your store.

Regardless of how a change is made, it always goes through the same process.

Edit site content record > Submit change > Review and preview > Approve or reject > Publish > changes go live

:::note Editing a record directly in Salesforce, outside the Website Builder and outside an agent, applies immediately and runs no publish step. That also means it does not clear your storefront cache, so the live site can serve the old version for a while. Usually only admins can do this. See changes not showing on the website. :::

In this section

• Edit your site with the Website Builder
• Review and approve a content change