Transept

For marketers & content teams

Localize a landing page, CTA and all

Import the page or paste the HTML. Translate with CTA copy pinned, product terms enforced, and a marketing styleguide steering the tone. Export the localized markup back to your CMS, or push it as a new Notion / Google Doc. The campaign goes live on time.

Start translating→

Free to begin · No card required

In context✦

Landing pages are one of the highest-ROI translation surfaces for marketing teams — and one of the trickiest. A landing page isn’t a document; it’s a structured artifact with inline styles, classes, scripts, and conversion-tested copy where every word has been A/B tested in the source language. Translating it badly costs the campaign. Generic AI tools flatten the HTML, lose the styling, and rewrite the CTA into something that doesn’t convert. This workflow keeps the markup intact, pins the CTAs, applies a marketing styleguide, and renders the localized page through Vision Proofread before it ships — so the campaign goes live in twelve languages on time, with copy that holds up.

A landing page workflow, start to ship

The standard landing-page localization recipe — refined from GTM § 9 and tested with marketers running campaigns in 8+ languages.

  1. Import or paste the page

    Paste raw HTML, drop in a Webflow export, or import a Notion / Google Doc draft. Inline styles, tracking pixels, and `data-*` attributes pass through unchanged.

  2. Pin the CTAs in your glossary

    Add "Get started", "Book a demo", and any product-name strings to the glossary. They get a single deterministic translation across every language, not a different rendering per page.

  3. Apply your marketing styleguide

    Tone, voice, sentence length, idiom handling — a marketing styleguide steers the translation toward copy that converts, not copy that translates literally.

  4. Vision Proofread before publish

    Render the localized page and run Vision Proofread to catch layout breaks — a CTA that ran long in German, a headline that wrapped onto two lines.

  5. Export back to your CMS

    Copy the markup back into Webflow, Framer, or your custom stack. Or push as a localized variant in your headless CMS.

Transept translating a landing page with CTA and product terms preserved

Why this beats copy-paste into DeepL

Markup-aware

Most translators flatten HTML into plain text. Transept treats it as structure, translates only the text nodes, and reassembles. The export renders identically.

CTA-pinned

CTAs that have been A/B tested in the source language stay deterministic in the target. No A/B-tested phrase becoming a different sentence in each market.

Layout-checked

Vision Proofread catches the German-compound-noun overflow before the campaign goes live, not after.

Footnotes✦

Questions, answered without the fluff

  • Yes — any HTML fragment works. Inline styles, classes, IDs, and `data-*` attributes are preserved. Test by exporting a page, running it through Transept, and pasting the result back in.
  • Image text isn’t replaced — Transept flags it for redesign in your design tool. The rest of the page is unaffected.
  • Those run as a runtime proxy on the page. Transept gives you the localized HTML as an artifact — useful for content that doesn’t live in a CMS or where you want the variant as a static page.
  • Yes — batch translation runs the page across every target language in one queue, with the same glossary and styleguide applied.
  • Yes — export the localized HTML into your CMS or A/B testing tool (Optimizely, VWO, Google Optimize) as a variant. The localized variant runs against the source on the same page; impressions and conversions track separately. Most teams localize the winner of a source-language test rather than testing multiple localized variants from cold.
  • In Publish-Ready Mode, usually 10–15 minutes of automated work plus 20–30 minutes of selective human review on the CTA copy and headline. For a campaign-critical page, budget another hour per language for native-speaker review via client review links.
  • Transept translates the meta tags (title, description, OG tags) as part of the HTML. Hreflang tags need to be added on the destination domain (your CMS handles that). Schema markup (`Product`, `Article`) passes through with translated content.
  • Yes — export the Webflow CMS collection as CSV, run batch translation across all items, re-import to Webflow. Webflow’s native localization supports per-item translations; the bulk import covers them.
  • Yes — that specific case is one of its most reliable catches. German compound nouns frequently exceed source-language button widths; Vision Proofread renders the localized page and flags overflow before the campaign goes live.
Related✦

Keep reading around this workflow

❧

Ship the next campaign in twelve languages

Start translating→

Free to begin · No card required