Changes not showing on the website

You changed something in Salesforce, the record looks right, but your website still shows the old version. Sync is usually a matter of seconds, so a change that is correct in Salesforce and wrong on the site is almost always one of a small number of publishing or timing causes.

Work through these checks in order. Most cases are resolved by the first two.

1. Check the change was published

Changes made in the Website Builder do not affect your live site until someone with approver access sets the Content Change records to Published. Until then the change exists only as a pending change, visible to you in the builder and to nobody else.

This is the single most common cause. If the change looks perfect in the builder but the live site never reflects it, check whether it was ever published.

:::note The Website Builder deliberately shows you current content rather than a cached copy, so it always looks up to date. Looking correct in the builder tells you the change was saved. It does not tell you the change is live. :::

2. Allow a moment for the cache

Your storefront holds rendered pages and page sections in a short-lived cache so that it loads quickly. After a change goes live, allow up to a minute for the site to pick it up, then reload.

If a minute passes and the page is still wrong, move on to the next step.

3. Clear your store’s cache

You can clear your store’s cache yourself, without contacting support.

1. Open the Store record in Salesforce.
2. Find the Cache Version field.
3. Change it to any different value. If it currently reads 1, set it to 2.
4. Click Save.

Any new value works. The value itself has no meaning; changing it is what discards the cached copies for that store.

This is also the fix to reach for when you changed content outside the Website Builder, for example by editing content blocks directly on their Salesforce records. Publishing from the builder clears the cache for you, and editing records directly does not, so the site can keep serving the previous version until the cache expires on its own.

:::note Publishing a content change clears the cache automatically, so you only need this step when a change did not go through the Website Builder. How many stores publishing covers depends on the scope of the publisher’s Store Role: a single store, every store in a store group, or every store. :::

4. Rule out your own browser

Check the page in a private or incognito window.

• Correct in a private window, wrong in your normal one. Your browser is holding an old copy. A hard reload usually fixes it, or clear your browser cache.
• Wrong in both. The cache on your store has not cleared yet. Go back to step 3.

Styling and layout are a special case. Your browser keeps your theme’s stylesheet and scripts for a long time on purpose, because those files rarely change. If new content appears but looks wrong, unstyled, or partly broken, your browser is pairing new content with an old stylesheet. Theme developers must give the updated file a new filename for returning visitors to receive it, which is covered in theme resources.

5. Products or categories missing from search and listings

Product search results, category listings, and sale prices shown on product cards are built from a search index that rebuilds on a schedule rather than instantly.

A product can be correct in Salesforce, synced, and visible on its own product page, while still being absent from search results or a category listing. The same applies to a new discount: the correct price is charged in the cart and shown on the product page before the discounted price appears on a product card.

The index rebuilds automatically every few hours, so this normally resolves without any action. If more time than that has passed, you can request an index rebuild.

Changing the Cache Version field does not affect this index. It is a separate system.

6. Article or page text not appearing in search

When you edit the body text of a content page or article, the page itself updates as normal, but the searchable text behind it is refreshed about once a day. For a short period a search may still match the old wording, or fail to match new wording, even though the page reads correctly when opened.

No action is needed. This catches up on its own.

Still not showing

If you have worked through every step above and the site is still wrong, the cause is probably not caching. Check for a sync error on the record using the sync error tool, then contact support with the store, the record, the change you made, and the time you made it.