renaming-services

To rename service documentation without broken links, you must rename the markdown file, update the Services List entry, add nginx 301 redirects, and fix remaining internal references to the old slug.

Updating nginx redirects requires adding 301 rules in nginx/redirects.conf mapping the old service path to the new slug, ensuring visitors hitting the old documentation URL are seamlessly forwarded.

You need 301 redirects for documentation files whenever a service slug or name changes, preventing 404 errors for existing internal references and external links pointing to the old documentation path.

Checking for remaining internal references involves searching the entire documentation base for the old slug name after renaming the file and updating the Services List, ensuring no broken links remain.

Using git mv to rename documentation files works, but you must also update the slug in the Services List component and add nginx redirects to maintain navigation integrity and prevent broken links.

The best way to prevent 404s after renaming a service is to add 301 redirects in nginx/redirects.conf from the old documentation path to the new slug, while auditing and fixing all internal references.