translate-sitelisted

# Claude Translator Static-site localization: turns a built site into N localized copies as real static pages. Keeps Core Web Vitals identical to the source language across LTR, RTL and CJK alike. --- ## The two decisions that define this approach **1. Substitute into built HTML by byte offset. Never re-render.** Each locale page is the source page with byte ranges spliced right-to-left. The document is never re-serialised from a DOM, so inlined critical CSS, the LCP element, asset hashes and the `width`/`height` attributes that hold CLS all carry over untouched. That is *why* locale pages match the source on CWV rather than merely resembling it. The alternative — real framework i18n — re-renders every page through the critical-CSS step. Critical-CSS tooling is known to drop a small, unpredictable share of each page's classes, which shows up as layout shift. Multiplying that across every locale is the biggest risk available. **Do not take it**, and say so if asked to "just use the framework's i18n". **Evidence, when the user asks whether this really preserves performance.** `doctranslator.com/fr` was built by this pipeline; against the English original it has 2,743 tags in identical sequence and all 2,031 `class` attributes matching, with page weight up 0.74% (French is longer). PageSpeed performance on 2026-08-25: desktop 100 vs 100, mobile 98 vs 98, with accessibility, best practices and SEO at 100 on every run of both. Anyone can check the markup claim in ten secon