Setup and operations
Connecting a WordPress Landing Site to DuckRoute
Treat WordPress as a destination application with its own URLs, plugins, cache, and security behavior—not as a single static page.
Prepare the WordPress destination
Update core, themes, and required plugins according to the site's maintenance policy, then verify its canonical URL and HTTPS behavior directly. Remove staging redirects and broken assets before connecting a flow.
Select delivery based on application needs
A redirect keeps WordPress on its own host, while reverse proxy or iframe modes introduce host, cookie, framing, and asset constraints. Test the chosen mode with the real theme and forms rather than a blank page.
Account for layered caching
WordPress plugins, host caches, browsers, and an edge provider can each retain content or redirects. Document purge ownership and test in a fresh session before deciding that DuckRoute selected the wrong destination.
Preserve campaign context safely
Confirm intended query parameters reach the landing page and analytics without being duplicated into form fields or logs unnecessarily. Validate redirect plugins so they do not create cycles with the public flow URL.
Run a WordPress launch check
Visit key templates on mobile and desktop, submit non-production test forms, follow navigation, inspect assets, and exercise the fallback page. Recheck after plugin or permalink changes that alter routing behavior.