Running several brands on one WordPress install is the cheapest way to operate a portfolio – provided the domains resolve correctly, keep their SEO, and don’t leak into each other. Domain Mapping System Pro handles exactly that: map any domain or subdomain to any post, page, product, category, or custom post type, and the visitor sees the mapped domain in the browser bar – no redirect, no second WordPress install, no multisite complexity unless you want it.
The Pro layer is where it stops being a novelty and becomes infrastructure: microsites, WooCommerce shop mapping, global mapping, force redirects, per-domain favicons, and Yoast SEO integration with per-domain sitemaps. The 2.2.x line has been maturing the hard parts – TranslatePress and Elementor compatibility on mapped domains. Here’s the working review.
Competitive Features
- Mapping without multisite. The core proposition: alias domains point at content on a single install, with the URL bar showing the mapped domain. Multisite is supported (via sunrise.php), not required – and you can even supplement an existing multisite with microsite capabilities.
- Microsites (Pro). Group pages, posts, and products around a domain with its own homepage and inner pages – a “much less complex multisite alternative” per the vendor’s own framing, and the honest description.
- WooCommerce integration (Pro). Map the Shop page, individual products, checkout and cart pages, or a whole product category with everything in it – brand-domain storefronts on one install.
- Global mapping (Pro). Map every unmapped page in one click, so visitors only ever see mapped domains – no canonical leakage to the primary brand.
- Yoast SEO integration (Pro). Custom titles, descriptions, and keywords per mapped domain, plus domain-specific XML sitemaps – 2.2.6 extended this to include global shop products in sitemaps.
- Language per domain (Pro). Attach each TranslatePress language to its own domain, with language switchers rewriting to mapped domains out of the box – country-branded multilingual setups without separate installs.
- Alias authentication (Pro). Users log in on alias domains and subdomains – WooCommerce account pages and protected areas behave as standalone sites.
- REST API. Domains can be added and deleted programmatically – the automation path for agencies managing many client mappings.
Key Features
- Subdirectory mapping (Pro). A URL like
your-site.com/landing-page/can display content from an entirely different internal post – campaign URLs without touching site structure. - Archive and taxonomy mapping (Pro). Map a blog category and all its posts, or any custom taxonomy archive, to a domain automatically – content-organized domains, not just single pages.
- Force redirect (Pro). Hide the unmapped version of any page – canonical control done with a checkbox.
- Per-domain favicons (Pro). Brand each mapped domain’s browser tab – small detail, big perceived separation.
- SSL across all domains. One install, one certificate strategy covering every mapped domain (server configuration required).
- Query string preservation. UTM parameters and search queries pass through mappings intact – 2.2.5.x specifically hardened this during redirects.
- Developer-accurate URL rewriting. Nav menu links, term links, and post-type links rewrite globally (2.2.5.x), with longest-path-match specificity so nested URLs resolve correctly.
- Performance maturation. 2.2.5.4 improved code performance up to 50% on larger sites and fixed a PHP memory issue – the plugin acknowledges its past weight and addresses it.
Comparison with Competitors
Domain Mapping System vs native multisite
The built-in alternative is WordPress multisite with domain mapping – the honest comparison is operational cost.
| Aspect | Domain Mapping System Pro | Multisite + domain mapping |
|---|---|---|
| Setup | Plugin + DNS aliases | Network config, sunrise.php |
| Content sharing | Same install, mapped content | Separate sites per domain |
| Microsites | Built-in | Manual per-site |
| Plugin maintenance | One stack | Per-site plugins |
| SEO per domain | Yoast integration, sitemaps | Per-site SEO setup |
Multisite wins when the brands genuinely need separate plugin stacks. DMS wins when the domains share content and infrastructure – which is most branding-mapping scenarios.
Domain Mapping System vs WordPress Automatic (content supply)
These sit in adjacent utility territory: DMS maps domains; WordPress Automatic imports the content that fills mapped microsites. They complement rather than compete – a multi-brand operation needs both the domain layer and the content pipeline feeding it.
| Aspect | Domain Mapping System | WordPress Automatic |
|---|---|---|
| Domain | URL infrastructure | Content pipeline |
| Job | Serve mapped domains | Import posts/products on schedule |
| Overlap | None meaningful | None meaningful |
Recommended Stack: Multi-brand catalogs that map domains to product categories pair naturally with the same import/export backbone – the External Importer Pro pulls product content from external sites into the mapped storefronts, while DMS keeps the domains serving them correctly.
Official Changelog
The registry tracks three versions for this plugin; the changelog covers them below.
Version 2.2.7
Release Date: June 12, 2026
- Fixed TranslatePress mapped locale switching
- Fixed Elementor Loop Grid post context on mapped domains
Version 2.2.6
Release Date: May 28, 2026
- Freemius SDK upgrade
- Fixed TranslatePress mapped locale detection
- Fixed nested child URLs for parent mappings
- Fixed overlapping domain replacements
- Included global shop products in Yoast sitemaps
- Fixed WooCommerce mapped login redirects
- Fixed Elementor listing context on mapped domains
Version 2.2.5.4
Release Date: April 2026
- Improved code performance by up to 50% on larger sites
- Fixed a PHP memory issue
- Fixed blank WooCommerce category pages
- Raised minimum PHP version to 7.4
Frequently Asked Questions
Do I need multisite to map multiple domains?
No. The plugin maps domains on a single WordPress install – that’s its core purpose. Multisite is supported (via a custom sunrise.php) when you want domain management across network sites, but it’s optional, not required.
Is the GPL version the full Pro plugin?
Yes. The GPL build is the complete Pro source under its original license – microsites, WooCommerce mapping, global mapping, Yoast integration, and per-domain branding all enabled. The vendor license key for auto-updates and 1-on-1 support is the only absence.
Can I use it on client sites?
The GPL license permits unlimited installations across personal and client sites, and the REST API makes programmatic domain management across a client portfolio practical.
What server configuration is required?
Two things outside the plugin: DNS records pointing every mapped domain at the same server, and the domains added as aliases in your hosting panel (cPanel or nginx/Apache config) with the WordPress install as the web root. The vendor documents both steps in detail.
Does it work with multilingual sites?
Yes, and the recent releases focused here: TranslatePress integration supports language-per-domain mapping with working language switchers, mapped locale detection and switching were fixed in 2.2.6-2.2.7, and ACF link/URL field rewriting is supported.
Will mapped domains hurt SEO?
The Pro plugin’s Yoast integration is designed to prevent that – per-domain titles, descriptions, and sitemaps, plus force-redirect options to control canonical versions. The 2.2.x fixes to sitemap generation and global product inclusion keep the SEO layer aligned with the mapping.
Leave a Reply