If a page you just updated still shows the old version, you have a cache problem. The fix takes about 30 seconds once you know where to look — but clearing the wrong cache at the wrong time can cause a new set of problems. This guide covers browser cache, plugin cache, and host-level cache in one place, with steps for every major setup.

What is WordPress cache and why does it exist?

When someone visits your site, their browser downloads your HTML, CSS, images, and scripts. Caching saves copies of those files so the next visit is faster — the browser loads from local storage instead of hitting your server again. That’s browser caching. Your server does something similar with server-side caching: it generates static HTML from your dynamic WordPress pages and serves that pre-built version to every visitor, skipping the database queries each time.

Both types of caching are good for performance. The problem is that cached files are old by definition. When you update a post, change a menu, or push a plugin update, the cached version of your site doesn’t know that yet. You’re looking at the live version in your admin panel; your visitors — and crawlers — are looking at whatever was cached last.

The crawl dimension most people ignore

Most articles on cache focus on what human visitors see. But search engine and AI crawlers hit the same cached pages. If Googlebot or GPTBot visits while your cache is stale, they index the old version. Updated content doesn’t get picked up until the next crawl — which, for lower-priority pages, could be weeks away. A cache that’s never cleared means your freshness signals decay even when you’re actively publishing. Linkilo’s Crawl Log Analyzer shows you exactly when Googlebot and AI bots last visited each page, so you can tell whether a crawl picked up your updates or was served an old cached version.

When you actually need to clear your cache

Not every cache problem requires clearing everything. Here are the situations where a cache clear is the right call:

When to clear vs. when to wait

Situation Clear which cache Why
Updated a post and changes aren’t showing Plugin or host cache first, then browser Server cache is serving the old page to everyone, not just you
Changed your theme or CSS Plugin/host cache + browser hard refresh Style files are cached separately; a full clear ensures both hit
Added or removed a redirect Host cache and CDN (if applicable) Cached redirect chains survive URL changes and can confuse crawlers
Debugging a site issue someone else reported Browser cache only (yours) You need to see what they see, not your personal cached version
Site running normally, no recent changes Don’t clear anything Clearing cache without cause forces your server to rebuild pages, temporarily slowing load times

How to clear your browser cache

Browser cache only affects what you see in your own browser. It doesn’t change what other visitors or crawlers see. Clear it when you’re troubleshooting something that looks different on your machine than it does elsewhere, or when you want to verify that a server-side change actually went through.

Chrome

Press Ctrl+Shift+Delete (Windows) or Cmd+Shift+Delete (Mac) to open the Clear browsing data panel directly. Set the time range to “All time,” check “Cached images and files,” uncheck everything else unless you specifically want to clear cookies too, then click “Clear data.” Alternatively: three-dot menu → More tools → Clear browsing data.

For a quick force-refresh without clearing all cache: Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) reloads the page while bypassing the cache for that single page load.

CiteTrack AI Chrome Extension

If you want to clear your browser cache and immediately audit the page for SEO, AEO, and GEO signals in one step, the CiteTrack AI Chrome Extension handles both. It clears browser cache directly from the extension, captures a screenshot of the current page state, and runs a full on-page audit covering traditional SEO signals alongside AI citation and geo-relevance signals. Install it from the Chrome Web Store. Useful when you’ve pushed a content update and want to verify what the page looks like cache-free while simultaneously checking whether it’s optimized for AI-driven search.

Firefox

Hamburger menu → Settings → Privacy & Security ₒ scroll to “Cookies and Site Data” → click “Clear Data” → check “Cached Web Content” → click Clear. Firefox also supports Ctrl+Shift+R / Cmd+Shift+R for a force-reload on a single page.

Safari

Safari menu → Settings → Advanced tab → check “Show Develop menu in menu bar” → then Develop → Empty Caches. On iOS: Settings → Safari → Clear History and Website Data (this clears cookies too, which is a downside).

How to clear your WordPress plugin cache

Plugin cache is the one that actually matters for what visitors and crawlers see. If your caching plugin is storing an old version of a page, every request — human and bot — gets that old version. Here’s how to purge the most common ones.

WP Rocket

In your WordPress admin bar, click the “WP Rocket” dropdown that appears when the plugin is active, then select “Clear cache.” Alternatively: Settings → WP Rocket → Dashboard tab → “Clear cache” button. WP Rocket also lets you clear cache for a single post from the post editor — useful when you’ve updated one article and don’t want to dump the whole site cache.

W3 Total Cache

Performance menu in your admin sidebar → Dashboard → “Empty all caches” button at the top of the page. W3 Total Cache has several cache types (page, object, database, minify) — the dashboard button clears all of them at once.

WP Super Cache

Settings → WP Super Cache → Contents tab → “Delete Cached Pages” button. The plugin shows you a count of cached files before you clear, which is useful for auditing how much is being stored.

LiteSpeed Cache

LiteSpeed Cache adds a toolbar item when active. Click “LiteSpeed Cache” in the admin bar → “Purge All.” You can also purge from the plugin settings: LiteSpeed Cache → Manage → Purge All.

Autoptimize

Settings → Autoptimize → scroll to the bottom of the options tab → “Delete Cache” button. Autoptimize primarily caches minified CSS and JS files, so clear it after any theme or script changes.

How to clear cache at the hosting level

Managed WordPress hosts build caching directly into their infrastructure, separate from any plugin. If you’re on one of these hosts, you need to clear at the host level — plugin cache clears alone may not be enough.

WP Engine

In your WordPress admin bar, “WP Engine” menu → “Purge all caches.” Or from the WP Engine User Portal: select your install → “Utilities” tab → “Clear all caches.” WP Engine’s cache is server-level and bypasses plugin caches entirely, so this is the one that counts on their platform.

Kinsta

Kinsta adds a “Kinsta Cache” button to your WordPress admin bar when you’re logged in. Click it → “Clear cache.” You can also clear from the MyKinsta dashboard: select your site ₒ “Tools” → “Clear cache.” Kinsta automatically clears cache when you publish or update content, but manual clears are useful after plugin or theme changes.

Bluehost

In your WordPress admin bar, hover over “Caching” → “Purge All.” If you’re using Bluehost’s built-in caching (not a separate plugin), this is the only purge option you need.

SiteGround

SiteGround’s caching (SuperCacher) is controlled from the SiteGround dashboard, not your WordPress admin. Log into Site Tools → Speed → Caching → Dynamic Cache tab → flush the cache icon next to your domain. SiteGround also offers the SG Optimizer plugin, which lets you purge directly from the WordPress admin bar.

How to clear Cloudflare cache

If your site runs behind Cloudflare, its CDN caches static assets (images, CSS, JS) at the edge. Clearing your plugin or host cache doesn’t touch Cloudflare. You need to purge it separately.

Cloudflare dashboard → select your domain → “Caching” in the left sidebar → “Configuration” → “Purge Cache.” You can purge everything (“Purge Everything”) or specific URLs (“Custom Purge”). Purge Everything is the safe default; Custom Purge is useful when you know exactly which files changed and want to avoid the performance hit of rebuilding the full cache.

If you use the Cloudflare WordPress plugin, you can also purge from the plugin settings inside your WordPress admin.

One cache problem that breaks internal links specifically: when you change a URL and set up a redirect, but your caching plugin still serves the old URL from cache. Visitors hit the cached old URL, get a 200 response (because cache serves it), and your redirect never fires. This is common after permalink changes, slug updates, or post moves.

If you’ve recently changed URLs on your site and redirects don’t seem to be working, clear your plugin and host cache first before assuming the redirect configuration is wrong. The redirect is often fine — the cache is just serving the old destination before the redirect chain can run.

Key Takeaways

  • Browser cache only affects your own view. Plugin and host cache affect what everyone — including crawlers — sees.
  • Clear server-side cache after publishing updates, changing your theme or CSS, or modifying redirects. Don’t clear it unnecessarily — it forces a full page rebuild and temporarily increases load times.
  • Managed hosts (WP Engine, Kinsta, Bluehost, SiteGround) have their own caching layer on top of any plugins. Clear at the host level, not just the plugin.
  • Cloudflare and other CDNs cache at the edge and require a separate purge — plugin and host cache clears don’t reach them.
  • Stale cache causes redirect failures. If a changed URL isn’t redirecting, clear cache before debugging the redirect itself.
  • Search bots and AI crawlers see cached pages. If you’ve updated content and want it picked up on the next crawl, clear the server cache and submit the URL via Google Search Console.

Frequently Asked Questions

Common questions about WordPress cache, when to clear it, and what breaks when you do

Does clearing cache delete my content?

+

No. Clearing cache deletes temporary copies of your pages — it doesn't touch your posts, pages, images, or database. After you clear cache, WordPress simply regenerates fresh copies of those pages on the next visit. Your content is always in the database, not the cache.

How often should I clear my WordPress cache?

+

Only when you need to — not on a schedule. Most caching plugins automatically invalidate cache for posts you update. Manual clears are for theme changes, CSS edits, redirect changes, or troubleshooting. Clearing cache unnecessarily forces your server to rebuild everything from scratch, which temporarily increases load times for your visitors.

Why do changes show for me but not other visitors?

+

Because most caching plugins bypass the cache for logged-in users. When you're logged into WordPress, you see the live version. Logged-out visitors — and all crawlers — see the cached version. This is the most common source of confusion when updating content. Clear the server-side cache to make the update visible to everyone.

Does clearing cache hurt my SEO?

+

Not directly. Cache clears don't signal anything to Google. However, immediately after a full cache purge, your server generates fresh pages on first visit — which can slow response times temporarily if you have high traffic. That brief slowdown could affect Core Web Vitals if Googlebot happens to crawl during that window. For large sites, consider clearing cache during low-traffic periods.

My caching plugin says cache is cleared but changes still aren't showing. Why?

+

You have multiple caching layers. In order: clear your plugin cache, then your host-level cache (WP Engine, Kinsta, Bluehost, SiteGround each have their own), then your CDN cache (Cloudflare or similar), then your browser cache. Each layer is independent. Clearing one doesn't touch the others. Work through them in that order until the change appears.

Will Google pick up my changes faster if I clear cache?

+

Clearing cache ensures Googlebot sees your updated content when it next visits — but it doesn't trigger a crawl. To request a faster recrawl, submit the URL via URL Inspection in Google Search Console after clearing cache. That combination (fresh cache + manual submission) is the fastest path to getting an update indexed.