diff --git a/.changeset/khaki-pumas-invite.md b/.changeset/khaki-pumas-invite.md
new file mode 100644
index 000000000000..fc3b81eaa27a
--- /dev/null
+++ b/.changeset/khaki-pumas-invite.md
@@ -0,0 +1,9 @@
+---
+"@logto/experience": patch
+---
+
+opt the sign-in experience out of browser auto-translation
+
+Browser auto-translation replaces the text nodes React created (`<font><font>…</font></font>`). React's DOM bookkeeping no longer matches the document, so the next update throws `NotFoundError: Failed to execute 'removeChild' on 'Node'`; the experience app has no error boundary, so the whole tree unmounts and the user is left on a blank page in the middle of signing in or signing up — a reload is the only way out.
+
+The experience is already localized per tenant (custom phrases plus language detection), so the page now ships `translate="no"` and `<meta name="google" content="notranslate">`, which is what Chrome, Edge and Safari read before offering or applying a translation.
diff --git a/packages/experience/index.html b/packages/experience/index.html
index 8ee801b5f7b6..f83d02734a6c 100644
--- a/packages/experience/index.html
+++ b/packages/experience/index.html
@@ -1,10 +1,13 @@
 <!DOCTYPE html>
-<html lang="en">
+<!-- `translate="no"`: browser auto-translation rewrites text nodes, which breaks React's
+     DOM bookkeeping and unmounts the app mid-flow. The experience is localized per tenant. -->
+<html lang="en" translate="no">
 
 <head>
   <meta charset="utf-8" />
   <meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover">
   <meta name="robots" content="noindex,nofollow" />
+  <meta name="google" content="notranslate" />
   <title></title>
   <script>
     /* See {@link packages/schemas/src/types/ssr.ts} */
