Burgi, the main question I have is why do you have the routes setup the way you currently do? For example, you have the template group was-ghet, and the template name wochenprogramm, which is a valid url of /was-ghet/wochenprogramm/, but you have the route defined as /was-ghet/, so if the user goes to /was-ghet/ they will see the wochenprogramm template. Why not just use the index template in the was-ghet group and not define a template route? All your template routes are defined this way, and it doesn’t seem to add any real benefit. You could just as easily use the index.html template in all of those groups and don’t define any routes. I could be wrong, but it doesn’t seem like you’re using EE’s native template routes correctly. If this is not the case, would you be able to further explain why you have the routes defined the way you do?

The route translations in Publisher should be the exact same thing in your default routes, just the translated version.

Based on what you’re doing, I’m not even sure you need routes defined at all. Routes are usually just used when you need to do something out of the norm with normal template routing… it looks like you’re just using EE’s templates as they normally would be used to create URLs. I think you can ignore the Routes all together, and the Route field in Publisher, and just enter the template translations into the field that has “Template” as the placeholder.

Did you read the EE docs about template routes? https://docs.expressionengine.com/latest/templates/routes.html

Can you edit the ticket and use the provided fields and add CP access so I can login and take a closer look?

Regarding “/de/fasten” and “/de/fasten/one” showing the same content, that is actually not a good idea SEO wise. You have 2 URLs showing the same stuff, Google actually penalizes you for that.

I’m not trying to be difficult, I’m just not sure why you want the content of the “fasting/one” template to show at the url fasting… why not just use the “fasting/index” template? I’m not understanding why you need to use routes at all. Based on what information I have so far, I think you’re overcomplicating it. Routes are only meant to be used for when you’re doing complicated URL routing. So far what I’ve seen is just “template_group/template” based default EE routing behavior, but you’re not taking advantage of the index template and EE’s default behavior.

If you look at the documentation it uses an example with an “events” template group: https://docs.expressionengine.com/latest/templates/routes.html#usage If you were to copy that example and put it into Publisher’s routes, then it’ll look like this:

/veranstaltungen/{date:regex[(\d{2}-\d{2}-\d{4})]}

https://www.dropbox.com/s/eb7jacm27xkfrcv/ticket-2173-events-route.png?dl=0