Now that I activated both, suffix and no suffix: do I have to add further configurations for no suffix? And for each language? Is there a possibility to combine the route configuration for all languages and with or without suffix? I hope You understand what I mean
Yes I know, but I want that URIs with and without suffix work.
May I ask why?
It’s generally not a good idea to have multiple URLs with the same content, even if you use the canonical meta tag.
If you want to make both formats work, I’d rather suggest to create a server-side redirect from *.html to * (or the other way around).
Regarding your question: You can nest sub routes as much as you like. Just define the common defaults in an intermediate sub route
That is not that uncommon and as long as you have canonical-urls in place, wich make sure only one of the two valid urls is indexed, everything is fine. In general canonical, menus and sitemaps all should point to the preferred format that shall be found by Google.
Ofc, with proper Canonical Tags it shouldn’t be a problem SEO wise, but IMO that’s not the only drawback.
The others (bloated caches, scattered analytics, …) might be negligible but what’s the advantage over a redirect? (just wondering)
I have three projects i had to configure that way after explicit request by customer/pm.
I see no advantage but i dislike pattern redirects on the webserver: The problem is that those redirects are not handled and known by Neos and often have unexpected side-effects. Configuring an alternate route that creates a redirect via fusion instead of renderinng the document would make sense. That way the redirect would only apply for node-uris and directly show 404 for other paths.