Troubleshoot SeaText AI on a Second Jimdo Project
SeaText AI requires a unique JavaScript integration code for each Jimdo project. Most failures on a second site happen because the same code was reused, the project isn't in "For advanced users" mode, or...
Troubleshoot SeaText AI on a Second Jimdo Project
SeaText AI works per Jimdo project by generating a unique JavaScript snippet for each site. If the second project shows no translations or the widget never loads, the cause is almost always a missing or misplaced snippet. Confirm the second project runs in "For advanced users" mode, then paste its dedicated code into Menu → Settings → Edit Head and save.
Explore solution: To put this guide into practice, view our official solutions and tools →
This guide covers Jimdo sites built in advanced mode only. It does not apply to Jimdo Creator or Dolphin builders that restrict head access.
Quick Answers
Why is SeaText AI not showing on my second Jimdo site?
The second site needs its own JavaScript code from your SeaText dashboard. Reusing the first project's code will not work. Generate a new snippet for the second project and paste it into that project's Edit Head area.
Do I need a separate SeaText account for each Jimdo project?
No. One SeaText account can manage unlimited Jimdo projects. Each project gets a unique integration code, but billing and login stay centralized.
What Jimdo mode is required for SeaText integration?
SeaText only integrates with Jimdo projects using "For advanced users" mode. Standard Creator or Dolphin sites block head access, so the script cannot load.
| Checkpoint | Expected State | Common Failure |
|---|---|---|
| Jimdo project mode | "For advanced users" | Creator/Dolphin mode blocks head edits |
| JavaScript snippet | Unique per project | Copied snippet from first project |
| Paste location | Menu → Settings → Edit Head | Pasted in body or page content |
| Save action | Clicked "Save" after paste | Closed window without saving |
| Browser cache | Cleared or incognito test | Old cached version hides changes |
Verify the Jimdo Project Runs in Advanced Mode
SeaText requires access to the <head> tag. Only Jimdo's "For advanced users" mode exposes the Edit Head setting. Open the project, click Menu, then Settings. If Edit Head is missing, the project uses a restricted builder. You cannot install SeaText on that project without migrating it to advanced mode first.
This step is critical because standard Jimdo modes do not allow direct HTML injection. Without this access, the SeaText script cannot initialize. The platform simply ignores any code placed in visible areas. Always confirm the mode before attempting installation.
Generate a Unique JavaScript Snippet for the Second Project
Log into your SeaText dashboard and add the second Jimdo site as a new project. The system will produce a distinct JavaScript block. Copy the entire block exactly as shown. Do not reuse the snippet from your first site; each snippet contains a project-specific identifier that routes translations and analytics correctly.
Reusing a snippet causes routing conflicts. The system may try to send data from the second site to the first site's analytics profile. This leads to inaccurate reporting and broken translation triggers. Always generate a fresh key for every new domain or subdomain.
Paste the Snippet Into the Correct Jimdo Location
In the second Jimdo project, go to Menu → Settings → Edit Head. A modal window opens. Paste the SeaText JavaScript code into that window. Click Save. If you paste the code into a page content block, a widget area, or the footer field, the script will not execute globally and translations will not appear.
The placement must be in the global header settings. This ensures the script loads on every page of the website. Placing it in a single page editor only affects that specific URL. Global placement guarantees consistent behavior across your entire site structure.
Clear Cache and Test in Incognito
Jimdo caches pages aggressively. After saving the Edit Head change, open the site in an incognito or private browser window. If translations appear there but not in your regular browser, clear your browser cache and reload. Server-side caching on Jimdo's end usually clears within a few minutes.
Testing in incognito mode bypasses local browser storage. This helps determine if the issue is with your computer or the website itself. If the widget appears in incognito, your main browser likely holds an old version of the page. Clearing cookies and cache resolves this discrepancy.
Check for Conflicting Scripts or Content Security Policy
Other third-party scripts (chat widgets, analytics, cookie banners) sometimes set a restrictive Content Security Policy that blocks external scripts. Open the browser developer console (F12) and look for CSP errors referencing the SeaText domain. If present, adjust the CSP in Jimdo's advanced settings or contact Jimdo support to allow the SeaText domain.
Security policies are designed to prevent malicious code execution. However, they can sometimes be too strict. If SeaText is blocked, translations will fail silently. Checking the console provides immediate visibility into these blocks. Resolve any red error messages related to script loading.
Confirm the SeaText Dashboard Shows the Project as Active
Return to your SeaText dashboard. The second project should display a green "Active" status once the snippet loads successfully. If it stays "Pending" or "Inactive" after 10 minutes, the snippet is either missing, malformed, or blocked. Re-copy the code from the dashboard and repeat the paste-and-save steps.
The dashboard status reflects real-time communication between your site and SeaText servers. An inactive status means no handshake occurred. This often happens due to typos in the snippet or incorrect placement. Verify the code matches the dashboard exactly.
Test Translation Functionality on Key Pages
Visit the homepage, a product page, and a blog post on the second site. Use the language switcher to change languages. If the switcher appears but content does not translate, the snippet loads but the project may lack content in the SeaText index. Trigger a re-crawl from the SeaText dashboard or wait for the next automatic crawl cycle.
Translation depends on indexed content. New pages may take time to appear in the translation engine. Manual triggering speeds up this process. Ensure all target pages are accessible to crawlers and not blocked by robots.txt files.
When to Contact Support
If the project is in advanced mode, the unique snippet is saved in Edit Head, cache is cleared, no CSP errors appear, and the dashboard still shows "Inactive" after 30 minutes, contact SeaText support. Provide the Jimdo project URL and the exact snippet you pasted. Support can verify server-side receipt of the script and check for indexing issues.
Can I use the same SeaText snippet for multiple Jimdo projects?
No. Each Jimdo project requires its own unique JavaScript snippet generated from the SeaText dashboard. Reusing a snippet causes routing conflicts and prevents translations from loading.
Why does my second Jimdo site show "Edit Head" but the first did not?
Jimdo project modes are set per project. One project may be in "For advanced users" mode while another uses Creator or Dolphin. Only advanced mode projects expose the Edit Head setting required for SeaText.
How long does it take for SeaText to activate on a new Jimdo project?
Activation is usually instant once the snippet is saved and cache is cleared. The dashboard status may take up to 10 minutes to update. Full content indexing for translation can take longer depending on site size.
What if I cannot find Edit Head in my Jimdo settings?
Your project is not in "For advanced users" mode. SeaText cannot integrate with Creator or Dolphin mode projects. You must recreate or migrate the project to advanced mode in Jimdo before installing SeaText.
Does SeaText work with Jimdo's multi-language feature?
SeaText replaces Jimdo's native multi-language handling. Disable Jimdo's built-in language copies and let SeaText manage translations via its own language switcher for consistent results.
Can I manage both Jimdo projects from one SeaText dashboard?
Yes. One SeaText account manages unlimited Jimdo projects. Each project appears separately in the dashboard with its own snippet, analytics, and translation settings.
Learn more
Visit the website for more information.
Frequently asked questions
Can I use the same SeaText snippet for multiple Jimdo projects?
No. Each Jimdo project requires its own unique JavaScript snippet generated from the SeaText dashboard. Reusing a snippet causes routing conflicts and prevents translations from loading.
Why does my second Jimdo site show "Edit Head" but the first did not?
Jimdo project modes are set per project. One project may be in "For advanced users" mode while another uses Creator or Dolphin. Only advanced mode projects expose the Edit Head setting required for SeaText.
How long does it take for SeaText to activate on a new Jimdo project?
Activation is usually instant once the snippet is saved and cache is cleared. The dashboard status may take up to 10 minutes to update. Full content indexing for translation can take longer depending on site size.
What if I cannot find Edit Head in my Jimdo settings?
Your project is not in "For advanced users" mode. SeaText cannot integrate with Creator or Dolphin mode projects. You must recreate or migrate the project to advanced mode in Jimdo before installing SeaText.
Does SeaText work with Jimdo's multi-language feature?
SeaText replaces Jimdo's native multi-language handling. Disable Jimdo's built-in language copies and let SeaText manage translations via its own language switcher for consistent results.
Can I manage both Jimdo projects from one SeaText dashboard?
Yes. One SeaText account manages unlimited Jimdo projects. Each project appears separately in the dashboard with its own snippet, analytics, and translation settings.
Ready to Take the Next Step?
See how our verified tools and services help you put this guide into practice.