Overview
This article helps you understand website caching on Access Volcanic and how it affects content updates. Caching temporarily stores copies of pages and data to speed up delivery and improve site resilience. Access Volcanic websites use both browser caching and platform caching via Varnish Cache, which can delay the visibility of recent edits for approximately two hours.
Key benefits
Deliver faster page loading times and improved user experience across your website.
Maintain website accessibility during temporary platform disruptions for approximately two hours.
Provide search engine crawlers with consistent access to stable, cached content.
Support better SEO performance through faster page delivery and reliable uptime.
Provide a correction window that may allow minor mistakes to be fixed before reaching all users.
Ensure resilience during incidents by serving cached versions when needed.
Before you start
Before working with cached content, make sure you understand:
Your website uses both browser caching and platform caching automatically.
Changes made in Staging typically take approximately two hours to appear live.
Platform caching cannot be disabled and applies to all Access Volcanic websites.
📌 Note: Manual cache clear by Support is available for urgent business-critical cases only and should be used sparingly as it can temporarily affect performance.
Understanding how caching works
Caching works through a two-layer system that stores copies of your website content.
Browser caching
Browser caching saves a local copy of pages and assets on each visitor's device to speed up repeat visits.
If your recent changes aren't visible, try a hard refresh, open the page in Incognito or Private mode, or clear your browser cache in the browser's settings.
Platform caching with Varnish Cache
Varnish Cache is a server-side system that stores page copies for approximately two hours.
When a visitor requests a page, Varnish Cache fetches it from the application, stores a copy, and serves it to visitors until it expires.
This prevents regenerating pages repeatedly and keeps your website fast and stable.
Edits normally appear on the live site within approximately two hours as the platform cache expires naturally.
Working with Staging and Primary Domains
Understanding the difference between Staging and Primary Domains helps you manage content updates effectively.
Using Staging for content preparation
Staging provides a safe environment to prepare and review changes before they go live.
Updates made in Staging generally appear on the live site within approximately two hours after publishing due to platform caching.
Use Staging for content work to avoid disrupting active users.
Making urgent updates on Primary Domain
Changes on the Primary Domain are visible almost immediately after a page refresh, subject to browser cache.
Use Primary Domain for quick changes or urgent updates.
If changes don't appear immediately, refresh the page and clear your browser cache.
🤓 Tip: If you're stuck on a Staging URL, switch to your Primary Domain by replacing the staging URL with your main website address. If you keep being redirected to Staging, refresh or clear your browser cache and cookies.
Verifying and managing content visibility
Follow these steps to check if your changes are visible and expedite updates when necessary.
Standard verification process
Check in Incognito or Private mode to bypass your browser cache.
Perform a hard refresh of the page using your browser's specific method.
Clear your browser cache in your browser settings if needed.
Wait approximately two hours for the platform cache to expire naturally.
For urgent visibility requirements
Publish changes on the Primary Domain and refresh the page.
Clear your browser cache and recheck the page.
Contact Support for a manual cache clear only if the change is business-critical and cannot wait.
⚠️ Important: Manual cache clear can temporarily affect platform performance as caches rebuild, so use this option sparingly for genuine emergencies only.
Expected update timelines
Understanding typical timelines helps you plan content releases and manage expectations.
Standard content updates
Expect approximately two hours for platform cache expiry before all users see changes. Plan content releases such as blog posts with this window in mind.
Urgent content changes
Make edits on the Primary Domain and refresh the page. If changes still aren't visible, clear your browser cache. For exceptional business-critical needs, contact Support to discuss a manual cache clear.
📌 Note: Support can perform a manual cache clear on a case-by-case basis for urgent needs, but this should be used sparingly due to potential performance impacts.
Service continuity during outages
Caching provides resilience during temporary platform issues.
Candidates can still apply for jobs during short-term incidents because cached pages remain accessible and functional until cache expiry.
Visitors can often continue browsing normally during temporary disruptions because the cache serves stable copies for approximately two hours.
Best practices
Follow these guidelines to work effectively with website caching.
Plan content releases with a two-hour cache window in mind.
Use Staging for routine edits and reserve Primary Domain edits for urgent changes.
Verify visibility with Incognito mode, hard refresh, or browser cache clearing before escalating.
Contact Support for manual cache clear only for urgent business-critical cases.
Allow sufficient time for cache expiry when fixing broken links before re-running SEO crawlers.
Document your edit location and timing to help with troubleshooting.
📌 Note: Platform caching applies automatically to all Access Volcanic websites and cannot be disabled, as it's essential for performance and resilience.
FAQs
Q1: What is Varnish Cache in simple terms?
Answer: Varnish Cache is a web application accelerator that sits in front of your website to cache and serve pages quickly, typically for approximately two hours.
Q2: Why do I see changes in the Admin Area but not on the live site?
Answer: The Admin Area shows your unpublished changes immediately, while public users still see the previous cached version until it expires naturally within approximately two hours.
Q3: Do I always need Support to make changes visible?
Answer: No, most of the time allowing the cache to expire naturally or using browser cache workarounds is sufficient. A manual cache clear is reserved for urgent cases only.
Q4: Does caching help with SEO performance?
Answer: Yes, faster and more reliable pages support better user experience and when search engines scan your site, which are positive factors for search performance.
Q5: How long do cached pages stay available during outages?
Answer: Cached pages remain accessible for approximately two hours during temporary platform disruptions, allowing visitors to continue browsing and candidates to apply for jobs.
Q6: Can I disable caching on my Access Volcanic website?
Answer: No, platform caching cannot be disabled as it's essential for website performance, resilience, and user experience across all Access Volcanic websites.
Q7: What's the difference between browser cache and platform cache?
Answer: Browser cache stores copies on individual visitors' devices for faster repeat visits, while platform cache uses Varnish Cache on the server to store copies for all visitors for approximately two hours.
Q8: When should I contact Support about cache clearing?
Answer: Contact Support for a manual cache clear only when changes are business-critical and cannot wait for the natural two-hour expiry period. This option should be used sparingly due to potential performance impacts.
Q9: My changes aren't appearing on the live site. What should I do first?
Answer: First check where you made the edit - if you edited in Staging, allow approximately two hours for platform cache expiry. Then view the page in Incognito or Private mode to bypass your browser cache completely, and perform a hard refresh or clear your browser cache entirely.
Q10: What advanced troubleshooting steps can I try?
Answer: Try front-end Edit mode if available, as some websites allow front-end editing, which may show changes faster than Admin Area edits. For urgent visibility, publish on Primary Domain and refresh, or contact Support to evaluate a manual cache clear.
Q11: I fixed broken links, but my SEO crawler still shows errors. What should I do?
Answer: Wait at least two hours for the cache to refresh after fixing broken links, then re-run your SEO crawler. The cached versions of pages may still show the old broken links until the cache expires naturally.
Q12: How do I force my changes to appear immediately?
Answer: Check the page in Incognito or Private mode, perform a hard refresh, clear your browser cache, and wait approximately two hours for platform cache expiry. For truly urgent business-critical changes, publish on Primary Domain and contact Support for evaluation.