Localizethat
Start localizing

COMPANY CONTEXT

Adapt localization to the content you’re creating

Localizing a press release shouldn’t work exactly like localizing an ad. Localizethat starts every workspace with defaults for common content types, so you can begin without configuring anything.

Content types

  • SEO / Editorial
  • Website / Landing page
  • Paid ad
  • Social post
  • Email
  • Press release
  • Product copy
  • Plain text

Three layers

LOCALIZETHAT DEFAULT

A sensible starting point for each content type.

WORKSPACE DEFAULT

Your company can customize the behaviour it wants as standard.

One-time override: change behaviour for a single localization without changing the workspace default.

What differs between content types

  • Ads may be more adaptive and concise.
  • Press releases stay closer to source.
  • SEO content preserves search intent and structure.
  • Product copy prioritizes terminology and specifications.

These are illustrative defaults, not regulatory requirements. Your team decides what each content type should do.

Start with best practice

Start with best practice. Adapt it to your company.

Create your first localization

Related guides

Company Context

The two kinds of context in Localizethat: what your team controls, and what grows from approved work.

Brand voice

How your company should sound across different types of content.

Market rules

Define how communication should adapt between markets without having to repeat the instructions every time.

Start localizing All resources