Opens in a new tab

WordPress Redis Multisite: Checks Before Setup

Plan Redis caching for a WordPress Multisite network. Learn what stays site-specific, what can be shared, and how to check Novra Object Cache before a change.

By Novra Code · · 10 min read

Novra Object Cache network card showing site keys per site, global groups shared and flush scope to confirm

WordPress Redis multisite caching can retain reusable data between page loads across a network. Use an integration that distinguishes site-specific entries from intentionally shared cache groups. Confirm hosting, the existing provider, and clearing scope before enabling or changing it.

Redis is a fast memory store. Novra Object Cache connects WordPress to Redis and provides cache diagnostics. Its public documentation lists Multisite support, making it an option when your host supports the required setup.

We make Novra Object Cache. This guide uses published documentation, not a test of your network. It separates confirmed features from questions your host or Novra support should answer before a change.

Map the network before choosing a cache

Start with what you operate, not how many domain names you own. A WordPress Multisite network contains several sites managed within one WordPress installation. Separate WordPress installations can also share a hosting server or Redis service.

Scope What it means What to record
WordPress installation The deployed WordPress setup, which can run a Multisite network. Its maintainer and current object-cache provider.
Multisite network A group of sites managed together, with some shared resources. The network administrator and which sites belong to it.
Network site One site within that network, with its own content and site context. A neutral label, its site ID, and representative tasks.
Independent installation or network A separate WordPress deployment, even when it shares hosting. Its separate owner and cache allocation.
Redis instance The Redis service handling cached data, potentially for more than one workload. Who operates it and whether other workloads share its resources.

A mapped domain can still belong to a network site. A different address does not create a separate WordPress installation. The WordPress domain-mapping documentation explains that distinction.

If one installation contains several networks, record that explicitly. Do not assume each network has an independent cache boundary. Ask the maintainer to confirm support for that arrangement.

Understand site-specific and global cache groups

A cache key names a stored entry. A cache group collects related entries. WordPress uses the current site’s ID, also called its blog ID, when handling site-specific groups on Multisite.

The default WordPress cache implementation adds a site prefix to keys in non-global groups. Groups marked global do not receive that site prefix in this implementation. This explains WordPress’s model; it does not establish Novra’s exact Redis key format.

WordPress registers global groups for shared data, including users. Shared user data is not automatically a leak: the same account can participate in several network sites. Site access and permissions still need their own checks.

Global does not mean every value should be identical everywhere. An API can include additional context in its key. For example, WordPress network-option caching includes the network ID in its keys.

Temporary cached values, called transients, also have different scopes. Ordinary transients and network-wide site transients are not interchangeable. The WordPress Transients API explains that its site-prefixed functions work network-wide on Multisite. Do not assume all transients belong exclusively to one network site.

Some groups deliberately remain non-persistent, meaning their entries do not survive between requests. Plugin-specific groups also need the behavior their developer intended. Redis does not automatically cache every database query or make private page output safe to share.

Include cross-site code in your checks

Custom code may read data from another network site during one request. WordPress’s site-switching API changes the site context and tells the cache about the switch. The developer must restore the original context afterward.

Include cross-site listings, scheduled jobs, or shared-content features in testing when you use them. Checking only the main site’s homepage will not exercise those paths.

Check what Novra documents for Multisite

The Novra Object Cache Multisite and licensing FAQ states that the plugin supports Multisite. It describes a network admin screen, blog-ID-based keys, and site-specific flushing. These are published product claims, not measurements of your installed version.

The FAQ’s brief key description does not explain whether global groups receive different handling or give the complete key format. Do not read it as a guarantee that every stored entry is private to one site.

The practical benefit is visibility inside WordPress. Novra documents separate connection, integration, and running-state checks. A drop-in is the integration file WordPress loads for its object-cache provider.

In a standard Multisite installation, the sites share that installation’s object-cache drop-in. Do not plan a separate competing drop-in for each subsite. A plugin’s activation label alone does not establish the scope of its cache or clearing operations.

For an existing Novra setup, use its Dashboard and Site Health checks in the administrator context your maintainer confirms. The Novra Site Health reference distinguishes these results:

  • Redis Object Cache Connection: whether Redis answered, or which error occurred.
  • Object Cache Drop-in: whether the integration is missing, belongs to Novra, or belongs to another provider.
  • Object Cache State: whether the checked request used Redis, ran without Redis, or had caching disabled.

A successful Test Connection checks the values currently in the form. It does not prove those values are the running cache’s effective settings. Host-defined settings can take precedence. Do not save changes or enable the integration again just to collect a baseline.

Novra requires Redis and PhpRedis, the PHP add-on used to communicate with Redis. PHP is the language WordPress runs on. Published minimums are WordPress 6.1, PHP 8.0, and Redis 5.0; Redis 6.0 or later is recommended. Novra does not supply or manage the Redis service.

Resolve network-specific questions before setup

The public pages do not settle every Multisite operating detail. Send these questions to your maintainer or Novra support with your network layout and plugin version:

  • Should this version be network-activated or activated another way? Which administrator role manages it?
  • Which settings are shared, and which can differ by site? Which effective values does the running integration use?
  • How are global groups and any custom groups handled, including a multi-network installation if applicable?
  • What exactly does site-specific flushing remove, and how are shared groups treated? Do enable actions or automatic clearing have different scopes?
  • How do network sites, mapped domains, and staging copies count toward the license allowance? Where should the license be activated?

Novra describes website-based plan limits and says the license controls updates, not caching features. Neither statement proves that one Multisite network uses only one activation. Confirm coverage before buying; do not infer it from technical Multisite support.

Separate namespaces, access, and clearing

A namespace is a naming boundary that helps entries avoid colliding. It is not, by itself, a permission boundary. These controls answer different questions:

Control What it addresses What it does not establish
Cache-key prefix Distinguishing keys belonging to an intended installation or environment. Who may read or remove those keys.
Redis database number A separate numbered key namespace within a Redis instance. Independent resources, access control, or protection from broader clearing.
Separate Redis instance A separately operated service and its assigned data. Secure access or isolation from every shared hosting resource.
Access controls Which clients can connect and which commands or keys they can use. Correct WordPress group handling or correct application permissions.
Flush or invalidation scope Which cached entries an operation removes or makes outdated. The same boundary for every other operation.

Novra documents a Key Prefix setting, but do not change a working prefix to test separation. Have the host confirm the effective allocation for production, staging, and independent installations.

Redis calls numbered databases a form of namespacing and advises against using them for unrelated applications in one instance. Redis Cluster supports only database zero. Let the host choose a supported architecture; do not assign one database per network site from a generic recipe.

Redis access rules can restrict commands and key patterns. Its access-control documentation covers that separate responsibility. Ask the host about permitted clients and operations, not just the prefix displayed in WordPress.

Clearing also depends on the operation. Redis documents database-wide clearing separately from clearing all databases. Neither command is inherently limited to one WordPress site’s prefix.

Novra’s setup documentation describes clearing after Enable Cache and after changing the stored-data format, called Serializer. Its site-specific flushing claim does not define the scope of every automatic action. Confirm the installed version’s behavior and affected workloads first.

Check two sites without changing production

Start with read-only observations of the existing setup. Use neutral labels such as Site A and Site B, not customer records. Keep passwords, license keys, and personal data out of the notes.

  1. Record ownership and prerequisites. Identify the network administrator, host, existing provider, and relevant software versions. Confirm that the host supports the intended Multisite integration.
  2. Choose a repeatable task on each site, such as opening a known public page and an authorized editor screen. Record expected content and role permissions first.
  3. Use separate browser sessions for anonymous visitors and test accounts. Reuse the same task inputs and record the site context. A network-wide account can still have different permissions on each site.
  4. Record connection, drop-in, running state, errors, and observed task results where available. An unavailable check is unknown, not a pass. One site’s status does not verify every site.
  5. Repeat representative tasks and note correctness before speed. If measuring time, keep the method consistent and separate initial observations from later repetitions.

The following checks are a suggested plan, not results from a Novra test. Use harmless test content and roles agreed with the site owner.

  • Site-specific content: Site A shows its expected title and page content; Site B shows its own.
  • Role-specific access: each test account sees only the content and actions its role permits on that site.
  • Intentionally shared data: a shared test account has the expected common identity without gaining unintended site permissions.
  • Cross-site features: shared listings or background tasks use the intended source site and return to the correct context.

Test changes only in an isolated environment

For a new integration or configuration comparison, have the maintainer prepare an appropriately isolated staging network, a backup, and a recovery plan. A cloned website is not isolated if its cache operations still affect production Redis.

After an agreed setup, repeat the Site A and Site B checks. Have the owner update a harmless test item through its normal workflow in staging. Verify the changed site, the unaffected site, and any deliberately shared data against the expected results.

This checks invalidation: whether outdated cached data stops being used after a change. The application developer should define the expected behavior for custom data and cross-site dependencies.

Do not flush production, restart Redis, overwrite a drop-in, or deactivate the network’s provider as a quick test. Prefix changes, Serializer changes, and other tuning belong in a separate, owned change plan.

Stop if content crosses sites unexpectedly, permissions are wrong, tasks fail, or comparable timings deteriorate. Record the last change and involve the maintainer. Use the agreed recovery plan instead of assuming a flush fixes the cause.

Read shared statistics at the right scope

Novra documents cache statistics, including hit ratio and memory use. Hit ratio describes successful lookups, not page speed. Its Site Health memory check is explicitly described as reporting instance memory.

Redis server-wide statistics can include other sites or applications using that instance. A site prefix or database number does not turn them into Site A’s exclusive measurements.

The public Novra documentation does not fully define each chart’s site, network, or instance scope. Record the displayed label and selected period, then ask for clarification where needed. Do not attribute shared memory or a network-wide improvement to one site without evidence.

Keep measurements blank until observed. This record is ready to copy:

Environment, network, and responsible maintainer:
Site A / Site B labels and site IDs:
Existing provider and confirmed Redis allocation:
Shared settings, activation, and license questions resolved:
Task, inputs, account role, and login state:
Expected site-specific content and intentionally shared data:
Connection / drop-in / running-state results for each site:
Observed Site A result:
Observed Site B result:
Staging change and expected invalidation, if applicable:
Timing method, individual observations, and time window:
Metric label and confirmed site / network / instance scope:
Errors, remaining uncertainty, and next responsible person:

Choose the next step for your network

Keep a working, supported object-cache provider unless a specific need justifies a change. If Redis or PhpRedis is unavailable, resolve hosting first. If activation, settings, clearing, or license scope remains unclear, get those answers before installation changes.

When the requirements and ownership are clear, use the Novra Object Cache operating guide with your maintainer. Follow the agreed staging plan rather than applying a generic single-site recipe to the network.

If WordPress-side controls and diagnostics meet an uncovered need, evaluate Novra Object Cache for your network. Published plans use a one-time payment and include a 30-day money-back guarantee. Confirm your network’s license coverage and hosting support before purchasing.

WRITTEN BY

Novra Code

Novra Code

Novra Code builds and maintains WordPress plugins for page caching, object caching and server-side tracking. Every post comes from the team that builds and ships those plugins.

About Novra Code
Network timing of a WordPress page request with the Waiting (TTFB) stage highlighted as the delay to find, Novra Cache
Caching

Reduce TTFB in WordPress: Find the Delay

Find what delays your WordPress page's first response. Separate redirects, network time and page generation, then decide whether page caching addresses the cause.

· 10 min read

WordPress cache layers from browser and CDN to the page cache and saved page, with the stale page cache copy marked, Novra Cache
Caching

Clear Cache in WordPress: Fix Outdated Pages

Changes saved but still missing? Identify the cache holding the old page, refresh only what needs updating, and verify the result with Novra Cache.

· 7 min read

NOVRA CACHE

A fast site,
ready for every visitor.

Novra Cache hands out ready-made pages, lighter images and leaner code. One plugin instead of a stack you have to babysit.