Docs
Getting Started
Launch your first site with the right defaults, a narrow rollout, and a review model that feels intentional from day one.
The dashboard is a signed-in workspace. If you are new, create an account first. If you already have access, continue into the app and pick up the same guide there.
Preparation
Before you create the first site
A good first launch starts with a few strong choices, not a long setup checklist.
What to have ready
Pick one representative URL
Start from the page that best expresses your site and brand. It gives the product something coherent to discover and model.
Know your source locale
This is the language your site is authored in. Getting it wrong weakens quality and muddles review.
Know your default locale
This is the baseline locale the site falls back to. It should reflect the primary customer or market experience.
Choose the first launch markets
A small, high-confidence set of locales is almost always better than trying to cover everything immediately.
How to define success
The first success is not "we enabled every locale." It is "we launched one site, one locale, with a clear review model and a delivery policy we actually understand."
If the team can explain why a locale is approved, what routes are eligible, and whether the output is user-visible or crawlable, the product is doing its job.
Runway
The first-success runway
Follow the shortest path that produces a confident first launch. Everything else can come later.
Step 01
Activate the right billing runway
Choose the plan that gives your first rollout enough room to generate reports, run translations, and recover without interruption.
Step 02
Submit one URL and create the site workspace
That first URL anchors the workspace and creates the initial delivery, locale, and brand defaults for the site.
Step 03
Set source locale and default locale carefully
The source locale tells the product what the site starts from. The default locale tells it what baseline experience to preserve.
Step 04
Choose the initial delivery posture
Pick runtime-only if you want the fastest user-facing proof, or indexable SEO if you already know localized routes need to become crawlable.
Step 05
Review the generated brand profile
Tighten product summary, tone, audience, protected terms, style directives, and evidence before the first locale becomes a release candidate.
Step 06
Generate the first locale report
Reports let you review one locale like a launch artifact instead of treating the first output as an invisible background process.
Step 07
Approve the first locale
Approval means the locale is intentionally being released under the current delivery rules, not merely that translation work exists.
Step 08
Verify DNS and confirm live delivery
A launch is not truly live until the hostname points correctly and the delivery policy can actually take effect on traffic.
Defaults
Make the right starting choices
These are the first decisions that shape whether the launch feels controlled or chaotic.
The choices that matter most
Runtime-only vs indexable SEO
Choose runtime-only when you want user-facing proof without immediately making localized routes part of the search footprint. Choose SEO mode when crawlable localized routes are a first-class launch requirement.
Path prefix vs locale subdomain
Path prefixes are usually the simpler default for one domain. Locale subdomains fit teams that already organize markets that way.
Approved locales only vs broader presentation
Approved-only is the safest default because it preserves launch intent. Broader locale presentation is better for exploration than for controlled release.
Monitoring now or later
Monitoring is not part of the first win. Turn it on once the core launch path is already healthy and the content update pattern is understood.
Recommended first rollout
- Start with one site and one or two target locales.
- Use runtime-only delivery when the goal is live user proof rather than immediate search exposure.
- Keep locale access on approved-only until the release model feels obvious.
- Defer monitoring until after the first locale is already stable and meaningful.
Avoidable pain
Common onboarding mistakes
These mistakes make the first launch feel harder than it needs to.
Launching too many locales immediately
The fastest way to lose clarity is to scale before the first locale workflow feels clean and reviewable.
Skipping brand cleanup
If the first brand profile is vague, the team ends up doing expensive review work downstream instead of fixing the source of quality.
Treating generated output as approved output
A locale is not launch-ready just because content exists. The product model depends on deliberate approval and release posture.
Turning on every advanced control at once
Start with the narrowest set of levers needed for the first launch. Then add monitoring, broader route classes, or connectors later.