Symptoms You Might Notice

You download the SeaText file from your account, place it in your Odoo addons folder, and refresh the Apps list. Nothing appears. You enable developer mode, click "Update Apps List", still no module. This is a common point of confusion.

Many users spend hours checking file permissions, verifying the addons path, and restarting the Odoo service. The module simply never shows up because it does not exist as an installable Odoo module.

Why SeaText Won't Show Up in the Apps List

SeaText integrates with Odoo through a JavaScript snippet, not through a traditional Odoo module. The Odoo Apps list only shows modules that are installed via the addons directory. SeaText is not such a module. Instead, you add the snippet to your website using Odoo's built-in "Embed Code" block. This means you do not need to place any file in the addons folder.

The snippet approach was chosen deliberately. A traditional Odoo module requires server-side installation, database migrations, and version-specific compatibility testing. A JavaScript snippet runs in the browser, works across Odoo versions, and updates automatically when SeaText improves its AI models. You get new features without upgrading Odoo or waiting for module releases.

What You Need to Do Instead

Follow these steps to install SeaText on your Odoo website:

1. Get a SeaText account. If you don't have one, create an account at seatext.com. The account is required to generate your unique JavaScript snippet.
2. Log in to your Odoo account and go to the Website module.
3. Edit the page where you want the SeaText widget to appear. Click the "Edit" button in the top-right corner.
4. Find the "Embed Code" block. Scroll through the "Blocks" panel on the left until you reach the "Dynamic Content" section. Drag the "Embed Code" block onto the page where you want the widget.
5. Paste your SeaText snippet. Click the "Edit" button on the new block, paste the JavaScript code from your SeaText account, and click "Save".
6. Hide the block on desktop (optional but recommended). In the "Visibility" section, select "Hide on Desktop" to avoid showing an empty block on desktop screens. Then click "Save" again.

According to the official SeaText Odoo integration guide, the Embed Code block lives under the "Dynamic Content" section of the Blocks panel. After placing the block, you click the "Edit" button in the right panel to input the code, then save. The "Hide on Desktop" option is in the "Visibility" section.

Common Mistake: Trying to Install a Module That Doesn't Exist

Many users expect SeaText to appear as a module in the Apps list because they are used to installing Odoo modules that way. SeaText is designed differently – it runs as a lightweight snippet on your website. If you placed a file in the addons folder, you can remove it. It will not make SeaText appear in the apps list.

This mistake stems from a mental model mismatch. Odoo's module system is powerful for backend features like accounting, inventory, or CRM. But for frontend website widgets that need to run on every page load without server-side logic, a snippet is simpler and more reliable. The snippet loads asynchronously, so it never blocks page rendering.

Prerequisites for the Integration

• An active SeaText account (free trial available).
• Administrative access to your Odoo Website module.
• A valid, real domain (development URLs like localhost are restricted for security reasons).

The domain requirement is important. SeaText ties each account to a single primary URL. This prevents abuse and ensures accurate analytics. If you run multiple Odoo websites on different domains, you need separate SeaText accounts. Subdomains count as separate domains unless configured otherwise.

Troubleshooting: If the Widget Still Doesn't Appear

If you have followed the steps and the SeaText widget does not show up on your site:

• Check your SeaText account. Make sure you are using the correct snippet for the domain you are testing on. Multiple domains require separate accounts.
• Clear your Odoo website cache. Go to Website > Configuration > Settings and clear the cache.
• Ensure the Embed Code block is not hidden on the device you are testing on. Double-check the visibility settings.
• Verify the JavaScript snippet is correct. Log in to SeaText, copy the code again, and paste it fresh.
• Test on a production URL. Development URLs like localhost or dynamic dev domains may not work properly.

Dynamic development domains (like those from ngrok or temporary staging environments) often fail because SeaText cannot reliably associate traffic with your account. Use a real domain with proper DNS for testing.

How the Snippet Works Under the Hood

When a visitor loads your Odoo page, the browser executes the SeaText snippet. The snippet creates a lightweight connection to SeaText's AI infrastructure. It analyzes visitor behavior — scroll depth, dwell time, click patterns — and dynamically rewrites page elements to match the visitor's intent.

For example, if a visitor arrives from a Google Ads campaign for "CRM software for small business", the snippet can rewrite your headline, value propositions, and call-to-action to match that search term. This happens in milliseconds, before the visitor sees the page. The AI agents run continuously, testing variants and allocating traffic to winners automatically.

This architecture means zero server load on your Odoo instance. All AI processing happens on SeaText's infrastructure. Your Odoo database and Python workers are untouched.

Limitations of the Snippet Approach

While the snippet method is fast and version-agnostic, it has trade-offs:

• No backend integration. SeaText cannot directly read Odoo models, create records, or trigger server actions. It only sees what renders in the browser.
• Content Security Policy (CSP) conflicts. If your Odoo instance has a strict CSP that blocks inline scripts or external domains, the snippet may be blocked. You may need to adjust CSP headers.
• Single-page application (SPA) navigation. Odoo's website uses traditional page loads, so the snippet re-initializes on each page. This works well. If you customize Odoo to use SPA-style navigation, you may need to re-trigger the snippet manually.
• No offline mode. The snippet requires internet connectivity to reach SeaText's AI. Visitors on restricted networks may not see optimizations.

If you need deep backend integration — like creating leads in Odoo CRM from chat conversations — you would need a custom module or webhook bridge. SeaText's free AI Website Chat agent can capture leads, but pushing them into Odoo requires additional setup.

Practical Scenarios: When to Use Which Approach

Key Facts: SeaText Odoo Integration

Frequently Asked Questions

Do I need to enable developer mode in Odoo?

No. The integration does not require developer mode. You only need to edit the website page using the standard Website editor.

Can I use the same SeaText account for multiple Odoo websites?

No. Each SeaText account is linked to a single primary URL. If you have multiple Odoo sites on different domains, create a separate SeaText account for each.

What if I accidentally placed a file in the addons folder?

Remove it. It will not cause issues, but it is unnecessary. The SeaText module is not a traditional Odoo module.

Does the SeaText snippet slow down my Odoo site?

No. The snippet is lightweight and loads asynchronously. It becomes active only when triggered by visitor behavior.

How do I remove SeaText from my Odoo site?

Delete the Embed Code block from the page editor. The snippet will stop working immediately.

Is there a cost to use SeaText with Odoo?

SeaText offers a free trial. After the trial, you need a paid subscription. Check the pricing page on the SeaText website for details.

Can SeaText translate my Odoo website into other languages?

Yes. The Website Translation agent supports 125 languages with zero code. It translates entire pages dynamically while preserving layout and functionality.

Will SeaText work with my custom Odoo theme?

Yes. The snippet operates on the rendered HTML. As long as your theme outputs standard HTML, SeaText can analyze and rewrite content. Highly customized JavaScript-heavy themes may need testing.

How does SeaText handle GDPR and data privacy?

SeaText processes visitor behavior data to optimize content. Review SeaText's privacy policy and data processing agreement for compliance details. The snippet does not collect personally identifiable information by default.

Can I A/B test SeaText against my original copy?

Yes. SeaText's AI A/B Testing agent automatically generates variants and uses multi-armed bandit allocation to send most traffic to winners. You can also run manual split tests.

To remove an unwanted authority link from Google's index, start by getting the link removed from the source page. If that's not possible, use Google's Disavow tool to tell Google to ignore the link. You can also use Search Console's Removals tool if the page is on a site you own. This guide walks through the full process step by step.

What counts as an unwanted authority link?

An unwanted authority link is a backlink pointing to your site from a page you didn't ask for and that may hurt your rankings. These links often come from spammy directories, irrelevant niche sites, or paid link schemes. Even if the linking site looks strong in domain authority, a bad context or a link you didn't approve can send a negative signal to Google.

You might also want to remove a link because you changed your brand or the page no longer fits your content. Whatever the reason, the removal process follows the same pattern.

Step 1: Audit your backlink profile

Before you can remove anything, you need to know exactly which links point to your site. Open Google Search Console and export the full list of backlinks. You can also use a backlink analysis tool like Ahrefs or SEMrush to filter for suspicious patterns.

Look for:

• Links from domains unrelated to your niche
• Links from sites with obvious spam signals (auto-generated content, no contact page, heavy ad density)
• Links with exact-match anchor text that looks forced
• Links from sites that have been penalized by Google in the past

Make a list of the unwanted ones. Check the source page to see if the link is still live.

Step 2: Remove the link at the source

The cleanest way to remove an unwanted authority link is to delete it from the original page. If you control that site, simply edit the page and remove the link or delete the page entirely.

If another site owns the page, contact the webmaster. Find the contact page or email address, and send a short, polite request. Explain which link is causing a problem and ask them to remove it or add a rel="nofollow" attribute. Be clear and give the exact URL.

If you don't hear back within a week, send a follow-up. If the webmaster never responds, move to the next step.

Step 3: Use Search Console's Removals tool (if the page is yours)

When the unwanted link sits on a page you own, you can temporarily block that page from Google search results using the Removals tool in Google Search Console. Go to Removals > New request and enter the URL of the page that contains the link.

This is a temporary fix. It hides the page from search results for about six months. To make the removal permanent, you must also delete or update the page itself. Use this only when you need a quick stopgap while you edit the page.

Step 4: Submit a disavow file

If the link is on someone else's site and they refuse to remove it, you can tell Google to ignore that link completely. Google's Disavow tool lets you submit a list of domains or URLs you want Google to disregard when evaluating your site.

Create a plain text file with one domain or URL per line. Upload it to the Disavow Links tool in Google Search Console. This doesn't remove the link from the internet; it just tells Google not to count it. Google will re-crawl and reprocess the file, which can take a few weeks.

Use disavow carefully. Only add links you are confident are toxic or irrelevant. Disavowing a good link can remove positive value.

Step 5: Verify and monitor

After you've removed or disavowed the link, wait two to four weeks and check Google Search Console. Confirm that the link no longer appears in your backlink report, or that Google has dropped it from its evaluation.

If you used the Removals tool, re-check after the temporary block expires to ensure the page is still gone or updated. If you disavowed, look at your Search Performance report to see if any ranking changes follow.

Key facts about authority link removal

Here's what you need to know about acting on unwanted links:

Seatext's own Authority Builder gives you control over your links. Every published link is a dofollow editorial link on a Seatext-controlled subdomain, and you can remove it from your dashboard at any time.

Limitations and when this advice doesn't apply

The disavow tool isn't a magic undo button. It's a fallback for links you couldn't remove at the source. It also doesn't affect your own pages if you're trying to remove a link that points out from your site. In that case, you'd edit your own page directly.

If the link comes from a high-authority, relevant page and you just don't like the anchor text, removing it might not be worth the risk. Weigh the potential harm against the effort required.

This guide assumes you're dealing with a standard backlink. If the link is part of a paid link network or a clear violation of Google's policies, you should also consider filing a spam report.

Common mistakes to avoid

• Disavowing links without checking relevance or spam signals first.
• Using the Removals tool on someone else's page.
• Not following up with webmasters after a first request.
• Uploading a disavow file that contains whole domains when only specific pages are problematic.
• Expecting instant results—Google takes time to process changes.

Frequently asked questions

How long does it take for a disavow to work?

Google says the disavow file is processed as its crawler revisits pages. It can take anywhere from a few weeks to several months, depending on how often Google crawls those pages.

Can I remove a backlink from another site myself?

No. You can't edit another site's content. Your only options are to ask the webmaster, use disavow, or use the Removals tool if you own the page.

Does disavow remove the link from Google's index?

No. The link still exists on the web. Disavow only tells Google to ignore it when computing your site's rankings.

What if the webmaster asks for money to remove the link?

Payments for link removal violate Google's guidelines. Don't pay. Instead, submit a disavow file and move on.

Should I remove every low-quality link I find?

Not always. One or two irrelevant links are unlikely to hurt you. Disavow only when the link is clearly spammy or part of a pattern of harmful links.

What's the difference between Removals and Disavow?

Removals temporarily block a page from search results. Disavow tells Google to ignore a link. Removals is for your own pages; disavow is for links from other sites.

If SeaText shows an authentication error with Thinkific, the fastest fix is to regenerate your Thinkific API key, paste the new key into SeaText, and save the connection. In most cases the error means Thinkific rejected the credentials SeaText is using. The key may be old, incomplete, or missing the permissions Thinkific requires.

After you update the key, confirm the Thinkific site URL in SeaText and give the connection a few minutes to sync. Then use SeaText's own verification step: visit your site, stay on the page for at least 40 seconds, and check that your website name appears next to the SEATEXT logo.

What the authentication error means

Authentication is the step where SeaText proves to Thinkific that it has permission to connect. An error at this step means Thinkific did not accept the API key or the connection details.

This is different from an authorization problem. Authentication checks who you are. Authorization checks what you can do. If the key is valid but lacks the right scopes, SeaText may connect but still fail to read or update your Thinkific content.

If you ignore the error, SeaText cannot finish linking your Thinkific site, and any setup that depends on that connection will stay incomplete.

What you need before you start

• Admin access to your Thinkific dashboard. You need this to create or regenerate an API key.
• Access to your SeaText account.
• The exact Thinkific site address, usually something like your-school.thinkific.com.
• The list of scopes or permissions SeaText asks for, if the integration settings show them.

Do not start until you have these. Trying to fix the error without admin access to Thinkific will not work.

How to fix the authentication error step by step

1. Log in to your Thinkific admin dashboard.
2. Find the API Keys section. In Thinkific, this is usually under Settings or a developer/API area.
3. Create a new API key, or regenerate the existing one. If you regenerate, Thinkific will replace the old key.
4. Copy the full new key. Do not add spaces, line breaks, or quote marks.
5. Open SeaText and go to the Thinkific integration settings.
6. Paste the new key in the API key field. Enter your Thinkific site address if the settings ask for it.
7. Save the connection.

If SeaText shows a success message, move to the verification section. If the error stays, check the common mistake below.

The most common mistake: updating the wrong key

The most common mistake is not updating the key SeaText actually uses. People create a new key in Thinkific, but SeaText still has the old one. The error stays because SeaText never sees the new key.

Another common mistake is copying the key with a hidden extra space. Browsers can add a space when you double-click a key. To avoid this, paste the key into a plain text editor first, copy it again, then paste it into SeaText.

A third mistake is confusing the API key with your Thinkific login password. SeaText needs the API key from Thinkific, not your account password.

How to verify SeaText reconnects

After you save the new key, check for a connected status in SeaText. The exact wording may be 'connected', 'active', or a green indicator.

SeaText's Thinkific integration guide uses a simple verification method. Add your website address in the format www.example.com, visit the page once, and stay for at least 40 seconds. Then wait at least five minutes. Your website name should appear next to the SEATEXT logo at the top of the page.

If you do not see it after 10 minutes, contact SeaText support. The guide says this can indicate an issue during installation on your platform.

If the error still appears

• Check the scopes on the API key. If SeaText needs to update pages, a read-only key may not be enough.
• Confirm you are entering the Thinkific site address in the field SeaText asks for. Some integrations need the subdomain only, not the full URL.
• Log out of SeaText and log back in. This clears a stale connection session.
• Check whether SeaText uses an API key or an OAuth connection. If it uses OAuth, click 'Reconnect' or 'Authorize' instead of pasting a key. Thinkific's developer docs explain OAuth authorization.
• Contact SeaText support with a screenshot of the exact error message and the steps you already tried.

Do not create a second API key every few minutes. Each new key can make it harder to tell which key SeaText is using. Fix one key, save it, and test it.

Key facts about SeaText and Thinkific

These facts come from SeaText's Thinkific integration page and homepage.

Limitations and when this fix doesn't apply

This walkthrough assumes the SeaText-Thinkific connection uses an API key. If the integration uses OAuth, regenerating an API key will not fix the problem. You need to reauthorize the connection from SeaText.

If the error appears when you try to log in to Thinkific itself, this is not a SeaText issue. Check your Thinkific account access first.

The SeaText JavaScript must be in your Thinkific site footer. A valid API key cannot fix a missing script. If the script is missing, SeaText may not see your site at all.

If your Thinkific plan does not include API access, you will not be able to create the key this fix depends on. Check with Thinkific support about plan limits.

Terms you may see

• Authentication: the step where Thinkific checks that the API key belongs to a valid account.
• API key: a secret code Thinkific gives you so another tool can connect to your account.
• Scope: a permission attached to an API key, such as read-only or read-and-write.
• Subdomain: the Thinkific address before thinkific.com, for example your-school.thinkific.com.
• OAuth: another way to authorize a connection, often using a 'Connect' or 'Authorize' button instead of a key.
• Site Footer Code field: the place in Thinkific's Code & Analytics tab where SeaText JavaScript is pasted.

FAQ

Why does SeaText still say authentication failed when my API key looks correct?

Check for an extra space or line break in the key, make sure SeaText has the newest key, and confirm the key has the scopes the integration needs.

Where do I find the Thinkific API key?

In your Thinkific admin dashboard, look for API Keys under Settings or in the developer area. If you cannot find it, check Thinkific's help documentation.

Will regenerating the API key break other tools?

Yes, if another tool uses the same API key. You will need to update that tool with the new key too.

How long does SeaText take to reconnect after I update the key?

Sometimes it reconnects immediately after you save. SeaText's guide also says to wait at least five minutes for your website name to appear next to the SEATEXT logo.

Should I use an API key or OAuth for Thinkific?

Use the method SeaText asks for. If the SeaText settings have an API key field, paste the key. If they show a 'Connect' or 'Authorize' button, use OAuth instead.

Can I fix this without Thinkific admin access?

No. You need admin access to create or regenerate the API key and to see the scopes attached to it.

For more on Thinkific's authorization options, see Thinkific's OAuth authorization guide.

When SeaText reports as active but your Weebly pages aren't showing any SEO changes, it's typically a configuration or activation gap—not a failure of the tool itself. This diagnostic guide walks you through the exact steps to identify why SeaText isn't producing output despite appearing connected.

Step 1: Confirm JavaScript Installation in Weebly

The most common reason SeaText shows active but has no effect is incomplete or incorrect JavaScript placement. SeaText relies on a JavaScript snippet injected into your site’s footer to function. If this code isn’t present or is malformed, the AI remains inert.

To verify:

1. Log in to your Weebly account and open the site editor.
2. Navigate to Website > Edit Site > Settings > SEO.
3. Scroll to the "Footer Code" section.
4. Confirm the SeaText JavaScript snippet is pasted exactly as provided in your SeaText account.
5. Look for extra spaces, line breaks, or missing characters—especially around the <script> and </script> tags.
6. If the code is missing or altered, copy it again from SeaText’s integration page and repaste it.

After pasting, save and publish the site. Unpublished changes will not load the script, even if saved in the editor.

Step 2: Verify Page Publication and Activation Wait Time

SeaText requires two triggers after installation: the page must be published live, and you must wait for activation to complete. Simply saving in Weebly’s editor does not deploy the script to visitors.

After publishing:

• Visit your live Weebly page in a browser.
• Stay on the page for at least 40 seconds—this allows SeaText to detect traffic and link to your account.
• Wait up to 10 minutes for your website name to appear next to the SeaText logo in your account dashboard.
• If the name doesn’t appear after 10 minutes, revisit the Footer Code to confirm the script is loading (use browser dev tools to check for 404 or blocked scripts).

Note: Localhost or development domains (e.g., your-site.weebly.com in preview mode) may not activate due to SeaText’s security restrictions on non-production URLs.

Step 3: Check for Weebly SEO Overrides

Weebly’s native SEO settings—such as page titles, meta descriptions, and header tags—can override or mask SeaText’s output if they conflict. SeaText modifies content in real time, but if Weebly’s settings are set to rewrite or suppress dynamic changes, you may not see the expected changes.

To test:

• Temporarily clear Weebly’s SEO fields (page title, meta description) for a test page.
• Publish the page and wait for SeaText activation.
• View the page source and look for SeaText-generated changes (e.g., rewritten headings, keyword-matched copy).
• If changes appear, the conflict was with Weebly’s SEO fields. Re-enter only essential, non-overriding values.

SeaText does not modify Weebly’s SEO fields directly—it injects or alters visible content and metadata after the page loads. If Weebly’s settings are set to cache or sanitize output aggressively, they may interfere.

Step 4: Review SeaText Per-Page Configuration

SeaText allows per-page activation and configuration. Even if the script is installed globally, individual pages may be excluded from optimization.

To check:

• Log in to your SeaText account and go to Configuration > Page Settings.

• Ensure the toggle for your Weebly page is enabled.
• Review any audience, keyword, or URL filters that might exclude the page (e.g., "only run on blog pages" or "exclude URLs containing /test").
• If using targeting rules, confirm they match your live URL exactly (including http vs https and trailing slashes).

SeaText does not optimize pages that are disabled in its configuration, even if the script is present.

Step 5: Test for Script Blocking or Conflicts

Browser extensions, ad blockers, or Weebly apps may block or alter the SeaText script before it runs.

To test:

• Open your live Weebly page in an incognito window (to disable extensions).
• View page source and search for "seatext" or the script URL.
• If the script is missing, check for content security policies or app-level overrides in Weebly.
• Temporarily disable any Weebly apps related to SEO, speed, or security and retest.
• Use browser dev tools (Network tab) to confirm the script loads with a 200 status.

Some Weebly themes or third-party apps may minify or defer scripts in ways that delay or prevent SeaText from executing before page render.

Step 6: Confirm AI Activation and Credit Status

SeaText shows as "active" in your dashboard if the script is detected, but the AI engine may not be engaged due to subscription status, usage limits, or manual deactivation.

Verify:

• Your SeaText subscription is active and not expired.
• You have not exceeded monthly usage limits (if on a capped plan).
• The "Activate AI" button in your dashboard is toggled on (not paused).
• You’ve completed the activation step: visiting the site and waiting for the domain to appear in the dashboard.

If the AI is paused or inactive, SeaText will load the script but make no changes to content.

Why This Matters: The Cost of Misdiagnosis

Assuming SeaText is broken when it’s merely misconfigured leads to wasted time, unnecessary support tickets, or premature abandonment of a working tool. Conversely, overlooking a simple publish step or Weebly SEO conflict can leave you thinking optimization is happening when it’s not—potentially affecting rankings and click-through rates.

By following this sequence, you isolate whether the issue is technical (script placement), procedural (activation wait), or configurational (Weebly overrides or SeaText settings). Most cases are resolved in Steps 1–3.

Key Facts About SeaText Weebly Integration

Limitations and When This Advice Does Not Apply

This guide assumes you are using SeaText’s standard Weebly integration via JavaScript footer injection. It does not apply if:

• You’re using a custom Weebly theme that alters or removes the footer section.
• Your site uses a content security policy (CSP) that blocks external scripts unless explicitly allowed.
• You’re attempting to optimize non-HTML content (e.g., embedded frames or third-party widgets).
• SeaText is intentionally paused for A/B testing or staging purposes.

If you’ve confirmed the script is live, published, and activated but still see no changes after 24 hours, contact SeaText support with your domain and a screenshot of the Footer Code setting.

Frequently Asked Questions

How long does it take for SeaText to start optimizing after installation?

After pasting the JavaScript and publishing the page, SeaText begins analyzing traffic immediately. Visible changes typically appear within 5–10 minutes of active visitor engagement, provided the domain is activated in your dashboard.

Can SeaText work if I haven’t published my Weebly site?

No. SeaText only runs on live, published pages. Changes made in the Weebly editor but not published will not load the script for visitors.

Will SeaText conflict with Weebly’s built-in SEO tools?

It can if Weebly’s SEO fields are set to rewrite or cache output aggressively. To avoid conflict, keep Weebly’s title and meta description fields minimal or empty when relying on SeaText for dynamic optimization.

What if I see the SeaText logo in my dashboard but no changes on the page?

This means the script is detected and the account is linked, but either the AI is inactive, the page is excluded in settings, or Weebly is overriding the output. Follow Steps 3–5 to isolate the cause.

Do I need to reinstall SeaText after updating my Weebly theme?

Only if the theme edit removes or alters the Footer Code section. Otherwise, the script persists through theme changes as long as it’s placed in the Footer Code area.

Is SeaText affected by Weebly’s site speed or caching features?

Weebly’s native caching does not block SeaText, but if you use a third-party speed app that defers or modifies scripts, test for interference. SeaText runs asynchronously and is designed to load after core content.

Can I use SeaText on a Weebly blog page?

Yes. SeaText works on any published Weebly page, including blog posts, as long as the JavaScript is in the Footer Code and the page is activated in your SeaText settings.

Quick Answer: Verify Installation and Wait for Activation

SeaText connects to HubSpot by embedding a JavaScript snippet in your site's Footer HTML. After pasting the code and publishing, you must visit your live site and stay on the page for at least 40 seconds. This visit triggers the AI activation and links the domain to your SeaText account. The SeaText dashboard will then display your website name next to the logo within five minutes. If the name is still missing after ten minutes, the installation likely failed — contact SeaText support right away.

How the HubSpot–SeaText Link Works

SeaText does not use an OAuth or API handshake with HubSpot. Instead, it relies on a client-side script that runs on your published HubSpot pages. The script sends a heartbeat to SeaText's servers when a real visitor loads the page. That heartbeat registers the domain in your SeaText account. Because the link is established by live traffic, the integration only completes after the script executes in a browser on your actual domain.

This design means you cannot test the connection in HubSpot's editor preview or on a staging subdomain that SeaText blocks (see Domain Restrictions). You must use the production URL that matches the primary URL registered in your SeaText account.

Step-by-Step Verification Checklist

1. Confirm the snippet is in the right place. In HubSpot, go to Settings → General → Advanced → Footer HTML. Paste the exact JavaScript snippet provided by SeaText. Do not wrap it in extra script tags or modify it.
2. Publish the changes. Click the orange Publish button at the top right of the HubSpot editor. Wait for the publish confirmation.
3. Visit the live page. Open the published URL in a browser. Stay on the page for at least 40 seconds. Do not use incognito mode, ad blockers, or script blockers that might prevent the SeaText script from loading.
4. Check the SeaText dashboard. Log in to your SeaText account. Look at the top of the page next to the SeaText logo. Your website name should appear there within five minutes.
5. If the name is missing after ten minutes, contact support. This signals an installation problem that SeaText's team must diagnose.

Common Reasons the Link Fails

Snippet Placed in the Wrong Field

HubSpot has multiple HTML fields (Head HTML, Body HTML, Footer HTML). SeaText's instructions specify Footer HTML. Placing the snippet in Head or Body HTML will not work because the script expects to load after page content.

Unpublished or Cached Changes

If you edited the Footer HTML but did not click Publish, the script never reaches visitors. Similarly, HubSpot's CDN or a browser cache may serve an old version. Hard-refresh the live page (Ctrl+Shift+R / Cmd+Shift+R) after publishing.

Domain Mismatch

Each SeaText account is tied to a single primary URL. If your HubSpot site lives on www.example.com but your SeaText account was created for example.com (or a development domain like staging.example.com), the heartbeat will not associate with your account. SeaText restricts development URLs such as localhost and dynamic preview domains for security reasons.

Multiple Domains Without Separate Accounts

If you run SeaText on more than one domain (e.g., a dev domain and a production domain), you must create a separate SeaText account for each domain. Sharing one account across multiple domains breaks the linking logic.

Script Blockers or Content Security Policy

Browser extensions (ad blockers, privacy tools) or a strict Content Security Policy on your HubSpot site can prevent the SeaText script from loading. Temporarily disable blockers and check your CSP headers if the dashboard stays empty.

Domain Restrictions and Multi-Site Rules

SeaText enforces two key constraints that directly affect HubSpot users:

• One primary URL per account. The account you create during sign-up locks to a single domain. You cannot add additional domains later.
• No localhost or dynamic preview domains. HubSpot's live preview URLs (e.g., hs-sites.com preview links) and local development environments are blocked. You must use a real, publicly resolvable domain.

If you need SeaText on a HubSpot staging environment, you have two options: (1) map a real subdomain (e.g., staging.yourdomain.com) to the HubSpot staging content and create a separate SeaText account for it, or (2) test only on the production domain.

What Happens After the Link Is Established

Once your website name appears next to the SeaText logo, the integration is active. You can then:

• Open the Main AI Hub in SeaText to activate specific AI agents (CRO, translation, personalization, etc.).
• Use Configuration to adjust AI parameters per page or site-wide.
• Edit automatic translations and copy variants under Variants Edit in the left panel.

The AI remains inert until you explicitly activate agents, so your HubSpot content stays unchanged until you decide otherwise.

Limitations of the Current Integration

• No bidirectional data sync. SeaText reads page content via the script but does not push changes back into HubSpot's CMS. Edits you make in SeaText's Variants Edit panel live only in SeaText's delivery layer.
• No HubSpot workflow triggers. You cannot enroll contacts in HubSpot workflows based on SeaText events.
• Single-account, single-domain model. Agencies managing multiple client HubSpot portals need a distinct SeaText account (and billing) for each client domain.
• Support-dependent troubleshooting. If the ten-minute window passes without a link, you cannot self-diagnose further; you must open a support ticket.

Key Facts at a Glance

Frequently Asked Questions

Can I test the integration on a HubSpot preview URL?

No. SeaText blocks dynamic preview domains (e.g., hs-sites.com links). You must publish to your real domain and visit that URL.

What if I have a HubSpot multisite setup with multiple brand domains?

Create a separate SeaText account for each brand domain. Each account gets its own snippet, dashboard, and billing.

Does the snippet slow down my HubSpot pages?

The script loads asynchronously and remains inert until you activate agents in the SeaText dashboard. No measurable impact on page speed before activation.

Can I use Google Tag Manager instead of Footer HTML?

SeaText's documented method is Footer HTML. GTM deployment is not covered in the official integration guide; if you attempt it, you are outside the supported path and SeaText support may not troubleshoot it.

What should I tell support if the link fails?

Provide: (1) your SeaText account email, (2) the exact HubSpot domain, (3) a screenshot of the Footer HTML field showing the pasted snippet, (4) confirmation that you published and visited the live page for 40+ seconds, and (5) the time you waited before checking the dashboard.

Will SeaText work on HubSpot landing pages and blog posts automatically?

Yes. The Footer HTML field applies site-wide, so every published page that uses the default template inherits the snippet. Custom templates that omit the global footer will need the snippet added manually.

Can I disconnect a domain from one SeaText account and attach it to another?

The source documentation does not describe a domain-transfer process. Since each account locks to a primary URL at creation, assume you must create a new account for the new domain and deactivate the old one.

To measure a SEATEXT preset's impact on Squarespace, you need three things: the script installed and activated, a conversion goal configured in your analytics platform, and a clean pre‑/post‑comparison window. The steps below walk through installation, goal setup, and the comparison process using either Squarespace Analytics or Google Analytics.

Prerequisites: Install and Activate SEATEXT on Squarespace

Before you can measure anything, the SEATEXT JavaScript must be on every page you want to test. In Squarespace, go to Settings → Developer Tools → Code Injection and paste the SEATEXT snippet into the Header field. Save and publish the site. Then visit several pages and stay at least 40 seconds so the AI activates and links to your account. Wait five minutes for the website name to appear next to the SEATEXT logo in your dashboard; if it does not appear after ten minutes, contact support.

Once connected, open the Main AI Hub, choose the preset you want to test (for example, the CRO Optimizer or Google Ads Landing Page Agent), and activate it on the target pages. The preset will begin generating variants for headlines, CTAs, and product blocks. SEATEXT reports conversion lift by page, keyword, and variant, so you can later match those reports to your own analytics.

Define What Counts as a Conversion

Decide which visitor actions matter: form submissions, button clicks, purchases, newsletter sign‑ups, or time‑on‑page thresholds. In Squarespace Analytics, use the Conversion Metrics panel to create a goal for each action. In Google Analytics (GA4), mark the corresponding events as conversions. Give each goal a clear name (e.g., "Contact Form Submit" or "Checkout Complete") so you can filter reports later.

Set Up a Clean Measurement Window

1. Baseline period: Collect at least two weeks of data with the preset turned off. Keep traffic sources, ad spend, and site content stable.
2. Activation: Turn the preset on in the Main AI Hub. Note the exact date and time.
3. Test period: Run the preset for a minimum of two weeks, or until each variant reaches 100+ conversions per variant (whichever comes later). Do not change other site elements during this window.
4. Comparison: In your analytics platform, compare the conversion rate for each goal between the baseline and test periods. Segment by device, traffic source, and landing page to see where the preset helped or hurt.

Use Squarespace Analytics for Quick Checks

Squarespace Analytics now includes conversion metrics that show goal completions, conversion rate, and revenue per visit. Open the Analytics panel, select Conversions, and filter by the goal you created. Set the date range to your baseline period, export the data, then repeat for the test period. Look for statistically significant changes (use a simple chi‑square test or an online significance calculator). Squarespace does not natively show variant‑level data, so you will rely on SEATEXT's own dashboard for which variant won.

Use Google Analytics (GA4) for Deeper Segmentation

GA4 lets you break down conversions by session source/medium, landing page, and custom dimensions. If you tag SEATEXT variants with a custom dimension (e.g., seatext_variant_id), you can build an Exploration report that shows conversion rate per variant alongside traffic source. This is the most reliable way to attribute lift to the preset rather than to a traffic mix shift. GA4 also supports statistical significance testing in Explorations.

Match SEATEXT's Internal Reports to Your Analytics

SEATEXT's dashboard reports conversion lift by page, keyword, and variant. Cross‑reference the winning variant IDs with your GA4 custom dimension or Squarespace goal completions. If SEATEXT shows a +12% lift on the "Pricing" page variant B, verify that GA4 shows a similar lift for sessions that saw variant B on that page. Discrepancies usually mean the variant was not served to all traffic (e.g., control group holdout) or that bot traffic inflated one side.

Common Mistakes That Invalidate the Test

• Changing ad campaigns, email sends, or site navigation during the test period.
• Running the test for too few conversions (under 100 per variant).
• Forgetting to exclude internal IP addresses from analytics.
• Comparing unequal time windows (e.g., baseline includes a holiday weekend, test period does not).
• Not waiting for the SEATEXT script to fully activate (the 40‑second visit and five‑minute connection check).

Key Facts from SEATEXT Documentation

Limitations of This Measurement Approach

• Squarespace Analytics does not expose variant‑level data; you must rely on SEATEXT's dashboard for which variant won.
• GA4 custom dimensions require developer setup (dataLayer push or GTM) to capture the SEATEXT variant ID.
• Statistical significance depends on traffic volume; low‑traffic sites may need months to reach confidence.
• SEATEXT's "proof before billing" model means the first lift measurement happens on the free pilot; paid plans start at $59/month after that proof.
• Bot traffic can distort conversion rates; SEATEXT's Bot Refund Agent filters some invalid clicks, but analytics filters should also be enabled.

Terminology Quick Reference

• Preset: A pre‑configured AI agent (e.g., CRO Optimizer, Google Ads Landing Page Agent) that rewrites specific page elements.
• Variant: An AI‑generated version of a headline, CTA, or block that SEATEXT tests against the original.
• Main AI Hub: The SEATEXT dashboard where you activate agents, adjust parameters, and view variant performance.
• Code Injection: Squarespace's header/footer script insertion point under Developer Tools.
• Conversion Metrics (Squarespace): Built‑in goal tracking for form submits, purchases, and custom events.
• GA4 Exploration: A custom report builder in Google Analytics 4 for segmenting by custom dimensions.

FAQ

How long should I run the baseline before activating a preset?

At least two weeks, or long enough to capture 200+ conversions per goal. This smooths day‑of‑week and traffic‑source variance.

Can I test multiple presets at once?

Not cleanly. Each preset rewrites different elements; overlapping changes make attribution impossible. Run one preset per measurement window.

What if my conversion rate drops after activation?

Check whether the preset is serving a control group (usually 10‑20% of traffic sees the original). If the drop persists across all variants, pause the preset and review SEATEXT's variant editor for off‑brand copy.

Do I need Google Tag Manager to capture variant IDs?

GTM is the easiest way, but you can also push the variant ID to the dataLayer directly from the SEATEXT callback if you have developer access.

How does SEATEXT's "proof before billing" work for measurement?

The free pilot runs until SEATEXT detects a minimum 5% conversion lift. Only then does the $59/month minimum plan start. Use the pilot period as your first measurement window.

Can I use Squarespace's built‑in A/B testing instead?

Squarespace does not have native A/B testing for copy. SEATEXT handles variant creation, traffic splitting, and winner rollout automatically.

What happens if the SEATEXT script fails to load on some pages?

Those pages serve original copy. In analytics, they will appear as the control group. Verify script presence with the browser dev tools Network tab on each template type.

Low-traffic sites cannot wait months for statistical significance on a 50/50 split test. The math is simple: a 2% conversion rate needs roughly 1,000 visitors per variant to detect a 20% lift with 95% confidence. At 500 monthly visits, that test runs for four months. Seasonality shifts. Ad creatives change. The winner is obsolete before you declare it.

AI A/B testing tools change the equation by replacing binary conversion tracking with behavioral telemetry. Instead of counting only purchases or form fills, they measure micro-engagement: scroll depth, dwell time per section, copy re-reads, hover patterns near CTAs, and rage clicks. Each session yields hundreds of signals. Bayesian multi-armed bandit algorithms then allocate traffic to winning variants continuously, not at a fixed endpoint. The result: reliable lift detection with a fraction of the traffic.

Why Traditional A/B Testing Fails on Low Traffic

Frequentist statistics assume a fixed sample size. You calculate the minimum detectable effect, set the horizon, and wait. On low-traffic sites the horizon stretches into quarters. Meanwhile the control drifts: ad messaging changes, competitors launch offers, seasonality shifts. The test measures a world that no longer exists.

Binary conversion tracking compounds the problem. A visitor who reads the entire pricing page, hovers over the CTA for 12 seconds, and leaves is counted identically to a 3-second bounce. Both register "no conversion." The signal-to-noise ratio collapses. You need more visitors to overcome the noise, but you don't have them.

How AI Reading Telemetry Changes the Math

SeaText's approach replaces the single conversion event with a stream of engagement signals. The agent tracks scroll velocity, time-on-text, copy re-reads, and hesitation patterns near conversion elements. A session that reads three headlines, pauses at the guarantee, and scrolls back to the value prop generates dozens of data points. The Bayesian model updates its posterior after every session. Traffic shifts toward the variant with the highest probability of being best - continuously, not at a fixed endpoint.

This reduces the required sample size by an order of magnitude. The source material notes "hundreds of data points per session" versus one binary outcome. A site with 1,000 monthly visitors can now run meaningful tests in weeks instead of months.

Decision Criteria for Choosing a Low-Traffic AI Testing Tool

1. Signal depth: Does the tool capture behavioral telemetry (scroll, dwell, hesitation) or only conversion events?
2. Allocation method: Bayesian multi-armed bandit, Thompson sampling, or sequential testing? Bandits shift traffic continuously; sequential tests stop early but still need a conversion event.
3. Variant generation: Does the tool write and deploy variants automatically, or must you create them manually?
4. Brand safety: Can you lock phrases, set tone guardrails, and prevent unauthorized claims?
5. Traffic control: Can you start on 5-10% of traffic and expand gradually?
6. Integration friction: Single script tag vs. SDK vs. data layer implementation.
7. Scope: Copy only, or layout, pricing, UX flows?

SeaText's Approach: What the Source Pack Confirms

SeaText deploys via a single script tag. The agent analyzes existing copy, generates challenger variants, and runs Bayesian multi-armed bandit tests with automatic winner shift. Conversion goals are defined by point-and-click on any element - form submissions, button clicks, trial signups. Brand guardrails enforce locked phrases, tone guidelines, and compliance boundaries. Selective traffic exposure starts at 5% or 10%, letting you review early results before expanding. The platform claims 20-35% average uplift from "subtle psychological shifts in clarity, specificity, and risk reversal" without redesign risk.

Limitations disclosed in the source material: SeaText optimizes copy (headlines, buttons, product descriptions, proof points). It does not restructure layouts, redesign pages, or test UX flows. The calculator projects uplift based on current conversion rate and average order value; actual results vary.

Other Approaches in the Market

Multi-armed bandit platforms like Dynamic Yield and Conductrics allocate traffic continuously but typically require manual variant creation and engineering integration. They excel at personalization rules and experience targeting but lack autonomous copy generation.

Sequential testing tools (Statsig, Eppo) use sequential probability ratio tests to stop experiments early when evidence is strong. They integrate with feature flag systems and suit product teams testing code changes. They do not generate marketing copy or analyze reading behavior.

AI copy generators (Jasper, Copy.ai) produce variants but leave testing to you. You must paste variants into a separate testing tool, define goals, and manage allocation. The handoff introduces delay and human error.

Check with the vendor for current pricing, traffic minimums, and integration specifics for any platform above. The comparisons reflect general market positioning, not verified feature parity.

Limitations and When This Advice Does Not Apply

• If your site has fewer than 500 monthly visitors, even behavioral telemetry may not accumulate enough signal for reliable Bayesian updating. Consider qualitative research (session recordings, user interviews) first.
• If you need to test structural changes - navigation, checkout flow, pricing tables - copy optimization tools cannot help. You need a full experimentation platform with dev resources.
• If your conversion event is extremely rare (e.g., enterprise demo requests at 0.1% rate), micro-engagement signals help but may still require months. Pair with leading-indicator metrics (pricing page views, scroll to testimonials).
• Regulated industries (finance, healthcare) may require legal review of every AI-generated variant. SeaText's brand guardrails help but do not replace compliance workflows.

Key Facts

FAQ

How much traffic do I need for SeaText to work?

The source material does not specify a hard minimum. It emphasizes that reading telemetry generates "hundreds of data points per session," drastically reducing sample size needs. Sites with 500-1,000 monthly visitors can see meaningful results in weeks. Below 500, consider qualitative methods first.

Does SeaText slow down my site?

No. The agent executes asynchronously via ultra-light edge CDN workers with sub-10ms latency, preserving Core Web Vitals and 100% PageSpeed scores (S3).

Do I need to write copy variants myself?

No. SeaText analyzes your product, industry, and visitor friction points to automatically draft, deploy, and benchmark high-converting copy variants on autopilot (S3).

Can I test layout changes or pricing structures?

SeaText optimizes copy only - headlines, buttons, descriptions, proof points. It does not restructure layouts, redesign pages, or test UX flows (S1).

What if the AI generates a claim that violates compliance?

Brand guardrails let you set locked phrases, tone guidelines, and compliance boundaries that AI variants must honor across all digital touchpoints (S1).

How does Bayesian bandit differ from traditional A/B testing?

Traditional tests split traffic 50/50 for a fixed horizon, then declare a winner at statistical significance. Bayesian bandits continuously update the probability each variant is best and shift traffic toward the leader in real time, capturing more conversions during the test.

Can I run SeaText alongside another testing tool?

Yes. The script-tag deployment is non-invasive. You can run SeaText copy tests while using a separate platform for layout or feature experiments. Ensure conversion goals don't conflict.

How SeaText Connects to Your ABM Stack

SeaText does not replace your ABM platform. It sits on top of your existing website and reads the account-level signals your ABM tool already collects — company name, industry, revenue tier, buying stage, intent topics, and custom fields. When a visitor from a target account lands on any page, SeaText swaps headlines, proof points, offers, and CTAs to match that account's profile before the page renders.

The connection happens in two ways: native integrations for the four major platforms, and a flexible webhook endpoint for everything else. Both paths feed the same personalization engine, so the visitor experience is identical regardless of how the data arrives.

Native Integrations: What Works Out of the Box

Each native integration maps ABM fields to SeaText personalization tokens automatically. You can override or extend the mapping in the SeaText dashboard without code changes.

Custom Webhook Integration for Other Platforms

If your ABM stack uses Terminus, Madison Logic, Triblio, or a homegrown CDP, you can push account data to SeaText via a secure webhook endpoint. The payload accepts any JSON structure — SeaText's mapping layer lets you define which fields drive which content changes.

Typical webhook payload includes:

• account_id (required)
• company_name
• industry, revenue_range, employee_count
• buying_stage, intent_topics
• custom_fields object for any proprietary scoring or segmentation

The endpoint responds in under 10ms at the edge, so there is no perceptible delay for the visitor. You control the refresh cadence — real-time on page load, or cached for the session.

What Gets Personalized for Target Accounts

SeaText rewrites any text element on the page: headlines, subheads, value propositions, social proof, product descriptions, pricing callouts, and CTA copy. The changes are scoped to the visitor's account profile, not just their referral source.

Common account-based personalization patterns:

• Industry-specific headlines: "Security compliance for healthcare" vs. "Security compliance for fintech"
• Account-tier offers: Enterprise accounts see "Request custom SLA"; mid-market sees "Start 14-day trial"
• Intent-driven proof: Visitors researching "SOC 2 automation" see customer logos and case studies from that category
• Competitive displacement: Accounts using a known competitor see migration-focused messaging
• Buying-stage CTAs: Early stage gets "Download benchmark report"; late stage gets "Book technical deep-dive"

All variations live on the same canonical URL. No duplicate pages, no routing rules, no CMS bloat.

Decision Criteria: Choosing Your Integration Path

If you are on one of the four native platforms, start there. The webhook path exists for everything else and gives you full control over what data drives personalization.

Step-by-Step: From Integration to Live Personalization

1. Connect your ABM platform via the SeaText dashboard (native) or configure the webhook endpoint (custom).
2. Map account fields to personalization tokens — SeaText suggests mappings based on your platform; review and add custom fields.
3. Define content rules for each segment: what headline, proof point, offer, and CTA each account tier or industry sees.
4. Set brand guardrails — lock approved phrasing, legal disclaimers, and tone parameters so AI-generated variants stay compliant.
5. Launch in shadow mode — SeaText shows you what would change for each account without visitors seeing it. Review a sample of target accounts.
6. Go live — enable for 10% of traffic, monitor conversion lift by account tier, then ramp to 100%.

Most teams reach step 6 within one week. The bottleneck is usually internal approval on messaging rules, not technical setup.

Key Facts

Limitations and When This Does Not Apply

• SeaText personalizes text content on existing pages. It does not build standalone microsites or 1:1 account pages — tools like Folloze or Mutiny specialize in that.
• Account identification depends on your ABM platform's match rate. SeaText cannot identify anonymous visitors that your ABM tool does not recognize.
• Webhook integrations require your engineering team to maintain the payload schema. If account fields change, you must update the push logic.
• Personalization only applies to visitors who land on your website. It does not affect ad creative, email content, or sales outreach.
• Enterprise brand teams often require legal review of AI-generated copy variants. Build that cycle into your launch timeline.

FAQ

Does SeaText replace my ABM platform?

No. SeaText reads signals from your ABM platform and acts on them at the website layer. You still need 6sense, Demandbase, RollWorks, or HubSpot for account identification, intent scoring, advertising orchestration, and sales alerts.

What if my ABM platform is not on the native list?

Use the custom webhook endpoint. Any system that can push a JSON payload with an account ID and the fields you want to personalize on will work. Terminus, Madison Logic, Triblio, and custom CDPs all integrate this way.

How fast does the personalization happen?

Under 10ms at the edge. The visitor sees the personalized version on first paint — no flicker, no layout shift, no client-side JavaScript delay.

Can I control what the AI writes for each account?

Yes. You define the messaging rules, approved phrases, and guardrails. SeaText generates variants within those boundaries. You can also lock specific copy so it never changes.

What happens if the ABM platform misidentifies an account?

SeaText falls back to your default page content. You can also set a confidence threshold — only personalize when the ABM platform's match score exceeds your defined minimum.

How do I measure the impact on target accounts?

SeaText tracks conversion lift by account tier, industry, buying stage, and custom segments. You see side-by-side performance of personalized vs. default content for each segment.

Is there a limit on how many account segments I can personalize for?

No practical limit. The engine handles thousands of segment-to-content mappings. The constraint is your team's ability to define meaningful rules for each segment.

Terminology

• Edge rewrite: Content modification at the CDN layer before the page reaches the browser, ensuring zero flicker.
• Canonical URL: The single, authoritative page URL — personalization creates variations without duplicating URLs.
• Shadow mode: Testing mode where personalization is computed but not shown to visitors, used for QA.
• Brand guardrails: Locked copy rules, tone parameters, and legal constraints that bound AI-generated variants.
• Account match rate: The percentage of website visitors your ABM platform can identify to a target account.

If Seatext is not connecting on Squarespace, the fastest path forward is to re-check the Code Injection steps, confirm the site is published, and refresh the page for at least 40 seconds. The site name should appear next to the Seatext logo within about five minutes. If it does not show up after 10 minutes, contact Seatext support, because that usually means something went wrong during installation on the platform.

Most connection problems come from a small mistake in the install process, not from a broken tool. The guide below walks through what to check, in what order, and when to stop and ask for help.

Start with the symptoms you are seeing

Before changing anything, name the symptom. The fix is different depending on what you see.

• Nothing happens after pasting the code. The script may not be saved, or the site may not be published.
• The site name never appears next to the Seatext logo. The script may be in the wrong field, or the account may be linked to a different domain.
• The site name appears, but AI features do not run. The connection is fine, but the AI has not been activated yet in the Main AI Hub.
• You see an error or a blank area where the script should be. Squarespace may be stripping part of the code, or a browser extension may be blocking it.

Pick the symptom that matches your case, then move to the matching fix below.

Re-check the install steps in the right order

Squarespace installs Seatext through Code Injection, which is a built-in field for custom scripts. The order matters, because each step depends on the one before it.

1. Open your Squarespace dashboard and go to the website panel.
2. Click the three dots icon and choose Settings.
3. Scroll to the bottom of the settings page and open Developer Tools.
4. Click Code Injection.
5. Paste the JavaScript snippet from your Seatext account into the Header field, not the Footer field.
6. Click Save.
7. Make sure the site is published, not just saved as a draft.

If any of these steps were skipped or done in the wrong place, the script will not load and Seatext will not connect.

Confirm the script is actually live on the page

Saving the code is not the same as the code running. Two quick checks help you tell the difference.

• View page source. Open your live site, right-click, and choose View Page Source. Search for seatext. If you see the snippet, the code is on the page. If you do not, the script was not saved or the site is not published.
• Hard refresh. Press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac. Cached pages can hide new code for a while.

If the snippet is missing from the source, go back to Code Injection and paste it again. Make sure you clicked Save and that the site is published.

Wait the right amount of time, the right way

Seatext needs real visitor activity to link your account to the site. Two timing rules matter.

• Stay on the page for at least 40 seconds. A quick bounce does not count. Open the site, scroll a little, and wait.
• Wait up to five minutes for the site name to appear next to the Seatext logo at the top of the Seatext dashboard.

If you only waited a minute or two, give it the full five before assuming the install failed.

Check for common Squarespace-specific issues

Some problems only show up on Squarespace. Run through this short list before contacting support.

• Code Injection is a paid feature on some plans. If you do not see the Developer Tools section, your plan may not include it. Squarespace documents which plans support Code Injection.
• The script went into the Footer field by mistake. Seatext needs the Header field. Footer placement can prevent the script from loading early enough.
• Custom CSS or another script is blocking it. Other code in the Header field can interfere. Try removing other custom scripts temporarily and test again.
• You are on a development or preview URL. Seatext restricts localhost and dynamic development domains for security reasons. Use your real published domain.
• You have multiple domains. Each Seatext account is linked to one primary URL. If you installed the script on a different domain than the one tied to your account, it will not connect.

Key facts about the Squarespace install

When to contact Seatext support

Stop troubleshooting and reach out if any of these are true.

• The site name still does not appear after 10 minutes of waiting.
• The script is in the page source but the site name never shows up.
• You see a partial install, where some pages connect and others do not.
• You are on a plan that should support Code Injection but the field is missing.

When you contact support, include the URL of your site, the Seatext account email, and a screenshot of your Code Injection field. That short list of details usually speeds up the fix.

What to do after the connection works

Once the site name appears next to the Seatext logo, the install is done. The next step is activation.

1. Open the Main AI Hub in your Seatext account.
2. Choose the AI features you want on each page.
3. Click Configuration to adjust the AI parameters.
4. Review the first round of automatic translations or copy variants Seatext generates for testing.

From here, Seatext runs in the background and you can edit or override any output.

Limitations to keep in mind

The install process has a few hard limits that are easy to miss.

• One domain per account. If you run a staging domain and a production domain, you need two Seatext accounts.
• No localhost support. Local development will not connect, even if the script is in place.
• Code Injection plan requirement. If your Squarespace plan does not include Code Injection, the install cannot complete.
• Header placement only. Footer placement is not supported for the connection step.

Frequently asked questions

How long does Seatext take to connect on Squarespace?

After you paste the script and publish the site, visit a page and stay for at least 40 seconds. The site name usually appears next to the Seatext logo within five minutes. If it has not appeared after 10 minutes, contact support.

Why is the Developer Tools section missing in Squarespace?

Code Injection lives under Developer Tools, and not every Squarespace plan includes it. Check your current plan or contact Squarespace support to confirm whether your plan supports custom code.

Can I install Seatext in the Footer field instead of the Header?

No. The install steps require the Header field. Footer placement can prevent the script from loading early enough to connect.

Does Seatext work on a Squarespace preview or staging domain?

No. Seatext restricts localhost and dynamic development domains for security reasons. Use your real published domain for the install.

Can one Seatext account cover multiple Squarespace sites?

No. Each Seatext account is linked to a single primary URL. If you run more than one site, create a separate account for each domain.

What if the script is in the page source but the site name still does not appear?

That usually points to a domain mismatch between your Seatext account and the site where the script is installed. Double-check the URL tied to your account, or contact Seatext support with your account email and site URL.

Do I need to reinstall Seatext if I change Squarespace templates?

Template changes can clear Code Injection in some cases. After a template switch, open Developer Tools and confirm the script is still in the Header field, then save and republish if needed.

Quick answer

SeaText stays invisible until the script loads, a real visitor spends roughly 40 seconds on the page, and the backend registers the domain. The most common reasons it doesn't appear are: the snippet was placed on only some pages, the site is on a free Wix plan (which blocks custom code), the domain is a localhost or staging URL that SeaText rejects, or you simply haven't waited the five-minute propagation window.

Follow the checklist below in order. Most issues resolve at step 2 or 3.

How SeaText activation works

SeaText uses a three-step activation model. First, the JavaScript snippet must load on every page of your site. Second, a real human visitor (you) must visit the site and stay for at least 40 seconds. This tells SeaText the domain is real and links it to your account. Third, the SeaText backend registers the domain and displays it next to the SeaText logo in your dashboard. Until all three steps happen, the AI agents remain inert. They do not run, collect data, or change your site. The activation visit is a security measure. It prevents bots or automated scripts from linking domains. You must simulate a real session: scroll, click, and interact. A short bounce looks like a bot and is ignored.

1. Confirm the snippet is on every page

Open the live site in an incognito window. View source (Ctrl+U) and search for seatext or the script ID you copied. If you don't see it, the code is not loading.

Before verification: The source code shows no script tag. The page loads without SeaText.

After verification: The source code contains the script tag. The page is ready for activation.

On Wix, go to Settings → Custom Code → Head. Ensure "All pages" and "Load code on each new page" are selected. Hit Apply and publish. On other platforms, verify the snippet sits in the <head> of your base template, not a single page block.

2. Use a supported, live domain

SeaText rejects localhost, 127.0.0.1, and many dynamic preview URLs (e.g., Netlify deploy previews, Vercel preview links). Each production domain needs its own SeaText account. If you are testing on a staging subdomain, create a separate account for that exact URL.

Before verification: You are using a localhost or staging URL. The SeaText backend cannot verify the domain.

After verification: You are using a live, public domain (e.g., example.com). The backend can link the domain to your account.

SeaText blocks development URLs for security. Dynamic preview domains may not reliably associate traffic with your account. Use a real domain—even a cheap .dev or .app—for testing.

3. Trigger the activation visit

After the script is live, open the site yourself. Stay on any page for at least 40 seconds. Scroll, click, and simulate a real session. This tells SeaText the domain is active and links it to your account. Close the tab and wait five minutes.

Before verification: You have not visited the site or stayed less than 40 seconds. The domain remains unlinked.

After verification: You have completed a 40-second visit. The backend begins processing the domain.

SeaText requires this visit to confirm you are a human owner. Short bounces are ignored. You can refresh the page several times during the 40 seconds—the key is total time spent.

4. Check the dashboard for the domain badge

Log into SeaText. At the top of the Main AI Hub you should see your website name next to the SeaText logo. If it appears, the connection succeeded. If not, proceed to step 5.

Before verification: No domain badge visible. The dashboard shows only the SeaText logo.

After verification: Your website name appears next to the logo. The domain is connected and ready.

Source S1 says: "Wait at least five minutes until you see your website name displayed next to the SEATEXT logo at the top of this page." If it does not appear after ten minutes, contact support.

5. Clear caches and hard-refresh

Browser cache, CDN (Cloudflare, CloudFront), or server-side cache (WP Rocket, W3 Total Cache) can serve an old HTML version without the snippet. Purge all caches, then hard-refresh (Ctrl+Shift+R). Re-check the source code.

Before verification: The page loads an old cached version. The script tag is missing from the source.

After verification: The page loads a fresh version. The script tag appears in the source.

Clearing caches is often overlooked. If you use a CDN, purge the cache for your domain. On WordPress, clear plugin caches and server-level caches (e.g., Nginx, LiteSpeed).

6. Verify plan restrictions (Wix and others)

Wix requires a paid plan to use Custom Code. Squarespace Business or Commerce plans are needed for code injection. Shopify allows scripts on all paid plans. If you are on a free tier, upgrade or move the snippet to a platform that permits it.

Before verification: You are on a free plan. Custom Code is blocked by the platform.

After verification: You have upgraded to a paid plan. Custom Code is now allowed.

Source S1 states: "To install custom code, you are required to have a paid plan on Wix." Check your platform's documentation for exact plan requirements.

7. Inspect the browser console for errors

Open DevTools → Console. Look for red errors referencing seatext, CSP (Content Security Policy) blocks, or 403/401 responses from SeaText endpoints. A CSP error means your site's policy forbids the script domain. Add the SeaText CDN domain to your script-src directive. The exact domain is in the snippet you copied.

Before verification: Console shows errors like "Refused to load script" or "403 Forbidden."

After verification: Console shows no errors. The script loads successfully.

If you see a CSP error, work with your security team to update the policy. For generic guidance, check with the vendor for the exact domain to whitelist.

8. When to contact support

If the domain badge is still absent after 10 minutes, email support with:
• Your SeaText account email
• The exact live URL where the snippet is installed
• A screenshot of the Custom Code / head injection settings
• Any console errors
Support can see server-side whether the ping arrived and why the domain was not registered.

Before verification: No badge after 10 minutes. You have not contacted support.

After verification: You have contacted support with the required information. Support helps resolve the issue.

Full Wix installation walkthrough

Follow these steps exactly as described in the SeaText integration guide (source S1).

1. Access your Wix account and navigate to the project you wish to translate.
2. In your Wix admin area, locate the Settings option and scroll down to find > Custom Code (located at the very bottom of the page, under “Advanced”).
3. Within the Custom Code section, click on “Add Code” under the “Head” section.
4. A pop-up window will appear. Paste the copied JavaScript code snippet into the designated text area labeled “Paste the code snippet here:”.
5. Under the section “Add Code to Pages”, select “All pages” from the dropdown menu. Then, choose “Load code on each new page” and click Apply.
6. Publish your site. The code is now active.

After these steps, go to incognito mode and view source. Confirm the script tag is present. Then perform the activation visit (step 3). Wait five minutes and check the dashboard. If the domain badge appears, you are done. If not, follow the checklist above.

Common mistakes

• Pasting the snippet into a page-specific code block instead of the global head.
• Forgetting to publish after saving Custom Code settings.
• Testing on a staging URL without a separate SeaText account.
• Assuming the AI widget appears instantly—SeaText is headless until activated.
• Leaving an old caching plugin active after adding the script.
• Not staying on the page for the full 40 seconds.
• Using a free Wix plan (Custom Code is blocked).

Platform-specific notes

Wix

Settings → Custom Code → Head → Add Code → Paste snippet → "All pages" + "Load code on each new page" → Apply → Publish. Free plans cannot do this. Source S1 confirms: "To install custom code, you are required to have a paid plan on Wix."

WordPress

Use a header/footer plugin (e.g., WPCode) or edit header.php in a child theme. Clear server cache (WP Rocket, LiteSpeed, Nginx) and CDN.

Shopify

Online Store → Themes → Edit code → theme.liquid → paste before </head>. Works on all paid plans.

Webflow

Project Settings → Custom Code → Head Code → paste → Publish to selected domains.

FAQ

Why do I need to stay on the page for 40 seconds?

SeaText uses the visit to verify the domain is real and to bind it to your account. Short bounces look like bots and are ignored.

Can I install one SeaText account on multiple domains?

No. Each primary domain requires its own account. Subdomains count as separate domains. Source S1 states: "Multiple Domains: If you need to use SEATEXT AI on multiple domains, you must create separate accounts for each domain."

What if my site has a strict CSP?

Add the SeaText CDN domain to your script-src directive. The exact domain is in the snippet you copied. If you are unsure, check with the vendor for the correct domain to whitelist.

Does SeaText work on localhost for development?

No. Localhost and similar development URLs are blocked for security. Use a real domain (even a cheap .dev or .app) for testing.

How do I know the script is actually loading?

View page source on the live site and search for the script tag. Network tab in DevTools should show a 200 response for the SeaText JS file.

What happens after the domain badge appears?

Go to the Main AI Hub, click Configuration, and activate the agents you need (CRO, Translation, Google Ads, etc.). The AI remains inert until you turn agents on.

Can I use SeaText on a free Wix plan?

No. Wix restricts Custom Code to paid plans. Upgrade or move to a platform that allows head injection on free tiers.

What if I have multiple websites?

Create one SeaText account per website. Each account is linked to a single primary URL.

Related resources

• SeaText Wix Integration Guide – Official installation steps for Wix.
• SeaText Homepage – Learn about all AI agents and features.

If SeaText does not appear after you save the code in Thinkific, start with the least invasive checks: clear the cache, confirm the code is in Settings > Code & Analytics > Site Footer Code, and save again. Then visit your live site and stay there for about 40 seconds. Wait at least five minutes, and contact SeaText support if the site is not linked after ten minutes.

The same symptom can come from different causes. The code can be in the wrong field, the browser can be showing an old page, or the JavaScript can be working while the account linking step never finished. Diagnose in that order rather than re-pasting the snippet over and over.

Work through the diagnosis in this order

Start with checks that cannot break your setup. The Thinkific integration page is the reference for every step.

1. Open the live site in an incognito window. A hard refresh using Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac also clears a local copy.
2. Confirm where the code is saved. SeaText says to put it in Site Footer Code under Settings > Code & Analytics.
3. Click Save after you paste the code.
4. Visit the site once and stay for about 40 seconds. This is part of the linking step.
5. Wait at least five minutes. Then check the SeaText account page for your domain next to the SEATEXT logo.
6. If nothing appears after ten minutes, copy a fresh snippet and re-paste it once.
7. If the site still does not appear, contact SeaText support instead of editing code by hand.

Check the Thinkific field before you change anything

SeaText's Thinkific walkthrough is specific about the location. In your Thinkific admin dashboard, go to Settings, then open the Code & Analytics tab. Paste the JavaScript into the Site Footer Code field and click Save.

If you placed the snippet in a header field, a page-specific code box, or another section, it may not load on the pages you are checking. Move it to Site Footer Code and save again. That is the field the SeaText documentation names.

This matters because the footer code loads on pages across the site. A page-specific field might work on that page only, which makes the widget seem missing elsewhere.

Rule out a stale page or an unpublished site

The browser is a common reason the widget looks missing. The SeaText snippet is loaded by JavaScript, and a cached page can keep showing the old version. Open the page in a private or incognito window, or use a hard refresh.

Also check that you are looking at the live public site. If Thinkific shows a preview or the site is not published yet, the saved code may not be part of the page visitors see. Save the code, then load the normal public URL.

Do the activation visit and wait for the link

Saving the code is only the first half. SeaText's integration instructions include a linking step: add your website address in the format www.example.com, visit the website once, and stay there for at least 40 seconds. That visit activates the AI and links it to your account.

After the visit, wait at least five minutes. Your website name should appear next to the SEATEXT logo at the top of the SeaText account page. SeaText says that if it does not appear after 10 minutes, you may need support help because the issue could be in the platform installation.

What the code does after it loads

The JavaScript snippet is the connection, not the result. It lets SeaText's AI tools run on the site, and your public visit confirms that the site belongs to your account. Those are two separate states, which is why a saved snippet alone is not enough.

If you expect a widget, a translated text, or a rewritten headline, the AI also needs to be activated in the Main AI Hub. The SeaText account has a configuration step for that. SeaText calls the first round of translations and variants optional editing, so the raw output can be reviewed before it goes live.

Key facts: SeaText on Thinkific, at a glance

Facts from SeaText's Thinkific integration documentation. Times are setup steps, not guarantees.

Common mistakes that make SeaText look missing

• Pasting into the wrong field. Use the Site Footer Code field under Code & Analytics.
• Checking an old browser tab. A private window is a faster test.
• Never making the activation visit. The 40-second visit is part of the setup, not extra effort.
• Checking the account too early. Wait five minutes first.
• Re-pasting the snippet several times. That does not fix a linking or cache problem.
• Using a preview URL in the website form. Use a public site address so the saved code can run.

A realistic setup scenario

Imagine you paste the code, save, then go back to the course page and see nothing. You refresh, still nothing. The fastest next move is not to edit code. Open an incognito window, go to the live URL, stay for 40 seconds, and wait five minutes. That sequence resolves the most common cases because it covers cache, live page, and linking in one pass.

If it still does not appear after ten minutes, the next step is the same: copy a fresh snippet once, confirm placement, and then contact support.

Limitations and when this checklist does not apply

This checklist assumes you are using the standard SeaText snippet from the Thinkific integration page. It may not cover a heavily edited snippet, a third-party script that blocks the code, or a Thinkific page that has no footer code support.

If you are testing inside the Thinkific course player or a mobile app that blocks third-party scripts, the widget can be absent even when the footer code is correct. Open the normal public site in a normal browser tab before you judge it.

The 40-second visit is meant for a real visit to the live page. A login wall, a coming-soon page, or a preview server can interfere with linking, so use the public URL whenever possible.

Frequently asked questions

Why does SeaText ask me to stay on the page for 40 seconds?

The visit is part of activation. SeaText says that staying on the page for at least 40 seconds activates the AI and links the website to your account.

How long should I wait before I see my site in the account?

Wait at least five minutes. Your website name should appear next to the SEATEXT logo. If it does not appear after 10 minutes, contact SeaText support.

Can I use a header code field instead of the footer?

The SeaText Thinkific instructions tell you to use the Site Footer Code field. Start there. If your site already has a different code management system, test the footer field first.

Why is the widget missing even though the code is saved?

Check the browser cache and the live URL first, then check the linking status in SeaText. A saved snippet is not linked until the activation visit happens and the site name appears in the account.

Should I paste the same code again?

You can paste a fresh copy once, but repeating that does not fix a linking issue. After the fresh copy, repeat the 40-second visit and the five-minute wait. If the site still does not appear, contact support.

What does a linked site look like?

Your website name appears next to the SEATEXT logo at the top of the account page. That is the signal that the installation can move to the AI activation step.

When to contact support

Contact SeaText support after you have completed the checklist in order: correct field, saved, live page, 40-second visit, five-minute wait, and a clean browser. If the site name still does not appear, that is when the SeaText documentation points you to the support team. Keep the integration page open so you can re-check the exact steps while you wait.

If SeaText content appears duplicated on Thinkific after a sync, the cause is almost always one of three things: two SeaText projects pointing at the same Thinkific site, the same JavaScript snippet pasted into Thinkific twice, or two sync schedules running at the same time. The fix is to identify which project owns the site, remove the extra code or schedule, and let one clean sync run.

Thinkific itself does not duplicate course content from a JavaScript tag. The duplication you see comes from SeaText pushing the same variant into the same page slot more than once. That happens when two installations overlap.

Why duplicate SeaText content shows up on Thinkific

SeaText installs on Thinkific by pasting a JavaScript snippet into the Site Footer Code field under Settings, then Code & Analytics. Once that snippet is live, SeaText reads the page and rewrites copy in the browser. If two snippets run on the same page, each one tries to write its own version of the headline, button, or section, and the second write often overlaps the first.

Three situations create this overlap:

• Two SeaText projects were linked to the same Thinkific URL, often after a test project was never deleted.
• The same JavaScript snippet was pasted into the Thinkific footer twice, sometimes after a theme or template change.
• Two sync schedules are active, so SeaText pushes variants from both projects on the same run.

Diagnose the duplication in the right order

Start with the cheapest check and move to the more specific ones. This order saves time because the first two causes cover most cases.

1. Open your Thinkific site in an incognito window and view the page source. Search for the SeaText snippet. Count how many times it appears.
2. Log in to SeaText and list every project. Check the website URL on each project card. More than one project pointing at the same Thinkific domain is the most common cause.
3. In SeaText, open each project and review its sync schedule. Two schedules firing at the same time will push overlapping variants.
4. Check the Thinkific footer code field for duplicate script tags, including any leftover code from a previous install.

Common mistakes that keep the duplication coming back

These are the patterns that turn a one-time fix into a recurring problem.

• Keeping a test project live. A test project created during setup is often left connected. It keeps syncing even after the main project is running.
• Pasting the snippet into multiple Thinkific themes. Thinkific lets you apply code at the site level and at the theme level. Code in both places runs twice.
• Re-running the link step after a domain change. When the Thinkific domain changes, a new project is sometimes created instead of updating the existing one.
• Two team members installing at the same time. Each person pastes the snippet without knowing the other already did.

Step-by-step fix for duplicated SeaText content on Thinkific

Work through these steps in order. Stop when the duplication clears.

1. Pick the project that should own the site. Choose the SeaText project that has the correct URL, language, and active variants.
2. Disable sync on every other project. In each extra project, turn off the sync schedule so it stops pushing variants.
3. Remove the extra JavaScript from Thinkific. Go to Admin Dashboard, then Settings, then Code & Analytics. Keep only one copy of the SeaText snippet in the Site Footer Code field. Click Save.
4. Clear the Thinkific cache. If you use a caching plugin or CDN, purge it so the old double-loaded page is not served.
5. Run a manual sync from the owning project. This pushes a clean set of variants through the single snippet.
6. Recheck the live page. Open the page in a fresh browser session and confirm the duplication is gone.

How to prevent the problem next time

One project per Thinkific site is the rule. Before any new install, confirm the existing project list in SeaText and decide whether to reuse or replace. When the Thinkific domain changes, update the URL inside the existing project rather than creating a new one. Treat the JavaScript snippet like a unique key: one site, one snippet, one project.

When the duplication is not from SeaText

Thinkific has its own course duplication feature for courses built with the Classic Course Builder. If the duplicated content is a full course, lesson, or page rather than a rewritten headline or button, the cause is inside Thinkific, not SeaText. In that case, review your course list and remove the duplicate course from the Admin Dashboard.

Key facts about SeaText on Thinkific

Limitations of this advice

This guide assumes the duplication is in rewritten copy such as headlines, buttons, or section text. It does not cover duplicated courses, lessons, or Thinkific pages, which are managed inside Thinkific. If the SeaText snippet is not visible in the page source at all, the install itself failed and the link step needs to be repeated.

Frequently asked questions

How do I know which SeaText project is the right one?

The right project is the one whose website URL matches your live Thinkific domain exactly, including the www prefix if you use one. It should also be the project where you actively edit variants.

Can I delete a SeaText project without breaking my Thinkific site?

Deleting a project stops it from syncing, but the JavaScript snippet stays in the Thinkific footer until you remove it. Remove the snippet first, then delete the unused project.

Why does the duplication only show on some pages?

SeaText only rewrites pages where variants are active. If two projects target different page sets, the overlap only appears on the pages both projects touch.

Do I need to reinstall SeaText after fixing the duplication?

Usually no. Removing the extra snippet and disabling the extra sync is enough. Only reinstall if the owning project loses its link, which you can confirm by checking whether your website name still shows next to the SeaText logo.

How long does a clean sync take to clear the old duplicates?

After you remove the extra snippet and purge any cache, the next manual sync from the owning project replaces the overlapping variants on the next page load. There is no separate cleanup step inside SeaText for this case.

What if the duplication comes back after a few days?

That usually means a second sync schedule is still active, or a team member re-pasted the snippet. Recheck the project list and the Thinkific footer code field.

Why Page-Level Verification Matters: Telemetry and Bot Refund Agents

When the SeaText AI verification handshake fails on a specific page, the immediate consequence is a total loss of telemetry. This is not merely a technical glitch; it has direct financial and operational implications for your marketing stack. Telemetry is the lifeblood of SeaText's autonomous agents, including the Bot Refund Agent. Without a successful verification, the AI cannot capture visitor behavior, making it impossible to perform real-time conversion optimization or bot detection.

The Bot Refund Agent relies on continuous, high-fidelity telemetry to identify invalid clicks. It analyzes forensic signals, such as mouse movement anomalies, rapid click patterns, and VPN signatures. If the verification fails, the agent cannot record this forensic evidence. Consequently, you lose the ability to automatically prepare refund-ready reports for Google and Meta. Given that bot traffic wastes up to 20% of ad budgets, a verification failure on key landing pages directly impacts your bottom line by preventing you from recovering wasted ad spend.

Verify Script Inclusion and Execution

The first step in troubleshooting is ensuring the SeaText JavaScript is actually loading on the problematic page. If you use a WordPress plugin like 'Insert Headers and Footers,' check that the code is active globally. Sometimes, page-specific settings in caching plugins or optimization tools can accidentally exclude certain pages from script execution.

To verify script loading, open your browser's developer tools (F12) and go to the Network tab. Refresh the page and search for 'seatext'. If the script is missing, re-save the code or ensure your header plugin is not failing on that specific URL. Remember that the AI remains inert until someone visits the page and stays active for at least 40 seconds. This dwell time triggers the initial activation handshake and links the session to your account.

Technical Mechanics of CSP Whitelisting (script-src and connect-src)

A Content Security Policy (CSP) is a security layer that helps detect and prevent certain types of attacks, including content injection attacks. If your site has a strict CSP, it may be blocking the SeaText script from executing or from sending data back to the servers. Understanding the technical mechanics of CSP whitelisting is crucial for developers.

The CSP is enforced via HTTP headers and utilizes specific directives. The two most relevant directives for SeaText are script-src and connect-src. The script-src directive controls where JavaScript files can be loaded from. If the SeaText script domain is not whitelisted here, the browser will refuse to download or execute the script. The connect-src directive controls where asynchronous HTTP requests (AJAX or fetch) can go. SeaText relies on this directive to send telemetry data back to its servers. If either directive is misconfigured, the browser console will display a violation error, halting the verification process.

To resolve this, you must update your CSP headers to whitelist the specific SeaText domains. For example, your header should include script-src 'self' https://seatext.com and connect-src 'self' https://seatext.com. If you use a third-party security plugin, navigate to its CSP settings and add these origins to the whitelist. Always test your changes in a staging environment before deploying them live.

Review Experiment Targeting Rules and Dynamic Logic

SeaText allows you to target experiments to specific URLs, paths, or segments. If the verification is failing only on one page, it is possible that a targeting rule is too restrictive or contains a typo that excludes the actual URL structure. This is particularly important for the Google Ads Agent, which dynamically rewrites landing page copy in real-time to match search keywords.

Go to your SeaText dashboard and check your active experiments. Ensure the URL pattern matches the live page exactly. For example, check if a trailing slash or a query parameter is causing the targeting logic to skip the page. The Google Ads Agent relies on precise targeting to deliver a 0ms zero-flicker page rewrite. If the targeting rules are misaligned, the AI cannot apply its dynamic keyword adaptation, severely hurting your Quality Score and ROAS.

Trade-offs: Real-Time AI Adaptation vs. Traditional Static A/B Testing

When troubleshooting verification, it helps to understand the underlying technology's trade-offs. Traditional static A/B testing relies on binary conversion tracking and null-hypothesis significance testing. It requires tens of thousands of visitors to reach 95% statistical confidence. For low-traffic B2B sites or niche ecommerce stores, running a single test can take 4 to 8 months, making the results obsolete by the time they are finalized.

In contrast, real-time AI adaptation uses millisecond-level reading telemetry. Instead of treating visitors as binary converters or bounces, the AI analyzes behavioral signals like eye-line dwell velocity, scroll deceleration, and friction points. It utilizes continuous multi-armed bandit optimization to automatically scale winning copy variants on live traffic. The trade-off is that traditional testing offers high statistical certainty but is too slow for modern web environments, while AI adaptation offers rapid, behavioral insights but requires trust in the AI's autonomous decision-making. Ensuring the verification handshake is active is the prerequisite for this advanced AI testing to function.

Caching, CDN, and Client-Side Blocks

If you use a Content Delivery Network (CDN) like Cloudflare or server-side caching, the browser might be serving an old version of the page that lacks the latest SeaText script. Clear your site cache and your CDN cache to ensure the most recent version of your code is being served to visitors. Additionally, browser extensions, particularly ad-blockers and privacy-focused tools, often identify tracking scripts as advertisements.

If the verification fails for you but works for others, it is likely a local client-side block. Test the page in an Incognito or Private window with all extensions disabled. If it works there, you will need to whitelist your site within your ad-blocker settings.

Limitations and Exceptions

SeaText verification will not work on 'localhost' or restricted development domains due to security protocols. Additionally, if your page is behind a password protection or a login wall, the AI agents may be unable to crawl the content properly for SEO optimization purposes. Ensure the page is accessible via a valid, real domain for best results. Each SEATEXT AI account is linked to a single primary URL, so if you use multiple domains, you must create separate accounts for each to ensure data integrity.

FAQ

How long does it take for verification to show in the dashboard?
It usually takes 5 to 10 minutes for the website name to appear in the dashboard after the script is correctly installed. However, the AI remains inert until a visitor stays on the page for at least 40 seconds to trigger the activation handshake.

Do I need a separate account for every domain?
Yes, if you are using multiple domains (e.g., a staging and a production site), you must create separate accounts for each to ensure data integrity. Each SEATEXT AI account is linked to a single primary URL.

How does the Bot Refund Agent use the telemetry from the verification?
The Bot Refund Agent uses the telemetry stream to detect bot clicks in real-time. It records forensic click evidence and automatically prepares refund-ready reports for Google and Meta. Without a successful verification, the agent cannot collect this evidence, preventing you from recovering up to 20% of your ad spend.

What if my CSP is managed by a third-party security plugin?
Open your security plugin's settings and locate the Content Security Policy section. Add the SeaText script and connect domains to the whitelist under the script-src and connect-src directives. If you cannot find these specific options, check with the vendor for advanced configuration documentation.

What does “connected but not working” mean?

You see a green “connected” indicator in the SeaText dashboard. But the AI agents do not rewrite copy, translate pages, or block bot traffic. This is a false positive. The dashboard only confirms that the script reached SeaText’s servers. It does not mean the AI is active on your site.

The connection indicator shows your domain name next to the SeaText logo. That means the script loaded successfully. However, the AI agents need to be activated separately. They also need a clean script environment to run. JavaScript errors, an expired API key, or a cached version of the page can block them.

In short, “connected” is not the same as “working”. You need to diagnose why the AI agents are not executing.

Why does this happen? (Root causes)

Five main reasons cause this false positive connection:

• Script not installed correctly. The JavaScript snippet must be placed before the closing </head> on every page. If you use WP Engine, install the official plugin. The script must be present on all pages, not just the homepage.
• JavaScript errors. Other plugins or themes can conflict with the SeaText script. Open the browser console (F12) and look for red error messages. They often reveal the exact conflict.
• Expired or missing API key. The AI needs a valid API key to function. Check the dashboard’s API settings. If the key expired, generate a new one.
• Cache or CDN serving an old version. If your site uses a caching plugin or a CDN (like Cloudflare), it may deliver a page without the SeaText script. Purge all caches.
• Activation wait time not met. After installing the script, you must stay on any page for at least 40 seconds. Then wait five minutes for the dashboard to update. Without this, the connection may not fully register.

Additionally, SeaText links one account to one primary URL. If you use multiple domains (e.g., a development domain and a production domain), you need separate accounts per domain. Localhost and other development URLs are restricted for security reasons. They will not show as connected.

Step-by-step diagnostic sequence

Follow this order to find the exact cause. Do not skip steps.

1. Open the SeaText General Integration page. Copy the latest JavaScript code from General Integration.
2. Reinstall the script. Paste it into your site’s global header (before </head>). If you use WP Engine, use the provided plugin. Save and publish.
3. Visit any page on your site. Stay on that page for at least 40 seconds. This activates the AI and links it to your account.
4. Wait five minutes. Refresh the SeaText dashboard. Look for your site name next to the SeaText logo at the top. If it appears, the connection is established.
5. Check the browser console. Open developer tools (F12) and go to the Console tab. Resolve any red error messages. Common errors: “SeaText is not defined”, “API key missing”, or “Failed to load script”.
6. Clear your cache. Clear the browser cache, or use an incognito window. Also purge any CDN or site cache plugin.
7. Verify the API key. Log into the dashboard, go to API settings. Ensure the key is active and not expired. If expired, generate a new key and update the script.
8. Test again. Reload the page. Wait 40 seconds. Check the dashboard for green status on each agent.

If the site name still does not appear after 10 minutes, contact support immediately. This indicates a deeper installation issue.

How to fix each common cause

Script not loading or placed in the wrong location. Reinstall from the General Integration page. Ensure the script appears before the closing </head> tag. Use the WP Engine plugin if you are on that platform. The script must be on every page, not just the homepage.

JavaScript errors. Open the console and look for errors. Common fix: temporarily disable other plugins or scripts to isolate the conflict. If the error is “SeaText is not defined”, the script did not load. Check your header file for missing code.

Expired or missing API key. In the dashboard, navigate to API settings. Copy the key. Ensure it is included in the script snippet. If you recently changed the key, update the script on your site. The key is essential for AI to function.

Cache or CDN serving an old version. Clear your site’s cache plugin (e.g., WP Rocket, W3 Total Cache). If you use a CDN, purge the CDN cache. Also clear your browser cache or test in incognito mode. This ensures the latest script is served.

Insufficient activation wait time. After installing the script, stay on a page for at least 40 seconds. Then wait five minutes for the dashboard to update. Do not navigate away during those 40 seconds. The AI needs to see a real visitor session to activate.

Multiple domains or development URLs. Each domain needs its own SeaText account. Development URLs like localhost or staging sites are not allowed. Use a real domain for testing. If you need to test on a development domain, contact support for options.

How to verify the AI is truly active

After the steps above, you should see real-time changes. For example, headlines may rewrite, translations may appear, or bot traffic alerts may show. The easiest way to verify is to check the agents panel.

Go to the SeaText homepage. Log in and view the agents panel. Each agent you activated should show a green “Active” status. If an agent shows “Inactive” or “Error”, click on it to see details.

You can also test by visiting a page on your site. Look for changes in the page content. For example, if you activated the Translation Agent, the page may appear in a different language. If you activated the CRO Optimizer, headlines may change based on visitor source.

If you still see no changes after 10 minutes, the AI is likely still blocked. Re-run the diagnostic sequence. Pay special attention to the console errors and API key.

Frequently asked questions

• Why does the dashboard say “connected” but nothing changes on my site? The connection indicator only tells you the script reached SeaText’s servers. The AI agents must be activated separately. Also, the script must run without errors. Check the console and agent activation status.
• How long should I wait after installing the script? Stay on a page for at least 40 seconds. Then wait five minutes for the dashboard to update. If you don’t see the site name after 10 minutes, contact support.
• Can a CDN prevent the AI from working? Yes. If the CDN caches a page without the new script, the AI cannot run. Purge the CDN cache and also clear your browser cache.
• Do I need a separate account for each domain? Yes. SeaText AI links one account to one primary URL. Using multiple domains requires separate accounts. Development URLs like localhost are restricted.
• What if I see JavaScript errors but can’t fix them? Common errors are caused by conflicting plugins. Temporarily disable other plugins one by one to find the conflict. You can also contact SeaText support with the console error logs.

If you have completed all steps and the AI still does not work, contact SeaText support. Provide them with the console errors, the exact URL where the script is installed, and a screenshot of the dashboard connection status. Support can check backend logs for further issues.

If SeaText AI fails to connect during Shopify setup, first retry the connection, confirm you are in the correct Shopify admin, and verify that the SeaText JavaScript snippet is installed in your active theme. Most connection failures come from a simple domain mismatch, a missing snippet, or an unsaved edit to theme.liquid.

The steps below follow the SeaText Shopify Integration guide. Use them in order, and test only when a step tells you to.

Do this before you retry

These checks take less than a minute and solve many failed connections.

• Wait 30 to 60 seconds, then retry the connection. Temporary network timeouts often clear on their own.
• Log into the Shopify admin for the exact store you want to connect. Check the store URL in the browser before you continue.
• Log into the SEATEXT AI account that goes with that store. The install requires an account before the script can connect.
• Open Online Store > Themes and confirm which theme is active. The snippet must go into the active theme.

Step-by-step recovery for a failed SeaText connection

Follow this order. Do not skip the verification step.

1. Open your SEATEXT AI account and confirm the script is visible. The JavaScript code appears in the integration section of your account. Copy it from there, not from another page.
2. Check the primary URL. Each SEATEXT AI account is linked to a single primary URL. Compare that URL to the exact Shopify storefront URL, including any www or subdomain.
3. Open your Shopify theme editor. Go to Online Store > Themes. Click the three-dot icon next to the active theme and choose Edit code.
4. Open theme.liquid. In the file list, find the Layout folder and select theme.liquid.
5. Paste the snippet and save. Place the SeaText JavaScript snippet where the integration guide shows, then click Save. Make sure the save finishes before you leave the page.
6. Reload with a clean view. Open the store in an incognito window or hard-refresh the page. A cached copy can make the connection look broken.
7. Preview a product page and inspect the HTML source. In your browser’s developer tools, verify that the data- attribute is present. This is the final proof that the snippet is live.

If the data attribute appears, the script is loaded. The remaining issue is likely on the account side, so move to the account checks below.

What “fails to connect” usually means

During Shopify setup, “fails to connect” means SeaText cannot match the script on your site to your SeaText account. The script may be missing, on a different domain, or on a domain SeaText does not accept.

The domain match matters more than the connection button. SeaText ties each account to one primary URL. If the store URL and that primary URL are not identical, the connection cannot stick.

This is also why you should not ignore the failure. A half-completed setup leaves the snippet on the page without an active account match, and later agents will not be able to run. The installation itself is secure, and the AI stays inert until activated, so you can retry without changing your live content.

Key facts to check during Shopify setup

Use this table as a quick checklist whenever setup fails.

Common setup mistakes that break the connection

• Wrong theme file. The snippet belongs in theme.liquid inside the Layout folder of the active theme.
• Unsaved edits. The code can look installed in the editor while the live page still has the old file.
• localhost testing. Development URLs such as localhost are restricted for security reasons, so the connection fails.
• Dynamic development domains. These may not work because SeaText may be unable to reliably associate traffic with your account.
• One account for two domains. You need a separate account for each domain, including a separate account for a development and production pair.
• Checking the wrong product template. The product description is usually in product.liquid or product-template.liquid. Inspect the page that actually renders the description.

When the connection failure is an account or domain problem

If the snippet is in the right file and the data attribute appears, the problem is usually account-side.

• Compare the store URL to the primary URL on the account. Include the protocol, the www, and any subdomain.
• If you run more than one website, create one account per website.
• If you use a development domain and a production domain, create separate accounts for each.
• If you use a dynamic development domain, expect it to fail. Switch to a valid real domain.

Start a fresh connection only after the account and domain are aligned.

Limitations to know before you retry

• One SEATEXT AI account is linked to one primary URL.
• One account per website is required when you use SeaText on several websites.
• localhost and similar development URLs are restricted.
• Dynamic development domains may not function properly.
• The AI remains inert until activated, so a successful connection alone will not change your site.

SeaText AI connection FAQ

Why does SeaText fail when I test on localhost?

SeaText restricts development URLs such as localhost for security reasons. Use a valid real domain instead.

Can one SeaText account cover two Shopify stores?

No. Each account is linked to a single primary URL, and SeaText requires separate accounts for separate websites.

What is a primary URL?

It is the main domain registered to your SeaText account. The storefront URL must match it for the script to connect.

How do I know the snippet is actually loaded?

Save the theme file, preview a product page, and inspect the HTML source in your browser’s developer tools. The data- attribute should be present.

I saved the code but the connection still fails. What should I do next?

Check that you pasted into the active theme’s theme.liquid, not a duplicate theme or the wrong template. Then compare the account primary URL with the store URL. If both are correct, create a separate account if you are using a second domain.

Will SeaText change content as soon as the snippet is installed?

No. The installation process is secure, and the AI remains inert until activated.

Where to get the exact integration steps

The SeaText Shopify Integration page is the reference for this recovery. It shows where the JavaScript code comes from, which theme file to edit, and how to verify the data- attribute. Keep it open while you retry the connection.

Open the Shopify Integration guide and run through the checklist once more.

If SeaText AI doesn't appear after installation, don't worry—this is a common issue that can usually be fixed with a few simple steps. First, make sure you've activated the AI by visiting your website and staying for at least 40 seconds. Then, wait 5-10 minutes for the connection to complete. If the problem persists, reach out to SeaText support right away.

If Seatext AI doesn't work on your product pages, the problem is usually in the setup, not the tool. Check three things first: the JavaScript snippet is installed on the exact page template, the product description is wrapped in the required element with a data- attribute, and the account you are logged into is linked to the same primary URL as your product-page domain. Work through those checks, then inspect the live page with your browser's developer tools. If everything passes and you still see no changes, contact Seatext support with your account URL and a screenshot of the HTML.

This article is a diagnostic guide. It moves from symptoms to likely causes to fixes. It also covers the common mistake that makes Seatext AI look broken on product pages even when the rest of the site works.

Check the basics first

Before you change any code, answer these questions:

• Do you have a Seatext AI account? The script is copied from your account area. Without an account, there is no script to install.
• Is the script installed on the same domain as your product pages? Each Seatext account is linked to a single primary URL. A script from one account will not run reliably on another domain.
• Is the domain a real, stable domain? Development URLs such as localhost are restricted, and dynamic development domains may not work.
• Have you activated at least one agent after installing the script? Seatext AI stays inert until you activate it.

Use this diagnostic sequence

Follow this order. It rules out cheap fixes first.

1. Open one product page in a regular browser window.
2. Use View Page Source or developer tools to confirm the Seatext script appears in the HTML.
3. Look for the data- attribute on the product description element.
4. Check the domain in your address bar against the primary URL for your Seatext account.
5. Log into Seatext and confirm the agents you need are active.
6. Save any template changes, clear your page cache if you have one, and reload the product page.
7. If nothing changes after step 6, contact support.

On Shopify, check theme.liquid and the product template

Shopify has a specific install path. The Seatext integration guide uses these steps:

1. In your Shopify admin, go to Online Store > Themes.
2. Next to your active theme, click the three dots icon and choose Edit code.
3. Open the Layout folder and find the file named theme.liquid.
4. Paste the Seatext JavaScript snippet and save the file.

Saving theme.liquid loads Seatext on your Shopify pages. But product descriptions need one more step. The product description is usually rendered in a file named product.liquid or product-template.liquid. Find the line that outputs the product description and wrap it with the required element that includes the data- attribute Seatext looks for. Save the file, then preview a product page.

To confirm it worked, open the same product page in your browser's developer tools and inspect the HTML source. The product description element should include the data- attribute. If it is missing, the template edit did not save, or you edited the wrong template.

The most common mistake: wrong domain or wrong account

The most common reason Seatext AI doesn't work on product pages is that the page is being viewed on a domain that does not match the Seatext account. Each Seatext account is linked to a single primary URL. When you paste the script on a second domain or on a staging URL, the account may not associate that traffic with your site. The result looks like a product-page bug, but it is an account mismatch.

This mistake happens often in product-page testing because you can have a development copy of your store at a URL like staging.example.com while the live store is at www.example.com. Seatext treats those as different domains. Create a separate account for each domain, and only test on a real domain. Localhost is blocked. Dynamic development domains may also fail because Seatext cannot reliably associate traffic with your account.

Why the agent may be active but nothing changes

Installing the script is not the same as turning on the feature. Seatext says the AI remains inert until activated. After you add the script, go to your Seatext dashboard and activate the agents you want on product pages. If the script is installed but no agent is active, the page will load normally and no copy changes will appear.

On product pages, the relevant agents are usually the ecommerce product copy agent, the translation agent, or the personalization agent. Which agents you need depends on your goal. The key point is that activation is a separate step from installation. Check that step before you dig into template code.

Symptom table: likely causes and fixes

When this advice does not apply

This guide is based on the official Seatext integration instructions, which currently give the most detail for Shopify. If your product pages run on a custom CMS or a different ecommerce platform, the generic script steps still apply: copy the JavaScript snippet from Seatext, paste it into your site's shared layout file, and make sure the product description markup includes the required data- attribute. The exact file names will be different.

This advice will not fix server errors, database issues, checkout failures, or problems caused by another app that rewrites your theme files. If a browser extension blocks third-party scripts, that can also look like a Seatext failure. Test in a normal browser window or an incognito window before assuming the installation is wrong.

Key facts at a glance

Terminology you may see in the docs

• Primary URL: the single domain linked to your Seatext account.
• theme.liquid: Shopify layout file that loads scripts across the theme.
• Product template: the Shopify file that renders product details, often product.liquid or product-template.liquid.
• Data- attribute: a custom HTML attribute that starts with data- and helps Seatext identify product description content.
• Activation: turning on an agent in the Seatext dashboard after installing the script.

FAQ

Why does Seatext AI work on my homepage but not on product pages?

Homepage and product pages often use different template files. The script may be in theme.liquid, but the product description still needs the required data- attribute wrapper in product.liquid or product-template.liquid. If it is missing, Seatext does not know which content to optimize.

Can I test Seatext on localhost?

No. Development URLs such as localhost are restricted for security reasons. Use a real, stable domain for testing.

Do I need a separate Seatext account for my staging site and my live site?

Yes. Each account is linked to a single primary URL. If you use a development domain and a production domain, create separate accounts for each.

I installed the script. Why is nothing changing on my product page?

Check that you activated an agent after installation. Seatext AI stays inert until activated. Then verify the product description markup has the data- attribute.

How do I verify the installation myself?

Open the product page in your browser, use developer tools to view the HTML source, and look for the Seatext script. Then find the product description element and confirm it contains the data- attribute.

What should I tell Seatext support if I still need help?

Send the primary URL of your Seatext account, the exact product-page URL, and a screenshot of the HTML source showing whether the script and data- attribute are present. That lets support compare your account against the page quickly.

If SeaText AI doesn't connect after installation, don't reinstall yet. Work through the short readiness checklist in this article. First confirm the script is loading, the account matches the domain, and at least one agent is activated. In most cases this fixes the issue without touching the code again.

SeaText installs as a JavaScript snippet. You paste it into your website, usually in Shopify's theme.liquid file. If the snippet never loads, or loads on a domain that isn't linked to your account, SeaText can't connect. Here is what to check, in the order that finds broken connections fastest.

Symptoms that SeaText AI isn't connecting

Before changing anything, know what a failed connection looks like. Check these symptoms:

• You view the page source and don't see the SeaText JavaScript snippet.
• On a product page, the data attribute is missing from the HTML source.
• You saved the snippet, but nothing changes on the page.
• You installed it on localhost or a dynamic preview domain.
• The script works on one website but not on a second domain with the same account.

Why this happens: five common causes

You don't have a SeaText account yet

The integration guide says: 'Before you can install the script, you need a SEATEXT AI account.' The script is tied to an account. If you skip this step, there is nothing for the script to connect to. Create the account first, then copy the JavaScript snippet from inside that account.

The domain doesn't match your account

Each SEATEXT AI account is linked to a single primary URL. If you paste the snippet on a different domain, a subdomain, or a staging environment, SeaText won't know those visits belong to you. For a second website, create a second account.

You're using localhost or a dynamic development URL

Development URLs like localhost are restricted for security reasons. Dynamic development domains may also fail because SeaText can't reliably connect traffic to your account. Use a real, valid domain when you test.

The snippet is missing, misplaced, or not saved

In Shopify, open Online Store > Themes > Actions > Edit Code. Go to the Layout folder and open theme.liquid. Paste the snippet where the integration guide shows, then click Save. For product descriptions, the output must be wrapped with the correct tag. If you skip the save button, the code is gone the moment you leave the page.

The AI is installed but not activated

The guide says the AI 'remains inert until activated.' A loaded script is not the same as an active agent. Go into your SeaText account and check that you've activated at least one agent before you judge the connection.

The SeaText connection readiness checklist

Run these checks in order. Stop and fix the first problem you find, then move on.

1. Check the basic connection. Confirm the site loads in your browser and your internet connection is up. A blank page is not a SeaText problem.
2. Confirm the account exists. Open your SeaText account and copy the snippet from this session. Don't use a snippet from an old email or a coworker.
3. Check the primary URL. The domain where the script lives must be the same domain registered in your account.
4. Rule out localhost. Localhost is blocked. Any test site must run on a real, valid domain.
5. View the page source. In your browser, right-click and select View Page Source. Search for 'SEATEXT' or the script name.
6. Open theme.liquid. In Shopify, go to Online Store > Themes > Edit Code, then Layout > theme.liquid and compare the snippet to what the integration guide shows.
7. Save all changes. Click Save after pasting the snippet.
8. Activate an agent. Log into SeaText and turn on at least one agent. The script stays inert until you activate it.
9. Test the data attribute. Load a product page, open developer tools, and check that the data- attribute appears in the HTML source.
10. Clear cache and retest. Your site or browser may be serving an old version that doesn't contain the snippet.
11. Talk to support. If every check passes, go to the SeaText website and contact support with what you've tested.

Troubleshooting table: symptom, likely cause, quick fix

Key facts to know before you reinstall

Limitations and cases where this advice doesn't apply

The integration guide has hard limits you should know before troubleshooting too long:

• Multiple websites need separate accounts. The source says one account for each website.
• One primary URL per account. You can't point the same account at two production domains.
• Localhost and similar development URLs are blocked. This includes dynamic dev domains that can't be tied reliably to the account.
• The AI is inert until activated. If you activated nothing, a working connection may still have no effect.

If you installed SeaText on a custom platform that isn't Shopify, the general connection rules above still apply, but the exact file names will be different. Look for the global template or layout file where your site's head is rendered.

What the technical words mean

• Primary URL: the single web address linked to your SeaText account.
• theme.liquid: the Shopify layout file that controls your theme's global HTML structure.
• Data- attribute: a custom HTML attribute you can look for in the page source to verify the tag is working.
• Inert script: a script that loads but does not run any agent until you activate it in SeaText.

Frequently asked questions

Why does SeaText need one account per domain?

Because each account is linked to a single primary URL. The guide says this directly. If you want SeaText on multiple websites, you need multiple accounts.

Can I test SeaText on localhost?

No. Development URLs such as localhost are restricted for security reasons. Use a real, valid domain for any test.

How do I know the script is actually on my page?

Open the page in your browser, view source, and search for 'SEATEXT.' Then go to a product page and verify that the data- attribute is present in the HTML using browser developer tools.

I pasted the code but the page still doesn't change. Did I connect?

Maybe not. Check that you clicked Save, the snippet is in the correct file, and you've activated an agent. A loaded script is not the same as an active agent.

What should I do if I've tried everything and it still won't connect?

Go to the SeaText website and contact support. Before messaging, write down what you've checked: the domain, the account, the file, and the page source result. That will speed up the fix.

If your SeaText AI connection fails, start by verifying the JavaScript snippet is on every page, confirming the domain is a real public URL, and waiting at least 5 minutes after a 40-second visit. If it's still not connected, check host-specific script blockers and clear platform/CDN cache.

If Seatext activation fails on Tilda, first verify you pasted the JavaScript snippet into the correct Tilda HEAD field or T123 block. Then save and publish the site. Visit the live URL for at least 40 seconds. Wait five minutes. If the site name still does not appear next to the Seatext logo, contact Seatext support with error logs, the Tilda site URL, and a screenshot of the code placement.