Multisite Network Setup and SEO Controls

Step 1: Define Network Ownership
Decide which settings belong to the network and which remain site-specific before enabling modules across a multisite installation. A network default can recommend modules, security, update channels, or SEO foundations, but each site still needs its own brand, public status, content, business details, social profiles, and permissions.

Step 2: Provision Conservative Defaults
Enable only the compartments the network expects and use defaults that are safe when a new site has no stored configuration. Do not make a new site indexable merely because the network is public, and do not copy one customer organization, schema identity, analytics value, sender address, or commerce secret into every site.

Step 3: Configure Each Site
Visit the individual site administration and set its site name, canonical host, indexing choice, sitemap, metadata, social image, organization or person identity, local business data, forms, privacy routes, and template assignments. Confirm network controls do not overwrite a deliberate site-level choice during autosave or update.

Step 4: Test Isolation and Scale
Create representative sites with different modules and indexing states, then verify caches, scheduled jobs, database tables, uploads, REST routes, permissions, and deletion behavior stay isolated. Test network activation and per-site activation, upgrade one existing site, and confirm a failure on one site does not break administration or public output across the network.
