Limiting the Finding in Magento
Check URL suffixes and rewrites along with web server rules. An additional normalization must not work against the generated catalog address.
Where to check the setting in Magento
Check URL suffixes and generated URL rewrites in the relevant Store View along with web server redirects. Compare the URL linked in the catalog with the final answer. A global slash rule must not have to correct the address generated by the shop for every page call.
Example of this specific finding
Illustrative control case: /consultation and /consultation/ deliver the same content each with 200 and different canonicals. The file address /assets/app.js should be treated separately.
follow-up audit in Magento
Set the desired content URL and match links, canonical and forwarding to it. Test file and API paths as your own control cases.
Derogations and scope
With and without slash can be technically different resources. Do not use a global slash rule without checking the routing.
Reference: Magento Open Source or Adobe Commerce with classic storefront. Consider store views and extensions; other storefront architectures have their own configurations.
Classify the general error
Definition, system-independent causes and further correction examples: Unify slash variants without losing file paths