What “Publish” Actually Does Behind the Scenes

Clicking Publish feels instant, but a few things happen behind the scenes before your change is visible to every visitor. Understanding this helps explain the occasional short delay, and is useful background if you ever need to raise a “my change isn’t showing” query with us.

Step one: saving to the database

When you click Publish (or Update), WordPress immediately saves your content to the site’s database. This part is instant — as far as WordPress itself is concerned, the change has happened.

Step two: caching

To keep the site fast, WP Engine serves most pages from a cache — a saved, ready-to-go copy of the page — rather than rebuilding it from the database on every single visit. This is great for speed, but it means a freshly published change doesn’t always appear the instant you publish it; the cached version needs to be cleared and rebuilt first.

In most cases this happens automatically within moments of publishing — WordPress and WP Engine are set up to clear the relevant cached pages as part of the publish process. Occasionally it can take a short while to fully propagate, particularly on pages that are cached at multiple levels (see below).

Step three: the CDN

On top of WP Engine’s own caching, content is also often distributed through a Content Delivery Network (CDN) — a network of servers in different locations that serve cached copies of your pages and images to visitors from whichever server is closest to them, again for speed. This adds another layer that occasionally needs a moment to catch up with a fresh change, particularly for images.

What this means in practice

• Most published changes appear within a few seconds to a minute.
• If a change genuinely isn’t showing after a few minutes, a hard refresh in your browser (Ctrl/Cmd+Shift+R) is worth trying first — see the separate article on cache and refresh basics, since your own browser can also be showing you an old cached copy on top of everything above.
• If it still isn’t showing after that, it’s worth flagging to us — it’s occasionally a sign the page needs its cache cleared manually on the server side.

Tips

• For urgent, time-sensitive announcements, publish a little ahead of when you need it live, where possible, to allow for this normal short delay.
• Don’t assume a missing change means your edit failed to save — check the post/page itself in the admin first (it will show your latest content there regardless of caching) before assuming something’s gone wrong.
• If you’re regularly waiting a long time for changes to appear, let us know — that’s not normal and worth investigating.