Website reading area
If text is missing or too much is translated, check the reading area first. Use site preferences to remember how a particular website should behave.
Open Site rules
Missing content
- Refresh the page after installing or updating.
- Scroll down: the default mode translates near your reading position.
- To include menus and buttons, enable all-node recognition under Advanced settings → Page recognition, then restore the original and translate again.
- For text inside an image or chart, use area translation.
Some sites keep author names, timestamps, votes, and navigation unchanged while translating articles, comments, or product descriptions. If the area you need is still missed, adjust its content rule or report the URL and area.
Explicit topic tags and Discourse category badges retain their original text. Examples include chatgpt, rate-limit, and API on forums, as well as standard tag links on blogs. Full-page and hover translation share this rule, including with all-node recognition enabled. Post titles and body text remain translatable.
In the OpenAI Developer Community, navigation, filters, and activity dates also stay in their original language. Bilingual translations appear below topic titles and excerpts, and discussion text remains translatable.
Translate every time—or leave it alone
Open Settings → Tools & learning → Website rules → Site preferences:
| Preference | Effect |
|---|---|
| Always translate | Translate new pages on that website automatically |
| Disable extension | Restore the original and stop the extension on that site; overrides automatic translation |
| Hide floating button | Hide the button while keeping shortcuts and other features available |
| Translation only | Show only translated text on this website; other websites keep the global display mode |
Preferences use the root domain and include its subdomains, without paths or ports. Re-enabling a disabled site restores its other preferences. Removing preferences returns to global defaults. Global automatic translation applies to non-disabled sites and keeps your saved list.
Choose Translation only when adding a site, or check it on an existing row. It does not enable automatic translation. Existing translations change display without another request; unchecking it returns to the global mode. Restore still returns the original text. A shortcut profile with an explicit display mode keeps its one-time choice. Google Translate supports bilingual display only, so choose another service for translation-only sites.
The extension menu also offers always-translate and disable-site controls. Restoring the current article keeps it original, including when following its table-of-contents links. Always-translate takes effect again on the next article. Turning it off affects future automatic triggers and leaves current translations in place.
Still wrong?
Content rules select article and protected areas by domain, path, and CSS selector. Effective preview checks saved matching rules and priority without visiting the website. Check the actual page after saving.
If you know webpage structure, follow Custom site rules and export a backup first. Otherwise, report a public URL, browser version, and a screenshot with private information removed on GitHub Issues. Explain which areas should translate and which should stay original.
Detailed fields are in the rule reference.
Content blocked by a no-translate marker
In the advanced JSON editor, use forceTranslate with CSS selectors matching the element carrying the marker, for example:
{
"version": 1,
"rules": [{
"id": "itch-comments",
"name": "itch.io comments",
"match": {"hosts": ["*.itch.io"]},
"forceTranslate": ["div[id^='game_comments_react_'][id*='_Game-Comments_']"],
"content": [{"css": [".post_body", ".post_body p", ".post_body li"], "atomic": false}]
}]
}This overrides only the matched element's translate="no", .notranslate, or data-notranslate="true" marker without editing page attributes. Separate markers on descendants, editors, code, hidden content, and protect/exclude rules remain protected. Match every marked ancestor you intend to override. Full-page, hover, and section translation share the result. Templates, export, overrides, and disabled rules retain the same behavior. Rules apply to content scope by default; set allScopes: true explicitly for all-node scope. The built-in itch.io rule includes this comment-shell exception.