When configuring a WordPress Multisite Network with a subdirectory structure (e.g., example.com/subsite/), you must avoid naming new subsites after existing WordPress system directories or rewrite endpoints.
The following reserved directory slugs must never be assigned to subsites:
pagecommentblog— Default virtual root for the primary network site (can be removed via settings).filesfeedwp-admin— Core administrative folder.wp-content— Core content folder containing media uploads, plugins, and themes.wp-includes— Core script libraries and dependencies.wp-json— WordPress REST API endpoint.embed— oEmbed discovery and response endpoints.
These 10 identifiers represent core functions, endpoints, and physical server directories used by the WordPress platform. Attempting to create a subsite utilizing any of these slugs can trigger routing conflicts with the core rewrite engine. While WordPress attempts to circumvent collisions by auto-appending numeric suffixes, doing so results in awkward, unintuitive URLs.
References
Support Independent Perspectives & In-Depth Insights
Every thoughtful analysis and candid critique comes from our dedication to truth and quality. We choose not to follow sensational algorithms or clickbait headlines.
Sustaining independent research requires reader support. Make a one-time or monthly contribution, securely processed by Google.
Payments secured by Google · Manage or cancel anytime in your Google Account




Comments