Four mechanisms
What you are actually buying
No native product
WordPress core, Squarespace, and SmugMug do not ship a first-party translation system for the site. The path is a plugin (WPML, Polylang, TranslatePress), an app such as Weglot, duplicated pages, or a second host per language.
UI or widget only
Gallery tools often change interface labels or add a Google Translate / page-translator widget. Buttons switch language; About copy, packages, portfolio titles, and captions usually stay in one language.
Metered first-party or overlay
Wix Multilingual and Weglot-style layers provide locale paths and a switcher. Machine translation is typically billed as platform or app word credits on top of the site plan.
Native spine + BYO keys
Locale paths and a switcher on the studio site; machine translation billed to your DeepL, Gemini, or OpenAI account; pages and posts publish per locale; missing entity rows soft-fall to primary; unpublished locale URLs return 404.
What the category ships today
Most photographer-facing site products treat language as an add-on, not as part of the media spine.
Squarespace’s help center documents multilingual through Weglot. Format markets the same Weglot integration for portfolio sites. SmugMug’s built-in option is a Google Translate content block. WordPress core has no multilingual product; WPML, Polylang, and TranslatePress are the usual stack, with their own licenses and update risk on top of hosting.
Wix Multilingual is first-party: language switcher, locale URL paths, and hreflang-style signals. Machine translation on that path is still commonly sold as word credits, and localized URL slugs remain a known limit of the product.
UI strings vs site copy
Clients decide from About text, package names, portfolio titles, and captions. If only “Download” and “Favorites” change language while that authored copy stays in English, the site is bilingual in the chrome and monolingual where it matters.
Without a translation model for those fields, the practical workarounds are duplicated pages with separate navigation, a second domain, or an overlay that rewrites text after render. Each one adds maintenance when the primary language changes.
How translation gets billed
Weglot and similar overlays usually meter translated words and destination languages separately from your site subscription. Plans scale with word count; exceeding the allowance can stop new translations or force an upgrade. Duplicating the site onto another domain avoids the meter and creates two archives to keep in sync.
On WordPress, the bill is the plugin (and often a companion for WooCommerce or SEO), plus the cost of keeping that stack compatible with themes and page builders after updates.
Bring-your-own keys reverse the meter: the studio pays DeepL, Gemini, or OpenAI directly for machine translation, and the platform supplies locale routes, the switcher, and publish rules instead of selling translation credits.
Locale URLs and missing translations
Each locale URL should match what you published for that language. Soft-falling a missing portfolio title or caption to the primary language shows a gap in one field. Serving a full primary page under a `/fr/` path, or swapping copy only in the browser, can leave visitors and crawlers looking at different documents for the same URL.
ArtInStack returns 404 for unpublished locale extras rather than filling the path with primary HTML. Soft-fall applies to missing entity fields, not as a substitute for a published page. For Search Console, sitemaps, and crawl verification on those URLs, see What Search Console is for.
| Mechanism | What you get |
|---|---|
| No native product | Plugin, app, duplicated pages, or a second host |
| UI or widget only | Interface language changes; authored copy often does not |
| Metered first-party or overlay | Locale paths and switcher; translation billed as credits |
| Native spine + BYO keys | Locales on the studio archive; API usage on your provider account |
Where ArtInStack fits
On ArtInStack, locales ride the same media spine as the public site, portfolios, products, and captions. You attach your own DeepL, Gemini, or OpenAI key for machine translation. Pages and posts publish per locale; entities soft-fall when a translation row is missing.
Connecting providers, placing the Language Switcher, and choosing which languages to enable are covered in Multilingual site languages. For delivery, print, and site fit against SmugMug, Pixieset, Squarespace, and WordPress, see One unified OS for your visual business.
Add languages on the same archive
Locale paths, a switcher, and your own translation keys. Then check crawl the same way you would for any other public URL.
Also in Guides: One unified OS for your visual business · Choosing the right platform · What Search Console is for