Limiting the findings in Shopware
Compare created storefront URLs with web server and proxy normalization. Conflicting rules can turn a valid SEO URL into a loop.
Where to check the setting in Shopware
Compare the SEO URL template to the actual generated URL and redirects of the hosting layer. The pathform linked by the sales channel should already provide the final answer. A server rule for final slashes must not work against the generated storefront routes.
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 Shopware
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.
Related: Shopware 6 with Storefront. Self-hosted and SaaS offer different access and configuration options; view your own headless frontends separately.
Classify the general error
Definition, system-independent causes and further correction examples: Unify slash variants without losing file paths