Sitecore content not updating after publish: causes and fixes

Short answerWhen published Sitecore content doesn't show on the live site, the item is usually not in a final workflow state, has a publishing restriction, or wasn't published in the right language. If the item did publish, the HTML cache, remote events on content delivery servers, custom code caching, or a CDN is serving the old version. Check the web database first to see which side the problem is on.

This is one of the most stressful Sitecore problems for content teams. The editor clicks publish, Sitecore says it worked, and the live page hasn't changed. Often someone then runs a full-site republish "to be safe", which makes everything slower and usually doesn't fix it.

The trick is to find out where the old content is coming from. There are only two possibilities: the new content never reached the web database, or it did, and something between the database and the visitor is serving an old copy.

First check: is the content in the web database?

In the Content Editor, use the database switcher (bottom right of the Sitecore desktop) to open the web database and find the item. Or check the item in the published target directly. If the new content is there, skip to the caching sections below. If it isn't, the item didn't publish, and the next three sections apply.

1. The item isn't in a final workflow state

Sitecore only publishes item versions that are in a final workflow state, such as "Approved". If the version is still in "Draft" or "Awaiting approval", the publish skips it without any error. The publish dialog still reports success.

Fix: open the item and look at the workflow bar at the top, or check the Workbox. Approve the version, then publish again. If this happens often, show editors where the Workbox is and what each workflow state means.

2. A publishing restriction or the wrong version

Items and versions can have publishing restrictions: "publishable from" and "to" dates, or the "Publishable" checkbox switched off. A restriction set months ago for a campaign is easy to forget.

Fix: on the Publish tab, open Change under Restrictions and check both the item and the version settings. Also check that a newer version exists in the language you're viewing.

3. The wrong language, or a related item wasn't published

A publish only includes the languages ticked in the dialog. On multilingual sites, editors often update one language and publish another. Also, many pages pull content from data source items, images or shared items stored elsewhere in the tree. Publishing the page doesn't publish those unless "Publish related items" is ticked.

Fix: publish with the right languages selected, and tick Publish related items when you've changed a data source item, a media item or a shared component.

4. The HTML cache didn't clear

If the content is in the web database but the page is still old, the HTML cache is a common culprit. After a publish, Sitecore clears the HTML cache for the sites listed in the HtmlCacheClearer configuration. A site that was added later and never included in that list keeps serving cached HTML until the app pool restarts.

Fix: open /sitecore/admin/showconfig.aspx on the content delivery server, search for HtmlCacheClearer, and confirm every site is covered. As a quick test, clear caches with /sitecore/admin/cache.aspx on a non-public server and see whether the page updates.

5. Content delivery servers aren't processing remote events

In a scaled setup, the content management server tells content delivery servers about a publish through the EventQueue table. Each server reads the events and clears its own caches. If one server doesn't process them, it keeps serving old content while the others are fine. This is why "it works on one server but not another" is such a typical symptom.

Common reasons:

  • Duplicate instance names. Each server needs a unique InstanceName setting. Servers cloned from the same image sometimes share one, and then they skip each other's events.
  • A huge EventQueue table. With millions of rows, servers fall behind and catch up late. See Sitecore database growth.
  • Clock differences between servers, which can make servers miss or misorder events.

Fix: check the Sitecore log on the affected server for event queue messages, confirm unique instance names in showconfig.aspx, and clean the EventQueue table.

6. Custom code is caching content

Developers sometimes cache data in static variables, in MemoryCache, or in a custom cache to make pages faster. If that cache isn't cleared on publish, it serves old content until it expires or the app restarts. Navigation menus and footers are typical examples.

Fix: if only some parts of the page are stale, ask a developer to search the code for custom caching and make sure it clears on the publish:end and publish:end:remote events, or switch it to Sitecore's own caching.

7. A CDN or reverse proxy is caching the page

If you use Cloudflare, Akamai, Azure Front Door or a similar service, it may hold the old page for minutes or hours, regardless of what Sitecore does.

Fix: check the response headers in your browser's developer tools for cache status headers. If the CDN is serving the page, purge that URL in the CDN, and agree sensible cache times for HTML pages. Some teams add an automatic CDN purge after each publish.

What not to do

Don't make full-site republishing the default fix. It doesn't help with caching problems, it slows publishing for everyone, and it hides the real cause. See why Sitecore publishing is slow for more on this.

What to do next

Start with the web database check. It tells you in one minute whether to look at publishing or at caching. If the problem keeps coming back, or only happens on some servers, it's usually remote events or a configuration gap, and I can track it down as part of a support engagement.

Prabh

Independent Sitecore developer and administrator. I help agencies and businesses keep Sitecore fast, patched and publishing.

Get in touch

Got a Sitecore problem that won't go away?

Tell me what's happening. You'll get a straight answer on whether I can help, usually within one business day.

Book a free 20-minute call