Seatext library

Can I Use SeaText AI Without a WordPress Plugin? Yes — Here’s How

Yes, you can use SeaText AI without a WordPress plugin. SeaText AI installs through a JavaScript snippet that works on any website, and you can activate it from your account once the script is...

Yes, you can use SeaText AI without a WordPress plugin. The service offers two integration paths: a simple JavaScript embed and a full REST API. Both work on any site that lets you add custom code.

Quick comparison: Embed vs. API

CriteriaJavaScript EmbedREST API
Setup complexityCopy‑paste a snippetRequires server‑side code
Server requirementNoneYes – a backend that can make HTTP calls
Real‑time content changesAutomatic on page loadManual calls per request
Best forStatic sites, Shopify, Wix, SquarespaceCustom apps, headless CMS, mobile back‑ends
Pricing detailsCheck with the vendorCheck with the vendor

What “without a WordPress plugin” actually means

WordPress plugins are a convenient shortcut, but SeaText AI does not depend on the WordPress ecosystem. The core technology is a JavaScript snippet that runs in the browser. As long as you can place that snippet in a page that loads on every visit, the AI will work.

The same snippet works on plain HTML, React, Vue, Shopify, Wix, Squarespace, or any platform that permits custom JavaScript. For WP Engine users, SeaText recommends the WP Engine custom‑JavaScript plugin – a hosting‑specific tool, not a SeaText‑specific WordPress plugin.

Prerequisites before you start

  • A SeaText AI account. Create one at the General Integration page.
  • A public domain name. Development URLs such as localhost are blocked for security reasons.
  • Access to edit the site’s HTML head or footer, or a site‑wide custom‑code area.
  • If you host on WP Engine, install the WP Engine custom‑JavaScript plugin first.

Embed method: step‑by‑step code

  1. Log in to your SeaText AI account.
  2. Navigate to General Integration and copy the JavaScript snippet provided.
  3. Paste the snippet into the <head> or <footer> of every page. Example:
<!-- SeaText AI embed start -->
<script src="https://cdn.seatext.com/integrations/seatext.js" async></script>
<script>
  window.SeaTextConfig = {
    apiKey: 'YOUR_PUBLIC_API_KEY',
    siteId: 'YOUR_SITE_ID'
  };
</script>
<!-- SeaText AI embed end -->

Save and publish the changes. The script loads on every page and stays inert until activation.

API method: overview and authentication

The API gives you full control from your backend. It is useful when you need to generate variants on demand, integrate with a headless CMS, or combine SeaText AI with other services.

  1. Generate an API token in the SeaText AI dashboard (Settings → API Access).
  2. Include the token in the Authorization: Bearer <token> header of every request.
  3. Call the endpoint https://api.seatext.com/v1/variants with a JSON payload describing the page URL and language.

Simple curl example:

curl -X POST https://api.seatext.com/v1/variants \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
    "url": "https://example.com/product",
    "language": "en",
    "content": "Original page HTML or markdown"
  }'

The response contains generated variants you can store or serve directly.

How to activate and verify the connection (embed)

  1. Visit or refresh your website several times and stay on a page for at least 40 seconds. This triggers the AI to link the domain to your account.
  2. Wait at least 5 minutes. Your site name should appear next to the SeaText logo on the General Integration page.
  3. If the name does not appear after 10 minutes, contact SeaText support as the documentation advises.

Security considerations

  • Domain verification: SeaText only activates on domains that belong to the account. This prevents a malicious site from hijacking your token.
  • API token scope: Tokens grant full write access to variants. Store them securely on the server side; never expose them in client‑side code.
  • Content integrity: The embed script runs in the visitor’s browser. It does not modify server‑side HTML, reducing risk of injection attacks.
  • Data privacy: SeaText processes content to generate variants. Review the privacy policy to ensure compliance with GDPR or CCPA if you handle personal data.

Performance impact

  • The embed script is loaded asynchronously, so it does not block page rendering.
  • Typical load time addition is under 200 ms on a standard 3G connection.
  • API calls add network latency equal to the round‑trip time of your server to SeaText’s endpoint (usually 100‑300 ms).
  • Cache generated variants on your CDN to avoid repeated API calls and keep page speed high.

Troubleshooting common errors

  1. Site name does not appear after 10 minutes: Verify the snippet is present on every page, not just the homepage. Check browser console for 404 errors on the script URL.
  2. API returns 401 Unauthorized: Ensure the token is correct, not expired, and included in the Authorization header.
  3. Variants are blank or unchanged: Confirm the content field in the API payload contains the full HTML of the page. Missing markup can cause the model to skip generation.
  4. Script blocked by CSP: Add https://cdn.seatext.com to your Content‑Security‑Policy script-src directive.

Comparing API vs. embed code

The table above gives a high‑level view. In practice:

  • Use the embed when you need a quick, zero‑maintenance integration.
  • Choose the API when you require server‑side control, custom variant pipelines, or need to integrate with a headless architecture.

Key facts about SeaText AI integration

ItemDetail
Installation methodJavaScript code snippet or REST API
Account requiredYes, create a SeaText AI account first
Supported platformsAny site that allows custom JavaScript or server‑side HTTP calls
Multiple domainsOne account per primary URL; separate accounts for each domain
LocalhostBlocked for security reasons
Activation checkVisit pages, stay 40 seconds, then wait up to 10 minutes for confirmation
WP EngineInstall the WP Engine custom‑JavaScript plugin to add the snippet

Limitations to know before you install

  • One primary URL per account. Each SeaText AI account links to a single domain. If you need both a development and a production site, create two accounts. This prevents cross‑domain data leakage.
  • Localhost is blocked. Development environments must use a real, publicly reachable domain. Otherwise the AI cannot associate traffic with your account, leading to activation failures.
  • Activation requires visitor behavior. The AI stays inert until a real visitor loads a page and stays for at least 40 seconds. Automated testing tools that load pages instantly may not trigger activation.
  • Confirmation can take up to 10 minutes. If the site name does not appear, the installation may be incomplete or the script may be blocked by a firewall or CSP.
  • No built‑in multi‑site management. Managing many sites means handling many separate accounts, each with its own API keys.

These limitations matter most for teams that rely on rapid staging environments or need a single dashboard for many domains.

Frequently asked questions

Do I need a WordPress site to use SeaText AI?

No. The service works on any website where you can add custom JavaScript or make HTTP requests.

What if my hosting provider blocks custom JavaScript?

Check the provider’s documentation. For WP Engine, SeaText supplies a dedicated plugin. For other hosts, you may need to enable a “custom code” feature or ask support.

Can I use SeaText AI on localhost?

No. The integration deliberately blocks localhost and other non‑public domains for security reasons.

How long does installation take?

Embedding the snippet takes under a minute. Activation requires a 40‑second visit and up to 10 minutes for confirmation.

Can I use one SeaText AI account for multiple websites?

No. Each account is tied to a single primary URL. Create separate accounts for each site you want to power.

What if the website name doesn’t appear after 10 minutes?

Contact SeaText support. Common causes are missing the snippet on all pages, CSP blocks, or network firewalls.

When should I choose the API over the embed?

Pick the API if you need server‑side control, custom variant pipelines, or integration with a headless CMS. Use the embed for quick, low‑maintenance setups.

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.

Learn more