Multisite & Network Use — SEO Copilot AI Docs
Agency

Multisite & Network Use

How SEO Copilot AI works in WordPress Multisite, when to network activate it, how licensing behaves on a network, and what Agency plan is intended to cover in larger WordPress environments.

At a glance

SEO Copilot AI can be used in standard single-site WordPress installations and in WordPress Multisite environments. Multisite support is intended for the Agency plan, where you want to manage SEO Copilot AI across a network of subsites from one WordPress Multisite installation.

Plan

Agency

WordPress Multisite support is intended for the Agency tier.

Install mode

Network

Install once in the network and activate where needed.

License scope

Per network

One Multisite installation is treated as one network environment.

Important: Agency Multisite support is meant for a single WordPress Multisite network. It is not the same as unlimited unrelated single-site installations spread across separate hosting accounts or standalone domains.

What “Multisite support” means

In WordPress Multisite, one WordPress codebase can run many sites under the same network. SEO Copilot AI can be installed once at the network level and then enabled for the subsites where you want to use it.

This is especially useful for agencies, organizations, schools, franchise environments, or internal web teams that maintain many related sites under one shared WordPress network.

Area How it works
Plugin installation The plugin is uploaded once in the network admin, just like other Multisite-capable plugins.
Activation model You can typically choose whether to network activate the plugin for all sites or activate it only on selected subsites.
Licensing The network environment is treated as the licensed installation context for Agency Multisite use.
Feature availability Paid capabilities depend on successful license verification. If the Agency license is active, eligible network use features are unlocked automatically.
Subsite usage Each subsite can use SEO Copilot AI where the plugin has been activated and where the site admin has permission to access the plugin screens.

Recommended setup flow

1

Install the plugin in Network Admin

In your WordPress Multisite network, go to Network Admin → Plugins → Add New / Upload Plugin and install SEO Copilot AI as you would any other plugin.

2

Activate the Agency license

Enter your Agency license key in the plugin’s License settings and run a verification. Once the license is accepted, the plugin will know that the installation is allowed to run in a Multisite environment.

3

Choose activation strategy

Decide whether you want SEO Copilot AI active on every subsite in the network, or only on selected sites. Smaller networks often prefer selective activation, while standardized environments may prefer network-wide activation.

4

Configure per-site usage

After activation, each subsite can use the plugin on its own content. This allows page-level and site-level work to happen where the actual posts, pages, products, and SEO data live.

Network activate or activate per site?

Both approaches can make sense depending on how your Multisite network is organized. The right choice depends on whether all subsites should have the plugin available by default, or whether only some sites need SEO Copilot AI.

Good fit for network activation

You manage a controlled network where every subsite is expected to use the same SEO tooling and where consistent rollout across all sites is important.

Better fit for per-site activation

You only want SEO Copilot AI on a subset of sites, or some subsites are temporary, experimental, or managed by teams that should not automatically receive the plugin.

  • Use network activation when you want consistent availability across the entire network
  • Use per-site activation when only selected subsites should have access
  • Keep activation selective if parts of the network are dormant, archived, or not intended to use AI-assisted SEO workflows

Licensing behavior in Multisite

For Multisite usage, the Agency plan is intended to cover one WordPress Multisite network. When the plugin verifies the license successfully, the network installation is recognized as the licensed environment and the Agency-tier capabilities become available.

The plugin still relies on the NordicDataTools license system, just as it does on single-site installs. The difference is simply that the installation context is a Multisite network rather than one standalone site.

Practical rule of thumb: one Agency license is intended for one Multisite network installation. If you run multiple completely separate Multisite networks, each one should be treated as its own installation context unless your commercial agreement says otherwise.

Things to keep in mind on larger networks

  • Each subsite has its own content, so analysis results and content recommendations are naturally tied to the subsite where the content exists
  • AI usage can grow quickly in larger networks because more editors and more subsites may run analyses regularly
  • Administrator roles matter — super admins and subsite admins may not see exactly the same options depending on how your network is managed
  • If your hosting environment blocks outbound HTTPS requests, license verification can fail for the whole network just like on a normal single-site install
  • On very large networks, it is a good idea to roll out gradually and confirm performance, permissions, and workflow expectations before enabling the plugin everywhere

Typical Multisite use cases

Agency client networks

A web agency manages many subsites for related brands, locations, or departments and wants the same SEO workflow available throughout the network.

Franchise or regional sites

A company runs many local market sites under one shared platform and wants local teams to improve titles, meta descriptions, FAQs, and structured content.

Internal enterprise web estates

A communications or digital team manages many business-unit sites and wants one common plugin instead of different tools on every subsite.

Education or membership networks

Schools, associations, and multi-branch organizations can use one network install while allowing each subsite to work on its own SEO quality.

Common questions

Do I need Agency for WordPress Multisite?

Yes — Multisite support is intended for the Agency plan. Free, Pro, and Business are not intended for WordPress Multisite network use.

Does one Agency license cover unlimited separate websites outside Multisite?

No. Agency Multisite support refers to one WordPress Multisite network installation. It should not be interpreted as unlimited separate standalone WordPress sites across unrelated environments.

Should I network activate the plugin for all subsites?

Only if that matches your workflow. Many teams prefer selective rollout first, especially on larger networks, so they can confirm permissions, AI usage patterns, and editorial processes before wider adoption.

Where should I enter the license key in a Multisite setup?

Use the plugin’s License settings in the environment where you manage the plugin installation and licensing for the network. In most cases, that means handling it from the network-aware administrative context rather than treating each subsite as a separate paid install.

What happens if license verification fails on a Multisite network?

The behavior is the same as on single-site installations: if the license cannot be verified, the plugin falls back to Free mode until a successful verification happens again. Your saved settings are not erased just because verification temporarily fails.

Best practice recommendation

If you run a serious Multisite environment, start with a small number of subsites first. Verify that the Agency license is active, confirm who should have access, test a few real SEO workflows, and then expand rollout to more sites once the setup feels stable and predictable.

Where to go next

  • License & Plans — understand the four plan tiers and licensing model
  • Settings — review the plugin settings and license section
  • Troubleshooting — common activation, connectivity, and license verification issues