Problem Statement:

Document360 currently validates redirect rules only for direct configuration conflicts (for example, a destination slug already used as another rule's source). It does not flag a redirect rule that is actively intercepting a slug belonging to a currently published, live article. As a result, an outdated or unnecessary redirect rule can silently cause a 404 error for a live article, and the only way to find it today is to manually search the redirect rules list for the affected slug after a reader reports the issue.

Suggested Enhancement:

Add a validation check (either at rule-creation time or as a periodic site health check) that flags redirect rules whose source path matches the slug of a currently published article, warning the author that the rule may prevent that article from being reached.

Customer Benefit:

Catches a class of 404 errors proactively instead of reactively, reducing troubleshooting time and reader-facing broken links after content restructuring.