{"id":876,"date":"2025-03-04T11:53:25","date_gmt":"2025-03-04T11:53:25","guid":{"rendered":"https:\/\/www.woodcentral.com\/-\/peter\/?p=876"},"modified":"2026-05-24T11:28:32","modified_gmt":"2026-05-24T11:28:32","slug":"mapping-a-multi-site-wordpress-blog-to-a-domain-name","status":"publish","type":"post","link":"https:\/\/www.woodcentral.com\/-\/peter\/mapping-a-multi-site-wordpress-blog-to-a-domain-name\/","title":{"rendered":"Mapping a multi-site WordPress blog to a domain name"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Mapping <code>www.blog.name<\/code> to your multi-site WordPress blog at <code>example.com\/blogname<\/code> and ensuring the URL displays as <code>www.blog.name<\/code> while users view it involves a combination of domain mapping and WordPress Multisite configuration. Here&#8217;s how you can achieve this:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisites<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>WordPress Multisite Setup<\/strong>: Have the Mutisite configured correctly. either as subdomains or subdirectories\u2014subdirectories in this case.<\/li>\n\n\n\n<li><strong>Domain Ownership<\/strong>: You need to own the domain <code>blog.name<\/code> and have access to its DNS settings.<\/li>\n\n\n\n<li><strong>Hosting Access<\/strong>: You\u2019ll need access to your hosting control panel (e.g., DirectAdmin, cPanel, Plesk) and WordPress admin dashboard.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Steps to Map <code>www.blog.name<\/code> to <code>example.com\/blogname<\/code><\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">1. Configure DNS Settings for <code>blog.name<\/code><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Go to your domain registrar (e.g., GoDaddy, Namecheap) where <code>blog.name<\/code> is registered.<\/li>\n\n\n\n<li>Update the DNS settings to point <code>www.blog.name<\/code> to your WordPress Multisite server:<\/li>\n\n\n\n<li><strong>A Record<\/strong>: Set <code>www.blog.name<\/code> to the IP address of your hosting server (e.g., the same IP as <code>example.com<\/code>).<\/li>\n\n\n\n<li><strong>CNAME Record<\/strong> (alternative): Point <code>www.blog.name<\/code> to <code>example.com<\/code> if you prefer a CNAME setup.<\/li>\n\n\n\n<li>Allow some time (usually a few hours, up to 48 hours) for DNS propagation.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">2. Add the Domain to Your Hosting<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Log in to your hosting control panel.<\/li>\n\n\n\n<li>Add <code>www.blog.name<\/code> as an <strong>addon domain<\/strong> or <strong>parked domain<\/strong> (depending on your host\u2019s terminology):<\/li>\n\n\n\n<li><strong>Addon Domain<\/strong>: If your host supports it, point <code>www.blog.name<\/code> to the same root directory as <code>example.com<\/code> (where WordPress is installed).<\/li>\n\n\n\n<li><strong>Parked Domain<\/strong>: Alias it to <code>example.com<\/code> so it resolves to the same server.<\/li>\n\n\n\n<li>Ensure the domain is recognized by your server alongside <code>example.com<\/code>.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">3. Map the Domain in WordPress Multisite<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Log in to your WordPress Multisite admin dashboard as a Network Admin.<\/li>\n\n\n\n<li>Navigate to <strong>Sites<\/strong> &gt; <strong>Add New<\/strong> (or edit the existing site for <code>example.com\/blogname<\/code>).<\/li>\n\n\n\n<li>If your Multisite uses a plugin like <strong>WordPress MU Domain Mapping<\/strong> (older method) or a modern alternative like <strong>WP Multisite Domain Mapping<\/strong>:<\/li>\n\n\n\n<li>Install and activate the plugin across your network.<\/li>\n\n\n\n<li>Go to the domain mapping settings (usually under <strong>Settings<\/strong> &gt; <strong>Domain Mapping<\/strong> or similar).<\/li>\n\n\n\n<li>Add <code>www.blog.name<\/code> as the custom domain for the site currently at <code>example.com\/blogname<\/code>.<\/li>\n\n\n\n<li>Set it as the <strong>primary domain<\/strong> so it displays <code>www.blog.name<\/code> in the browser instead of <code>example.com\/blogname<\/code>.<\/li>\n\n\n\n<li>If you\u2019re not using a plugin (native Multisite since WordPress 4.5+):<\/li>\n\n\n\n<li>Edit the site under <strong>Network Admin<\/strong> &gt; <strong>Sites<\/strong>.<\/li>\n\n\n\n<li>Update the <strong>Site Address (URL)<\/strong> to <code>www.blog.name<\/code>.<\/li>\n\n\n\n<li>WordPress will handle the mapping natively if the domain is properly pointed to your server.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">4. Update WordPress Configuration (if needed)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Open your <code>wp-config.php<\/code> file in the root directory of your WordPress installation.<\/li>\n\n\n\n<li>Ensure the Multisite domain settings allow custom domains by adding or verifying this line:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>  define('DOMAIN_CURRENT_SITE', 'example.com');<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You don\u2019t need to change this to <code>blog.name<\/code>, as it defines the main network domain. The mapping handles the rest.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">5. Test and Troubleshoot<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Clear any caching (browser, server, or CDN like Cloudflare) to ensure the changes take effect.<\/li>\n\n\n\n<li>Visit <code>www.blog.name<\/code> and verify it loads the content from <code>example.com\/blogname<\/code>.<\/li>\n\n\n\n<li>Check that the URL remains <code>www.blog.name<\/code> in the address bar (this confirms the mapping works).<\/li>\n\n\n\n<li>If you encounter issues:<\/li>\n\n\n\n<li>Double-check DNS settings.<\/li>\n\n\n\n<li>Ensure your <code>.htaccess<\/code> file is correctly configured for Multisite (especially if using subdirectories):<br><code>apache RewriteEngine On RewriteBase \/ RewriteRule ^index\\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . \/index.php [L]<\/code><\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">6. SSL Certificate (Optional but Recommended)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>To secure <code>www.blog.name<\/code>, install an SSL certificate:<\/li>\n\n\n\n<li>Use a free service like Let\u2019s Encrypt via your hosting panel.<\/li>\n\n\n\n<li>Update the site URL in WordPress to <code>https:\/\/www.blog.name<\/code>.<\/li>\n\n\n\n<li>Test with <code>https:\/\/www.blog.name<\/code> to ensure it works.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Outcome<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once completed, visitors typing <code>www.blog.name<\/code> will see the content from <code>example.com\/blogname<\/code>, and the browser will display <code>www.blog.name<\/code> as the URL. This setup leverages WordPress Multisite\u2019s ability to map custom domains to individual sites within the network.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you run into specific issues (e.g., hosting limitations, plugin conflicts), let me know your setup details (hosting provider, Multisite type), comment below and I\u2019ll refine the advice!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Mapping www.blog.name to your multi-site WordPress blog at example.com\/blogname and ensuring the URL displays as www.blog.name while users view it involves a combination of domain mapping and WordPress Multisite configuration. Here&#8217;s how you can achieve this: Prerequisites Steps to Map www.blog.name to example.com\/blogname 1. Configure DNS Settings for blog.name 2. Add the Domain to Your &#8230; <a title=\"Mapping a multi-site WordPress blog to a domain name\" class=\"read-more\" href=\"https:\/\/www.woodcentral.com\/-\/peter\/mapping-a-multi-site-wordpress-blog-to-a-domain-name\/\" aria-label=\"Read more about Mapping a multi-site WordPress blog to a domain name\">Read more<\/a><\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-876","post","type-post","status-publish","format-standard","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/posts\/876","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/comments?post=876"}],"version-history":[{"count":0,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/posts\/876\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/media?parent=876"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/categories?post=876"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.woodcentral.com\/-\/peter\/wp-json\/wp\/v2\/tags?post=876"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}