Root Cause
The issue arose from conflicting rewrite rules in WordPress, affecting both Landing Pages and native pages. An initial quick fix only partially addressed the problem, as it didn't account for scenarios where the cache was invalidated. This led to requests being directly exposed to the core, causing route conflicts.
Resolution
To resolve the issue, the structure of Landing Pages was moved to a unique prefix to prevent conflicts. Rewrite rules were adjusted to avoid collisions with other pages and posts. A complete revalidation of the cache and routing flow was conducted after these changes.
Action Plan
Moving forward, automated tests for routes and permalinks will be implemented in both production and staging environments. Proactive monitoring for unusual traffic will be set up, and procedures for cache invalidation and fallback scenarios will be documented. The architecture of custom URLs will be reviewed before new launches, and a rollback plan for the web project will be configured.