Sites at Kinsta use our full page and object caching technology to remain lightning fast. By default, the Kinsta Cache is a plugin installed on every site that is hosted by us and is available from the left-hand side of your WordPress admin dashboard. This is used to intelligently clear the cache on appropriate pages of your website. The plugin is required to ensure your site runs smoothly in our environment.
Kinsta cache plugin
Kinsta Cache Plugin Settings
The Kinsta cache plugin is set to work harmoniously with WordPress and our infrastructure, and on most sites won’t need any modifications. This enables automatic clearing of cache on important parts of your site when you make page and post content updates. You can also manually clear the cache on your WordPress site with the following methods.
- Press the “Clear Cache” button within the Kinsta Cache plugin
- Press the “Clear Cache” button on the WordPress admin toolbar
- Clear cache from within the MyKinsta dashboard
Adding Custom Caching URLs
We already purge single pages and key pages such as the home page immediately and impose a minimal throttle time on archive pages. This ensures high availability at all times. However, depending on how your site’s configuration, additional caching rules might be needed. You can add custom paths to purge whenever your site is updated.
1. Add Single Path Custom URL
If you need cache cleared on an exact URL (post or page), you can enter this as a single path rule. Example:
Cache – custom URL single path
2. Add Group Path Custom URL
The group path purges all the URLs which start with that specific URL. This can be especially useful say if you have custom post type and need the cache cleared on it and the posts underneath it. For example, if you add
https://yourdomain.com/custom-post-type/ as a group path URL, then it will purge the cache on the following:
Cache – custom URL group path
You aren’t allowed to add only “/” as a path, as this would trigger a clear of the full site’s cache with a post/page update. Purging all pages would take a significant toll on server resources especially during high load times and frequent publishing schedules. This could also degrade the performance of your site for visitors as it would have to re-cache everything.
If you have clients and prefer they not see any Kinsta branding, you can also white label the plugin.