Direct Answer: Personalizing Ads by Search Query Length

Google Ads does not have a built-in feature to create personalization rules directly based on the length of a user's search query. The common method to achieve this is by capturing the exact search query a user typed. This is done by appending the query to your landing page URL using Google Ads' ValueTrack parameters. Once the query is on your landing page, you can use code to measure its length. Based on this length, you can then display different content, such as headlines, special offers, or page layouts.

Why Personalize by Query Length?

Personalizing your landing page content based on search query length can significantly improve user experience and conversion rates. When a user searches for something, they have a specific intent. A short, precise query often indicates a user who knows exactly what they want and is ready to buy. For example, someone searching "red running shoes size 9" is likely looking for a specific product and wants to see pricing and availability immediately.

Conversely, a longer, more descriptive query might suggest a user who is still in the research phase. They might be comparing options, looking for information, or trying to understand a problem. For instance, a search like "best lightweight running shoes for marathon training with arch support" indicates a need for detailed information and comparisons.

By matching the landing page content to the user's apparent intent, you reduce friction. This alignment, known as "ad scent," ensures that the user sees relevant information right away. It prevents the "Ad Scent Disconnect," where an ad promises something specific, but the landing page is generic. This disconnect leads to immediate user frustration and a high bounce rate.

Tailoring content based on query length helps you:

• Improve Relevance: Show users exactly what they are looking for.
• Increase Engagement: Keep users on your page longer by providing valuable content.
• Boost Conversion Rates: Guide users more effectively toward a purchase or desired action.
• Enhance User Experience: Make the journey from search to solution smoother.

This approach treats query length as a proxy for user intent. While not a perfect measure, it's a practical way to segment your audience and deliver more targeted experiences.

Technical Setup: Capturing and Using Query Length

Implementing personalization based on query length involves several technical steps. You need to modify your Google Ads setup and your landing page's code.

Step 1: Capture the Search Query in Google Ads

The first step is to ensure that the actual search query is passed to your landing page. You can do this by adding a ValueTrack parameter to your ad's final URL or tracking template.

1. Navigate to Your Campaign or Ad Group: In your Google Ads account, select the specific campaign or ad group you wish to personalize.
2. Edit Final URL Suffix or Tracking Template: Locate the settings for your ads. You will typically find an option to edit the "Final URL suffix" or the "Tracking template."
3. Add the ValueTrack Parameter: Append the following parameter to your existing suffix or template. If you are using the final URL suffix, it might look like this: ?search_query={query}. If you are using a tracking template, it would be part of the URL construction.
4. Save Changes: After adding the parameter, save your changes.

Explanation of {query} and {keyword}:

• {query}: This parameter captures the exact search term the user typed into Google. This is the most comprehensive option for capturing user intent.
• {keyword}: This parameter captures the keyword that triggered your ad. If you are using broad match or phrase match keywords, this might not be the exact search term. It's useful if you only need to match based on the bidded keyword itself.

Once this is set up, every click from this ad will direct the user to a URL that includes the search query. For example, if a user searches for "buy blue widgets online" and clicks your ad, their landing page URL might become: https://www.yourwebsite.com/landing?search_query=buy+blue+widgets+online.

Step 2: Read the Query Parameter on Your Landing Page

With the search query now appended to the URL, you need to write code on your landing page to read this parameter and extract the query string.

You can add a JavaScript snippet to your landing page. It's best to place this script just before the closing </body> tag or within your tag management system (like Google Tag Manager).

const params = new URLSearchParams(window.location.search);
const rawQuery = params.get('search_query') || ''; // Get the raw query string

// Calculate character count
const queryLengthChars = rawQuery.trim().length;

// Calculate word count
const wordCount = rawQuery.trim().split(/\s+/).filter(Boolean).length;

// Store the data globally for easy access
window.seatextQueryData = {
  rawQuery: rawQuery,
  queryLengthChars: queryLengthChars,
  wordCount: wordCount
};

This script does the following:

• It uses `URLSearchParams` to easily access query parameters from the URL.
• It retrieves the value associated with the `search_query` parameter. If the parameter is not found, it defaults to an empty string.
• It calculates the character count of the trimmed query (removing leading/trailing whitespace).
• It calculates the word count by splitting the trimmed query by spaces and filtering out any empty strings.
• It stores these values in a global JavaScript object `window.seatextQueryData` for use in other parts of your page's logic.

Step 3: Define Your Personalization Buckets

Before you can swap content, you need to decide what constitutes "short," "medium," and "long" queries for your specific business. These definitions should align with user intent and the type of content that best serves each intent.

Here's an example of how you might define these buckets:

• Short Queries (e.g., ≤ 20 characters / ≤ 3 words): These often represent high-intent searches for specific products or services. Users are likely ready to purchase or make a decision.
  • Content Strategy: Focus on direct calls to action, pricing, availability, and immediate purchase options. Example: "Buy red shoes now."
• Medium Queries (e.g., 21-50 characters / 4-7 words): These might indicate users who are comparing options, looking for features, or seeking more detailed product information.
  • Content Strategy: Provide comparison tables, feature highlights, testimonials, or case studies. Example: "Compare best running shoes for flat feet."
• Long Queries (e.g., > 50 characters / > 7 words): These typically signal users who are in the early research or informational stage. They might be asking questions or exploring a topic broadly.
  • Content Strategy: Offer educational content, guides, FAQs, or detailed explanations. Example: "What are the benefits of using natural skincare products for sensitive skin?"

The exact character or word count thresholds will vary depending on your industry and target audience. It's crucial to analyze your own search query data to determine the most effective segmentation.

Step 4: Implement Content Swapping Logic

Now, you'll use the `window.seatextQueryData` object to dynamically change elements on your landing page.

Here's a client-side JavaScript example to change a headline:

// Ensure the script runs after the DOM is ready
document.addEventListener('DOMContentLoaded', function() {
  if (window.seatextQueryData) {
    const { queryLengthChars } = window.seatextQueryData;
    let headlineText = 'Discover Our Amazing Products'; // Default headline

    if (queryLengthChars <= 20) {
      headlineText = 'Exact Match - See Price & Buy Now!'; // For short, high-intent queries
    } else if (queryLengthChars <= 50) {
      headlineText = 'Compare Features and Benefits'; // For medium queries
    } else {
      headlineText = 'Learn Everything You Need to Know'; // For long, research queries
    }

    const headlineElement = document.getElementById('main-headline');
    if (headlineElement) {
      headlineElement.textContent = headlineText;
    }
  }
});

In this example:

• The code waits for the page's HTML to be fully loaded.
• It checks if `window.seatextQueryData` exists.
• It uses the `queryLengthChars` to determine which headline to display.
• It finds an HTML element with the ID `main-headline` and updates its text content.

Server-Side Rendering (SSR): If you are using a server-side framework like Next.js, PHP, or Ruby on Rails, you can read the `search_query` parameter on the server before rendering the HTML. This allows you to choose the correct page template or content blocks to send to the browser, resulting in a faster, flicker-free experience for the user.

Step 5: Test and Verify Your Implementation

Thorough testing is essential to ensure your personalization is working correctly.

1. Use Test URLs: Manually construct URLs with different search queries to simulate various lengths. For example:
   • Short query: `https://www.yourwebsite.com/landing?search_query=red+shoes`
   • Medium query: `https://www.yourwebsite.com/landing?search_query=best+red+running+shoes+for+women`
   • Long query: `https://www.yourwebsite.com/landing?search_query=how+to+choose+the+right+red+running+shoes+for+marathon+training`
2. Check Browser Console: Open your browser's developer console (usually by pressing F12). Navigate to the "Console" tab. You should see the `window.seatextQueryData` object populated with the `rawQuery`, `queryLengthChars`, and `wordCount`.
3. Verify Content Changes: Inspect the elements on your page (like the headline) to confirm they have changed according to the query length and your defined rules.
4. Test Across Buckets: Repeat the process for short, medium, and long queries to ensure all your defined personalization rules are functioning as expected.
5. Monitor Performance: After launching, closely monitor your conversion rates and user behavior metrics to assess the impact of your personalization efforts.

How SeaText's Google Ads Agent Enhances Personalization

SeaText's Google Ads Agent is designed to optimize landing pages by matching them to specific keywords in real time. While it doesn't natively evaluate query length, it can be integrated into a broader personalization strategy.

The agent works by reading the incoming `utm_term` or ValueTrack `{keyword}` parameter on page load. It then rewrites key elements of the landing page, such as the headline, subhead, and proof points, to align with the matched keyword. This process happens very quickly, often in under 15 milliseconds at the edge, minimizing latency.

Extending SeaText for Query Length Personalization:

• Combine with Custom Logic: You can run the SeaText agent alongside the JavaScript snippet described earlier. Your custom script can first determine the query length bucket.
• Pass Length as a Custom Parameter: You could potentially pass the determined query length bucket (e.g., `short`, `medium`, `long`) back to SeaText as a custom parameter.
• AI-Generated Variants: SeaText's AI could then be configured to generate specific copy variants for each of these length-aware buckets, further enhancing the personalization.

This combination allows you to leverage SeaText's speed and keyword-matching capabilities while adding the layer of personalization based on query length.

Key Facts from SeaText

SeaText offers tools that can assist in landing page optimization, including aspects relevant to personalization.

Limitations and Considerations

While personalizing by query length is powerful, it's important to be aware of its limitations and potential drawbacks.

• Campaign Type Restrictions: The ValueTrack parameter {query} is only available for Search Network campaigns. It cannot be used for campaigns like Shopping, Display, or Performance Max. For these campaign types, capturing the exact search query for length-based personalization is not directly possible.
• Client-Side Rendering Impact: If you implement personalization using client-side JavaScript, there might be a slight visual delay or "flicker" as the content updates after the initial page load. Server-side rendering or edge computing can mitigate this.
• Query Length as a Proxy: Search query length is an indicator of intent, but not a definitive one. A very short query could be vague, and a long query might still be navigational rather than transactional. Always validate with data.
• Google Ads Policy Compliance: Ensure your personalized content adheres to Google Ads policies. You cannot use the search query to display misleading, discriminatory, or prohibited content. The personalization must be relevant and not deceptive.
• Technical Complexity: Implementing and maintaining this type of personalization requires technical expertis

You activate SeaText AI on specific page types by installing the JavaScript snippet site-wide, then using the Main AI Hub in your SeaText dashboard to enable agents only on the URLs or page categories you select. The AI stays inert until you turn it on for each page type, giving you full control over where each of the 20 specialized agents runs.

Prerequisites before you start

Before configuring page-type activation, complete these one-time setup steps:

• Create a SeaText AI account — each account links to a single primary domain. If you manage multiple domains (for example, a staging and a production site), you need a separate account for each.
• Install the JavaScript snippet on every page — copy the code from your SeaText dashboard and paste it into the <head> of your site template so it loads everywhere. On WP Engine, use the dedicated plugin to add custom JavaScript.
• Verify the connection — visit your site several times and stay on a page for at least 40 seconds. Wait up to five minutes for your website name to appear next to the SeaText logo in the dashboard. If it does not appear after 10 minutes, contact support.

Step-by-step: activate agents for a page type

1. Open the Main AI Hub in your SeaText dashboard.
2. Choose the agent you want to run — for example, the Google Ads Landing Page Agent, the Ecommerce Product Copy Agent, or the Website Translation Agent.
3. Click "Configuration" for that agent to adjust its parameters.
4. Select the target pages — you can specify individual URLs, URL patterns, or page categories (such as blog posts, product pages, or landing pages) where the agent should be active.
5. Save and publish the configuration. The agent will begin working only on the pages you designated.

Understanding page types and agent matching

SeaText provides over 20 autonomous agents, each designed for a specific job. Matching the right agent to the right page type is where the value lives:

• Google Ads Landing Page Agent — rewrites headlines, offers, and CTAs in real time to match the keyword that triggered the ad. Best on paid landing pages.
• Ecommerce Product Copy Agent — optimizes product names, descriptions, and CTAs. Deploy on product detail and category pages.
• Website Translation Agent — translates every page element into up to 125 languages. Enable site-wide or only on international-facing sections.
• Visitor Source Rewrite Agent — adapts copy to match the visitor's origin (Google, Meta, email, referral). Useful on high-traffic entry pages.
• AI A/B Testing Agent — generates variants and scales winners. Works on any page where you want continuous copy optimization.
• Bot Protection Agent — detects invalid paid clicks and builds refund-ready reports. Activate on pages receiving paid traffic.

You can run multiple agents on the same page type. For instance, a product page might run the Ecommerce Product Copy Agent, the Translation Agent, and the A/B Testing Agent simultaneously.

Configuration options per agent

Each agent exposes its own configuration panel in the Main AI Hub. Common settings include:

• Target URL patterns — use wildcards (e.g., /blog/*, /product/*) to capture entire page types.
• Language scope — for the Translation Agent, choose which of the 125 languages to enable.
• Aggressiveness level — for rewriting agents, control how much the AI may change headlines, body copy, or CTAs.
• Exclusion rules — prevent the agent from running on specific URLs even if they match the broader pattern.

Changes take effect immediately after you save. No code redeployment is required.

Verification: confirm the agent is live on your page type

1. Open a page that matches your target pattern in an incognito browser window.
2. Check the browser console for the SeaText initialization log — it should show the active agent IDs.
3. If the agent rewrites copy (e.g., Google Ads Agent), click a test ad and verify the headline or CTA changes to match the keyword.
4. In the dashboard, navigate to "Variants Edit" to see the generated variants for that page and language.

If nothing appears after five minutes, re-check your URL pattern and ensure the JavaScript snippet loads on that page.

Common mistake: activating before the snippet is verified

Users often configure agents in the Main AI Hub before the site connection is confirmed. The dashboard will accept the configuration, but the agents will not run because the snippet has not yet linked to your account. Always wait for the website name to appear next to the SeaText logo before setting up page-type activation.

Limitations and when this approach does not apply

• Development domains — localhost and dynamic staging URLs are restricted for security. Use a real domain (e.g., staging.yourdomain.com) with its own SeaText account.
• Single-page applications with client-side routing — the snippet must re-initialize on each route change. If your framework does not trigger a full page load, you may need to call the SeaText initialization function manually after route transitions.
• Pages behind authentication — agents cannot rewrite content they cannot crawl. Public-facing page types work best.
• One account per primary URL — you cannot manage multiple distinct domains from a single dashboard. Each domain needs its own account and snippet.

Key facts

FAQ

Can I activate different agents on blog posts versus product pages?

Yes. In the Main AI Hub, set the target URL pattern for each agent — for example, /blog/* for the AI SEO Content Factory agent and /product/* for the Ecommerce Product Copy Agent.

Do I need to reinstall the snippet when I add a new page type?

No. The snippet is installed once site-wide. You only update the agent configuration in the Main AI Hub to include the new URL pattern.

How quickly do configuration changes take effect?

Immediately after you save in the Main AI Hub. No code deployment or cache clearing is required.

Can I test an agent on a single URL before rolling it out to a whole page type?

Yes. Enter the exact URL in the agent's configuration instead of a wildcard pattern. Once verified, expand to the broader pattern.

What happens if two agents try to rewrite the same element?

Agents operate on different layers (headlines, CTAs, translations, etc.). Conflicts are rare, but you can adjust aggressiveness settings or exclusion rules to prevent overlap.

Is there a limit to how many page types I can configure?

No practical limit. You can create as many URL patterns and agent combinations as your site structure requires.

Can I use SeaText on a staging environment?

Yes, but you must use a real domain (e.g., staging.yourdomain.com) with its own SeaText account. Localhost and dynamic preview URLs are blocked.

What You Need Before You Start

Setting up SeaText AI on a development Odoo domain is a straightforward process, but you need a few things in place first. The most important requirement is a real, accessible domain. SeaText restricts development URLs like localhost for security reasons, and dynamic development domains may not function properly because SeaText might be unable to reliably associate traffic with your account.

You also need a SeaText account. Each SeaText account is linked to a single primary URL. If you want to use SeaText on both a development domain and a production domain, you must create separate accounts for each domain.

Development Setup vs. Production Setup: Key Differences

Understanding the differences between setting up SeaText on a development domain versus a production domain helps you avoid common pitfalls. The table below compares the two approaches.

Who should use the development setup? Teams that need to test SeaText agents, validate integration, or prepare for launch without affecting live traffic. Who should use the production setup? Teams ready to deploy SeaText on their live site to optimize conversions and ad spend.

Practical takeaway: Always use a separate account for each environment. Never reuse a production snippet on a development domain. Check with the vendor for any additional environment-specific requirements.

Step-by-Step Setup Process

Step 1: Create a SeaText Account for Your Development Domain

Go to the SeaText website and create an account. Use the exact development domain you plan to use — not your production domain. This ensures SeaText associates traffic correctly with your development environment.

Step 2: Copy the JavaScript Code Snippet

After logging in, navigate to the integration section of your SeaText dashboard. Copy the JavaScript code snippet provided for your account. This snippet is unique to your account and domain.

Step 3: Log In to Your Odoo Backend

Log in to your Odoo account and access the Website module from the dashboard. This is where you manage your website pages and blocks.

Step 4: Open the Page Editor

Navigate to the page you wish to edit and click the Edit button to open the editing panel. This gives you access to the block-based editor.

Step 5: Add the Embed Code Block

In the editing panel, scroll through the Blocks panel until you reach the Dynamic Content section. Locate the Embed Code module and drag it into the desired location on your website editor.

Step 6: Paste the SeaText Code

Once the module is placed, click the Edit button located in the right panel to input the code. In the pop-up window that appears, paste the code snippet provided by SeaText AI into the designated area, then click Save to apply the changes.

Step 7: Hide the Block on Desktop (Optional but Recommended)

To ensure the block is hidden from view on desktop devices, select the Hide on Desktop option in the Visibility section. After making this adjustment, click Save once more to finalize your changes. This prevents the embed block from appearing as a visible element on your page.

Step 8: Verify the Installation

Visit or refresh your development domain. The SeaText AI script should load silently in the background. The AI remains inert until activated, so you won't see visible changes until you activate the agents you need.

Why a Separate Account for Development Matters

SeaText links each account to a single primary URL. If you try to use the same account on both your development and production domains, SeaText may not associate traffic correctly. This can lead to inaccurate data and broken agent behavior.

Create one account per website. This applies to development domains, staging domains, and production domains. Each gets its own account and its own JavaScript snippet.

How the Setup Works: Mechanics and Trade-offs

When you paste the SeaText JavaScript snippet into Odoo's Embed Code block, the script loads on every page where the block appears. The script communicates with SeaText's servers to associate visitor traffic with your account. This association relies on the domain URL you registered.

The trade-off is clear: you need a stable, real domain. Localhost is blocked because it doesn't resolve publicly, making traffic association unreliable. Dynamic development URLs change frequently, which breaks the association. A stable development domain ensures SeaText can track and optimize correctly.

Another trade-off involves visibility. The Embed Code block can appear as a visible element on your page. Hiding it on desktop keeps your site clean, but you must remember to save the visibility setting. If you skip this step, visitors may see an empty or broken block.

Practical Use Cases for Development Setup

Developers often use SeaText on a development domain to test new agents before launch. For example, you might activate the AI CRO Reading Analysis agent on a staging site to see how it analyzes visitor behavior. This lets you validate the integration without affecting live conversions.

Marketing teams use development setups to preview copy variants. You can test the Google Ads Landing Page AI agent on a development domain to see how it rewrites landing pages for different keywords. This helps you plan campaigns before going live.

Ecommerce teams use development domains to test product copy optimization. You can activate the Ecommerce Product Copy agent on a staging site to see how it improves product descriptions. This ensures the agent works correctly before you deploy it to production.

Limitations and When This Setup Doesn't Apply

This setup guide applies to Odoo's Website module. If you're using a different CMS or a custom-built site, the integration method differs — you'd paste the JavaScript snippet directly into your site's HTML head or body instead.

If your development domain is behind a VPN, requires authentication, or isn't publicly accessible, SeaText may not be able to reach it. Ensure your development domain is publicly accessible over HTTPS.

If you need to test SeaText on multiple development environments, create a separate account for each one. There's no way to share one account across multiple domains.

Dynamic development domains may not function properly. SeaText might be unable to reliably associate traffic with your account. Use a stable domain.

Frequently Asked Questions

Can I use localhost for SeaText on Odoo?

No. SeaText restricts localhost for security reasons. Use a real, valid domain instead.

Do I need a separate SeaText account for my development domain?

Yes. Each SeaText account is linked to a single primary URL. Create a separate account for each domain you want to use.

Will SeaText change my Odoo site immediately after installation?

No. The AI remains inert until you activate the agents. Installation is safe and doesn't alter your content.

What if my development domain changes frequently?

Dynamic development domains may not function properly. SeaText might be unable to reliably associate traffic with your account. Use a stable domain.

How do I hide the Embed Code block from visitors?

In Odoo's editor, select the Hide on Desktop option in the Visibility section of the block settings, then click Save.

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

No. To use SeaText on several websites, create one account for each website.

Learn More and Get Started

Ready to set up SeaText AI on your development Odoo domain? Visit the Odoo Integration page for detailed instructions, pricing, and support. The page includes the exact JavaScript snippet you need and step-by-step guidance for a smooth setup.

For more information about SeaText's AI agents and how they can boost your conversion rate, explore the SeaText homepage. You'll find details on agents like AI CRO Reading Analysis, Google Ads Landing Page AI, and Website Translation.

Start with a free account today and activate the agents that fit your goals. The installation takes less than a minute, and the AI stays inert until you're ready to deploy it.

Set Up SeaText AI on a Development Store in 6 Steps

You can test SeaText AI on a development store, but the setup differs from a live site. The key rule is simple: use a valid, real domain and create a separate account for that domain. Localhost is blocked, and dynamic development URLs may not work reliably.

Here is the exact process, based on SeaText's Shopify integration guide.

Step 1: Create a Dedicated SeaText AI Account

Do not reuse your production account. Each SeaText AI account is linked to a single primary URL. If you need to use SeaText on both a development domain and a production domain, create separate accounts for each.

Go to the SeaText AI signup page and register with the email you use for testing. Use a real domain for the development store, such as dev.yourstore.com or a Shopify development store URL that resolves publicly. Avoid localhost or any URL that changes on every preview.

Step 2: Copy the JavaScript Snippet

After creating your account, log in to SeaText AI. The integration page shows a JavaScript code snippet under the section labeled "SEATEXTCODEINTEGRATION." Copy that entire snippet.

The snippet is inert until you activate agents, so pasting it into your development theme will not alter live content or affect your production store.

Step 3: Open Your Shopify Theme Code

Log in to your Shopify admin for the development store. Navigate to Online Store > Themes. Find the theme you want to test with and click the three dots icon, then select Edit code.

On the Edit Code page, open the Layout folder and locate theme.liquid. This file controls the global structure of every page.

Step 4: Paste the Snippet Before the Closing Head Tag

Paste the SeaText JavaScript snippet into theme.liquid, ideally just before the closing </head> tag. This ensures the script loads on every page of your development store.

Click Save to preserve your changes. The snippet is now installed but inactive until you activate agents in the SeaText dashboard.

Step 5: Activate Agents One at a Time

Return to your SeaText AI dashboard. You will see a list of autonomous agents, such as the CRO Optimizer, Google Ads Landing Page Agent, and AI A/B Testing Agent. Activate only the agents you want to test.

Start with one agent. For example, activate the CRO Optimizer and observe how it behaves on a few product or landing pages. Then activate the next agent. This controlled approach helps you isolate any issues and understand what each agent changes.

Step 6: Verify the Installation

Open a page on your development store in a browser. Use the browser's developer tools to inspect the HTML source. Confirm that the SeaText script tag is present in the <head> section.

Then check the SeaText dashboard. It should show your development domain as connected. If the dashboard does not recognize the domain, re-check that you used a real, stable URL and that the snippet was saved correctly.

What Counts as a Valid Development Domain

SeaText restricts localhost for security reasons. Dynamic development domains, such as those that change on every preview or use temporary subdomains, may not function properly because SeaText cannot reliably associate traffic with your account.

Use a stable, publicly resolvable domain for testing. A Shopify development store with a permanent .myshopify.com URL or a custom development subdomain like dev.yourbrand.com works better than a local tunnel or preview link that expires.

Common Mistake: Reusing the Production Account

The most frequent setup error is using the same SeaText account for both development and production. Because each account is tied to one primary URL, the dashboard will not correctly track or optimize a second domain. You may see agents fail silently or traffic data attributed to the wrong site.

Always create a separate account for the development store. This also keeps your test data separate from live performance metrics.

What You Can and Cannot Test on a Development Store

A development store is ideal for testing installation, agent activation, and basic content changes. You can verify that the snippet loads, agents appear in the dashboard, and copy rewrites work on sample pages.

However, features that depend on real visitor traffic will not produce meaningful results. For example, the AI CRO Reading Analysis Agent analyzes visitor reading behavior, and the Bot Protection Agent detects invalid clicks in paid traffic. Without real visitors or ad campaigns, these agents have no data to process. Use the development store to confirm technical setup, then move to a live or staging environment with real traffic for performance testing.

Key Facts About SeaText AI Development Store Setup

How to Verify Each Step Before Moving On

After each step, perform a quick check to avoid compounding errors.

• After account creation: Confirm the dashboard shows your development domain as the primary URL.
• After pasting the snippet: Save the theme file and reload a page. Check the page source for the SeaText script tag.
• After activating an agent: Visit a test page and look for the expected change, such as a rewritten headline or CTA.
• After testing: Deactivate agents you do not want running on the development store.

When This Setup Does Not Apply

This guide assumes you are using a Shopify store with access to theme code. If you are on a platform that does not allow custom JavaScript in the head, you may need a different installation method. SeaText's documentation focuses on Shopify integration, so check with SeaText support for other platforms.

Also, if your development store is only accessible via localhost or a password-protected preview that changes URLs, SeaText may not work at all. In that case, use a staging subdomain on a real domain instead.

Frequently Asked Questions

Can I use the same SeaText account for development and production?

No. Each SeaText AI account is linked to a single primary URL. Create separate accounts for each domain to avoid tracking and optimization errors.

Why does SeaText block localhost?

SeaText restricts localhost for security reasons. The platform needs a valid, real domain to reliably associate traffic and activity with your account.

Do I need to pay for a development store account?

SeaText offers a free 1-month pilot trial, which you can use on a development store. Check the pricing page for current terms and any limitations on premium features.

Which agents should I test first on a development store?

Start with agents that change on-page content, such as the CRO Optimizer or Ecommerce Product Copy Agent. These show visible results without needing real traffic. Save traffic-dependent agents like Bot Protection for a live environment.

How do I know the snippet is installed correctly?

Open your development store in a browser, right-click and select "View Page Source," then search for the SeaText script tag. You can also check the SeaText dashboard for a connected domain status.

What if my development URL changes on every preview?

Dynamic development domains may not function properly with SeaText. Use a stable subdomain or a permanent development store URL instead.

Can I test the Google Ads agent without running ads?

You can activate the agent and verify it loads, but it will not rewrite pages meaningfully without real ad clicks and keyword data. Use a staging environment with test campaigns for a more realistic test.

Adding SeaText AI to Additional Webflow Domains

Integrating SeaText AI with multiple Webflow domains is straightforward. Each domain requires its own distinct SeaText account to maintain security, isolate data, and ensure accurate tracking. This guide walks you through the process of adding a second, third, or subsequent Webflow site to your existing SeaText setup.

Prerequisites for Adding a New Domain

Before you begin adding SeaText AI to a new Webflow domain, ensure you have the following in place:

• An Active SeaText Account: You should already have an account with SeaText. If not, you'll need to create one first.
• A Webflow Site Plan: Accessing custom code in Webflow requires an active Site plan. Make sure your new Webflow project has this enabled.
• A Valid Domain: Development URLs like localhost are restricted. Use a real, valid domain for your Webflow site. Dynamic development domains may also cause issues with SeaText's ability to associate traffic with your account.

Step-by-Step Integration Process

Follow these steps to integrate SeaText AI with your new Webflow domain:

1. Create a New Site in the SeaText Dashboard

Log in to your SeaText dashboard. Navigate to the section for managing your websites or domains. Look for an option to 'Add New Site' or 'Create New Account' for a new domain. Follow the prompts to set up a new entry specifically for your additional Webflow domain. Each new site entry will generate a unique embed code.

2. Copy the SeaText Embed Snippet

Once your new site is created in the SeaText dashboard, you will be presented with a unique JavaScript embed snippet. This code is specific to the new domain you just added. There will be a clear button or link to copy this code to your clipboard.

3. Access Custom Code in Webflow

Go to your Webflow dashboard and select the specific Webflow project for the new domain you are integrating. Click on the three dots next to your project name and select 'Settings'. Within the project settings, navigate to the 'Custom Code' tab, which is typically found on the far right.

4. Paste the Embed Snippet into Webflow

In the 'Custom Code' section of your Webflow project settings, you'll find fields for adding code to the or of your site. Paste the SeaText embed snippet you copied into the appropriate section, usually the tag, as instructed by SeaText.

5. Publish Your Webflow Site

After pasting the code, save your changes in the Webflow project settings. Then, publish your Webflow site by clicking the blue 'Publish' button, usually located in the top right corner of the Webflow designer or dashboard. This action makes your site live with the SeaText integration.

6. Activate and Verify the SeaText AI

Important: After publishing, you need to activate the SeaText AI. Visit your newly updated website and stay on the page for at least 40 seconds. Refresh the page a few times. This action helps SeaText recognize and link the traffic to your new account. Within five minutes, you should see your website name appear next to the SeaText logo at the top of your SeaText dashboard. If it doesn't appear after 10 minutes, contact SeaText support.

Understanding Multiple Domain Requirements

SeaText AI is designed to work on a per-domain basis. This means that if you manage multiple websites, whether they are for different clients, different stages of development (like staging and production), or simply different projects, each one needs its own dedicated SeaText account and integration. This separation is crucial for several reasons:

• Data Isolation: Each account ensures that data collected and analyzed by SeaText for one website does not interfere with or get mixed with data from another. This is vital for accurate reporting and analysis.
• Security: Linking a specific account to a primary URL enhances security. It prevents unauthorized access or accidental integration with the wrong site.
• Accurate Tracking: SeaText relies on associating website traffic with specific accounts. Having separate accounts for each domain ensures that traffic is correctly attributed and processed for the intended website.

Attempting to use a single SeaText embed code across multiple domains will not work as intended and will likely lead to data not being recorded or being incorrectly attributed.

Common Mistakes to Avoid

When setting up SeaText AI on multiple Webflow domains, a common pitfall is attempting to use the same embed code for all sites. Each domain requires a unique code generated from a separate site entry in your SeaText dashboard. Another mistake is forgetting to publish the Webflow site after adding the custom code, which means the integration will not be active.

Verifying the Integration

After completing the steps, verification is key. First, check your SeaText dashboard. You should see your new website listed next to the SeaText logo within 5-10 minutes of activating the AI on your site. If your website name appears, the integration is likely successful. You can also test by navigating your website and observing if SeaText's functionalities begin to appear or if data starts populating in your SeaText analytics. If you encounter issues, re-check the custom code placement in Webflow and ensure the site has been published.

Key Facts about SeaText AI and Webflow Integration

Limitations and Considerations

SeaText AI's multi-domain functionality is built on a per-account, per-domain model. This means that while you can manage many sites, each one is treated as an independent entity within your SeaText account structure. Development domains, such as localhost, are explicitly restricted for security reasons. If you use dynamic development domains, SeaText may not be able to reliably associate traffic with your account, potentially leading to integration issues. Always ensure you are using a valid, live domain for your Webflow projects when integrating SeaText.

Frequently Asked Questions

Can I use the same SeaText embed code on multiple Webflow sites?

No, you cannot use the same embed code. Each Webflow domain requires a unique SeaText account and its corresponding embed snippet to ensure proper functionality, data isolation, and security.

What happens if I don't have a Webflow Site plan?

Without an active Webflow Site plan, you will not have access to the 'Custom Code' section in your project settings. This prevents you from pasting the SeaText embed snippet, and therefore, you cannot integrate SeaText AI into your site.

How long does it take for SeaText AI to recognize a new domain?

After publishing your Webflow site and visiting it for at least 40 seconds, SeaText AI should recognize the new domain and display it in your dashboard within 5 to 10 minutes. If it takes longer, contact SeaText support.

Are there any costs associated with adding more Webflow domains?

The cost is tied to your SeaText plan, which may have limits on the number of domains you can manage. Adding more domains might require upgrading your SeaText plan if you exceed the limits of your current subscription. Check your specific SeaText plan details for domain allowances.

What should I do if my website name doesn't appear in the SeaText dashboard after 10 minutes?

If your website name does not appear in the SeaText dashboard after 10 minutes, it indicates a potential issue with the installation. Please contact SeaText support immediately for assistance.

Learn more about this service

See how this page can help with your next step.

Learn more

How to Set Up SeaText AI on a Staging Domain for Testing

What You Need Before You Start

You need a SeaText AI account. Create one if you haven’t already. You also need admin access to your Shopify store. Basic familiarity with Shopify’s theme editor helps. Each domain requires its own SeaText account. Do not use localhost or development URLs. Those are restricted for security reasons. Use a valid, real domain. The AI remains inert until you complete the setup. This ensures your site content stays intact.

Step‑by‑Step Integration

1. Copy the SeaText JavaScript code. In your SeaText dashboard, locate the integration snippet. Copy it exactly. Excerpt: "Copy the Javascript code from SEATEXT AI which appear in this section below."
2. Paste the script into your theme. In Shopify admin, go to Online Store → Themes → Actions → Edit code for the active theme. Open the theme.liquid file in the Layout folder. Paste the script just before the closing </head> tag. Do not place it in the body tag. The script must load early.
3. Identify the product description file. Usually it is product.liquid or a section named product-template.liquid. Open that file.
4. Wrap the description output with the SeaText tag. Replace the existing output line (e.g., {{ product.description }}) with:

   <div data-seatext="product-description">{{ product.description }}</div>

   Excerpt: "Implement the Tag in Your Product Descriptions To optimize your product descriptions effectively, please follow these steps: Step 1: Access Your Shopify Theme Code [...] Step 2: Locate the Product Template [...] Step 3: Wrap the Product Description [...]"
5. Save the changes. Click the Save button in the editor.

After saving, the AI is ready to generate copy. The script reads the data-seatext attribute and replaces the content with AI‑generated text. It does not modify your original Liquid code. The original description remains in the template.

How the data-seatext Attribute Works with Shopify Liquid

Shopify Liquid renders the product description as HTML. The data-seatext attribute is a custom HTML attribute. It does not interfere with Liquid. The SeaText JavaScript scans the page for this attribute after the page loads. It then sends the content to the AI for processing. The AI generates new copy and replaces the inner HTML of the div. The attribute must be present in the HTML source. You can verify this using browser developer tools. The AI remains inert until it finds the attribute. This means it does not affect performance on pages without the tag. The tag can be used on other elements, not just product descriptions. For example, you can add it to a section to optimize a headline. The attribute value (e.g., "product-description") tells the AI which type of content to generate. This helps the AI produce context‑appropriate copy.

Troubleshooting Common Integration Conflicts

Other Shopify apps may modify the product description. For example, SEO apps often add meta tags or rewrite content. Translation apps may wrap the description in a different element. These changes can break the SeaText tag. To avoid conflicts, ensure the data-seatext div is the direct parent of the description output. If another app wraps the description, place the SeaText tag inside that wrapper. You may need to adjust the order of app scripts. Also check that no other script removes the data-seatext attribute. Common conflicts arise with lazy‑loading scripts. They may defer the description rendering. SeaText expects the attribute to be present on page load. If the description is loaded asynchronously, the AI may not find it. Use the data-seatext attribute on a static placeholder. Then update the placeholder with the actual description. Test your store after installing any new app. If the SeaText tag stops working, inspect the HTML source. Look for the attribute. If missing, re‑edit the template. Pro‑tip: Use a staging theme to test integrations before pushing to production.

Best Practices for Managing AI‑Generated vs Manual Descriptions

SeaText AI adds suggestions on top of your original description. It does not overwrite your manual copy. You can accept or edit the AI output. This gives you control. For best results, write a clear, concise manual description first. The AI uses that as a base. It enhances the copy with persuasive language and keywords. Avoid writing very short descriptions. The AI needs context to generate relevant content. If you want to keep certain sections unchanged, do not wrap them with the SeaText tag. Use the tag only on the part you want optimized. For example, wrap only the main description, not the specifications. You can also use multiple tags per page. Each tag will be processed independently. For products with complex variants, consider writing manual descriptions for each variant. The AI cannot generate variant‑specific logic. It sees the same description for all variants. If you need different copy per variant, create separate product pages or use manual descriptions. Pro‑tip: Review AI‑generated descriptions before publishing. Check for accuracy and brand voice. Make edits as needed.

Monitoring Performance Impact After Script Implementation

The SeaText script is lightweight. It loads asynchronously after the page is ready. This minimizes impact on page load speed. However, you should still monitor performance. Use Shopify’s built‑in performance reports. Check page load time before and after installation. Use Chrome DevTools to measure the script’s loading time. Open the Network tab and reload the product page. Look for the SeaText script. It should load in under 100ms. If the script delays rendering, check if it is placed correctly. The script must be in the head section. This allows it to load early. But it should not block other resources. The AI processing happens after the page renders. So the user sees the original description first. Then the AI replaces it. This can cause a brief flash of original content. This is normal. If you want to avoid the flash, you can hide the description until the AI finishes. Use a CSS class that hides the element initially. Then show it after the AI updates it. Pro‑tip: Run a Lighthouse performance test. Aim for a score of 90 or above. The script should not degrade your score.

Limitations of SeaText AI for Product Descriptions

SeaText AI cannot handle complex variant‑specific logic. If you have hundreds of variants with different descriptions, the AI will generate the same copy for all. You must manually create per‑variant descriptions. The AI also cannot generate images, videos, or other media. It only works with text. It may not understand niche industry jargon without training. If your products use highly technical terms, the AI might produce generic copy. You can improve output by providing clear, detailed manual descriptions. The AI requires a valid domain. It will not work on localhost or development URLs. Each domain needs its own SeaText account. The AI only works on pages where the data-seatext attribute is present. It does not affect other pages. The AI cannot integrate with third‑party inventory systems or ERP. It is a front‑end tool. It does not update your Shopify admin or backend. The AI does not generate meta descriptions, titles, or alt text. You must add separate tags for those. The AI may occasionally produce incorrect or off‑brand copy. Always review before publishing. It is not a replacement for human oversight. Pro‑tip: Use the AI as a starting point. Edit and refine the output to match your brand standards.

FAQ

• Do I need a developer? No, the steps use Shopify’s built‑in code editor and require only basic HTML knowledge.
• Will SeaText overwrite my existing copy? It adds AI‑generated suggestions on top of the original description; you can accept or edit them.
• Can I use the same account on multiple stores? Each domain needs its own SeaText AI account, as noted in the integration guide.
• Is there an extra cost for product description generation? The feature is included in your SeaText subscription; see the pricing page for details.
• Can I use the same tag on multiple product templates? Yes, you can add the tag to any template that renders the description. It works on all product pages.
• Does SeaText work with Shopify’s Online Store 2.0? Yes, it works with both classic and Online Store 2.0 themes. The steps are the same.
• What happens if I remove the tag? The AI will stop generating descriptions for that product. The original description will display as normal.
• How do I exclude certain products? Do not add the data-seatext tag to those products. The AI only processes pages with the tag.
• Can I use SeaText with a custom development theme? Yes, as long as you can edit the theme code. The same integration steps apply.

Running SeaText on multiple Thinkific sites is not a separate product. It is the same integration repeated on each school you own. Each Thinkific site gets its own JavaScript snippet, its own connection to your SeaText account, and its own AI settings.

This guide walks through the full process, from prerequisites to activation. You will learn how to add a second or third Thinkific site without breaking the first one.

Why separate Thinkific sites need separate integrations

Thinkific treats each school as an independent website. If you run two schools, each has its own admin dashboard, its own domain, and its own page code.

SeaText also treats each website as a separate integration. One snippet cannot be reused across two domains. The AI agents, translations, and variants must know which site they belong to.

This matters for tracking. If both schools shared one snippet, sessions from School A and School B would mix in the same dashboard. You would not know which school produced a lead, a bot click, or a sale.

The correct approach is simple: generate a new snippet for each site, paste it only into that site, and connect each domain separately.

How SeaText connects to Thinkific

SeaText connects through JavaScript, not a Thinkific app installation. You place the snippet in the Site Footer Code of each Thinkific theme. This snippet loads on every page that uses the theme.

When a visitor opens a page, SeaText reads the page context in the browser. It can rewrite headlines, buttons, offers, and product copy before the page finishes painting. That is why the snippet must be unique per site; the script needs to know which site it is working on.

The connection is confirmed by a human visit. This visit proves the snippet is installed and that the domain resolves to your Thinkific school. The 40-second dwell time gives SeaText enough time to record the session and link it to your account.

Once the link is active, SeaText agents can perform their work. Without this activation step, the snippet may be installed but the site will not appear in your dashboard.

Prerequisites before you start

• Admin access to every Thinkific site you want to connect.
• A SeaText account with an active subscription that allows multiple websites. Check your plan limits before adding more sites.
• A list of each site's public address in the format www.example.com.
• A real browser on a desktop or mobile device for the 40-second activation visit.

You should also decide which AI agents each school needs. A course business may want translation and bot protection. A lead-generation school may want the Google Ads Landing Page Agent first. You can change this later.

Step-by-step: add a second or third Thinkific site

1. Open SeaText and go to Integrations → Thinkific → Add New Site. Copy the JavaScript code shown for the new site. This snippet is unique to that site.
2. Log in to the target Thinkific school's Admin Dashboard. Navigate to Settings → Code & Analytics tab.
3. Paste the snippet into the Site Footer Code field. Click Save. Do not paste it into any other code field.
4. Return to SeaText and add the site address using the website form. Use the full domain, for example www.example.com, without http:// or a trailing slash.
5. Visit the live Thinkific site once and stay on the page for at least 40 seconds. This activates the AI and links the site to your SeaText account.
6. Wait at least five minutes. The site name should appear next to the SeaText logo at the top of the SeaText page. This confirms the connection.
7. If the site does not appear after 10 minutes, contact SeaText support. An issue during installation may need their help.
8. Repeat steps 1 through 7 for every additional Thinkific site.

The order above is important. If you paste the snippet before adding the site address in SeaText, the activation visit still works but the dashboard may show a confusing status. Follow the order to keep things clean.

After connection: activate AI agents per site

Once a site shows in your dashboard, go to the Main AI Hub. This is where you choose which AI agents run on that site.

Each agent works independently on each connected site. For example, you can turn on the Translation Agent for a French-language school and leave it off for your English-only school.

• Google Ads Landing Page Agent: rewrites landing page copy to match paid search intent.
• Translation Agent: creates localized versions in up to 125 languages from your existing page context.
• Bot Protection Agent: detects bot clicks and builds refund-ready reports for Google, Meta, TikTok, or Reddit.
• AI A/B Testing Agent: generates variants and scales the winners.

Click Configuration on each agent to adjust its parameters for the selected site. Do not assume settings from Site A will carry over to Site B; per-site configuration is intentional.

Manage settings per site: variants, languages, and tests

After activating an agent, SeaText may generate an initial round of automatic translations and variants. You can review and edit them manually.

Log in to SeaText and choose Variants Edit in the left panel. Select the site URL and language you want to edit. Use this screen to review, create, or manually edit translations and variants for that school only.

This per-site editing is useful when two schools target different audiences. School A may sell courses to beginners and needs simple wording. School B may sell advanced training and needs more technical terms. You can keep both message styles separate.

A/B tests are also scoped to the selected site. A winner in School A does not automatically replace copy in School B. This prevents one experiment from changing content across all your properties.

Practical scenarios for two or more Thinkific schools

Scenario 1: you run an English school and a Spanish school. Connect both sites, then activate the Translation Agent on the Spanish school with Spanish as the target language. On the English school you may not need translation at all. Per-site configuration lets each school meet its market.

Scenario 2: you run a course business and a coaching business. The course school needs the AI A/B Testing Agent and the Translation Agent. The coaching school needs the Google Ads Landing Page Agent and Bot Protection Agent because it spends heavily on paid traffic. Each school gets its own stack, its own reports, and its own test history.

Scenario 3: you are an agency managing Thinkific sites for clients. You may want the same agent setup across all sites. Even then, you must add each client site separately and activate agents manually. That protects each client's data and keeps reports clean.

Verification checklist

• View the live page source and confirm the SeaText snippet is present in the Site Footer Code.
• In SeaText, confirm the site name appears next to the SeaText logo after 5 to 10 minutes.
• Open the Main AI Hub and confirm agents show Active status for that site.
• Run a test visit: open the site in an incognito window, stay for 40 seconds, then check the SeaText dashboard for a recorded session.
• Repeat the checklist for each Thinkific site you added.

Common mistakes and troubleshooting

• Copying the same snippet to multiple sites. This is the most common error. Generate a fresh snippet per domain through Add New Site.
• Pasting the snippet into the wrong code field. Thinkific has several code areas. Use Site Footer Code only.
• Using an automated bot to visit the site. The 40-second activation visit must be a real browser session. Curl or wget will not trigger the link.
• Checking the dashboard too early. Wait at least five minutes after the visit. If nothing appears after 10 minutes, contact support.
• Forgetting to select the correct site in the dashboard. When you edit settings, always check the site selector at the top of the page.

If the site still does not connect, a content security policy or a caching plugin may block the script. Ask SeaText support for help; they see integration failures regularly.

Limitations and when this advice does not apply

• Thinkific requires a separate paid plan for each school. SeaText cannot bypass that requirement.
• If your SeaText plan caps the number of connected websites, upgrade before adding more sites.
• Subdirectory or subdomain setups still count as separate sites when they have distinct Thinkific admin dashboards.
• The integration only works on sites where you can edit the Site Footer Code. Thinkific sites without admin access cannot be connected.
• If you only have one Thinkific site, you do not need the multi-site steps. Just follow the single-site integration from the start of this guide.

Frequently asked questions

Can I use one SeaText snippet for multiple Thinkific sites?

No. Each Thinkific site needs its own snippet generated through Add New Site.

Do I need a separate SeaText subscription for each Thinkific school?

Not necessarily. One SeaText account can manage multiple sites if your plan allows it. Check your plan's website limit before adding a school.

What if the site name never appears next to the SeaText logo?

Wait 10 minutes, then contact SeaText support. The snippet may be blocked by Thinkific's Content Security Policy or placed in the wrong code field.

Can I activate different AI agents on different Thinkific sites?

Yes. In the Main AI Hub, select the site first, then enable or disable agents per site.

Does SeaText translate each Thinkific site into 125 languages automatically?

The Translation Agent can be activated per site. It translates pages into up to 125 languages using your existing page context, but you must enable it for each site individually.

Will SeaText bot detection work across all my Thinkific sites?

Yes. The Bot Protection Agent runs per connected site and builds refund-ready reports for Google, Meta, TikTok, or Reddit for each school's paid traffic.

How do I edit variants for one Thinkific site without affecting another?

Go to Variants Edit in the left panel, choose the site URL and language, then edit that school's content. Changes stay within the selected site.

Prerequisites

Before you begin, you need a SeaText AI account. Each SeaText account is linked to a single primary URL. This design isolates analytics, translations, and AI personalization per domain. If you share an account across domains, visitor data mixes and the AI cannot learn distinct patterns for each site. Security restrictions block localhost and dynamic preview URLs because they cannot be verified as stable, public endpoints. SeaText requires a valid, real domain (for example, dev.example.com) to associate traffic consistently with your account. Dynamic development domains may not function reliably because the domain changes per session, breaking the link between visits and your account.

Step-by-step installation

1. Create a SeaText account for the development domain. Sign up at SeaText and register the exact development domain you will use.
2. Copy the JavaScript snippet. In your SeaText dashboard, locate the integration code for the new account.
3. Open Squarespace settings. From the Squarespace dashboard, click the three-dot icon next to your site and select Settings.
4. Navigate to Developer Tools. Scroll to the very end of the settings page and click Developer Tools.
5. Open Code Injection. Click Code Injection to access the header and footer fields.
6. Paste the snippet into the Header field. Place the SeaText JavaScript code in the HEADER area. The header loads before page content, ensuring the script initializes early and can rewrite text before the visitor sees it. Footer injection runs after the DOM is built, which delays activation and may cause flicker.
7. Save and publish. Click Save, then ensure the site is published so the script loads on the live development domain. Squarespace's template rendering injects the header code into every page's <head> tag during server-side rendering, so the script is present on first paint.

Development domain considerations

SeaText treats each domain as a separate account. If you run a staging subdomain and a production domain, you will manage two accounts. This isolation keeps analytics, translations, and AI variants separate. However, dynamic preview URLs (like Squarespace's built-in preview links) may not work because the domain changes per session. Use a fixed subdomain mapped in Squarespace's domain settings for reliable tracking. Local development environments such as localhost or 127.0.0.1 are blocked for security reasons. SeaText cannot verify ownership of non-public addresses. To test AI features securely before going live, set up a password-protected staging subdomain (e.g., staging.example.com) with basic auth or IP allowlisting. This gives you a real, public DNS name that SeaText can recognize while keeping the site private.

Activation and verification

After publishing, visit the development domain several times and stay on a page for at least 40 seconds. This activity activates the AI and links the domain to your SeaText account. The 40-second threshold ensures the visit is genuine human engagement, not a bot or health check. SeaText's backend then processes the visit, associates the domain with your account, and propagates the connection across its edge network. This propagation takes 5 to 10 minutes because the system must update distributed caches and confirm the domain's DNS resolution. Immediate verification is not possible because the activation pipeline is asynchronous. In your SeaText dashboard, the development domain name should appear next to the SeaText logo at the top of the page. If it does not appear after 10 minutes, contact SeaText support — this usually indicates an installation issue on the platform.

Common mistakes

• Pasting into the Footer instead of the Header. The script must load early; the Header field ensures it runs before page content.
• Forgetting to publish. Changes in Code Injection only take effect after you publish the site.
• Using a single account for multiple domains. Each domain needs its own account; sharing an account breaks tracking and AI personalization.
• Testing on localhost or dynamic preview URLs. These are blocked or unreliable; use a real, static subdomain.
• Script not loading due to caching. If changes do not appear, clear Squarespace's cache by republishing, or open the page in an incognito window. Use browser developer tools (Network tab) to verify the SeaText script loads with a 200 status. Look for the script URL containing your account ID.
• Ad blockers or privacy extensions blocking the script. Test with extensions disabled to rule out interference.

Trade-offs and Workflow Integration

Running separate SeaText accounts for development and production adds operational overhead. You must manage two dashboards, two sets of AI variants, and two translation memories. However, this separation prevents test data from polluting production analytics. During deployment, coordinate by promoting validated AI variants from the development account to the production account manually or via SeaText's export/import features. Teams should document which variants are approved for production. Use a staging subdomain that mirrors production traffic patterns (e.g., same UTM parameters) so the AI learns realistic behavior. When moving to production, create the production account, install the script on the live domain, and repeat the activation steps. Treat the development account as a sandbox: experiment with aggressive personalization, new languages, or radical copy rewrites without risking live revenue.

Key facts

Limitations

SeaText cannot be installed on Squarespace's internal preview links or local development environments. The script relies on a stable, publicly resolvable domain to associate traffic. If your workflow uses ephemeral preview URLs, set up a permanent staging subdomain instead. Also, the AI remains inert until activated by real visits; automated crawlers or health checks may not trigger activation.

FAQ

Can I use the same SeaText account for my production and development sites?

No. Each SeaText account is linked to a single primary URL. You must create a separate account for each domain.

Why is my development domain not showing in the SeaText dashboard after 10 minutes?

Either the script is not loading (check Header placement and publish status), the domain is not a valid public URL, or the activation visits were too brief. Contact support with your account and domain details.

Does SeaText work on Squarespace's free trial sites with built-in domains?

Yes, as long as the domain is a real, public URL (e.g., your-site.squarespace.com). The same account-per-domain rule applies.

Can I install SeaText via Google Tag Manager instead of Code Injection?

The official integration uses Code Injection. GTM may work but is not documented; SeaText support recommends the native Header injection for reliability.

What happens if I change the development domain later?

You will need a new SeaText account for the new domain. Update the script in Code Injection accordingly.

Is there a way to test SeaText without a public domain?

No. Security restrictions block localhost and non-public URLs. Use a password-protected staging subdomain if you need privacy.

Learn more about this service

See how this page can help with your next step.

Learn more

How to Set Up SeaText on Your Ecommerce Site

To set up SEATEXT on WP Engine, visit the official SEATEXT installation page and choose WP Engine from the platform list. The page gives you a code snippet to copy and paste into your WP Engine site. That's it — the entire process typically takes less than a minute, and you don't need to edit files or write code.

SEATEXT works with WP Engine because it's a simple snippet that you add once. From there, you can activate the scripts and agents you need (like the CRO Optimizer or Bot Refund Agent) from your SEATEXT dashboard. The instructions on the installation page are platform-specific, so use them exactly.

Prerequisites for Installing SEATEXT on WP Engine

Before you begin, you need two things:

• A WP Engine hosted WordPress site where you have admin/owner access.
• A SEATEXT account (free to start – you can sign up from the same page).

If you have access to the WP Engine dashboard and your site is live, you're ready. You don't need to install a separate plugin, but if you prefer installing plugins, check the simple wp Engine code instead—WP Engine is a managed host that lets you add code in specific places, like the theme header or via a third-party code snippet plugin.

Step-by-Step Installation for WP Engine

1. Go to SEATEXT's installation page. (You can find the direct link in the menu on SEATEXT's homepage – it's the “Select your platform to start” option.)
2. On the page, scroll to the platform list and click WP Engine.
3. Copy the code shown. The code is a small ...snippet, usually JavaScript.
4. In your WP Engine site, go to your theme's header (or use a code plugin). Paste the snippet before the footer.
5. Check the page by viewing the source to confirm the snippet appears. If the snippet loads correctly, you're ready to activate SEATEXT from the dashboard.

This process matches SEATEXT's official guidance: after the snippet is installed, you can select which pages to activate and choose the agents you want.

What to Do After the Snippet Is Installed

Once your snippet is live, log in to your SEATEXT dashboard. You'll usually see a notification that the installation works, and you can begin choosing the tools you want to run. SEATEXT offers several agents – each one handles a different part of site optimization. For example:

• CRO Optimizer – matches headlines and offers to visitor keywords.
• Bot Refund Agent – identifies invalid clicks and can generate refund evidence for Google/Meta.
• Website Translation Agent – translates your site into 125 languages.
• Visite Source Adaptation Agent – sends visitors to the best page for their source.

As soon as the snippet is active, the agents can start improving your conversion rate. There's no need to wait for a manual project or to create separate landing pages.

How to Check the Installation Is Working

After you add the snippet, do a quick check: open your homepage in a new incognito window, and look at the page source (Ctrl+U) to confirm the code appears before the tag. Also go to your SEATEXT dashboard – the “Plugins” or “Installation” section should show that your site is registered. If you don't see it, re‐check whether you copied the full code and placed it in the right location.

One common mistake: pasting the code into a category or a single post by mistake. The snippet must be added site‐wide, so place it in your theme's header.php or a global code plugin, not inside page content.

Key Facts About SEATEXT as a Tool

These are taken from the official SEATEXT site (version 1). Actual performance varies, and the “+35% more leads” type claims are based on SEATEXT’s own client data, not a guarantee.

Limitations and When This Advice Doesn't Apply

This direct setup works for most WP Engine users. If you're using a heavy caching setup, page builder, or a security plugin that blocks scripts, you might need to clear the cache or whitelist the SEATEXT script. Also, if you have a multisite network or a fully custom theme with severe code restrictions, you should still follow the official steps on Installation page; those cases may require extra steps.

SEATEXT requires a visible snippet – you cannot avoid adding some code. If you want a pure no-code alternative, SEATEXT's own plugin for WordPress also works, but for WP Engine it's at the same installation page.

Terminology You'll See in the Installation Steps

Snippet – the small JavaScript code you copy and paste into your site.
Agents – the autonomous AI functions you activate after installation, each focused on a specific growth metric.
Activation – the switch that turns on an agent. You choose one, set keywords or campaigns, and then SEATEXT start optimizing that area.

No need to memorize terms – you'll see them in the dashboard, and the Help button gives you a guide on “Get help with ChatGPT” if you ever get stuck.

Frequently Asked Questions

Does SEATEXT work on WP Engine if I have a plugin that caches my site?

Caching plugins are common on WP Engine, and they can hide your changes. After adding the snippet, clear the cache from your caching plugin. Some users also need to turn on “script delay defer” – if your script doesn't load properly, it's usually a cache issue.

Do I need to change the theme to add the code?

No. You can use WP Engine's built-in “Code Snippets” plugin or a custom code plugin to add the snippet to the header, without editing your theme files directly.

How long does the installation take?

We see from SEATEXT’s homepage that it takes “under 1 minute.” And the SDK says“No programming is needed after the snippet is installed.” So expect around 1–2 minutes once you follow the platform's steps.

Is SEATEXT free to install on WP Engine?

The installation itself is free – you can add the snippet and see the dashboard. Some agents have free tiers (e.g., Website Translation Agent is free), while others are paid based on your activity. The pricing link on SEATEXT's site tells you the current plans.

What if I already use a caching plugin like WP Rocket?

WP Rocket or LiteSpeed may combine or delay the script. Add SEATEXT to the “Delay JS” and add “EL EXCLUDE” from the speed optimization to make sure the code runs instantly. SEATEXT works with all WordPress caching tools that allow you exclude specific scripts.

Can I undo the installation if I change my mind?

Yes. Remove the snippet from your theme header or plugin and refresh the cache. From the SEATEXT dashboard, you can manually remove the site connection.

Wrap-Up

Setting up SEATEXT on WP Engine doesn't involve any tricky developer work. Open the official installation page, pick WP Engine, copy the snippet, paste it into your site, and switch on the AI agents you need. You can see the final result within a day or two in your conversion metrics.

Start by creating a separate GA4 data stream or view for each language version of your site. Add hreflang annotations so search engines serve the right language to each user. Tag every language switcher link with UTM parameters (for example, utm_source=language_switcher&utm_medium=internal&utm_campaign=lang_switch) so you can see which language a visitor chose. Enable enhanced e-commerce for each locale and send purchase events with a language parameter. Finally, build a custom exploration in GA4 that groups sessions, conversions, and revenue by the language dimension, then import your translation cost data (per word, per project, or per month) to calculate net profit per language.

Prerequisites before you begin

You need editor access to your GA4 property and Google Tag Manager container. Your site must already serve translated pages — either on subdirectories (/de/, /fr/), subdomains (de.example.com), or separate ccTLDs. You also need a list of every language you support and the corresponding URL pattern. If you use SeaText's Website Translation Agent, it publishes translated pages under language subdirectories automatically and injects the lang attribute on the <html> tag, which makes the next steps easier.

Step 1: Create language-specific GA4 views

In GA4, go to Admin > Data Streams. If you use subdirectories, keep one web stream and use a custom dimension for language. If you use subdomains or ccTLDs, create a separate web stream for each. Then create a custom dimension named page_language (event scope) that pulls the language code from the URL or the lang attribute. In GTM, add a Data Layer Variable that reads document.documentElement.lang or parses the first path segment. Attach this variable to every GA4 event tag as the page_language parameter.

Step 2: Implement hreflang annotations

Add <link rel="alternate" hreflang="x" href="..." /> tags in the <head> of every page, including a self-referencing tag and an x-default fallback. SeaText's Translation Agent inserts these automatically when it publishes a new language. Verify with Google's Search Console International Targeting report or the hreflang checker in Screaming Frog. Missing or incorrect hreflang tags cause search engines to show the wrong language, which pollutes your ROI data because visitors land on a page they cannot read.

Step 3: Tag language switchers with UTM parameters

Every link that changes the site language — whether a dropdown, flag icon, or text link — must carry UTM parameters. Example: /de/product?utm_source=language_switcher&utm_medium=internal&utm_campaign=lang_switch&utm_content=de. In GTM, create a Click Trigger that fires on the switcher's CSS selector, then a GA4 Event tag named language_switch with parameters target_language and switcher_location (header, footer, product page). This lets you see how often visitors switch languages and whether they convert after switching.

Step 4: Configure per-locale e-commerce tracking

Enable enhanced e-commerce in GA4. For each purchase event, include currency (ISO 4217), value, and a custom language parameter that matches your page_language dimension. If you use SeaText's Conversion Relay (CAPI), it forwards 100% of real purchases to Meta and Google CAPI with the same language parameter, so your ad platforms can optimize for buyers in each language. Test with GA4 DebugView: trigger a test purchase on a translated page and confirm language=de (or your test language) appears in the event parameters.

Step 5: Build custom reports by language

In GA4 > Explore, create a Free Form exploration. Rows: page_language. Columns: Sessions, Users, Engagement Rate, Conversions, Purchase Revenue, Average Purchase Revenue. Add a filter for the date range you want to analyze. Export to Google Sheets monthly. In Sheets, add a column for translation cost per language (from your vendor invoices or SeaText's usage dashboard). Calculate: Net Profit = Purchase Revenue - Translation Cost; ROI = (Net Profit / Translation Cost) * 100. This gives you a living ROI dashboard per language.

Step 6: Connect translation costs to revenue data

Translation costs include per-word fees, platform subscriptions, project management time, and QA. If you use SeaText, the Translation Agent charges per published word and shows usage in the dashboard. Export that monthly, join on language code in your Sheets dashboard, and you have a complete cost side. For manual projects, ask your LSP for a breakdown by language and date. Without cost data, you only have revenue — not ROI.

Key facts

Common mistakes that break ROI tracking

• Mixing languages in one GA4 view without a language dimension. You cannot separate revenue by language later.
• Forgetting UTM tags on language switchers. You lose visibility into language-switch behavior and post-switch conversions.
• Using auto-translate widgets that don't create indexable URLs. Search engines cannot rank them, and GA4 sees them as the same page.
• Not sending currency and language with purchase events. Revenue rolls up into a single bucket.
• Ignoring translation maintenance costs. Updates, new pages, and QA add up; omitting them inflates ROI.

Terminology

hreflang

HTML link attribute that tells search engines which language and region a page targets.

CAPI (Conversions API)

Server-side endpoint that sends conversion events directly to Meta or Google, bypassing browser blockers.

UTM parameters

Query-string tags (utm_source, utm_medium, utm_campaign, utm_content) that attribute traffic to a source.

Enhanced e-commerce

GA4 schema that captures product impressions, add-to-cart, checkout steps, and purchases with rich parameters.

Translation ROI

(Net profit from translated content / Total translation cost) × 100.

Limitations and when this approach does not apply

This setup assumes you control the website code and can deploy GTM. If your translated pages live on a third-party marketplace (Amazon, App Store) or a headless CMS that blocks GTM, you need server-side event forwarding instead. The cost-side data requires access to invoices or a translation platform with usage reporting; if you work with multiple freelancers without centralized billing, you must consolidate costs manually. SeaText's Translation Agent centralizes this, but other workflows may not.

FAQ

How long until I see reliable ROI numbers?

Wait for at least 500 sessions per language after implementation. Fewer sessions make conversion rates noisy. For low-traffic languages, aggregate quarterly.

Can I track ROI without GA4?

Yes. Matomo, Plausible, or server-side logs work if you can attach a language identifier to each session and purchase. The principles — separate views, language dimension, cost join — are identical.

What if I use automatic browser-language redirects?

Redirects hide the language choice from analytics. Add a language_switch event on the redirect landing page, or use a JavaScript snippet that pushes the detected language to the data layer before the redirect fires.

Do I need separate GA4 properties for each language?

No. One property with a page_language custom dimension is cleaner. Separate properties make cross-language comparisons harder and hit property limits.

How do I handle currencies in ROI calculations?

Convert all revenue to your reporting currency using the monthly average exchange rate from your finance team. Keep the original currency in GA4 for ad-platform optimization.

Can SeaText's Translation Agent help with the tracking setup?

It publishes translated pages under language subdirectories, injects hreflang and lang attributes, and exposes a usage dashboard for cost data. You still need to configure GA4/GTM as described, but the structural prerequisites are handled.

What is the minimum viable setup if I have no developer time?

Enable GA4 enhanced measurement, add hreflang via your CMS or SeaText, and manually export translation invoices monthly. Join in Sheets. It is not perfect, but it beats guessing.

How to Set Up Variant Tests for Logged In Users

To set up variant tests for logged in users, you must identify the user uniquely and assign them to a specific variant consistently. This ensures that a user sees the same experience every time they visit. Manual setup requires code changes to link user IDs to test groups. Automated tools handle this dynamically based on visitor data.

Traditional A/B Testing vs. Seatext AI Approach

Seatext fits teams needing fast iteration without large traffic volumes. Traditional tools suit enterprise sites with high traffic and strict compliance needs. Check with the vendor for specific pricing details.

Prerequisites for Targeted Testing

Before starting, ensure you can identify logged in users reliably. You need a distinct ID or email address for each account. Your tracking system must capture this data before the page renders. Without consistent identification, users might see different variants on each visit.

Verify that your analytics platform supports user properties. Most modern systems allow you to send a user ID with page views. If you use a third-party tool, check its documentation for user identification methods. This step prevents data fragmentation across sessions.

Seatext simplifies this by using AI Personalization Agents. These agents detect visitor context automatically. They adapt content without requiring manual user ID mapping. This reduces the technical burden on your engineering team.

Step 1: Define Your Variants

Decide what changes you want to test. Common options include headlines, product descriptions, or call to action buttons. Keep changes specific so you can measure their impact clearly. Avoid changing multiple elements at once unless using a multivariate test.

Seatext allows you to generate copy variants automatically. Its AI agents suggest improvements based on what converts best. You can review these suggestions before publishing them. This reduces the time spent writing test content manually.

The AI CRO Reading Analysis feature helps identify friction points. It analyzes scroll depth and time on page. These signals indicate which headlines or offers resonate most. You can focus your tests on high-impact areas.

Step 2: Configure User Targeting

Set conditions to include only logged in users in your test. In most tools, you add a rule based on user properties. For example, require that the user ID is not empty. This excludes guests and anonymous visitors from the experiment.

You can also narrow the scope further. Target users with specific purchase histories or subscription levels. This helps you test features relevant to particular segments. Seatext adapts content in real time to match visitor intent automatically.

For example, you might test different pricing displays for loyal customers. Or you could test welcome messages for new subscribers. The AI Personalization Agent handles these rules dynamically. You do not need to write complex code for each segment.

Step 3: Implement the Test

Deploy the variants to your site. If using code, integrate the SDK and initialize the feature flag. If using a no-code tool, paste the snippet into your website header. Seatext requires no code changes for most agents.

Ensure the test loads quickly. Slow scripts can frustrate users and hurt performance. Seatext operates at the edge to minimize latency. This keeps your site fast while running experiments in the background.

Seatext's AI Split URL Testing offers 0ms zero-flicker tests. This means users see the optimized version instantly. There is no delay or visual shift during page load. This improves user experience and test accuracy.

Step 4: Verify User Assignment

Check that logged in users see the correct variant. Log in as a test user and browse the site. Use browser developer tools to inspect network requests. Look for the user ID being sent to the testing platform.

Confirm that the variant persists across pages. Navigate to different sections of your site. The experience should remain consistent throughout the session. If it changes unexpectedly, review your targeting rules.

Seatext tracks results by page and version. You can see which variants drive sales or engagement. The AI agents update content based on performance. This creates a continuous improvement loop without manual intervention.

Why Traditional Methods Fail Low-Traffic Sites

Classic A/B testing often requires large sample sizes. This delays results for sites with low traffic. Logged in users represent a smaller segment than overall visitors. Waiting for statistical significance can take months.

AI reading telemetry solves this problem. It analyzes behavior like scroll depth and time on page. These signals indicate intent faster than conversion events. You can scale winning variants without waiting for perfect data.

Standard analytics treat all visitors the same. A user who reads for 90 seconds is logged like one who bounces in 3 seconds. AI reading telemetry captures these nuances. It identifies friction points before they cause drop-offs.

Seatext uses Autonomous AI Marketing Agents. These agents test headlines, offers, and CTAs continuously. They scale multilingual sales on autopilot. This is ideal for niche ecommerce stores or B2B sites.

Limitations and Considerations

Test only one major change per user group at a time. Mixing too many variables makes results hard to interpret. Ensure your user identification is secure. Do not expose sensitive data in test URLs or logs.

Some users might have ad blockers or privacy settings. These can interfere with tracking scripts. Seatext forwards purchase signals directly to ad platforms. This bypasses browser restrictions to maintain data accuracy.

Seatext's Conversion Relay forwards purchases to Meta and Google CAPI. This ensures your data reflects real human activity. It protects your ad spend from bot clicks. The Bot Refund Agent recovers wasted budget automatically.

Common Mistakes to Avoid

Do not test on all users if you target logged in accounts. This dilutes your sample size and confuses results. Exclude internal traffic like employees or partners. They do not represent real customer behavior.

Avoid changing variants too frequently. Users need time to react to changes. If you switch too often, you lose trend data. Let tests run long enough to gather meaningful signals.

Do not ignore international markets. Seatext supports multilingual content and product descriptions. This lets you test globally without managing separate campaigns. Activate premium agents when you need advanced features.

How Seatext Simplifies the Process

Seatext uses autonomous AI agents to manage tests. You do not need to write code or configure complex rules. The agents detect visitor context and adapt content automatically. This includes logged in status and past behavior.

The platform tracks results by page and version. You can see which variants drive sales or engagement. Seatext also protects your ad spend from bot clicks. This ensures your data reflects real human activity.

Seatext integrates with your existing analytics. It forwards verified near-buyer signals to ad algorithms. This helps your ad campaigns perform better. You get a full loop from traffic acquisition to conversion.

Next Steps for Implementation

Start with a simple headline test for logged in users. Compare a generic message against a personalized one. Monitor add to cart rates and time on page. Use these insights to guide future experiments.

When ready, scale to more complex variations. Seatext supports multilingual content and product descriptions. This lets you test globally without managing separate campaigns. Activate premium agents when you need advanced features.

Explore the free agents first. Seatext offers 8 AI agents at no cost. You can install the platform and understand how it works. Upgrade to premium when you need all 20+ agents for $59/month.

Contact enterprise sales for custom agents. Teams can discuss managed rollouts. This ensures smooth integration with your workflows. Seatext helps you turn visitors into paying customers faster.

Quick answer: export and attach a complete console log

Open your browser's Developer Tools with F12 (or Cmd+Option+I on Mac), switch to the Console tab, right-click anywhere in the log area, and choose Save as… to write a .log file. Attach that file to your support ticket along with the browser name and version, the SeaText snippet you pasted into your SPA, and a short description of what you were doing when the problem appeared.

Why a clean console export matters for SeaText

SeaText runs as an asynchronous JavaScript snippet that mounts on your single-page application (React, Vue, Angular, or plain HTML). The snippet writes to localStorage, makes cross-origin requests, and rewrites page content in real time. When something behaves unexpectedly — missing translations, variant not swapping, bot-refund agent not firing — the browser console is the only place that shows load order, network failures, CORS blocks, or JavaScript exceptions. A raw screenshot misses timestamps, stack traces, and filtered messages; a saved log preserves everything.

Step-by-step: capture a useful log file

1. Reproduce in a clean session. Open an incognito/private window, disable extensions that inject scripts, and navigate to the page where SeaText is installed.
2. Open Developer Tools before the action. Press F12, click the Console tab, and enable Preserve log so navigation doesn't clear history.
3. Filter wisely. Keep All levels selected (Errors, Warnings, Info, Verbose). SeaText's own messages are logged at info level; hiding them removes clues.
4. Trigger the issue. Perform the exact steps that caused the problem: page load, language switch, variant change, ad click, etc.
5. Save the log. Right-click in the console pane → Save as… → name it seatext-console-YYYYMMDD-HHMM.log.
6. Gather context. Copy the User-Agent string (navigator.userAgent in console), note the SeaText snippet version (visible in the Network tab as the script request), and paste the snippet you embedded in your index.html or SPA entry point.
7. Attach to ticket. Open your SeaText support channel (dashboard chat, email, or help-center form) and attach the .log file plus the context block.

Fill-in-the-blank context template

Copy the block below into your ticket. Replace every bracketed placeholder with your actual values.

Browser + version: [e.g., Chrome 126.0.6478.114]
Operating system: [e.g., macOS 14.5, Windows 11 23H2]
SeaText snippet source: [dashboard → Installation → Copy snippet]
Framework + version: [React 18, Vue 3, Angular 17, plain HTML]
Snippet placement: [index.html <body> / main.tsx / bootstrap.js / other]
CSP headers: [paste Content-Security-Policy header value or "none"]
Reproduction steps:
1. [step one]
2. [step two]
3. [step three]
Expected behavior: [what should happen]
Actual behavior: [what happens instead]
Attachments checklist:
☐ console.log file
☐ HAR export (if network errors)
☐ localStorage.json (run copy(JSON.stringify(localStorage,null,2)))
☐ screenshot of Network tab filtered for SeaText request
☐ snippet exactly as deployed

Support ticket template (copy-paste)

Subject: SeaText issue — [short description, e.g., "translation not applying on variant switch"]

Environment:
- Browser: [browser + version]
- OS: [operating system]
- Framework: [framework + version]
- Snippet location: [where you pasted the snippet]
- CSP: [header value or "none"]

Steps to reproduce:
1. [step one]
2. [step two]
3. [step three]

Expected: [describe expected outcome]
Actual: [describe actual outcome]

Attached:
- seatext-console-YYYYMMDD-HHMM.log
- network.har (optional)
- localStorage.json (optional)
- deployed-snippet.txt (exact snippet from your repo)

Additional notes: [anything else support should know]

Annotated sample console log excerpt

The example below shows the structure SeaText support expects. Timestamps, log levels, and SeaText prefixes are preserved. Lines marked illustrative are not guaranteed to appear in every project.

[2024-07-15T14:32:10.123Z] INFO  [SeaText] Snippet injected, async load started
[2024-07-15T14:32:10.456Z] INFO  [SeaText] Fetching configuration from https://api.seatext.com/v1/config (illustrative URL)
[2024-07-15T14:32:10.789Z] INFO  [SeaText] Configuration received, initializing agents
[2024-07-15T14:32:11.012Z] INFO  [seatext-translation] Language set to 'es-ES'
[2024-07-15T14:32:11.015Z] INFO  [seatext-cro-optimizer] Variant 'hero-v2' selected for campaign 'summer-sale'
[2024-07-15T14:32:11.020Z] WARN  [seatext-bot-refund] Bot score 0.87 — session flagged for review
[2024-07-15T14:32:11.025Z] ERROR [seatext-translation] Failed to fetch translation bundle: TypeError: Failed to fetch
    at translate.js:245:17 (illustrative filename)
    at async applyTranslations (translate.js:112:5)
[2024-07-15T14:32:11.030Z] INFO  [SeaText] Visitor ID stored in localStorage
[2024-07-15T14:32:11.035Z] INFO  [seatext-visitor-source] Referrer detected: google.com, campaign: summer-sale

Decision table for common console or network errors

What to include in the context block

• Browser + version (e.g., Chrome 126.0.6478.114)
• Operating system
• SeaText snippet source (dashboard → Installation → Copy snippet)
• Framework and version (React 18, Vue 3, Angular 17, etc.)
• Whether you load the snippet in index.html <body> or via a framework-specific bootstrap file
• Any Content-Security-Policy headers that might block inline scripts or localStorage
• Steps to reproduce, numbered
• Expected vs. actual behavior

Common mistakes that slow down diagnosis

Verifying the snippet loads correctly

After you paste the SeaText snippet into your SPA entry point (per the SPA integration guide), open the Network tab, filter for the SeaText script request, and confirm:

• Status 200 for the script request
• Response contains the SeaText initialization code
• No CORS errors in Console
• localStorage shows a visitor ID after first load

If any of these checks fail, include the Network tab HAR export (Right-click → Save all as HAR) alongside the console log.

Key facts about SeaText's client-side behavior

When the log won't help and what to do instead

• Server-side rendering errors: SeaText snippet runs in the browser; SSR logs belong in your backend.
• Network-level blocks (corporate proxy, firewall): Console shows net::ERR_BLOCKED_BY_CLIENT; provide HAR file and IT team contact.
• Third-party script conflicts: If another vendor mutates window or localStorage, isolate by disabling them one by one.
• Mobile Safari / in-app browsers: Use remote debugging (Safari Web Inspector on macOS, Chrome DevTools for Android) to pull logs.

FAQ

Do I need to enable "Verbose" logging in Chrome?

Yes. SeaText's diagnostic messages are emitted at the verbose level. If the dropdown reads "Default levels", switch to "Verbose" before reproducing.

Can I just copy-paste the console text into the ticket?

You can, but copied text loses timestamps and line numbers. A saved .log file is preferred; paste only as a last resort.

What if the issue only happens in production?

Reproduce in a staging environment that mirrors production CSP headers and domain structure. If impossible, open an incognito window on production, capture the log, and note the exact URL and campaign parameters.

Does SeaText support need my localStorage dump?

Sometimes. In the console, run copy(JSON.stringify(localStorage, null, 2)) and paste the output into a localStorage.json attachment.

How do I know which SeaText agent caused the error?

Log lines prefixed with [SeaText] or seatext- indicate the agent (e.g., seatext-bot-refund, seatext-translation). Include those lines in your description.

Can I filter the log before sending to reduce size?

Keep the full log. Support greps for SeaText prefixes; removing unrelated lines may delete timing context.

What if the console is empty but SeaText still doesn't work?

Check the Network tab for failed SeaText script loads, then verify your CSP allows the script origin (check with the vendor for the exact domain).

Limitations of this guide

These steps cover browser-console export for SeaText's client-side snippet. They do not cover server-side SeaText API logs, dashboard audit logs, or mobile-app WebView debugging beyond remote-inspection basics. For those, ask support for the specific export procedure.

Stop the test in your testing dashboard, set the winning AI variant as the default content for all visitors, and monitor performance post-deployment to confirm the gain holds. This is the cleanest way to end a test and lock in the improvement without losing data or confusing your team.

Step-by-step: How to stop a test

Follow these steps in order. Each one builds on the last, so don't skip ahead.

1. Confirm the win is real. Check that the variant has reached statistical significance and has enough sample size. Avoid the peeking trap—don't stop just because the numbers look good early. Use a confidence level of at least 95% if your testing tool supports it.
2. Stop the test in your dashboard. Find the test, click stop, and choose the winning variant as the default. In SeaText, you can use the Variants Edit panel to review and manually edit variants before you finalize the winner.
3. Set the winning variant as the default content for all visitors. This may mean publishing the variant or making it the control. Make sure the change is live for everyone, not just a segment.
4. Monitor performance after deployment. Track conversion rate and other key metrics for at least a few days. This confirms the gain holds in real traffic and catches any unexpected side effects.
5. Document the result. Record what you learned, the sample size, the confidence level, and the final lift. This helps you plan future tests and avoid repeating mistakes.

Prerequisites before you stop

Before you stop any test, make sure you have these in place:

• Statistical significance. The result should be unlikely to be due to chance. Most tools show this as a confidence percentage.
• Enough sample size. A small sample can give misleading results. Wait until the test has run long enough to cover multiple traffic patterns, like weekdays and weekends.
• No external changes. If you changed your ad campaigns, site design, or offers during the test, the results may be contaminated. Stop the test only if the environment stayed stable.
• Access to the testing dashboard. You need permission to stop the test and edit variants. In SeaText, you must have an account and the AI script installed and activated on your domain.

Verify the win is real

Don't trust a single metric. Look at the full picture:

• Check conversion rate by page, keyword, and variant. SeaText provides conversion reporting by page, keyword, and variant, so you can see if the win is consistent across segments.
• Look at secondary metrics. Bounce rate, time on page, and click-through rate can reveal if the variant is actually better or just gaming one metric.
• Run a sanity check. If the lift is huge (like 300%), it's probably a bug or a tracking error. Real wins are usually modest.
• Consider the peeking trap. If you checked the results multiple times and stopped as soon as it looked good, your confidence level is lower than it appears. Use a stopping rule before you start the test.

What to do after you stop

Once the winning variant is live, your work isn't done. Here's what to do next:

• Monitor for regression. Watch the conversion rate for at least a week. If it drops back to the old level, the win may have been a fluke or the variant may not work in all contexts.
• Update your documentation. Record the test hypothesis, the variant, the sample size, and the result. This builds a knowledge base for future tests.
• Plan the next test. Use what you learned to form a new hypothesis. Continuous testing is more valuable than a single win.
• Consider rolling out to other pages. If the variant worked on one page, test it on similar pages. SeaText's agents can run continuous tests across your site, so you can scale the winning approach.

Key facts about SeaText's testing

SeaText's CRO Optimizer agent is built for this exact workflow. Here are the facts from the source documentation:

Limitations and when this advice doesn't apply

This process assumes you have a proper A/B testing setup. It doesn't apply if:

• You're testing a brand-new page with no traffic. You need enough visitors to reach significance. If you have very low traffic, consider a longer test or a different method.
• You're using a tool that doesn't let you stop and set a default. Some tools only let you pause, not promote a variant. Check your tool's documentation.
• You're testing multiple variants at once. If you have more than two variants, you may need a more complex stopping rule, like a multi-armed bandit.
• You're in a regulated industry. If you need to prove the test was fair, you may need to keep the test running longer or document more thoroughly.

Also, SeaText requires a valid domain and an activated account. Development URLs like localhost are restricted, and you must wait at least five minutes after installation for the AI to link to your account. If you don't see your website name in the dashboard, contact support.

FAQ

How long should I run an A/B test before stopping?

Run it until you reach statistical significance and have enough sample size. There's no fixed time. A common rule is at least one full business cycle (a week) to cover different traffic patterns.

What is the peeking trap?

It's when you check the results repeatedly and stop as soon as the numbers look good. This inflates the chance of a false positive. Decide your stopping rule before you start the test.

Can I stop a test early if the variant is clearly winning?

Only if you have a pre-defined stopping rule, like a confidence level of 99% or a minimum sample size. Otherwise, you risk acting on noise.

What if the winning variant doesn't hold up after I deploy it?

Monitor performance for a few days. If the gain disappears, you may have had a false positive or the variant may not work in all contexts. Roll back to the original and investigate.

Does SeaText automatically stop tests and deploy winners?

SeaText's CRO Optimizer agent automatically identifies which text lifts conversion rate over time. You can review and edit variants in the Variants Edit panel, and then set the winner as the default. The agent runs continuously, so it can keep testing new variations after you deploy.

What metrics should I use to confirm a win?

Use conversion rate as the primary metric, but also check secondary metrics like bounce rate, time on page, and revenue per visitor. SeaText provides conversion reporting by page, keyword, and variant.

Bots train your ad algorithms every time they click: the platforms see engagement, adjust bidding, and expand targeting toward similar fraudulent patterns. The fix is a detection layer that sits on your landing pages, scores each session in real time, blocks or flags bots before your conversion pixels fire, and exports evidence packages that Google, Meta, TikTok, and Reddit accept for refunds.

Why bot traffic corrupts ad algorithms

Ad algorithms optimize for the signals you send them. When bots click, scroll, or fill forms, those actions look like high-intent behavior. The algorithm then bids more aggressively for similar traffic, creating a feedback loop that wastes budget on non-human visitors. Clean data breaks the loop.

This corruption is not just wasted spend. It distorts your audience profiles, retargeting lists, and conversion reports. Over weeks, smart bidding models shift toward bot-heavy placements and audiences. You pay more for clicks that never produce a customer, and your optimization signals become noise.

How ad algorithms learn from bot signals

Google Ads and Meta use machine learning to predict which clicks will convert. They look at historical user actions: clicks, time on site, page scrolls, form submissions. A bot that mimics those actions gets the same weight as a human. The model cannot tell the difference unless you flag it.

Once the model sees dozens of bot visits with high engagement, it assumes that traffic pattern is valuable. It raises bids for similar sources. Your campaign budget funnels toward that pattern, driving more bots. The only way to stop this is to prevent the bot signals from reaching the algorithm in the first place.

How bot detection works on the page

A lightweight script analyzes device fingerprint, mouse dynamics, scroll velocity, IP reputation, and behavioral anomalies. Sessions that fail the checks are tagged as invalid. The tag travels with the click ID so your analytics and ad platforms can exclude them from conversion reporting and audience building.

Behavioral analysis looks at how a visitor moves the cursor, the rhythm of scrolling, and how quickly they interact with elements. Bots often lack natural variation. They may click at perfect intervals or scroll in a linear pattern. Device fingerprinting checks browser version, screen size, installed fonts, and hardware profiles. IP reputation flags datacenter and residential proxy ranges known for abuse.

Key methods to stop bots from poisoning your data

• Pre-pixel filtering: Block or quarantine bot sessions before your Google Ads, Meta, or TikTok pixels fire. This keeps retargeting audiences clean.
• Click-level evidence: Capture timestamp, IP, user agent, behavioral score, and page interaction logs for every suspicious click.
• Refund-ready reports: Export CSV or API payloads formatted for each platform’s invalid-click dispute process.
• Automated exclusion lists: Push confirmed bot IPs and device IDs to platform blocklists daily.

These methods work together. Pre-pixel filtering prevents the algorithm from learning from bots. Evidence lets you reclaim the wasted spend. Exclusion lists stop repeat offenders before they reach your page again.

Step-by-step: Setting up bot protection for ad campaigns

1. Add the detection snippet to your site (one-line JavaScript or GTM tag).
2. Connect your ad accounts so the agent can match click IDs to sessions.
3. Enable “filter before pixel” mode for each campaign you want protected.
4. Review the first 7–14 days of flagged traffic in the dashboard; adjust sensitivity if false positives appear.
5. Download the platform-specific evidence pack and submit refund requests.
6. Schedule weekly exports to keep blocklists current.

Start in monitor mode if you worry about blocking real users. Most detection tools offer a dry-run phase. You see which sessions would be flagged without actually stopping them. After a week, review the patterns and enable filtering with confidence.

Comparison of bot protection approaches

Takeaway: On-page behavioral agents give the most granular evidence because they see the actual session, not just the click.

Practical scenarios and decision criteria

Choose an approach based on your traffic volume, budget, and technical resources. A small advertiser can rely on platform filters and manual review. A large ecommerce brand with thousands of daily clicks needs automated filtering and refund processing.

If you see a high bounce rate from certain placements or a sudden spike in conversions that never turn into sales, suspect bot traffic. Check your server logs for repeat IPs, unusual session durations, or empty referrers.

For agencies managing multiple accounts, a unified bot protection layer saves time. It centralizes evidence and makes refund claims consistent across clients. Check with the vendor for specific integration limits.

Monitoring and tuning your bot protection

After deployment, track the false positive rate. Legitimate users may be flagged if they use old browsers or have aggressive pop-up blockers. Adjust the sensitivity threshold based on your audience profile.

Monitor the percentage of flagged traffic daily. A sudden jump often signals a new bot attack. Compare it with your ad platform’s invalid click reports. If they diverge, investigate why and update your rules.

Keep your blocklists fresh. Bot networks rotate IPs weekly. Automated exclusion lists that sync daily are more effective than static lists.

Limitations and when to escalate

• Sophisticated residential botnets can mimic human behavior well enough to pass behavioral checks; combine with IP reputation feeds.
• Refund policies vary by platform — Google and Meta have formal processes; TikTok and Reddit are newer and may require manual appeals.
• The agent only protects traffic that lands on your pages; it cannot stop bots from clicking ads that never reach your site (e.g., accidental clicks in-app).
• If your site uses heavy client-side rendering, the detection script may not load before the bot leaves. Consider server-side integration for critical pages.

Key facts

FAQ

Does this stop bots from clicking the ads in the first place?

No. It stops bots from reaching your landing page and firing your conversion pixels. The click still happens on the ad platform, but the algorithm never sees a conversion signal from that session.

How quickly does the algorithm recover after I clean the data?

Typically 1–2 weeks of clean conversion data are enough for smart bidding to re-calibrate, provided you also exclude the flagged click IDs in the platform interface.

Can I use this alongside Google’s invalid-click protection?

Yes. The agent works as a second layer; its evidence can supplement Google’s own findings when you file a refund request.

What if legitimate users are flagged as bots?

The dashboard shows a false-positive rate. Start in “monitor only” mode, review flagged sessions for a week, then enable filtering once you’re comfortable.

Is there a minimum spend requirement?

No. The agent activates on any site with the snippet; refund value scales with your bot traffic volume.

How do I submit the evidence to Meta or Google?

Download the platform-specific CSV from the dashboard and upload it through each platform’s invalid-click dispute form (Google Ads → Tools → Invalid clicks; Meta → Business Help → Report invalid traffic).

Will blocking bots hurt my page load speed?

No. The detection script is lightweight and asynchronous. It runs in the background and does not delay page rendering.

Can I use it with CMS platforms like WordPress or Shopify?

Yes. Seatext offers a one-line snippet or GTM tag that works on any site, including WordPress, Shopify, Wix, and custom platforms.

Install a bot detection agent on your site that monitors every paid click, separates human visitors from automated traffic, and produces refund-ready reports for Google Ads, Meta, TikTok, Reddit, and other platforms. The agent filters bot traffic before it reaches your analytics and retargeting pixels, then documents each suspicious session with timestamps, behavior patterns, and IP data that ad networks accept for credit requests. Teams typically recover 12–20% of wasted spend once the evidence pipeline is live.

How bot detection works on paid traffic

The agent sits on your landing pages and watches every session that arrives from a paid campaign. It scores behavior in real time — mouse movement, scroll depth, dwell time, click patterns, device consistency, and network reputation. Sessions that fail the human threshold are flagged as invalid. The system does not block the click at the network level; instead it builds a forensic record that you submit to the ad platform for a refund. This approach keeps your ad delivery intact while creating an audit trail.

According to SeaText documentation, the agent "detects suspicious paid traffic, separates real buyers from bots, and creates evidence your team can use for Google, Meta, TikTok, Reddit, and other ad refund workflows" (S2). The same source notes the agent provides "fraudulent click detection and session evidence" and "refund-ready reports for ad platforms" (S7).

Step-by-step: set up bot protection and refund workflow

1. Add the tracking snippet. Paste the SeaText JavaScript snippet into your site header or use the one-click install for WordPress, Shopify, Webflow, Wix, and other platforms (S4). The snippet loads in under a minute and starts scoring traffic immediately.
2. Activate the Bot Refund Agent. In the SeaText dashboard, enable the Bot Protection Agent. Choose which campaigns or traffic sources to monitor — Google Ads, Meta Ads, TikTok, Reddit, or custom UTM sources.
3. Configure evidence thresholds. Set the sensitivity for what counts as suspicious: rapid bounce, zero scroll, non-human mouse paths, data-center IPs, known VPN ranges, or behavioral anomalies. Start with the default profile; tighten after reviewing the first week of flagged sessions.
4. Review flagged sessions daily. The dashboard shows each flagged visit with a session replay, IP metadata, behavioral score, and campaign tag. Confirm the flags look accurate before exporting.
5. Generate refund reports. Click "Export Refund Package" to produce a CSV or PDF formatted for each platform's dispute form. The report includes click IDs (gclid, fbclid, ttclid), timestamps, behavioral evidence, and a summary of invalid spend by campaign.
6. Submit to ad platforms. Upload the package through Google Ads "Invalid Clicks Contact Form," Meta "Ad Account Billing Disputes," TikTok "Traffic Quality Appeal," or Reddit Ads support. Keep the submission ID for tracking.
7. Enable pixel filtering. Turn on "Bot filtering before pixels poison retargeting audiences" (S2, S7) so flagged bots never fire your conversion pixels. This keeps lookalike and retargeting pools clean.

Using evidence to recover spend from Google, Meta, and others

Ad platforms require structured evidence: click IDs, timestamps, and a clear explanation of why the traffic is invalid. The agent automates this packaging. SeaText notes that "clients use bot evidence to request refunds for invalid Google and Meta clicks while keeping ad pixels cleaner" (S6). The same source lists supported platforms: "Google, Meta, TikTok, Reddit, and other ad refund workflows" (S2, S6).

Refund timelines vary. Google typically responds in 5–10 business days. Meta often credits within a week. TikTok and Reddit may take longer and sometimes request additional logs. Keep the raw session data for at least 90 days in case of follow-up questions.

Protecting retargeting and lookalike audiences

Bot clicks that fire conversion pixels corrupt your retargeting pools and lookalike models. When bots trigger "Purchase" or "Lead" events, the platform learns to find more bots. The agent prevents this by suppressing pixel fires for flagged sessions before the browser sends the event. SeaText describes this as "bot filtering before pixels poison retargeting audiences" (S2, S7). This protection runs automatically once the agent is active and pixel filtering is enabled in step 7 above.

What recovery rates to expect

Public claims from SeaText cite a range: "Get back up to 18% of your Google and Meta ad spend lost to bot clicks" (S2), "Get back up to 20% of Google and Meta spend with bot protection" (S6), and "Recover up to 20% of ad spend" (S7). Actual recovery depends on your industry, traffic sources, and how aggressively you set detection thresholds. E-commerce sites with high-volume Google Shopping campaigns often see the highest percentages; B2B lead-gen with lower volumes may see smaller absolute dollars but similar rates.

Limitations and when this approach does not apply

• Organic and direct traffic. The agent only scores sessions that carry paid-campaign identifiers (UTMs, click IDs). It does not filter bot traffic from SEO, email, or direct visits.
• Platform approval is not guaranteed. Google, Meta, and others make the final refund decision. Strong evidence improves odds but does not ensure credit.
• Sophisticated residential botnets. Bots that mimic human mouse paths, use residential IPs, and vary dwell time can evade behavioral scoring. The agent updates its models continuously, but no system catches 100%.
• No network-level blocking. The agent does not stop the click at the ad network. It only documents and filters post-click. For pre-click blocking, you need platform-level invalid-click settings or a dedicated click-fraud firewall.
• Implementation requirement. You must control the landing page code to install the snippet. If you send paid traffic to third-party funnels you cannot edit, this method will not work.

Key facts

Terminology

• Click ID (gclid, fbclid, ttclid): Unique parameter appended by the ad platform to each paid click. Required for refund claims.
• Invalid traffic (IVT): Clicks or impressions generated by bots, scrapers, or non-human actors. Divided into General IVT (known crawlers) and Sophisticated IVT (evasive bots).
• Retargeting pixel: JavaScript tag that fires when a user completes an event (purchase, lead). Poisoned pixels teach platforms to target similar low-quality users.
• Lookalike audience: Platform-generated audience modeled on your converters. Bot conversions degrade model quality.
• Refund-ready report: Structured evidence package formatted to match a platform's dispute submission requirements.

FAQ

How long before I see refund credits?

Most teams submit their first refund package within 7–14 days of installation. Platform review takes 5–15 business days. Credits appear as account balance adjustments, not cash payouts.

Does this replace Google's automatic invalid-click filtering?

No. Google already filters some General IVT. The agent catches Sophisticated IVT that slips through and provides the documentation Google's automated system cannot produce for a manual appeal.

Can I use this with a click-fraud firewall like ClickCease or CHEQ?

Yes. Firewalls block at the network level; the agent documents post-click behavior and builds refund evidence. They complement each other.

What if my landing pages are on a third-party funnel builder (Unbounce, Instapage, ClickFunnels)?

You need the ability to paste the JavaScript snippet into the page header. Most major funnel builders allow custom code injection. If yours does not, you cannot use this agent on those pages.

Will enabling pixel filtering break my conversion tracking for real users?

No. The agent only suppresses pixels for sessions it flags as bots. Human sessions fire pixels normally. You can verify by checking the "Pixel Status" column in the session log.

Is there a minimum spend threshold to make this worthwhile?

Sites spending under $1,000/month on paid ads may not recover enough to justify the setup time. The agent is free to install; the paid plan starts at $59/month after a proof period (S8).

Can I export raw session data for my own analysis?

Yes. The dashboard allows CSV export of all scored sessions, not just flagged ones. Useful for BI tools or custom modeling.

To style content inside an Odoo Embed Code block, open the page editor, click the Embed Code block, then select the Style tab in the right panel. From there you can adjust padding, margin, borders, background color, and visibility settings without writing CSS. For deeper customization, wrap your embed code in a <div class="your-class"> and add matching CSS rules in the website's Custom Code area under Website → Configuration → Custom Code, or place a <style> block directly inside the embed snippet.

What the Embed Code block actually does

The Embed Code block is an Inner Content building block that lets you paste raw HTML, CSS, and JavaScript into any page. It does not sanitize or sandbox your snippet, so whatever you paste runs in the page context. That means your styles can affect the embed, and the embed's styles can leak out to the rest of the page if you are not careful.

Odoo 17 and later surface a Style tab for every block, including Embed Code. The tab exposes the same layout and design controls you get on structure blocks: spacing, borders, background, box shadow, and responsive visibility. Those controls write inline styles on the block's wrapper element, so they apply to the container, not to the inner markup you pasted.

Prerequisites before you start styling

• Editor access on the target website (Website → Edit).
• An Embed Code block already placed on the page (drag it from Dynamic Content in the Blocks panel).
• The third-party snippet or custom markup you want to style, copied and ready to paste.
• Basic familiarity with CSS selectors if you plan to write custom rules.

Step-by-step: styling with the built-in Style tab

1. Open the page in edit mode and click the Embed Code block. The right panel switches to that block's settings.
2. Select the Style tab at the top of the panel.
3. Adjust Spacing (padding and margin) to create breathing room around the embed.
4. Set a Background color or image if the embed has transparent areas.
5. Add a Border and Border Radius to frame the embed visually.
6. Use Box Shadow for depth.
7. Open Visibility and toggle Hide on Desktop, Hide on Mobile, or both if the embed should only appear on certain devices.
8. Click Save in the top-right corner of the editor.

These changes are stored on the block instance, so they survive theme updates and do not require a developer.

Step-by-step: adding custom CSS via the website Custom Code area

1. In the website editor, open the Website menu (top-left) and choose Configuration → Custom Code.
2. In the Head or Body tab, paste your CSS rules wrapped in <style> tags.
3. Use a class selector that matches the wrapper you added inside the Embed Code block, for example:

   <style>
     .my-embed-wrapper iframe { width: 100%; height: 400px; border: none; }
     .my-embed-wrapper .cta-button { background: #0066cc; color: #fff; }
   </style>

4. Return to the Embed Code block, click Edit, and wrap your snippet:

   <div class="my-embed-wrapper">
     <!-- your third-party embed code here -->
   </div>

5. Click Save on the block, then Save on the page.

This approach keeps styles centralized, version-controlled in the Custom Code UI, and reusable across multiple embed blocks.

Step-by-step: inline <style> inside the embed block

1. Click the Embed Code block and choose Edit.
2. Paste a <style> block before your markup:

   <style>
     .widget-container { max-width: 600px; margin: 0 auto; font-family: inherit; }
     .widget-container .title { font-weight: 600; color: #1a1a1a; }
   </style>
   <div class="widget-container">
     <!-- embed markup -->
   </div>

3. Click Save.

Use this method for one-off embeds that will never be reused. It avoids a round-trip to the Custom Code screen but mixes presentation with content.

Expert perspective: when to choose which method

If you manage dozens of pages and want consistent framing for every third-party widget, put the layout rules (width, spacing, border) in the Style tab and the widget-specific typography or color overrides in Custom Code. The Style tab is faster for non-technical editors; Custom Code scales better for design systems. Inline <style> is a last resort for quick prototypes or embeds that live on a single page and will be removed soon.

A common mistake is targeting the embed's internal elements from the Style tab. The Style tab only styles the block's outer wrapper. To reach inside an iframe or shadow DOM you must use CSS injected via Custom Code or the embed provider's own theming options.

Key facts

Limitations and gotchas

• Iframe isolation: Styles defined outside an iframe cannot penetrate it. The embed provider must expose theming parameters or allow CSS injection.
• Style leakage: Unscoped CSS in Custom Code or inline <style> can affect unrelated page elements. Always namespace your classes (e.g., .seatext-embed- prefix).
• Theme updates: Inline styles on the block wrapper persist, but Custom Code CSS is theme-agnostic and survives theme changes.
• Performance: Large <style> blocks on many pages increase DOM size. Prefer the centralized Custom Code area.
• Editor preview: The Odoo editor may not render third-party scripts fully. Always publish and view the live page to verify.

Verification checklist

1. Publish the page.
2. Open the live URL in an incognito window.
3. Inspect the embed wrapper in DevTools: confirm your custom class is present and your CSS rules apply.
4. Test responsive behavior at mobile, tablet, and desktop breakpoints.
5. Check that Hide on Desktop/Mobile toggles work as expected.
6. Validate no console errors from the embed script.

Terminology quick reference

• Embed Code block: Inner Content building block that accepts raw HTML/CSS/JS.
• Style tab: Per-block visual controls for spacing, background, border, shadow, visibility.
• Custom Code: Site-wide CSS/JS injection point under Website → Configuration.
• Dynamic Content: Blocks panel category containing Embed Code, Form, and other interactive snippets.
• Visibility section: Responsive display toggles in the Style tab.

FAQ

Can I use SCSS or Less in the Custom Code area?

No. Odoo's Custom Code field accepts plain CSS only. Compile your preprocessor output locally and paste the resulting CSS.

Why do my Style tab changes not affect the embed's inner text?

The Style tab targets the block's wrapper element. Inner content lives inside your markup or an iframe, so you must style it with custom CSS that matches your wrapper class.

How do I center an embed horizontally?

In the Style tab set left and right margin to auto, or add .my-wrapper { margin: 0 auto; max-width: 800px; } in Custom Code.

Can I animate the embed entrance?

Yes. Add a CSS animation on your wrapper class in Custom Code. Keep it subtle; heavy animations hurt CLS scores.

What if the embed provider loads its own stylesheet that conflicts with mine?

Increase specificity (e.g., .my-wrapper .provider-class) or use !important sparingly. If the embed loads inside an iframe, you cannot override its internal styles from the parent page.

Does the Embed Code block sanitize scripts?

No. Odoo does not strip <script> tags. Only paste code you trust.

Can I reuse a styled embed across multiple pages?

Save the block as a custom building block (click the block → Save as custom block). The saved block retains Style tab settings and inner markup.

To sync SeaText AI settings after restructuring your Webflow navigation, update the page slug references in each override or use the auto-match feature that maps by current live URL. Then verify each page in the SeaText dashboard to confirm the AI is active on the correct URLs.

Why Restructuring Navigation Breaks SeaText Mappings

When you move pages, rename slugs, or change the hierarchy in Webflow, the URLs that SeaText AI associates with your overrides change too. SeaText links each AI configuration to a specific page URL. If that URL no longer exists, the AI settings for that page stop applying.

This is not a Webflow issue. It is a mapping issue. SeaText stores your page-level settings against the URL it saw when you activated the AI. After a restructure, you need to tell SeaText where those settings should live now.

What You Need Before You Start

• An active Webflow Site plan (required to access Custom Code settings).
• Your SeaText AI account credentials.
• A list of the old URLs and the new URLs for every page you moved or renamed.
• At least 40 seconds of time on each page after publishing so the AI can activate and link to your account.

Step 1: Publish Your Restructured Webflow Site

Before SeaText can see the new URLs, your changes must be live. In Webflow, click the blue Publish button at the top right corner. Wait for the publish to complete.

Do not skip this step. SeaText cannot map to a URL that does not exist yet.

Step 2: Visit Each Changed Page to Reactivate the AI

Open each page that has a new URL in your browser. Stay on the page for at least 40 seconds. This activates the AI and links it to your account for that specific URL.

If you have many pages, visit them in order. You do not need to do this all at once, but each page must be visited before SeaText will recognize it.

Step 3: Check the SeaText Dashboard for Connection Status

Log in to your SeaText AI account. Look at the top of the page next to the SEATEXT logo. Your website name should appear there.

If you do not see your website name after 10 minutes, contact SeaText support. This could indicate an installation issue on your platform.

Step 4: Update Page-Level Overrides in the Configuration Panel

Go to the Main AI Hub and click on Configuration. This is where you adjust AI parameters for each page.

For every page you moved or renamed, find the old URL entry and update it to the new URL. If the old entry no longer appears, add a new entry for the new URL and reapply the settings you want.

Step 5: Use the Auto-Match Feature for Bulk Updates

If SeaText offers an auto-match feature that maps by current live URL, use it. This scans your live site and matches existing overrides to the new URLs automatically.

This is the fastest option when you have many pages. It works best when the page content is the same and only the URL changed.

Step 6: Verify Each Page in Variants Edit

Navigate to Variants Edit in the left panel of your SeaText account. Select the URL and language you want to check.

Confirm that the AI is generating variants for the correct new URL. If a page shows no variants, the AI is not active on that page yet.

Step 7: Test the Live Page

Visit the new URL in a fresh browser session. Check that the AI-generated content appears as expected. If you see the original static content, the mapping is still broken.

Repeat the visit-and-wait cycle if needed. Sometimes the AI needs a few visits to fully activate on a new URL.

Common Mistakes After a Restructure

What If You Have Multiple Domains or Websites?

Each SeaText AI account is linked to a single primary URL. If you use SeaText on multiple domains, you must create separate accounts for each domain.

This applies to development and production domains too. Do not try to use one account for both. Create a separate account for each domain you want to use.

Limitations and When This Advice Does Not Apply

Development URLs such as localhost are restricted for security reasons. SeaText may not function properly on dynamic development domains because it cannot reliably associate traffic with your account.

If you only changed the navigation menu labels but did not change any page URLs, you do not need to sync anything. SeaText maps by URL, not by menu position.

If you deleted pages entirely, those overrides are orphaned. You can remove them from the Configuration panel to keep your account clean.

Key Facts at a Glance

FAQ

How long does it take for SeaText to recognize a new URL?

After you visit the page for 40 seconds, SeaText should link it to your account within about five minutes. If you do not see your website name in the dashboard after 10 minutes, contact support.

Do I need to reinstall the SeaText script after restructuring?

No. The script stays in your Webflow Custom Code settings. You only need to update the page-level mappings in the SeaText dashboard.

What if I changed the URL but not the page content?

Use the auto-match feature if available. It maps by current live URL and should find the new URL automatically.

Can I use one SeaText account for both staging and production?

No. Each account is linked to a single primary URL. Create separate accounts for staging and production domains.

What happens to my overrides for pages I deleted?

They become orphaned. You can remove them from the Configuration panel to avoid confusion.

Why does SeaText not work on localhost?

Development URLs are restricted for security reasons. SeaText cannot reliably associate traffic with your account on dynamic development domains.

Do I need to re-edit the AI variants after a URL change?

No. The variants are tied to the page content, not the URL. Once the mapping is updated, the existing variants should apply to the new URL.

How the SeaText–Odoo connection works

SeaText does not push data into Odoo's database. Instead, it injects a JavaScript snippet into your Odoo website pages. That snippet reads the page DOM, applies the active variant (test version, translated copy, personalized content), and sends analytics events back to SeaText. Because the variant logic runs in the browser, every visitor sees the correct version instantly — there is no background job, cron task, or API sync to configure.

This client-side approach means the sync is continuous and real-time. When you publish a new variant in the SeaText dashboard, the next page view on your Odoo site fetches the updated variant map and applies it. No Odoo cache clear or module upgrade is needed. The process is invisible to your visitors and requires no ongoing maintenance from your team.

Install the SeaText snippet in Odoo

Before you can install the script, you need a SEATEXT AI account. If you don't have an account yet, you can create one on the SeaText website. The installation process is secure, and the AI remains inert until activated, ensuring the integrity of your website's content.

1. Log in to your Odoo account and access the Website module from the dashboard.
2. Within the Website module, navigate to the page you wish to edit and click on the Edit button to open the editing panel.
3. In the editing panel, scroll through the Blocks panel until you reach the Dynamic Content section.
4. Locate the Embed Code module within the Dynamic Content section and drag it into the desired location on your website editor.
5. Once the module is placed, click on the Edit button located in the right panel to input the code.
6. In the pop-up window that appears, paste the JavaScript snippet provided by SEATEXT AI into the designated area, then click Save to apply the changes.
7. To ensure the block is hidden from view on desktop devices, select the Hide on Desktop option in the Visibility section. After making this adjustment, click on Save once more to finalize your changes.

Repeat these steps for each page that should run SeaText variants. The snippet is the same across pages; SeaText's dashboard controls which variants fire where. You have now successfully installed SEATEXT AI on your website using JavaScript.

What "variant changes" means in this context

SeaText creates variants for three main use cases:

• A/B test copies — alternative headlines, CTAs, or body text generated by the AI Copy A/B Testing agent. This agent generates copy variants and scales the winners automatically.
• Translations — full-page or segment-level translations across 125 languages via the Website Translation agent. This unlocks global search traffic with one click.
• Personalizations — real-time copy swaps based on visitor source, behavior, or profile via the AI Personalization agent. This adapts site copy in real time to visitor context.

When you publish a new variant in the SeaText dashboard, the next page view on your Odoo site fetches the updated variant map and applies it. No Odoo cache clear or module upgrade is needed. The variant map is fetched from SeaText's CDN on every page view, so changes propagate instantly.

Verify that variants are live

1. Open an incognito browser window and visit the Odoo page where you embedded the snippet.
2. Open the browser dev tools → Console. Look for a log line like SeaText: variant applied or network request to api.seatext.com.
3. In the SeaText dashboard, open the Live Preview for the same URL. The preview should match what you see in incognito.
4. If you run an A/B test, check the Experiments report after a few visits — traffic should split across variants.

If the variant does not appear, confirm the Embed Code block is not inside a cached Odoo snippet block and that the page is published (not in draft). Also verify that the page URL matches the primary URL associated with your SeaText account.

Common misconfiguration pitfalls

When you need a fresh snippet

Regenerate the JavaScript snippet in the SeaText dashboard only when:

• You add a new domain (each domain gets its own account and snippet).
• You rotate the API key for security.
• SeaText support instructs you to upgrade the snippet version.

After regenerating, replace the code in every Embed Code block across your Odoo pages. Remember that each SEATEXT AI account is linked to a single primary URL. If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain.

Limitations of the client-side approach

• SEO crawlers — Googlebot executes JavaScript, so translated or tested content is indexable. Other bots (some social scrapers, older crawlers) may see the original Odoo content.
• Server-side personalization — SeaText cannot modify Odoo backend data (product prices, stock, ERP fields). Variants only affect rendered HTML.
• First-contentful-paint flicker — On slow connections, the original text may flash before the variant applies. The edge-install option (Cloudflare Workers) eliminates this.
• Dynamic development domains — These may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account.

Key facts

FAQ

Do I need to clear Odoo cache after publishing a new SeaText variant?

No. The variant map is fetched from SeaText's CDN on every page view. Odoo's HTML cache only stores the page shell with the Embed Code block; the variant swap happens in the browser.

Can I sync SeaText variants into Odoo product fields (e.g., product.description)?

No. SeaText operates on the rendered frontend. It does not write back to Odoo models. If you need translated product descriptions stored in Odoo, use Odoo's native translation tools or a connector that writes to the database.

What happens if I uninstall the Embed Code block?

Variants stop rendering immediately. The SeaText dashboard still holds your variant data, but no visitor will see them until you re-add the snippet.

Does SeaText work with Odoo's multi-website feature?

Yes. Create a separate SeaText account for each Odoo website (each gets its own primary URL). Embed the corresponding snippet on each website's pages.

How do I test a variant on a staging Odoo instance?

Staging domains (e.g., staging.example.com) count as separate primary URLs. Create a dedicated SeaText account for the staging domain, install its snippet, and test there. Do not use the production snippet on staging.

Can I control which Odoo pages run which variants without editing each page?

Yes. In the SeaText dashboard, use URL targeting rules (exact match, regex, path prefix) to activate variants only on specific paths. The same snippet stays on every page; the dashboard decides what fires where.

What if I need to use SeaText on multiple domains?

You must create separate accounts for each domain. Each SEATEXT AI account is linked to a single primary URL. This ensures traffic is correctly associated with your account and variants fire on the right domain.

Is the installation process secure?

Yes. The installation process is secure, and the AI remains inert until activated, ensuring the integrity of your website's content. The snippet only activates when you publish variants in the SeaText dashboard.

What happens if I use a development domain like localhost?

Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain for these cases. Dynamic development domains may not function properly, as SEATEXT AI might be unable to reliably associate traffic with your account.