Your public site keeps copies of recently-viewed pages so visitors don't wait while the database and application rebuilds the same page over and over. Those copies live in two layers:

• Varnish — the fast in-memory layer that sits in front of the site.
• Cloudflare — the global edge layer that delivers your pages from servers near each visitor.

When you publish or update content, the cached copies don't know they're out of date until they expire on their own (which can take hours). Clearing the cache forces the layers to fetch a fresh copy on the next visit.

You almost never need to clear the entire site. Targeted clears (one page, one section) are faster, safer, and don't slow the site down for visitors. Reach for narrow options first.

Click Clear Cache in the top-right of any admin screen.

The dropdown is organized into three scope tiers — pick the one that matches what you actually edited:

If you don't have permission to clear cache, the button will be disabled. Ask an admin if you need access.
 

The top tier is for clearing exactly one URL. Two buttons sit side-by-side, with a list of recently-edited content below them.

Clear Current Page

Visible only when you're editing a piece of content that has a public URL. The button shows up on:

• Articles
• Pages
• Events
• Products
• Classifieds
• Directory listings
• Newsletter issues
• Blogs
• Authors
• Galleries
• Publication editions

It's the solid blue button on the left when both buttons are present. The label beneath ("Just this article", "Just this product", etc.) tells you exactly which page will be cleared.

Use it whenever you've just hit Save on an edit page and want the change live for visitors right now.

Homepage

The button on the right (or full-width if you're not on an editable page). Clears just the site's homepage at /.

Use it when you've changed something that affects the homepage — featured content, newsletter promo, hero block, top headlines.

Recently Edited

A list under the two buttons showing the 12 most recently updated items across articles, pages, events, products, and newsletter issues — site-wide, not just yours.

Each row shows:

• A color-coded badge (Article, Page, Event, Product, Newsletter)
• The title
• When it was last edited ("3h ago", "Yesterday", or an absolute date for older items)

Click any row to clear that one item's cache. This is the fastest way to clear cache for something a teammate just edited without leaving the page you're on.

"Not yet published" rows appear greyed out and disabled. Drafts have no public URL yet, so there's nothing in the cache to clear.

The middle tier is for clearing a group of related URLs at once. The light grey background visually separates this scope from the single-page actions above.

Quick Clears

Eight pre-built buttons cover the common content sections:

Click one and that section's cache is cleared in a single shot.

Use Quick Clears when a structural change ripples through a whole section — e.g., you reorganized topics, edited a shared template, or changed a setting that affects how article pages render.

By URL Pattern

For everything Quick Clears doesn't cover, type a regex pattern that matches the paths you want to clear and press Clear.

The patterns match the URL path only — they don't follow content tags or relationships. If a page's path doesn't literally start with what you typed, it won't be cleared.

Click Show pattern examples to reveal a panel of clickable starting points:

Click an example to drop it into the input, then edit the slugs to match your real path before pressing Clear.

The CSS / JS pattern is useful after a stylesheet or script change. If editors report the site looks broken after a deploy, this pattern forces fresh asset files to load.

The small grey link at the bottom of the dropdown. Clicking it opens a confirmation panel that requires a deliberate "Yes, clear everything" before anything happens.

This is the nuclear option. It invalidates every cached page across Varnish and Cloudflare and rotates the Memcached metakey. Site speed will noticeably degrade for visitors until the caches repopulate — every request has to be rebuilt from the database. On a busy site this can take many minutes.

Only use it when:

• You made a change that affects every page (rare — e.g. a global header/footer update that the section quick-clears don't cover)
• You need a clean slate after a major deploy
• A targeted clear didn't work and you've ruled out other causes

If you're not sure, ask in #engineering or check with someone who is — the cost is real and visible to readers.

Most clears finish in well under a second. You'll see a toast notification in the top-right:

• Green → success. Visitors will get fresh content on their next visit.
• Red → something went wrong. The toast shows the reason; usually it's worth retrying or asking an admin.

The dropdown closes automatically after a successful clear.

Refresh your browser to verify. If you're checking your own change, hit your page in a new incognito window — your normal browser may have its own local cache that's separate from the site cache.

"I cleared the cache but my change still isn't showing"

Try in this order:

1. Hard refresh — Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows). Your browser keeps its own cache.
2. Open an incognito / private window to bypass browser cache entirely.
3. Check whether the change actually saved. Sometimes a save is interrupted by a network blip.
4. Confirm the page is published. Drafts don't appear publicly no matter how often you clear cache.
5. Try Clear Current Page again in case the previous clear hit a slow Cloudflare region.

"I don't see Clear Current Page"

It only appears on edit pages for content types that have a public URL. If you're on the dashboard, a list view, or settings, only Homepage shows in the One Page tier. Use Recently Edited to clear specific items from anywhere in the admin.

"The Recently Edited list is empty"

This site hasn't had recent edits, or the GraphQL query is taking longer than usual. The list reloads every time you open the dropdown.

"My pattern didn't clear what I expected"

Patterns are regex matches against the URL path. They don't follow:

• Topic tags ("clear all articles tagged Food Safety")
• Author relationships ("clear everything by Jane Smith")
• Content groupings other than path

If a topic page is at /articles/topic/food-safety, the pattern ^/articles/topic/food-safety will clear that listing — but it won't also clear individual articles tagged with that topic. For that, you'd run All articles from Quick Clears.

"I see a 404 error after clicking Clear"

The cache reset returned an error from the server. The most common cause is a permissions issue or a mid-deploy state. Try again in a minute, and if it persists, check with engineering.

• Clear narrow first, broad only if needed. A single-page clear is instant and invisible to readers. A site-wide clear makes the site slow for everyone for several minutes.
• Use Recently Edited for teammate changes. When someone says "I just updated X, can you clear it?", open the dropdown, find their item in the list, click. Faster than navigating to the edit page.
• Coordinate big clears. If you're going to use Clear entire site cache, give the team a heads-up so support knows why pages are slow.
• Asset changes need their own clear. Editing a stylesheet or script doesn't get cleared by a content-section quick-clear. Use Show pattern examples → All CSS and JavaScript files.
• Refresh in incognito to verify. Your own browser cache lies to you; visitors aren't seeing what you're seeing.