Before lowercasing URLs for SEO, establish which parts your application treats as equivalent. Two public documentation paths might serve the same answer, while a mixed-case identifier or token must retain its exact value. A blanket rewrite can tidy a URL report while breaking the route a reader needs.

The practical job is to define one intended public address for each answer and preserve the meaning of everything else. Audit the actual responses, links and route handling before writing a normalization rule.

The examples below use fictional Larch Docs. No production deployment or crawler test is claimed. The aim is a reviewable route policy that a developer can verify against their own application.

Separate a path from the data it carries

Suppose Larch Docs serves the same guide at /Guide/Export and /guide/export. Both display instructions for exporting a public sample report.…