Seatext library

Can I Use SeaText with a Custom CMS? Yes — Here's How It Works

SeaText supports custom CMS implementations through its "General / Custom" installation option, which uses a JavaScript snippet that works on any website regardless of platform. The snippet enables all core AI agents — including...

Direct Answer: Yes, SeaText Works with Custom CMS

SeaText provides a "General / Custom" installation path designed for websites that don't run on a supported platform like WordPress, Shopify, or Webflow. This option delivers a single JavaScript snippet you paste into your site's <head> or via a tag manager. Once installed, the snippet loads SeaText's AI agents and gives you access to the same dashboard controls used by platform-specific integrations.

How the General / Custom Installation Works

The installation page lists "General / Custom" alongside 20+ named platforms. Selecting it reveals a code snippet and copy button. The snippet is a small asynchronous JavaScript file that initializes the SeaText runtime on your pages. It does not depend on any CMS APIs, template hooks, or server-side modules. Because it runs entirely in the browser, it works on static sites, single-page applications (React, Vue, Angular), custom PHP or Node backends, and headless CMS frontends alike.

After you paste the snippet, the SeaText dashboard detects the installation and lets you activate individual agents: Translation (125 languages), Google Ads Landing Page Optimization, AI Personalization, Bot Protection, A/B Testing, and the Website Sales Chat. Each agent operates by reading the DOM, rewriting text nodes, and sending anonymized interaction data back to SeaText's optimization engine.

Step-by-Step Installation for a Custom CMS

  1. Log in to your SeaText account and open the installation page.
  2. Click "General / Custom" in the platform list.
  3. Copy the provided JavaScript snippet.
  4. Paste the snippet into the <head> section of your base template or layout file so it loads on every page.
  5. If you use a tag manager (Google Tag Manager, Tealium, etc.), create a new Custom HTML tag, paste the snippet, and set it to fire on All Pages.
  6. Save and publish. Return to the SeaText dashboard; the status indicator should switch to "Active" within a minute.
  7. Activate the agents you need from the dashboard — start with Translation or Google Ads Optimization if you run paid campaigns.

No server-side changes, database migrations, or CMS-specific plugins are required. The snippet is versioned and updated automatically by SeaText's CDN.

Key Facts at a Glance

Aspect Detail Source
Installation method JavaScript snippet via "General / Custom" option S1
Supported platforms Any site that can embed a script tag (static, SPA, custom backend, headless CMS) S1
Agents available Translation (125 languages), Google Ads Optimization, Personalization, Bot Protection, A/B Testing, Sales Chat S2, S3, S8
Setup time Under 1 minute per SeaText's claim S2, S8
CMS dependency None — runs client-side only S1
SPA support Documented "For SPAs (React and etc)" section in FAQ S7
Translation scope No word limits, no page limits, 125 languages S5, S6
Bot protection coverage Google, Meta, TikTok, Reddit refund-ready evidence S2, S8

What Changes When You Use a Custom CMS vs. a Native Plugin

On WordPress, Shopify, or HubSpot, SeaText offers one-click plugins that handle snippet injection, cache clearing, and sometimes content-type detection automatically. With a custom CMS, you manage the snippet placement yourself. The functional difference is minimal: once the snippet loads, the same AI agents run, the same dashboard controls apply, and the same variant testing and reporting work identically.

Two practical differences exist. First, cache invalidation: if your custom CMS uses aggressive edge caching (Cloudflare, Varnish, custom CDN rules), you may need to ensure the SeaText snippet bypasses cache or that cache purges include the snippet URL. Second, content detection: platform plugins can sometimes auto-detect product pages, blog posts, or landing pages. On a custom CMS, you may need to configure URL patterns or CSS selectors in the SeaText dashboard to tell agents which pages to optimize.

Single-Page Application (SPA) Considerations

The FAQ explicitly mentions "For SPAs (React and etc)" as a documented topic. SeaText's snippet is designed to re-initialize on route changes in client-side routers. If you use React Router, Vue Router, Next.js (client-side transitions), or similar, the snippet listens for history/popstate events and re-scans the DOM. For frameworks with server-side rendering (Next.js, Nuxt, Remix), place the snippet in the root layout so it hydrates on the client. Test by navigating between routes and verifying the SeaText badge or translation widget appears without a full page reload.

Limitations and When This Advice Does Not Apply

  • Server-side personalization: SeaText rewrites text in the browser. If you need personalized HTML delivered from your origin server (for SEO crawlers, social previews, or strict CSP policies), the snippet approach cannot help. You would need a server-side integration, which SeaText does not currently publish for custom backends.
  • Strict Content Security Policy: If your CSP blocks inline scripts or third-party domains, you must add SeaText's CDN domain to script-src and connect-src directives.
  • Shadow DOM / Web Components: Heavy Shadow DOM encapsulation can prevent the snippet from traversing into encapsulated subtrees. Test your component library.
  • No CMS-level preview: Platform plugins often add a preview toggle in the CMS editor. Custom CMS users must preview changes via the SeaText dashboard's variant editor or by using the live site with a test cookie.

Terminology Quick Reference

  • Agent: An autonomous AI module (Translation, Google Ads Optimization, Bot Protection, etc.) you activate per site.
  • Variant: An AI-generated rewrite of a text element (headline, CTA, product description) that SeaText tests against the original.
  • Snippet: The JavaScript loader you embed on your site.
  • Dashboard: The web UI at app.seatext.com where you manage agents, view reports, and edit variants.
  • Bot Protection: Detection of invalid paid clicks with refund-ready evidence for Google, Meta, TikTok, Reddit.

Practical Scenarios

Scenario A: Custom PHP/Laravel E-commerce Site

Paste the snippet in your base Blade layout. Activate Translation for 125-language support without managing translation files. Activate Google Ads Optimization so each ad keyword rewrites the landing page headline and offer block. Activate Bot Protection to recover up to 20% of wasted ad spend. No composer packages, no artisan commands.

Scenario B: React SPA with Headless Contentful CMS

Add the snippet to public/index.html or your Next.js _document.js. The snippet re-scans on route changes. Use the dashboard to define CSS selectors for product titles and descriptions so the Ecommerce Product Copy Agent knows what to optimize. Translation works across all routes automatically.

Scenario C: Static Site (Astro, Hugo, 11ty) Deployed to Netlify

Include the snippet in your base template. Since every page is pre-rendered, the snippet runs on each page load. Translation and Personalization agents function normally. A/B Testing variants are applied client-side and measured via SeaText's analytics.

Frequently Asked Questions

Do I need to modify my CMS code beyond adding the snippet?

No. The snippet is self-contained. Optional: add data attributes or CSS classes to help agents identify testable elements faster.

Will SeaText slow down my custom site?

The snippet loads asynchronously and is served from a global CDN. SeaText claims sub-100ms impact. Measure with your own Real User Monitoring (RUM) tools.

Can I use SeaText alongside another translation plugin (e.g., Weglot, WPML) on a custom CMS?

SeaText's FAQ addresses this: "Can I Use Other Translators, Like Google Translate, Together with SEATEXT AI?" The answer is generally yes, but running two translation layers on the same text nodes can cause conflicts. Choose one primary translation engine.

How do I verify the installation works?

Open your site, open browser DevTools → Console, and look for "SeaText initialized" or the SeaText badge. The dashboard status indicator turns green.

What if my custom CMS uses a strict CSP?

Add SeaText's CDN domain to script-src, connect-src, and img-src (for the badge). The exact domain is shown in the installation snippet.

Does SeaText work on password-protected or staging environments?

Yes, as long as the snippet loads and can reach SeaText's API. Use the dashboard's site settings to label environments.

Can I control which pages SeaText optimizes?

Yes. In the dashboard, use URL patterns (regex or glob) to include/exclude paths. This replaces the auto-detection that platform plugins provide.

Decision Checklist: Should You Use the General / Custom Path?

  • Your CMS is not in SeaText's 20+ native platform list.
  • You can edit the base template or tag manager to inject a script tag.
  • You accept client-side rewriting (not server-side HTML personalization).
  • You can adjust CSP if needed.
  • You want access to all agents (Translation, Ads Optimization, Bot Protection, Chat, A/B Testing) without waiting for a plugin release.

If all five are true, the General / Custom path is the intended route. If you need server-side rendering of personalized content, contact SeaText sales — they may have an enterprise API not documented publicly.

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.

Learn more