About this plugin
Easily manage a large number of landing pages or small websites from a single WordPress site.
This plugin offers an easy way to map different domains to different landing pages on your WordPress site. Now you can easily maintain a large number of small sites from a single WordPress installation.
You don’t have to set anything up, it works out of the box.
Just point a domain that you own to your WordPress installation. In WordPress, create a page for that domain. The slug should be the domain name without ‘www’ and with the.
’s replaced by hyphens.
com/blog/wp-developer-eu is the same).
Benefits:
-
Easily reuse and maintain elements like forms on several domains at once.
-
Bring in more traffic using landing pages for multiple domains without hassle.
-
Favicon support for each domain, fallback from child pages to parents.
-
g. FAQ posts, portfolio posts.
-
The rest of your website keeps working as usual.
Caveats:
-
htaccess, these are clearly marked #ruigehond007 (this is my seventh plugin).
-
g. com/blog) you need to take an extra step for this to work, see installation tab.
-
g. WooCommerce products need additional work to be able to access the main cart.
-
If you need more flexibility (and more work) there is WordPress Multisite.
I put special care in making the plugin very lightweight, you will notice it has virtually no effect on the speed of your installation.
Favicons
Switch on with_favicon on the settings page, to allow adding favicons to each landing page (and other pages and posts as well).
Supplying the correct favicon(s) is your responsibility, the plugin will not verify their validity.
As a rule of thumb I would use a small(ish) SVG for modern browsers, and a 32×32 pixel ICO file as fallback.
You may need a plugin to be able to upload ICO and SVG files, since they are blocked by default.
htaccess
htaccess to make webfonts function properly, you can add them right after ‘#END WordPress’:
(eot|ttf|otf|woff|woff2)$"> Header set Access-Control-Allow-Origin "*" </FilesMatch> </IfModule> # END ruigehond007
You may need to switch on headers module in your Apache configuration, if it is not already.
NGINX
htaccess files as standard. conf file:
(eot|ttf|otf|woff|woff2)$ { add_header Access-Control-Allow-Origin *; }
conf file. In your hosting environment this may be done by disabling ‘direct delivery’ or something similar.