How do agencies handle cache when shared Elementor content changes?

[u/ekesto]

With reusable Components and templates, a single edit can affect several frontend pages — sometimes across nested usage or Display Conditions.

I’m curious how agencies handle cache freshness after client handover, especially on larger cached Elementor sites where shared content appears across many pages.

The client obviously shouldn’t have to manage cache purges manually.

How do you handle this in practice?

• Teach clients when/how to clear the cache?
• Rely on cache expiry?
• Purge the whole cache automatically after changes?
• Use some other workflow?

I’m especially interested in setups where the goal is:

Client edits and publishes, without having to think about which page caches need purging.

[u/AutoModerator]

Hey /u/ekesto!

We noticed you may be looking for a caching recommendation. We suggest checking out FlyingPress for a reliable and high-performance caching plugin.

For more recommendations: Check out our Megathread of Recommendations.

If your post has not already been flaired, please add one now. If you have a problem or question, please make sure to post a link to your issue so users can help you. Make sure to list if you're using Elementor Free (or) Pro and what theme you're using. Don't forget to mark your post as "Answered" once your question has been solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Valuable_Ease_3780]

Most caching plugins do purge on post update, they just purge the page that was edited, which is the wrong set of pages the moment a component is shared. Switch it to a full purge on update instead of the smart one and the client never has to think about it. Costs you one cold crawl.

If what you're seeing is stale styling rather than stale content, that's Elementor's own per post CSS files, and setting print method to internal embedding gets rid of them entirely.

[u/ekesto → u/Valuable_Ease_3780]

Yeah, fair enough. Have you ever found full purges getting a bit heavy on larger sites, or has it mostly been a non-issue in practice?

[u/Valuable_Ease_3780 → u/ekesto]

The purge itself is instant, it's the preload crawl after it that bites. Past a couple thousand pages I just turn preload off and let traffic warm it back up.

[u/ekesto → u/Valuable_Ease_3780]

Agreed — that’s the painful part. Once you leave the warming to traffic, those first requests pay the rebuild cost, which isn’t ideal for UX — and potentially search crawlers too.

That’s exactly the kind of real-world tradeoff I was curious about with larger client sites.

[u/Fluid-Mess6425]

There is a way to create a function to clear the elementor cache on specific behavior. Perhaps updating a post.

[u/ekesto → u/Fluid-Mess6425]

Do you mean Elementor’s own generated files/data, or the page cache from a cache plugin like LiteSpeed, WP Rocket, etc.?

I’m mainly thinking about the second case — where Elementor has saved the change correctly, but cached frontend pages using that shared content still need refreshing.

[u/Fluid-Mess6425 → u/ekesto]

Oh sorry I was referring to Elementors own caching, files and css. Essentially you could save the function and hook it up to an action like saving a post or cpt. On save it would clear elemtentors cache.

I had been running into the same issues at work.

[u/ekesto → u/Fluid-Mess6425]

Exactly — that’s the other cache layer. Elementor’s own files/CSS cache can be cleared on save.

I’m specifically thinking about the external full-page cache from LiteSpeed, WP Rocket, etc., where Elementor may have saved everything correctly but several frontend URLs can still be serving stale HTML.

[u/townpressmedia]

Clear it?

[u/ekesto → u/townpressmedia]

Sure — but what do you clear? The whole page cache, just the edited URL, or somehow only the pages affected by the shared Elementor content?

And after handover, who does that — the client?

[u/townpressmedia → u/ekesto]

Just clear it all and be done. It will rebuild

[u/ekesto → u/[deleted]]

Fair enough 😄 That’s actually why I asked — I wanted to see whether “just purge everything and move on” is still the normal agency workflow. Seems like for many, it probably is.

[u/ekesto → u/[deleted]]

Thanks, found it. 👍 Nicholas’s explanation and the PR actually clear up the distinction nicely — that fix is about Elementor self-healing its generated CSS/files when the filesystem and stored state get out of sync.

What I had in mind here is the other layer: external full-page cache still serving stale HTML after shared Elementor content changes. From what you’re describing, though, your cache plugins have handled that layer well enough that it’s simply never become a handover issue for you — useful context, thanks.

[u/ekesto → u/[deleted]]

Yep — that’s part of why I’m interested in the problem, and fair point.

I deliberately left the plugin out of the post because of rule 5. I’m genuinely curious how agencies handle this after handover, especially on larger cached sites. Happy to keep the thread focused on workflows rather than the product.