Multiple Domain Mapping on Single Site

So far we only know WP Fastest Cache to work out of the box. Also W3 Total Cache is able to work with our plugin, but it requires some settings:

• In "General Settings" from W3TC, you can enable the page cache
• In "Page Cache" W3TC, you need no enable the "Cache alias hostnames" checkbox and leave the "Additional home URLs" field empty! For W3 Total Cache, keep in mind that CSS/JS combine and minify will only work for pages of your main domain but not for mapped pages. We recommend WP Fastest Cache ;)

Yes. We use Elementor mostly and it works also on mapped pages or posts. If you use another page builder and have troubles, try to activate the enhanced compatibility mode in the settings page (see screenshot #2).

You should always aim to have only one URI connected to one specific (landing-)page or post. If you use our plugin, the mapped content will be reached with the additional domain and the original URI as well. Therefore you should set up a 301-redirection from the original URI to the new domain or use the canonical meta-Tag. If you use Yoast SEO, it will generate the correct canonical-Tag for you right out of the box. For the redirection, there are many famous plugins out there...

Yes. But you have to define these domains in the IDN format. For example the domain www.küche.at would need to be put in as www.xn--kche-0ra.at. You can use the Verisign IDN Conversion Tool to find out these representation for your domains.

Yes. But do not try to have a certificate only for an additional domain but not for the main domain or vice versa: Browsers will detect mixed content or non-existing certificates and display security warnings. So you must have all or none of your domains SSL-secured. Mapped pages will be linked with the same protocol as the main domain.

Yes.

Yes. Instead of those original URLs, the sitemap shows the mapped domains. Sometimes it is necessary to disable and re-enable XML-Sitemap functionality in the Yoast SEO settings as well as flushing your permalinks in order to reflect the mappings. BUT there is one disadvantage so far: We do not provide a new sitemap for each mapping. This would be better for SEO, so you can handle a new domain in a different Property in Google Search Console. We will try to find a solution for that problem.

Unfortunately not - some parts work, some not. It is difficult to find out and by now we do not see a chance for us to take the time needed for good support and compatibility. WooCommerce seems to use a lot of link-generating functions that are not in WordPress core. This seems to be necessary for different product types and so on. On top, also the XML sitemaps from Yoast SEO display some links mapped and some not. If you want to use custom domains for parts of your WooCommerce store, this plugin is probably not (yet) the right decision.

Generally we do not offer compatibility with these plugins yet, since they have their own functionality to use additional domains for specific languages. This is something we are going to test out in more detail for future versions. If you have set up your multilanguage-plugin (like WPML or Polylang) to automatically forward users to the page that represents the browser-language, it is very likely that this will not work with the domain mapping plugin.

So far this plugin is only developed to map domains on a single-site installation. Multisite has the ability to use different domains per website already built in. If you are not sure if you should use a single- or multisite installation, please refer to the WordPress Codex: If you plan on creating sites that are strongly interconnected, that share data, or share users, then a multisite network might NOT be the best solution. from WordPress Codex

Although the plugin changes the include paths of scripts and styles to the mapped domains, it can happen that paths inside css-files still refer to your main domain. If your webserver is configured to disable scripts, fonts, ... from other domains, these resources will be blocked. Here you can see how to setup CORS to enable cross-domain ressources: CORS-Setup

This is pretty complex and we can not support you here. This article will help you: Cross-Domain Tracking with Google Analytics.

If you are on the frontend of your site and logged in, it will happen that you do not see the admin bar and seem to be logged out when viewing URIs with mapped domains. This is because WordPress uses cookies to save the login-state. These cookies only exist on your main domain and so they are not able to recognize you when viewing URIs with mapped domains.

Yes. Please stick to this support thread regarding nginx-setup and be sure to change the "PHP Server-Variable" setting to the recommended option for nginx. Unfortunately we cannot provide support for nginx, since we are working with apache by default.

Great. We have built in some actions and filters so you can build your own solutions on top of our plugin. So far, we do not have a documentation online. Just search for "falke_mdma" to find our action hooks or "falke_mdmf" to find our filter hooks. We have tried to place good comments, so you will find out what you can achieve with them :)

Yes. We do not store any user data - neither from you or your visitors. Only the settings are saved in your local database.