Your checklist looks complete, so I’d suspect this is related to HubSpot’s routing cache rather than a configuration issue. When language settings are changed on an existing multilingual setup, HubSpot doesn’t always refresh the routing immediately, which matches your symptoms of the settings looking correct while the site still forces /de/ and the root URL returns a 404.
There’s a HubSpot Community thread describing very similar behavior, along with a workaround that has helped others:
The workaround is to temporarily change the homepage slug to something that has never been used before (for example /temp123), publish it, verify it’s live, then unpublish it, remove the slug so it’s blank again, and publish once more. That publish cycle appears to force HubSpot to regenerate the routing instead of continuing to serve the previous configuration.
Since you’ve already confirmed the multilingual settings, I’d be curious whether this multilingual group originally used /de prefixes before “Use prefix in slug” was disabled. If so, it’s possible the group is still holding on to the old routing metadata. If the slug reset doesn’t help, creating a brand new multilingual homepage group would be a good way to determine whether it’s stale metadata or an account level routing issue.
Thanks for laying this out so clearly, it really helps! While we wait for someone from the community to jump in, here are a few resources that might be useful in the meantime:
Also tagging in a few folks who may have run into this before:
Welcome to the Community @jasmin! It looks like maybe you’ve got an answer from @FYossef - it looks like a good solution (I agree it looks more like a HubSpot routing/cache issue, not a missing domain or SSL setting). Hopefully that helps!
From your description, the setup sounds correct, so a few things come to mind:
Verify that the German page is actually selected as the Primary page within the multilingual language group. Sometimes the label looks correct, but the group wasn’t properly updated.
Check Settings > Content > Domains & URLs > Language Settings and confirm that German (Switzerland) is set as the primary language for that domain and that “Use prefix in slug” is disabled for the primary language.
Open the page settings for the German homepage and confirm the content slug is truly blank (not “/” or “de”). Republishing the page after saving can sometimes refresh the routing.
If the multilingual group was created after the page already existed, it’s possible the language group retained an old URL mapping. In that case, I’ve seen recreating the multilingual variation (or, as a last resort, recreating the language group) resolve unexpected routing behavior.
The fact that https://www.workwithjasmin.com/ returns a 404 instead of redirecting suggests HubSpot isn’t recognizing any page as the root page for that domain, rather than an SSL or DNS issue.
One question: Was this homepage originally created as a standalone page and later converted into a multilingual group, or was it multilingual from the beginning? That detail could help narrow down whether this is a configuration issue or stale metadata.