Which languages does Marcus support?
Marcus uses Claude as its underlying model, which handles 95+ languages with varying degrees of fluency. Major European languages work exceptionally well — English, German, French, Spanish, Italian, Portuguese, Dutch, Polish, Czech, and Nordic languages all produce natural, idiomatic content.
Less common languages and non-Latin scripts are supported but may require more review. Marcus can generate content in Arabic, Hebrew, Japanese, Korean, Chinese, Thai, and others. Quality depends on how much training data Claude has seen in that language. For business-critical content in less common languages, plan to have native speakers review the output before publishing.
Marcus does not translate existing content word-for-word. Instead, it generates new content in each language based on your brief. This means tone and phrasing adapt naturally to each language's conventions rather than sounding like machine translation.
URL structure: subpaths vs subdomains
Marcus defaults to subpath structure: yoursite.com/en/, yoursite.com/de/, yoursite.com/fr/. This is the most common approach for multilingual sites and works well for SEO because all language variants share the same domain authority.
Subdomain structure (en.yoursite.com, de.yoursite.com) is possible but requires manual DNS configuration on your end. Marcus generates the sites with the correct internal linking, but you'll need to point each subdomain to the right hosting location after export.
The subpath approach is simpler and recommended unless you have specific technical requirements. Marcus sets the correct lang attributes on each page and generates hreflang link tags in the HTML head so search engines understand the language relationships.
Hreflang tags and language switchers
Marcus automatically generates hreflang annotations for multilingual sites. These are HTML tags in the page head that tell Google and other search engines which language versions of a page exist and how they relate to each other. Proper hreflang setup prevents duplicate content issues and helps users land on the right language variant from search results.
The language switcher appears in your site's navigation. Marcus builds a simple dropdown or link list that lets visitors switch between language versions of the current page. The switcher respects your site's existing design system and uses native language labels (Deutsch, Français, Español) rather than English names for every language.
If you're exporting the site as a ZIP, the hreflang tags and switcher markup are included. You don't need to add or configure anything manually. They're part of the generated HTML.
Workflow: one brief per language
You don't write one brief and get five languages out. Instead, you brief Marcus separately for each language variant you want. This gives you control over regional differences in messaging, local examples, and cultural nuance.
For a German site, you might emphasize GDPR compliance and EU hosting. For a US English site, you might focus on speed and integrations. Marcus adapts tone and content based on what you tell it, so identical briefs will produce similar but not mechanically translated results.
This approach takes more time upfront than clicking a "translate" button, but it produces better results. You're not translating — you're creating localized content that reads naturally in each language.
Pricing: each language is a separate project
Marcus pricing works by project, not by language. If you want your site in English, German, and French, that's three projects. On the Builder plan (€29/month for one project), you'd need to upgrade. The Studio plan at €290/month covers up to 25 projects, which is enough for a site in ten languages with room to spare.
The free tier includes one project with up to five pages. You can use that to test a single-language site, but you won't be able to build all language variants without upgrading.
Each project exports as its own ZIP file. If you're hosting the site yourself, you'll merge the language folders into a single directory structure. If you're using Marcus hosting (available on Studio), the multilingual setup is handled for you.
Limitations and practical workarounds
Marcus doesn't offer automated synchronization between language variants. If you update the English version, you'll need to regenerate the German and French versions separately. There's no "sync all languages" button. This is intentional — translations aren't just find-and-replace operations, and forcing automatic sync leads to awkward phrasing.
Shared assets like images and icons work across languages, but you'll need to manage file paths carefully if you're self-hosting. Marcus generates relative links that assume a shared /assets/ folder at the root level.
Right-to-left languages (Arabic, Hebrew) require additional CSS adjustments that Marcus doesn't automatically apply. The content will generate correctly, but layout mirroring for RTL is manual work after export.
When multilingual makes sense
Building a multilingual site with Marcus is worth it if you're targeting specific regions with distinct languages and you have the budget for multiple projects. It's not worth it if you're just hedging bets or hoping to rank in markets you don't actively serve.
Good candidates: a SaaS tool launching in Germany, France, and Spain; a consulting firm with offices in three countries; an e-commerce brand expanding into the Nordics. Bad candidates: an English blog adding ten languages "just in case"; a local business with no international customers adding French because a competitor did.
If you're unsure, start with one language. Build the English site, see how it performs, then expand to other languages once you have traffic and demand. Marcus makes it easy to add languages incrementally — you're not locked into a decision upfront.