Disclosure: This article contains affiliate links. I may earn a commission if you buy through them. This is a researched guide, not a claim of hands-on testing.
SiteGround backups and caching solve different problems. Backups help recover from mistakes or failures. Caching helps serve reusable content efficiently. You need both configured appropriately, and neither removes the need to test changes.
If this operating setup fits your needs, check the current SiteGround offer while you compare the requirements below.
Know the backup service you have
The current backup guide describes up to 30 daily copies on shared hosting and up to seven on Cloud hosting. Standard restore options are included. GrowBig and higher plans have five manual-backup slots. Premium Backup adds extra functions, including download access and additional points.
These details are plan-specific. Website Builder uses a separate recovery workflow from Site Tools. Identify the actual product you use before following a tutorial for a different dashboard.
Choose a restore scope deliberately
The Site Tools guide distinguishes restoring all files and databases from restoring particular files, databases, or mailboxes. A full-site restore replaces current data with the selected point. It can therefore remove work created after that point.
For WordPress, posts and settings live largely in the database, while themes, plugins, and media live in files. Restoring only one layer may not reverse the relevant change. Diagnose the problem before selecting scope.
For stores and membership applications, preserve recent orders and registrations before a database rollback. If uncertain, ask support. An old working version is not automatically safe to apply over newer transaction data.
Take a checkpoint before changes
Create a manual point when the plan supports it before a theme switch, significant update, or import. Keep an independent files-and-database archive if longer retention or portability matters.
The official guide warns that deleting a site removes access to its backups. Download or manually preserve the site before deletion. Do not rely on the host to retain an accessible archive after cancellation.
Understand the cache layers
SiteGround documents static delivery, dynamic full-page caching, and Memcached. Speed Optimizer provides controls for its WordPress environment. CDN caching is another layer serving content from distributed locations.
A cached page can avoid repeating work for each visitor. A personalized account page cannot safely be treated like a public article. Default exclusions and application compatibility matter more than maximizing the number of cached requests.
Keep personalized content out of public cache
Check cart, checkout, login, and member pages. Verify they show the right visitor’s information and are excluded where required. Do not remove private or no-cache controls merely to improve a performance score.
If a plugin sets a session cookie on every page, it may reduce cache effectiveness. Investigate whether that behavior is necessary and ask the developer for guidance. Removing security or personalization controls without understanding them can create worse problems than a slow page.
CDN requirements are separate
The current SiteGround CDN guide requires SiteGround nameservers. It also distinguishes Premium features from the free service. If you use another DNS provider, verify what that means before enabling the CDN.
Moving nameservers moves responsibility for the whole DNS zone. Preserve mail and verification records first. Do not activate a cache feature at the cost of breaking business email.
Purge the correct cache after changes
SiteGround documents flushing Dynamic Cache through Site Tools and controls in Speed Optimizer. Memcached and CDN have separate controls. Browser cache is yet another layer.
If an old design remains visible, identify where the old response is stored. Purging only your browser may not affect other visitors. Purging every layer repeatedly without checking the cause can also make diagnosis confusing.
After restoring a backup, clear relevant caches so you can assess the recovered version. Test logged out because administrator views can bypass cache and show a different result from the public page.
A safe change routine
- Record the current working behavior.
- Take an appropriate backup.
- Make one significant change at a time.
- Test the affected functions.
- Purge the relevant cache.
- Check public desktop and mobile views.
- Keep the recovery point until verification is complete.
For content updates, confirm the new article text appears. For layout work, test archives and navigation too. For stores, validate transaction functions separately from cached page rendering.
Measure performance responsibly
Compare the same page under comparable conditions. A logged-in uncached request and a logged-out cached page are different workloads. Do not conclude a host is faster from one score taken under different conditions.
Use performance evidence to identify actual bottlenecks. Oversized images, unnecessary scripts, and inefficient plugins can remain slow even on a well-configured cache. Fix the application as well as delivery.
Frequently asked questions
Does a backup clear the cache?
Recovery and cache invalidation are separate concerns. Follow the supported restore process and verify the public version afterward.
Are backup downloads always included?
The current guide describes download access as a Premium Backup function. Check your plan and service.
Should checkout be cached like an article?
No. Personalized and transactional pages need appropriate exclusions.
Use the tools for their actual jobs
Make recoverable copies before risky edits and cache only content that can safely be reused. A clean, reliable site depends on disciplined testing as much as the host’s feature list.
Next step
Check SiteGround through my affiliate link against the requirements above before purchasing. Compare the current checkout and renewal terms, and keep a copy of the offer you accept.
Sources and review date
Official documentation checked October 5, 2026. Features, offers, and account eligibility can change. Editorial recommendations are based on the documented scope, not independent performance benchmarks.
- Backup service documentation
- Caching layers
- CDN requirements
- Cache flushing
- Cache-ratio guidance
Build the business behind the tools
The tools in this guide are part of a bigger picture. At Ecommerce Paradise, I teach how to build and run a high-ticket ecommerce business. Start with a clear business model, then choose the tools that help you execute it.
If you are still figuring out the model, read my high-ticket dropshipping guide. You will understand the relationship between your store, suppliers, customers, and profit before spending money on software.
For product research, use my high-ticket niches list to explore categories and narrow down your ideas. Go deep before you go wide.
Next, work through my supplier sourcing guide so you know how to research manufacturers and approach them about becoming an authorized dealer.
My business formation checklist helps you organize the legal and financial setup. Use it to prepare your questions and confirm the requirements that apply to your business.
Get help putting the pieces together
If you want me to help you work through your next decisions, check out my private coaching. Bring your actual questions so we can focus on what is holding you up.
If you want a complete business build, take a look at the done-for-you store service. Review the scope and choose the support that fits your situation.
Trevor Fenner is the founder of Ecommerce Paradise. His main projects are Ecommerce Paradise, Supplier Paradise, and Review Paradise, which is currently in development. TrevorFenner.com publishes research-based reviews and practical guides to online business tools and remote-work services, with clear affiliate disclosures.