Verified theme & plugin compatibility
WP Landing Kit works with many WordPress themes and plugins, but direct mapping support and cross-domain behavior depend on how the third-party product stores and routes its content.
How to assess compatibility with an unlisted plugin
WP Landing Kit serves all mapped domains from one WordPress installation. It does not create separate global menus, widgets, headers, or footers for each mapped domain. If you need a different presentation per domain, use page-level or template-level controls available in your active theme or page builder.
For LMS, event, forum, community, shop, or other complex plugins, run this quick check:
- Publish a test item in that plugin's content type.
- Go to WP Landing Kit > Settings and check whether that public post type appears in Mappable Post Types.
- Go to WP Landing Kit > All Domains, open your domain, and confirm the test item can be selected as a Resource in the mapping row.
If the content is a page, post, or public custom post type, you can map it directly. If the plugin uses virtual routes instead, those routes are not direct mapping targets. Use the workflow in Mapping Custom Domains to Virtual Plugin Routes.
Complianz can run on mapped pages, but consent is not synchronized across different root domains. Browsers treat each root domain separately, so visitors may need to provide consent again on each one.
If a plugin is not listed below, it is not automatically incompatible. It means it has not yet been added to the tested or customer-verified list.
Landing Kit tested and customer verified
- Astra Theme
- Beaver Builder
- Bricks theme
- Brizy
- CartFlows
- Divi
- Dokan
- Easy Digital Downloads
- Elementor
- Gravity Forms
- JetPack
- Oxygen Builder
- Rank Math
- TranslatePress
- WooCommerce
- Yoast SEO