Troubleshooting WP Landing Kit URL Mapping Redirect Conflicts
WP Landing Kit maps URL paths on your mapped domain to specific pages or posts on your WordPress site. If you find that visiting a mapped URL (for example, subdomain.example.com/offer) redirects to your main site's homepage instead of showing the intended page, a conflicting redirect rule is likely overriding the plugin's mapping.
This article explains the common causes of these conflicts and how to resolve them.
Common Causes of Mapping Redirects
The following sources can produce redirect rules that override WP Landing Kit's path mappings:
- WordPress redirect rules — A redirect rule set in Settings > Reading, a plugin, or manually in the WordPress database that sends a specific slug or path to another URL.
- Redirect or SEO plugins — Plugins such as Redirection, Rank Math, or Yoast SEO can define per-URL or global redirect rules that run before WP Landing Kit's mapping logic.
.htaccessrules — CustomRewriteRuleorRedirectdirectives in your site's.htaccessfile can intercept requests before WordPress loads.- Hosting-level redirects — Rules configured in your hosting control panel (for example, cPanel's Redirects tool) that forward a domain or path before the request reaches WordPress.
📝 Note: WP Landing Kit's own global redirect feature — which redirects visitors from the original WordPress URL to the mapped domain URL — is a separate behaviour. See Global redirect settings for details on that feature.
How to Diagnose the Conflict
1. Check active redirect plugins
- Open your WordPress admin and go to the Plugins screen.
- Look for any redirect or SEO plugin that manages redirects (for example, Redirection, Rank Math, Yoast SEO).
- Open the plugin's redirect manager and search for rules that match the path or slug you mapped in WP Landing Kit.
2. Check WordPress permalink and slug redirects
- Go to Settings > Permalinks in your WordPress admin and note your permalink structure.
- If you have previously configured a redirect rule that points a specific slug to your homepage or another URL, that rule may conflict with the mapped path.
3. Inspect your .htaccess file
- Access your site's root directory via FTP, SFTP, or your hosting file manager.
- Open the
.htaccessfile and look forRewriteRuleorRedirectdirectives that target the affected URL path.
4. Test with browser developer tools
- Open the affected mapped URL in a browser.
- Open DevTools (F12) and go to the Network tab.
- Reload the page and inspect the first request. Look for a
301or302response and check theLocationheader — it shows where the redirect is pointing.
Resolution Steps
Once you have identified the conflicting rule, follow the steps below to remove it and restore the mapping.
Remove the conflicting redirect rule
- If the rule is in a redirect plugin: Open the plugin's redirect manager, locate the rule, and delete it.
- If the rule is in
.htaccess: Remove or comment out theRewriteRuleorRedirectdirective that targets the affected path. - If the rule is in your hosting control panel: Go to the redirects section of your hosting admin and remove the matching rule.
Verify the WP Landing Kit mapping is correctly configured
- Go to WP Landing Kit > All Domains and click Edit on the relevant domain.
- In the Mappings table, find the row for the affected URL path.
- Make sure the Action is set to Map (not Redirect) and that the Resource field points to the correct page or post ID.
- Click Save Changes.
Flush WordPress permalink rewrites
After removing the conflicting rule, flush the rewrite rules so WordPress picks up the correct routing:
- Go to Settings > Permalinks in your WordPress admin.
- Click Save Changes without making any modifications.
This forces WordPress to regenerate its rewrite rules and ensures WP Landing Kit's mappings take priority.
Verify the Fix
After completing the steps above:
- Clear your browser cache or test in a private/incognito window.
- Visit the mapped URL (for example,
subdomain.example.com/offer). - Confirm the correct page loads instead of redirecting to the homepage.
💡 Tip: If the page still redirects after clearing your browser cache, check whether your hosting or a CDN is caching the old redirect response. Clear the cache at the hosting or CDN level as well.
Prevention Tips
To avoid redirect conflicts when using WP Landing Kit path mappings:
- Avoid creating global slug redirects for paths that are also defined in WP Landing Kit's mapping table.
- When using a redirect plugin, review its rules before adding new mappings to WP Landing Kit.
- After any
.htaccesschange, flush permalink rewrites in Settings > Permalinks. - Test new mappings in a staging environment before deploying to production.
