Update 301 redirects

[glenn-jocher]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

WARNING ⚠️ this PR is very large, summary may not cover all changes.

🌟 Summary

🔗 This PR standardizes many Ultralytics Docs links by removing trailing slashes from internal URLs, improving link consistency across comparison pages, the README, and GitHub issue templates.

📊 Key Changes

• Updated a large number of internal documentation links from paths like /page/ to /page across many comparison articles and reference pages.
• Cleaned up links in key repository files, including:
  • README.md
  • .github/ISSUE_TEMPLATE/bug-report.yml
  • .github/ISSUE_TEMPLATE/feature-request.yml
• Applied the same URL formatting cleanup across many model comparison docs covering YOLO26, YOLO11, YOLOv10, YOLOv8, YOLOv7, YOLOv6, YOLOv5, RT-DETR, EfficientDet, DAMO-YOLO, PP-YOLOE, and more.
• Kept page content and messaging essentially the same; this is primarily a documentation/link hygiene update 🧹

🎯 Purpose & Impact

• Improves consistency across the docs site, making links easier to maintain and less error-prone 🔧
• Helps avoid duplicate URL styles for the same page, which can reduce confusion for users and search engines 🌐
• Makes contributor-facing templates and README links cleaner and more reliable for onboarding new contributors 🤝
• Low-risk change overall: no feature or model behavior changes, just better documentation quality and navigation ✨

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/docs 🚀 PR! This is an automated message to help with review readiness—an engineer will assist shortly. Please review the checklist below to help ensure a smooth merge 😊

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/docs main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

This PR looks clean. The changes are limited to normalizing documentation URLs by removing trailing slashes, and I did not find any genuine bugs, broken diff-local syntax issues, or maintainability concerns in the modified lines shown.

⚠️ Large PR: Review focused on critical issues. Some details may not be covered.

[UltralyticsAssistant]

Merged! 🎉 Thanks @glenn-jocher for this wide-reaching docs cleanup and for improving link consistency across the repo.

As Leonardo da Vinci said, “Simplicity is the ultimate sophistication.” This PR reflects that well: a low-risk but high-value refinement that makes the docs cleaner, easier to maintain, and more reliable for contributors and users alike.

Really appreciate the attention to detail here—small improvements like this strengthen the overall Ultralytics documentation experience.