Redirect rules only ever get added — never validated or cleaned up. After a few years of article renames and IA restructures, any long-lived project accumulates hundreds of rules with no way to tell which ones still work.

Three failure modes build up silently:

Inactive rules — the source slug points to a live article again (a rename was reverted, or the article was recreated), so the rule can never fire

Broken rules — the destination article was later renamed or deleted, so the redirect sends readers to a 404

Chained rules — the destination is itself caught by another rule, adding needless hops that slow readers down and dilute SEO link equity

Today, the only way to find these is exporting the rules CSV and manually cross-referencing every source and destination against live articles — across every language.

Ask: A health check on the Article redirect rules page that flags each rule as Inactive / Broken / Chained / Healthy, with bulk delete and one-click "flatten chain." Bonus: warn when renaming or deleting an article would break existing rule destinations and show a per-rule hit count so unused legacy rules can be retired confidently.

Document360 already knows which slugs resolve — this validation could run natively in seconds.