WordPress Multisite Management Checklist: Network Settings, Updates, Roles, and Site Audits
multisitenetwork administrationdomain mappinguser rolesupdatessite audits

WordPress Multisite Management Checklist: Network Settings, Updates, Roles, and Site Audits

CCode Craft Studio
2026-11-18
6 min read

A practical WordPress Multisite checklist for network settings, domains, roles, updates, backups, audits, and safely retiring sites.

Managing WordPress Multisite safely requires more than updating plugins across several sites. This reusable checklist helps you separate network-level work from site-level administration, verify domain and path settings, control roles and access, test changes, monitor storage and backups, and retire inactive sites without leaving security or maintenance gaps.

Overview

WordPress Multisite lets one WordPress installation serve multiple sites from a shared network. That shared structure can simplify development and maintenance, but it also creates dependencies. A network-level plugin change may affect every site. A user can have different roles on different sites. A domain change can involve WordPress settings, DNS, web-server routing, and certificates. A backup that covers only one site may not be enough to restore the network.

Start by documenting the boundaries of your installation. Record the network address, site addresses, whether sites use subdirectories or subdomains, the hosting environment, PHP and database versions, active themes and plugins, scheduled backup locations, and the person responsible for network administration. Treat this document as an operational reference rather than a one-time setup note.

Keep a clear distinction between these four areas:

  • Network administration: global settings, network-enabled plugins, available themes, network users, and site creation or removal.
  • Individual site administration: content, menus, widgets, site-specific settings, users assigned to that site, and selected themes or plugins.
  • Hosting and infrastructure: DNS, domain routing, SSL certificates, PHP configuration, database access, server resources, caching, and filesystem permissions.
  • Deployment workflow: staging, code review, version control, testing, release notes, rollback, and post-deployment checks.

Use the following ownership map before changing anything:

TaskPrimary ownerOperational note
Create, archive, or delete a siteNetwork administratorConfirm retention, redirects, backups, and stakeholder approval first.
Change DNS or a mapped domainHosting layer and network administratorVerify routing, certificates, canonical URLs, and email dependencies.
Install or update a network pluginNetwork administrator and deployment processTest representative sites before activating it across the network.
Edit site content or menusIndividual site administratorKeep site-specific changes separate from shared code.
Change PHP or server configurationHosting layer and deployment processTest compatibility and document the rollback path.
Review users and permissionsNetwork administrator with site ownersRemove unnecessary access at both network and site level.
Run backups and restore testsHosting layer and network administratorConfirm that files, databases, uploads, and configuration can be recovered.

Checklist by scenario

When creating a new site

  • Decide whether the site should use a subdirectory, subdomain, or mapped domain.
  • Choose a descriptive site title, administrator email, language, timezone, and permalink structure.
  • Confirm whether the site should be publicly accessible, private, or temporarily blocked from search engines during development.
  • Assign only the site-specific users who need access. Avoid giving network administrator privileges for routine content work.
  • Activate an approved theme and the smallest practical set of plugins.
  • Record the site owner, purpose, launch status, domain, and review date in the network inventory.
  • Test the homepage, login, forms, media uploads, navigation, responsive layout, and email notifications.

When changing domains or paths

  • Capture a backup before changing the site address, network address, or path configuration.
  • List every URL involved, including the public domain, administrative URL, mapped domain, media URLs, and any integration endpoints.
  • Coordinate DNS records, web-server routing, SSL certificates, redirects, and hosting configuration before testing the new address.
  • Check whether hard-coded URLs exist in content, theme files, plugin settings, custom CSS, forms, or external integrations.
  • Test login cookies, administrator screens, media files, canonical links, sitemaps, forms, and redirects from both logged-in and logged-out sessions.
  • Keep the old address available long enough to identify missed links and communicate the change to users.

When updating core, themes, or plugins

  • List the affected sites and identify which ones use the relevant theme, plugin, custom code, or integration.
  • Review compatibility notes and test the update on staging or a representative copy of the network.
  • Check high-risk sites first, such as sites with custom templates, membership features, WooCommerce, forms, or external APIs.
  • Test network administration, site dashboards, publishing, media uploads, search, forms, scheduled tasks, and critical frontend journeys.
  • Deploy during a maintenance window with a documented rollback plan.
  • Record the version, date, test results, affected sites, and any follow-up work. The WordPress update testing checklist can support this release process.

When reviewing users and roles

  • Export or record network users, their network roles, the sites they can access, and the date of their last review.
  • Remove accounts belonging to former contributors and reduce elevated roles that are no longer required.
  • Check for users who have access to a site but no current business reason to retain it.
  • Use named accounts rather than shared administrator credentials so changes can be traced.
  • Review administrator email addresses and recovery methods before removing an account.

When deactivating or retiring a site

  • Confirm the owner’s approval, required retention period, redirect destination, and final public status.
  • Take a final backup and label it with the site name, date, and reason for retention.
  • Decide whether to archive, make the site private, redirect it, or remove it from the network.
  • Remove obsolete users, integrations, scheduled tasks, domains, and DNS records only after checking dependencies.
  • Update the network inventory and monitor the old URL for broken links, unexpected traffic, or missed references.

What to double-check

A multisite network can appear healthy while individual sites develop quiet problems. Add these checks to a recurring audit:

  • Inactive sites: identify sites with no recent content, login, or owner activity. Confirm whether they are intentionally dormant.
  • Orphaned users: find accounts without a current owner, business purpose, or valid site assignment.
  • Unused plugins and themes: remove or document components that are inactive, unsupported by your workflow, or no longer needed.
  • Storage growth: review uploads, backup folders, logs, temporary files, and unusually large media directories.
  • Failed backups: check recent backup status, available storage, notifications, retention, and whether a restore has been tested.
  • Scheduled tasks: inspect publishing, cleanup, email, import, and integration jobs. Use the WordPress cron jobs guide when a background task needs investigation.
  • Performance: compare slow dashboards, high-traffic sites, database growth, cache behavior, and expensive plugins rather than assuming one network-wide fix will suit every site.
  • Security: review administrator access, unexpected files, plugin sources, exposed debug settings, and recent configuration changes.

For each review, record the finding, affected site, owner, priority, next action, and completion date. A short audit log is more useful than an undocumented assumption that someone else is monitoring the network.

Common mistakes

  • Assuming network activation is harmless: a plugin can behave differently across themes, content models, and site configurations. Test representative sites first.
  • Confusing network administrators with site administrators: site owners usually need control of their content, not every network setting.
  • Changing URLs without an infrastructure plan: WordPress settings alone do not complete a domain migration. DNS, routing, certificates, redirects, and integrations also matter.
  • Backing up only the database: a practical recovery plan should account for uploads, plugins, themes, configuration, and the database.
  • Editing shared files directly: place custom behavior in maintainable, reviewed code and keep a record of deployments. The WordPress code review checklist is useful before releasing shared changes.
  • Deleting before documenting: archive the final state and dependencies before removing a site, user, domain, or plugin.
  • Skipping staging: a staging copy cannot reproduce every production condition, but it is safer than using live sites as the first test environment.

When to revisit

Use this checklist before creating a site, changing a domain, rolling out a plugin, assigning elevated access, or deactivating a site. Schedule a broader review before seasonal planning cycles and whenever your hosting provider, deployment workflow, caching layer, PHP version, domain structure, or backup tool changes.

At minimum, perform a documented network audit twice a year. Review the current WordPress and plugin requirements, hosting capacity, domain-mapping behavior, backup recovery process, user list, inactive sites, storage growth, and update-testing procedure. Recheck these items after major WordPress releases rather than relying on an old setup document.

Finish each audit by choosing three concrete actions: one access or security improvement, one reliability improvement, and one maintenance task. Assign an owner and due date for each. That final step turns a WordPress multisite management checklist into a repeatable developer workflow instead of a document that is consulted only after something breaks.

Related Topics

#multisite#network administration#domain mapping#user roles#updates#site audits
C

Code Craft Studio

WordPress Development Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.