Localization sweeps catch shorter strings and path-prefixed locales

Locale sweeps now flag short untranslated strings like menu items and buttons, not just full sentences, and correctly handle sites that keep locales under a path prefix.

Localization sweeps got more accurate and more flexible. The untranslated-content check previously only caught full sentences, so short strings such as menu items, buttons, and nav labels could slip through untranslated. It now compares each line of a page against the base-locale rendering of the same page and flags anything that matches, which works even for locales the old sentence-based check could not read. A related check catches the opposite case: a page where the base locale's own text leaks into the locale you are testing.

Sites that keep their base locale under a path prefix (for example /en-us/ next to /fr-ca/) are now handled correctly instead of producing malformed target URLs, and a sweep can run headed instead of headless when you want to watch it execute.

  • Flags short untranslated strings, not just full sentences
  • Catches pages where the base locale's own text leaks into a translated page
  • Fixes apps created from the Studio UI silently running a sweep with zero checks configured
  • Handles sites that keep locales under a path prefix
  • Sweeps can run headed so you can watch one execute