Localization and audit usually pull apart
Most teams bolt translation on after the fact: a page is copied per language, the copies drift, and the audit trail forks. Multiply that by a dozen markets and the version a German regulator reads is no longer the version your reviewer approved — and you can't prove otherwise.
One source, many locales
In StaticOwl a page has a single canonical version. A market (region) and a language are axes on top of it, not copies of it.
- A translation is a per-field override on the canonical page — you change only the text that differs, and the rest inherits the source
- When the source changes, its translations are flagged stale, so a localized page can't silently fall behind the original
- Each locale publishes to its own indexable URL with reciprocal hreflang and a self-canonical, so search engines see distinct, correctly-tagged pages instead of duplicate content
The audit trail spans the languages
Localization doesn't get its own, weaker history.
- Edits — source or translation — land in the same versioned, hash-chained history
- A review binds to the content hash of the version it approved; edit the page afterward and the review goes stale, in any language
- Retention sweeps and data-subject erasure apply across markets, not per copy
- An audit pulls one signed export bundle covering all locales
What you ship
A site that reads in the visitor's language and holds up to a regulator's questions — from one page your team actually maintains.
Talk to us