WordPress Multisite Sitemap: Complete Setup Guide

WordPress Multisite lets you run dozens of sites from a single installation, but it also multiplies your sitemap complexity. Each subsite needs its own sitemap, its own Search Console property, and careful coordination to avoid cross-site URL leakage. This guide walks through every step.

How WordPress Multisite Works

WordPress Multisite is a built-in feature that enables a single WordPress installation to host multiple websites. All sites share the same database, plugin files, and core WordPress code, but each site has its own set of posts, pages, users, and settings. A super admin manages the network while individual site admins manage their own content. From an SEO perspective, each site is a distinct entity that search engines treat independently — requiring its own sitemap and Search Console property.

Subdomain vs Subdirectory Multisite

WordPress Multisite supports two URL structures. Subdomain networks host each site at a unique subdomain: site1.example.com, site2.example.com. Subdirectory networks host them under paths: example.com/site1/, example.com/site2/. For sitemaps and Search Console, subdomains are treated as separate domains and require separate property verifications. Subdirectory sites can be managed under a single domain property. Neither is inherently better for SEO, but the choice affects how you structure your sitemap and GSC setup.

Yoast SEO for Multisite

Yoast SEO Premium supports Multisite networks. When network-activated, Yoast generates a separate sitemap for each subsite under that site's URL. For a subdirectory site at example.com/shop/, Yoast places the sitemap at example.com/shop/sitemap_index.xml. The network admin can configure global defaults while each site admin customizes their own sitemap inclusions and exclusions. One limitation: Yoast does not automatically create a single network-wide sitemap index that aggregates all subsites — you'd need to build that manually or use a dedicated plugin.

Rank Math on Multisite Networks

Rank Math also supports Multisite and handles per-site sitemaps similarly to Yoast. Its network module allows the super admin to set network-wide defaults and lock or unlock specific settings for site admins. Rank Math places each site's sitemap at its own root: example.com/sitemap_index.xml for the main site and example.com/site2/sitemap_index.xml for a subdirectory subsite. One advantage of Rank Math is its built-in support for news and video sitemaps at the per-site level without a separate extension.

The Sitemap Index Approach

For networks with many subsites, a network-level sitemap index file is the cleanest architecture. This master index file lists each subsite's sitemap URL as a <sitemap> entry. Google can parse it in one request and then fetch each child sitemap independently. You can create this index manually as a static XML file or generate it dynamically with a custom plugin or WordPress filter. Submit the master index to your root domain's Search Console property if you're using a domain property (which covers all subdomains and subdirectories).

Submitting Each Subsite to GSC

Each subsite needs its own Google Search Console property. For subdomain sites, add a URL-prefix property like https://site1.example.com/ or use a Domain property for site1.example.com. For subdirectory sites, a single Domain property for example.com covers all paths, or you can add individual URL-prefix properties like https://example.com/site1/. Once verified, submit the sitemap for each subsite in its own GSC property. The Sitemaps report in each property will then show indexed URLs and any errors specific to that site.

Cross-Site Internal Linking in Multisite

Internal links between subsites in a Multisite network behave like external links from a crawling perspective — especially in subdomain setups. Googlebot treats links from site1.example.com to site2.example.com as cross-domain links. This means PageRank signals are diluted rather than concentrated within a single domain. In subdirectory networks, cross-site links stay within the same domain, which is better for link equity. When planning your content and internal linking strategy, account for how URL structure affects link flow.

Common Multisite Sitemap Problems

Several issues appear frequently in Multisite sitemap setups. First, plugins that are not network-activated may generate sitemaps only for the main site, leaving subsites uncovered. Second, subdomain sites require wildcard DNS and SSL — if a subsite's domain doesn't resolve or returns a certificate error, its sitemap becomes unreachable. Third, deactivated sites may still have their sitemaps returning 200 responses with stale content. Audit each subsite's sitemap independently with a crawl tool to catch these gaps.

Testing Your Multisite Sitemap Setup

To verify your Multisite sitemaps are correctly configured, check each sitemap URL directly in a browser and confirm it returns a 200 status and valid XML. Use Google Search Console's sitemap submission tool for each property and review the "Submitted URLs" count against your expected page count. Tools like Screaming Frog can crawl an entire network in a single session if you provide all starting URLs. Also confirm that each subsite's robots.txt contains the correct Sitemap: directive pointing to that site's own sitemap — not the network root's sitemap.