Glossary
Plain-English definitions of the terms you'll meet when managing multiple WordPress sites — from bulk updates and incremental backups to Core Web Vitals and care plans.
The practice of maintaining one or more WordPress websites — applying updates, running backups, monitoring uptime and security, optimizing performance and managing users — ideally from a single centralized dashboard rather than logging into each wp-admin separately.
Applying WordPress core, plugin and theme updates across many sites at once from a central interface, instead of updating each site individually. Bulk updates save agencies hours and reduce the security risk of running outdated software.
A lightweight WordPress plugin installed on each managed site that securely links it to a management platform. It exposes a authenticated API the dashboard uses to run updates, backups and monitoring. WP MegaManager uses the free MegaManager Connector plugin.
A backup that stores only the files and database rows that changed since the last backup, rather than copying everything every time. Incremental backups are faster and use far less storage than full backups while still allowing complete restores.
Object storage that implements the Amazon S3 API, letting you store backups and files in buckets you own. Providers include Backblaze B2, Wasabi, Cloudflare R2 and AWS S3. Using your own bucket avoids vendor lock-in — you control retention and can move providers anytime.
Automated checks that periodically request your site to confirm it is online and responding. When a check fails, the system sends an alert so you can react before clients notice. Multi-region monitoring checks from several locations to avoid false positives.
A set of Google metrics measuring real-world page experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). They are a Google ranking signal, so monitoring them across client sites matters for SEO.
A persistent store (often Redis or Memcached) that caches the results of database queries so WordPress doesn't repeat expensive lookups on every request. A working object cache dramatically reduces server load and speeds up dynamic, logged-in and WooCommerce pages.
A cache that stores the fully rendered HTML of a page so repeat visitors are served a static copy instead of regenerating the page with PHP and database queries each time. Page caching is one of the highest-impact WordPress performance optimizations.
Checking installed plugins, themes and WordPress core against a database of known security vulnerabilities (such as the WPScan database) to flag components that need updating before they can be exploited.
Cleaning and maintaining the WordPress database — removing post revisions, expired transients, spam comments and orphaned metadata, then optimizing tables. A lean database speeds up queries and reduces backup size.
A recurring service an agency or freelancer sells to clients covering ongoing maintenance — updates, backups, security monitoring, uptime checks and support. Management platforms make care plans profitable by letting one person maintain many sites efficiently.
A private copy of a live WordPress site used to test updates, plugins and changes safely before deploying them to production. Testing on staging prevents broken updates from taking down a client's live site.
Client-facing maintenance reports branded with the agency's own logo and colors instead of the tool vendor's. They summarize the work performed (updates applied, backups taken, uptime, security status) to demonstrate the value of a care plan.
Granting a contractor or support agent time-limited access to a WordPress site without sharing the real admin password. Access automatically expires, reducing the security risk of long-lived shared credentials.
Manage updates, backups, uptime and security across all your WordPress sites from one dashboard.
Start Free Beta
