Weglot?

NOT REALLYA prototype of the interface is possible, but the durable product depends on difficult systems beyond the UI. Build a safer adjacent workflow instead.

BUILD FIRST

A non-sensitive or read-only version of the core experience
A manual review step wherever correctness or trust matters
A narrow companion tool that removes a real piece of work

LEAVE FOR LATER

Regulated decisions, payments, or irreversible actions
Claims of correctness, compliance, or uptime that the MVP cannot support
Sensitive integrations until security, support, and auditability are ready

RESEARCH NOTES

What this tool actually does.

Checked 2026-09-06

Weglot is a SaaS website localization/translation platform that turns an existing website into a multilingual site without code. It connects to 70+ CMS/website platforms (WordPress, Shopify, Webflow, custom sites) via a no-code install, then auto-detects new content and translates it. It supports 110+ languages using AI engines (DeepL, OpenAI, Gemini) plus an optional custom 'AI Language Model' that learns a brand's tone from manual edits. Translated pages live under language-specific URLs (subdirectories, subdomains, or top-level domains) with hreflang tags and translated metadata for multilingual SEO. It adds a language switcher and auto-redirects visitors based on browser settings. Editing tools include a Translations List, a Visual Editor for in-context translation, glossary rules ('always/never translate'), translation memory, custom languages (e.g. Mexican Spanish), and CSV/XLIFF e

SOURCES

RESEARCHED BUILD PROMPT

Give this to your coding agent.

Build a self-hosted web app that replicates the core Weglot-style workflow: turning an existing static or CMS-backed website into a multilingual site without rewriting it. The app should let a user register a site URL, pick target languages, and have the system crawl pages, extract translatable strings (headings, paragraphs, metadata, alt text, forms), and produce machine translations that the user can review and edit before publishing. Requirements: (1) a crawler that discovers pages and extracts content into a translation project; (2) integration with a translation API (e.g. DeepL or an OpenAI-compatible endpoint) with a configurable API key; (3) a review UI with a translations list and an in-context visual editor overlay showing the original vs. translated page; (4) a glossary of always/never-translate terms and a translation memory that reuses accepted translations; (5) publishing that rewrites the site into language-specific paths (e.g. /fr/) and injects hreflang tags, translated <title>/<meta> tags, and a language switcher; (6) optional visitor auto-redirection based on Accept-Language. Use a stack you can justify (e.g. Node/Python backend, a headless browser for crawling/rendering, SQLite/Postgres storage, a simple web frontend). Do NOT copy Weglot's brand, logo, copy, or UI; build an original interface. Explicitly out of scope: multi-CMS plugins, paid billing, professional human-translation marketplace, and a hosted SaaS control plane. Deliver a README covering setup, how to point it at a site, how translation keys and glossary work, and important limitations (JS-rendered content, rate limits, SEO caveats, and that machine translation quality is not guaranteed).

Visit the official product page