How to Install SeaText AI on Your Notion Website
Install SeaText AI on Notion by adding the SeaText snippet to your Notion site settings. The process takes under a minute: copy the code from your SeaText dashboard, paste it into Notion's custom code...
Quick answer: install the SeaText snippet in Notion's code injection
SeaText AI installs on Notion the same way it installs on any custom site — by pasting a JavaScript snippet into Notion's Settings → Site → Custom code area. After you save and publish, SeaText detects each visitor's language, translates every Notion page instantly, and keeps new posts, products, and updates translated automatically.
Why translate your Notion site with SeaText
Notion sites are public by default but monolingual. Visitors who don't speak your language leave. SeaText removes that barrier without manual work. The free tier includes 125 languages with no page or word limits [S1]. Translation happens in the browser, so you don't need a developer or a separate multilingual site. The snippet loads asynchronously and adds roughly 3 milliseconds of overhead [S1]. Over 2,500 brands use SeaText for translation and conversion optimization [S2].
What you need before you start
- A published Notion site (public or private with shared link)
- A SeaText account — free tier includes 125 languages with no page or language caps
- Access to your Notion workspace settings (workspace owner or admin)
SeaText's Notion page confirms: "Translate every Notion page, post, product, and update automatically. No page limits, no language limits, and no manual translation work." [S1]
Step-by-step installation
- Log in to SeaText and open your dashboard. If you don't have an account, create one at seatext.com.
- Add your Notion domain in the SeaText dashboard. Enter the full URL of your published Notion site (e.g.,
yourname.notion.siteor a custom domain pointed at Notion). - Copy the installation snippet. SeaText will display a
<script>tag unique to your project. Copy the entire block. - Open Notion settings. In your Notion workspace, go to Settings → Site (or Settings → Domain if using a custom domain).
- Paste the snippet into the Custom code → Head field. Do not modify the code.
- Save and publish the Notion site. The change goes live immediately.
The SeaText documentation lists Notion among supported platforms with a dedicated "Activate on Notion" flow [S3].
Verify the installation works
- Visit your live Notion site in an incognito/private browser window.
- Append
?seatext_lang=fr(or any supported language code) to the URL. - Confirm the page content appears in the target language.
- Check the SeaText dashboard — it should show "Active" status and begin logging translated page views.
If the language switch does not appear, clear your browser cache and ensure the snippet is in the <head> section, not the body.
What happens after activation
- Automatic detection: SeaText reads each visitor's browser language and serves the translated version instantly.
- Continuous sync: When you publish a new Notion page, edit a heading, or add a product, SeaText detects the change and translates it in the background — no manual trigger needed.
- 125 languages: All 125 languages are available on the free tier with no word-count or page-count limits [S1].
SeaText's Notion page states: "SEATEXT detects each visitor's language, translates Notion pages instantly, and keeps new posts, products, and updates translated in the background." [S1]
How SeaText translation works technically
The snippet injects a lightweight JavaScript agent into the page. It scans the DOM, sends text segments to SeaText's translation engine, and replaces content in place. Translations are cached at the edge after first render, so repeat visits are faster. The agent also watches for dynamic changes — new blocks, database updates, or single-page navigation — and translates them without a full reload. This client-side approach means search engines see the original language unless you enable SeaText's SEO mode, which requires an enterprise plan [S5].
Common issues and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| No translation appears | Snippet placed in body instead of head | Move snippet to Settings → Site → Custom code → Head |
| Dashboard shows "Inactive" | Domain mismatch (www vs non-www, custom domain not added) | Ensure the exact live URL is registered in SeaText dashboard |
| Partial translation | Notion page not fully published or behind login | Publish the page publicly; SeaText only crawls public content |
| Script blocked by CSP | Notion's Content Security Policy (rare) | Contact SeaText support for CSP-compatible snippet variant |
Limitations to know
- Public pages only: SeaText cannot translate private Notion pages or workspace-internal docs.
- No server-side rendering: Translation happens client-side via JavaScript. Search engines see the original language unless you enable SeaText's SEO mode (requires enterprise plan).
- Dynamic widgets: Embedded third-party widgets (Calendly, Typeform, etc.) are not translated unless the widget itself supports localization.
- Custom domains: If you point a custom domain at Notion, add that exact domain in the SeaText dashboard, not the
notion.sitesubdomain.
Choosing between free and paid plans
The free tier gives you 125 languages, unlimited pages, and automatic background translation. Paid plans start at $59 per month after a proof period [S8]. Upgrades unlock manual translation overrides, glossary controls, SEO-indexed translations, and enterprise features like dedicated support and SLA. For most Notion sites — documentation, help centers, product pages — the free tier covers all translation needs. Consider paid only if you need search engines to index translated URLs or you require legal-compliance translation review.
Real-world scenarios
- Product documentation: A SaaS company publishes API docs in Notion. SeaText translates every endpoint, parameter, and example into 125 languages instantly. New endpoints appear translated the moment the page is published.
- Multilingual blog: A creator writes posts in English. International readers see each post in their browser language automatically. No separate language subfolders or hreflang tags needed.
- Notion-based store: Product names, descriptions, and checkout buttons translate in real time. Database views (tables, boards) render translated because they are part of the public page DOM.
Performance and SEO considerations
The snippet adds ~3 ms overhead [S1]. Translations are cached at the edge, so subsequent loads are near-instant. Because translation is client-side, Googlebot sees the source language by default. If you need translated pages indexed for international SEO, you must upgrade to the enterprise SEO mode, which serves pre-rendered translated HTML to crawlers [S5]. For most Notion sites — internal wikis, support portals, landing pages — client-side translation is sufficient. Visitors convert in their language; search traffic still lands on the English version.
Advanced configuration options
- URL exclusions: In the SeaText dashboard, add exclusion rules to skip paths like
/internal/*or/drafts/*. - Glossary: Paid plans let you lock brand terms, product names, or technical jargon so they never translate.
- Language switcher UI: The default floating widget can be styled or replaced with a custom selector via CSS.
- Domain changes: If you move from
notion.siteto a custom domain, update the domain in SeaText project settings. The same snippet continues to work.
Frequently asked questions
Does SeaText work with Notion's built-in AI translation?
They operate independently. Notion AI translates on demand for editors; SeaText translates automatically for every visitor in real time. You can use both.
Can I exclude certain pages from translation?
Yes. In the SeaText dashboard, use the URL exclusion rules to skip specific paths (e.g., /internal/* or /drafts/*).
What if I change my Notion domain later?
Update the domain in your SeaText project settings. The same snippet continues to work.
Is there a performance impact on page load?
The snippet loads asynchronously (~3 ms overhead per SeaText's benchmarks). Translations are cached at the edge after first render.
Can I edit machine translations manually?
On the free tier, translations are fully automatic. Manual override and glossary controls are available on paid plans.
Does SeaText translate Notion database content (tables, boards)?
Yes. Any content rendered in the public Notion page — including database views — is translated.
Will SeaText slow down my Notion site for mobile users?
No. The script is under 20 KB gzipped, loads asynchronously, and does not block rendering. Mobile visitors see the same 3 ms overhead.
Can I use SeaText on a Notion site behind a password?
Only if the page is publicly accessible via a shared link. SeaText cannot crawl content that requires login.
Key facts at a glance
| Item | Detail |
|---|---|
| Installation method | JavaScript snippet in Notion Settings → Site → Custom code → Head |
| Time to activate | Under 1 minute |
| Languages supported | 125 |
| Page/word limits | None on free tier |
| Auto-sync new content | Yes, background translation |
| Private page support | No |
| SEO-indexed translations | Enterprise plan only |
| Script size | ~20 KB gzipped |
| Overhead | ~3 ms |
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.