Feature request: exact URL-level cache purge API for Speed Optimizer

ekesto
(@ekesto)

3 days, 5 hours ago
Hi SiteGround team,

I’m the developer of Cache Autopilot, a WordPress cache freshness plugin that works alongside existing cache plugins.

Cache Autopilot determines which frontend URLs are affected by a WordPress change, purges only those pages through the active cache plugin, and then preloads them again in the background.

I had a closer look at Speed Optimizer and saw that you already expose:
```
sg_cachepress_purge_cache( $url );
```
The only issue for our use case is that the Dynamic Cache implementation also purges descendant paths. For example, purging:
```
/blog/
```
can also purge:
```
/blog/page/2/
/blog/child/
```
For Cache Autopilot, we need an integration point that purges only the supplied frontend URL while leaving unrelated descendants cached.

Would you consider exposing an exact-URL mode through the public API?

For comparison, some of the cache plugins we currently support expose integrations like:
```
// Cache Enabler
\Cache_Enabler::clear_page_cache_by_url( $url );

// LiteSpeed Cache
do_action( 'litespeed_purge_url', $url );

// FlyingPress
\FlyingPress\Purge::purge_urls( [ $url ] );
```
The idea is simply: Cache Autopilot determines the affected URL, and the cache plugin remains fully responsible for invalidating that URL through its own cache logic.

I’m happy to handle the integration and testing on the Cache Autopilot side.

Cache Autopilot:
https://wpcacheautopilot.com/
https://wordpress.org/plugins/cache-autopilot/

Best regards,
Beat Schenkel

Viewing 2 replies - 1 through 2 (of 2 total)

Plugin Support miroslavtyurdiev
(@miroslavtyurdiev)

2 days, 7 hours ago
Hi Beat,

Thanks for reaching out and taking the time to build integration support for Speed Optimizer in Cache Autopilot!

After careful consideration from our development team, we won’t be adding an exact-match purge parameter or API option, as the current behavior is an intentional design choice within our caching architecture.

In Speed Optimizer, clearing a target URL along with its descendant paths ensures that no stale cached content is left behind across the URL hierarchy (such as sub-pages). Maintaining these invalidation safeguards is key to preventing cache inconsistencies across SiteGround-hosted sites, and exposing an exact-match purge could bypass those protections.

Because of this, sg_cachepress_purge_cache( $url ) remains our standard public integration function. While we understand this broad invalidation scope differs from exact-URL clearing, we encourage you to utilize the existing function while accounting for its hierarchical purge behavior in your plugin’s logic.

We really appreciate your feedback and your efforts to support Speed Optimizer!

Best Regards,
Miroslav Tyurdiev
- This reply was modified 2 days, 7 hours ago by miroslavtyurdiev.
Thread Starter ekesto
(@ekesto)

2 days, 3 hours ago

HI Miroslav,

Thanks for checking this with the development team and for the detailed explanation. I understand the architectural reasoning. Unfortunately the hierarchical purge behavior doesn’t fit Cache Autopilot’s targeted invalidation model, so we’ll leave Speed Optimizer unsupported for now. Thanks again for taking the time to review it.

Best wishes,
Beat

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Tags