For the best results we recommend the same system requirements as WordPress itself. Similarly, we recommend the latest version of WordPress.
- WordPress compatible hosting with the ability to add alias or addon domains.
- Dedicated IP address (an IP address which is unique to your website. No other websites or accounts use your dedicated IP address).
- WordPress 5.0 or above (we recommend the latest version of WordPress).
You should be familiar with:
- WordPress and the WordPress admin.
- Installing and activating plugins within WordPress.
- Adding alias or addon domains withing your WordPress host.
- Managing DNS records for your domain names (wherever they are hosted). Specifically, you’ll need to be able to add/manage A-Records.
NOTE: Multisite compatibility and known issues with multisite installs
Landing Kit was intended for single-site WordPress installations, but you can use it with multisite as well. Keep in mind that multisite already includes domain mapping options for sub-sites and that Landing Kit is not intended as a replacement for that functionality. While Landing Kit does work with multisite installs there are known incompatibilities with miscellaneous 3rd party domain mapping plugins.
2. Recommended hosts
In theory, any WordPress compatible host with the ability to add alias or addon domains should work, but here are a few recommended hosts tested and known to work with Landing Kit.
3. Quick-start walkthrough
Just a quick video to get you started.
4. Quick-start guide
- Upload and activate the Landing Kit plugin.
- Head to
Settings > WP Landing Kitto configure your global settings.
Domainsto add and map your first domain to any published post, page or custom post type item.
- Within your hosting control panel (e.g. cPanel or other hosting admin), add your mapped domain as an
Addon Domain(pointed to your WordPress root folder).
- Wherever you purchased or manage domain DNS records, add an A-record to the domain you just mapped with a host value of
@and the static IP address for your WordPress server.
5. Custom post type settings
By default, the plugin is configured to work on the core
page post type. It is possible, however, to activate support for the core post type and you can also enable support for any custom post types that are configured as public.
To enable support for post types
- Head to
Settings > WP Landing Kit.
- Check the post types you want to support next to the
Mappable Post Typessetting.
The following things will happen once a post type is enabled:
Mapped Domainadmin column will be added to the admin post list screen for that type.
Mapped Domainmeta box will appear on the post edit screen for that post type.
- The post type will be searchable within the Mapped Page setting when editing a domain's settings directly in
If you disable support for a given post type
- Requests made to any domain that is mapped to an unsupported custom post type will be redirected back to the main site's domain. The redirect will maintain any path and query string.
NOTE: Mapped domain post titles are limited to domains
When entering a domain as the post title, the protocol, path, and query string are removed so it is only possible to enter the domain host. e.g. If you enter a post title of
http://example.com/some/page?with=query, the URL will be stripped down to
example.com on post save.
6. Global redirect settings
If a post has a mapped domain the post would be accessible on both the mapped domain and the original URL. This could result in duplicate content issues. We have a 301 redirect in place that redirects the original site's post URL to the mapped domain.
e.g. If the original post is at
example.com/post-name and the post has a mapped domain of
product.com, any requests made to
example.com/post-name will be 301 redirected through to
How to disable the post to domain redirect
- Head to
Settings > WP Landing Kit.
- Find the
- Uncheck the
Redirect original posts to mapped domainscheckbox.
7. Enforcing protocols
By default, mapped domains will be accessible by either http or https protocols. It is possible to enforce a particular protocol.
Enforcing protocols at the domain level
When creating/updating a domain in
Domains you can determine a domain's protocol via the
Enforce Protocol setting. If the setting is set to
none, the global fallback settings will be checked for protocol enforcement. If the global settings are not configured to enforce a protocol, the requested protocol will be honored.
Enforcing protocols at the global level
You may define a global setting for enforcing protocols on mapped domains. To do so:
- Head to
Settings > WP Landing Kit
- Under the
Global Domain Settings, set the
Enforce Protocolsetting to the desired protocol.
8. WP Landing Kit + SEO Plugins
Landing Kit is known to play well with SEO plugins, but here are a few things to keep in mind.
The plugin appears to be working fine with the Yoast SEO plugin. When a served under a mapped domain, the Yoast SEO plugin pulls the title, description, and canonical meta from the individual page.
All In One SEO Pack
To ensure the All In One SEO Pack plugin uses the page-level SEO meta, some configuration is required.
Pages served under mapped domains are effectively home pages and by default, the All In One SEO Pack plugin looks for home page SEO meta set up in
WP Admin > All In One SEO > General Settings > Home Page Settings (meta box). Any meta set in that meta box would, of course, appear on any mapped domain so what we want to do is tell the All In One SEO Pack plugin to use page-level meta for SEO.
To do so, simply enable the Use Static Front Page Instead option in the Home Page Settings meta box.