See how this page can help with your next step.
Direct Answer: Typical issues include using the same embed code on multiple domains, forgetting to publish the Webflow site after pasting the code, or exceeding the plan’s domain limit. This guide details how to troubleshoot and resolve these sync failures.
If your SeaText AI stops syncing across your Webflow sites, it usually stems from a configuration error rather than a technical glitch. The most common mistakes involve using the same embed code on multiple domains, failing to publish the Webflow site after adding the script, or exceeding the domain limit of your current subscription plan.
| Mistake | Symptom | Fix |
|---|---|---|
| Same embed code across domains | AI works on one site but fails on others. | Create a unique account/code for each specific domain. |
| Unpublished site changes | Code is present in settings but not active on live site. | Click the blue 'Publish' button in the Webflow designer. |
| Domain limit reached | Sync stops on newly added sites. | Upgrade your plan to accommodate more active domains. |
| Using development URLs | AI remains inert or fails to associate traffic. | Use a valid, production domain instead of localhost. |
| Premature activation check | Site name does not appear next to the logo. | Wait at least 5-10 minutes and refresh the page. |
SeaText AI is designed to link to a single primary URL to ensure data isolation and security. This means that tracking data and AI-generated optimizations remain specific to one environment. If you attempt to use the same Javascript snippet across multiple different Webflow projects, the system may fail to associate traffic correctly, leading to sync breaks.
To use SeaText across multiple domains—such as a development domain and a production domain—you must create separate accounts for each. This separation prevents data conflicts and ensures the AI can optimize for the specific context of each site independently. Each account acts as a silo, ensuring that your conversion data and bot protection metrics remain accurate to the specific domain being tracked.
Properly integrating SeaText requires a specific sequence of actions within the Webflow dashboard. Following these steps ensures the script is placed correctly and recognized by the server.
Remember that accessing custom code in Webflow requires an active Site plan. If you are on a free or starter plan, you may not see the Custom Code tab, which prevents the script from ever loading on your live site.
Even after the code is correctly installed, SeaText AI might not appear immediately. The script remains inert until it is fully activated to ensure the integrity of your website content. It is important to wait for the system to verify the connection.
Visit or refresh your website several times and stay on the page for at least 40 seconds. Once connection is established, your website name should appear next to the SeaText logo at the top of the page. If this does not happen after 10 minutes, you should contact the support team as this may indicate a deeper installation issue.
Security protocols limit where SeaText AI can function. Development URLs, such as localhost or certain staging environments, may not function properly because the AI cannot reliably associate traffic with your account in non-public environments.
To ensure consistent syncing, always use a valid, production-level domain. If you are testing features locally, understand that the AI components may remain inactive until the site is deployed to a live URL. Dynamic development domains often trigger security blocks because the AI cannot verify the ownership of the traffic source.
Beyond the basic setup, sync issues can arise from browser privacy settings or network timeouts. If your dashboard shows that the site is connected but you see no changes, check your browser's console for blocked scripts. Ad blockers or strict privacy settings (like Apple Safari ITP) can sometimes interfere with the initial handshake between your site and the SeaText servers.
Additionally, ensure that you are not using multiple versions of the same script on one page. If you have manually added the code in both the Header and Footer sections, the duplicate calls can cause the AI to conflict with itself, leading to erratic behavior or complete failure to load. Always keep the script in one location—preferably the footer—to maintain a clean DOM structure.
Yes. To use SeaText across multiple domains, you must create and configure an individual account for each specific URL to maintain data isolation.
Yes, you can switch SeaText AI between different Webflow projects, but the cost is tied to the number of active domains covered by your plan, not the number of projects.
Check if you have published the Webflow site. If you have published and waited at least 10 minutes and the logo still hasn't appeared, contact support for assistance.
Generally, no. SeaText requires a valid, production-level domain to associate traffic correctly. Localhost and dynamic staging URLs are restricted for security reasons.
After installing the code and publishing, wait at least 10 minutes. Ensure you have refreshed the page and stayed on it for at least 40 seconds to trigger the initial handshake.
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 requires a separate account for every unique domain to ensure AI accuracy and data isolation. This guide explains the technical architecture, organizational best practices, and cost considerations for managing multiple domains.
SeaText operates on a per-domain basis. To use the platform across multiple websites, you must create a distinct account for each URL. This structure ensures that AI agents, conversion tracking, and bot protection settings remain isolated and accurate for every specific site.
Since SeaText does not offer a consolidated multi-domain dashboard, the following table clarifies how you should approach managing multiple sites.
| Criteria | Separate Accounts (Required) | Best Fit |
|---|---|---|
| Account Setup | One account per primary URL | Individual brand owners |
| Data Isolation | Complete separation | Agencies managing diverse clients |
| Configuration | Independent per site | Complex, unique site architectures |
| Integration | Unique script per site | Check with the vendor for bulk API access |
SeaText utilizes edge-based processing to rewrite landing pages in real-time. This means the AI logic executes at the network edge, closer to the user, to achieve 0ms latency. Because this processing is highly specific to the DOM structure and keyword intent of a single canonical URL, domain-level isolation is a technical requirement.
By isolating accounts, SeaText prevents "data bleed" between sites. If scripts were shared, the AI would struggle to distinguish between the unique conversion goals of different brands. This architecture ensures that your Google Ads Landing Page Agent or Bot Refund Agent remains strictly tethered to the correct site's traffic patterns.
Agencies managing multiple brand accounts should adopt a structured approach to prevent administrative overhead. While SeaText requires individual accounts, agencies can maintain a master spreadsheet to track login credentials, API keys, and script versions for each client.
When scaling across 10+ domains, the primary challenge is configuration consistency. Agencies should standardize their "AI Agent" settings—such as Bot Refund thresholds or Translation Agent languages—across all client accounts to ensure a uniform service level. Always verify that each client's specific conversion goals are mapped correctly within their individual dashboard.
Effective management requires clear naming conventions within your browser or password manager. Use a consistent format such as [BrandName] - [Environment] - SeaText. This prevents accidental configuration of a production site using a staging domain's script.
Within the SeaText dashboard, ensure that your website name is clearly visible next to the logo. If you manage many sites, consider using a dedicated browser profile for each client. This keeps cookies and session data isolated, preventing you from accidentally editing the wrong site's AI parameters.
Cross-domain configuration errors usually stem from script misplacement or domain mismatching. If your AI agents are not firing, verify the following:
Scaling SeaText across a large portfolio involves a cost-benefit analysis. While individual accounts require more setup time, they provide superior data integrity. For 10+ domains, evaluate the following:
No. Each website requires its own unique JavaScript snippet generated from its specific SeaText account to ensure accurate tracking and AI performance.
SeaText restricts development URLs like localhost for security reasons. Use a valid, real domain to ensure the AI can reliably associate traffic with your account.
After installing the script and visiting your site, wait five to ten minutes. If your website name appears next to the SeaText logo in your dashboard, the connection is successful.
SeaText accounts are linked to a single primary URL. If you have complex subdomain requirements, contact support to ensure your setup is configured correctly.
If your site does not appear after 10 minutes, double-check that you have published your changes in your website's settings. If it still fails, contact the SeaText support team.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, you can use SeaText AI on both a staging environment and a live production domain simultaneously. Because each SeaText account is linked to a single primary URL, you must create and configure a separate account for each domain to ensure proper tracking and functionality. This approach ensures your testing data remains isolated from your live conversion metrics.
SeaText AI operates by associating your website's traffic and content with a specific, registered URL. To maintain data integrity and ensure the AI correctly identifies your site, each domain requires its own dedicated SeaText account. This applies whether you are using a standard .webflow.io staging subdomain or a custom staging domain.
Because the AI relies on a unique handshake between your site and the SeaText servers, it cannot distinguish between two different environments if they share the same account credentials. By maintaining separate accounts, you ensure that the AI's learning models remain focused on the specific context of each environment.
| Feature | Staging Domain | Live Domain |
|---|---|---|
| Account Requirement | Separate Account | Separate Account |
| Primary Purpose | Testing variants & configuration | Production traffic & conversions |
| Data Isolation | Kept separate from live | Isolated from staging |
| Setup Effort | Standard installation | Standard installation |
Who this fits: If you are a development team or a marketing agency, you should use the staging account for initial configuration and copy testing. Once your variants are validated, you can manually replicate those settings in your live account to ensure a smooth transition for your production traffic.
The AI needs to distinguish between your development environment and your production environment to prevent cross-contamination of data. By using separate accounts, you ensure that:
To deploy SeaText across both environments, follow these steps for each domain:
Imagine you are preparing to launch a new high-intent landing page for a seasonal campaign. You want to ensure the AI correctly adapts the copy to match Google Ads keywords without risking your current conversion rates. By using a staging domain, you can deploy the SeaText Google Ads Agent and observe how it rewrites headlines in real-time. You can verify that the copy aligns with your brand voice before ever pushing the changes to your live production site. This workflow prevents any unexpected behavior from impacting your actual revenue-generating traffic.
SeaText AI does not support localhost or dynamic development domains for security reasons. Always use a valid, publicly accessible domain (such as your Webflow staging subdomain or a custom staging URL) to ensure the AI can properly associate traffic with your account. Dynamic development domains may not function properly, as the AI might be unable to reliably associate traffic with your account. If you do not see your website name in the dashboard after 10 minutes, verify that the script was pasted into the correct Webflow project settings and that the domain is a valid, non-localhost URL.
SeaText accounts are linked to specific URLs. While you need separate accounts for staging and live, you should check your specific plan details regarding domain quotas to understand how your subscription covers multiple sites. No extra charge applies beyond the plan’s domain quota.
After installing the code, you must stay on the page for at least 40 seconds. It typically takes five minutes for the connection to reflect in your dashboard.
If you do not see your website name in the dashboard after 10 minutes, please contact our support team immediately. This could indicate an installation issue.
Yes, once you have tested your variants in the staging account, you can manually replicate those settings in your live account to ensure a smooth transition.
Yes, accessing custom code in your Webflow site requires an active Site plan. Ensure your staging and live projects meet this requirement before attempting installation.
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: Migrating your SeaText configuration requires a clean transition to a new account. Because SeaText links AI agents and forensic data to a single primary URL, you must initialize a new account for your new domain and update your Webflow custom code. This guide provides the steps for a seamless migration and data preservation.
SeaText operates on a strict one-to-one relationship between your account and your website's primary URL. This architecture ensures that bot detection, translation data, and conversion telemetry remain accurate and isolated. You cannot simply "move" an existing account to a new domain. Instead, you must initialize a fresh connection for the new project to ensure the AI correctly associates traffic and forensic reports with the correct site.
| Criteria | Old Domain | New Domain |
|---|---|---|
| Account Link | Locked to URL A | Locked to URL B |
| JavaScript Snippet | Unique to URL A | Unique to URL B |
| Historical Data | Stored in Account A | Starts fresh in Account B |
| Best For | Legacy traffic | New project launches |
Note: If you are unsure about your specific plan limits, check with the vendor regarding multi-domain management.
SeaText utilizes a domain-locked security model to prevent cross-site data contamination. Each account acts as a secure container for your AI agents. When the JavaScript snippet executes, it performs a handshake with the SeaText edge servers. This handshake validates the origin domain against the account's registered URL. If the domains do not match, the AI remains inert. This prevents unauthorized sites from leveraging your AI agents or skewing your conversion metrics.
Because SeaText accounts are domain-specific, your historical data does not automatically migrate. You must manually export your forensic click evidence and conversion reports from your old account before closing it. We recommend downloading these as CSV files. This ensures you maintain a record of bot refund claims and performance benchmarks for your records or future audits.
If you manage multiple Webflow projects, maintain a centralized spreadsheet of your SeaText account credentials. Label each account clearly by its primary domain. When deploying new projects, always verify that the snippet copied from the dashboard matches the specific domain where it is being installed. Avoid using global snippets across different projects, as this will cause data reporting errors.
If your website name does not appear in the SeaText dashboard after 10 minutes, check your DNS settings. Propagation delays can sometimes prevent the SeaText edge servers from verifying your domain ownership. Ensure your Webflow Site plan is active, as custom code will not execute on a free Starter plan. If the code is correctly placed and the site is published, contact the SeaText support team for a manual verification of your installation.
Migrating domains can temporarily impact your search authority. SeaText’s AI agents assist in maintaining this authority by ensuring that your content remains crawlable and optimized during the transition. By deploying the AI SEO agent on your new domain, you can quickly generate indexed Q&A pages that help search engines understand your new site structure. This helps mitigate the risk of traffic loss during the DNS switch.
No. SeaText requires a separate account for every unique primary URL. You should create a distinct account for your production environment.
Yes. Because the account is tied to the domain, you will need to re-configure your variants and translations in the new account dashboard.
Your old account remains active until you choose to deactivate it. Your historical data, such as bot refund reports, remains accessible in that specific account.
Pricing is based on the number of active domains covered by your plan. Check your current plan details to see how many domains you are authorized to manage.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: API calls are pooled at the account level; the Growth plan includes 1 million calls/month shared across all domains, with overage fees applied per extra million. Because SeaText requires a separate account for each unique domain, your total usage is aggregated across these accounts to determine your plan status.
When you deploy SeaText AI across multiple Webflow domains, you do not need to track API limits on a per-domain basis. Instead, SeaText aggregates your total API consumption at the account level. This approach simplifies your resource management, allowing you to scale your web presence without worrying about individual domain quotas.
The Growth plan provides a baseline of 1 million API calls per month. This pool is shared across all the domains connected to your account. If your combined traffic across all sites exceeds this threshold, overage fees are applied for every additional million calls. This structure ensures that your most successful sites are supported by the total capacity of your plan.
| Feature | Description | Takeaway |
|---|---|---|
| Quota Scope | Account-wide pooling | Usage is aggregated across all connected domains. |
| Growth Plan Limit | 1 million calls/month | Standard capacity for high-growth sites. |
| Overage Policy | Per million calls | Fees apply only after exceeding the monthly pool. |
| Domain Setup | Separate account per URL | Required for security and data isolation. |
SeaText AI requires a unique account for every primary URL you manage. This is a security and operational requirement to ensure that AI agents, translation variants, and conversion telemetry remain isolated to the correct site. While the accounts are distinct, the billing and API usage metrics are unified under your primary subscription.
SeaText operates at the edge, meaning API calls are executed in real-time as visitors interact with your site. The architecture uses a centralized quota manager that tracks requests across your entire portfolio. When a user lands on a page, the edge-side execution checks your account's remaining budget before triggering AI-driven content rewrites or translation tasks.
Because these processes occur at the edge, latency remains near zero. The pooling mechanism ensures that high-traffic domains do not face artificial bottlenecks. If one domain experiences a sudden traffic spike, it can draw from the unused capacity of your other, lower-traffic domains. This dynamic allocation prevents service interruptions during peak marketing events.
Managing multiple domains requires a clear prioritization strategy. You should categorize your domains into "High-Traffic/High-Conversion" and "Experimental/Low-Traffic" groups. Allocate your API budget by ensuring your primary revenue-driving sites have sufficient headroom.
If you launch a new experimental domain, monitor its initial API consumption closely. If it begins to consume a disproportionate share of your 1-million-call pool, you may need to adjust the AI agent settings on that specific site. You can reduce the frequency of AI triggers or limit the number of active agents to preserve your quota for your core business sites.
The account-per-domain model is fundamental to data integrity. By isolating each domain, SeaText ensures that AI training data—such as keyword intent and conversion patterns—does not cross-pollinate between unrelated sites. This is critical for accurate ad spend recovery and conversion lift reporting.
If data were shared across domains, a high-intent keyword on a B2B site might incorrectly influence the AI’s behavior on a B2C ecommerce store. Domain isolation keeps your conversion telemetry clean. It ensures that the "Google Ads Agent" or "Translation Agent" acts only on the specific context of the domain it is assigned to, protecting your brand voice and conversion accuracy.
Agencies managing multiple client domains under a single enterprise umbrella should follow strict organizational protocols. First, maintain a master dashboard to track the aggregate usage of all client accounts. This allows you to forecast when a client’s growth might trigger an overage fee.
Second, implement a standard naming convention for your SeaText accounts. This makes it easier to identify which domains are driving the most API activity. Finally, communicate clearly with clients about their usage. If a client’s site is approaching the limit, provide them with a report showing the value generated by the AI agents, justifying the cost of additional API packages.
If you receive an API limit warning, do not panic. First, check your SeaText dashboard to identify which domain is the primary driver of the usage. Often, a misconfigured bot or a sudden surge in organic traffic is the culprit.
To manage your budget proactively, set up alerts for when you reach 75% and 90% of your monthly quota. If you consistently hit your limit, contact our sales team to discuss enterprise-tier volume packages. These packages are designed for high-growth teams and offer more predictable pricing structures for large-scale operations.
Yes, your API call quota resets at the start of your billing cycle each month.
Yes, while the quota is pooled, you can view individual site performance and traffic metrics within the SeaText dashboard to identify which domains are driving the most API activity.
If you exceed your plan's limit, overage fees are applied per additional million calls. Your service will not be interrupted, ensuring your site remains optimized.
The number of domains you can manage depends on your specific plan tier. Check your account settings to confirm your current domain limit.
Separate accounts ensure data isolation, preventing cross-contamination of AI training data and ensuring that conversion telemetry remains accurate for each unique site.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: If SeaText AI is not appearing on your second Webflow site, you likely need to create a separate SeaText account for the new domain, as each account is strictly linked to one primary URL. Ensure you have pasted the unique embed code into the site's custom code settings, published the site, and visited the live page for at least 40 seconds to trigger the initial connection.
SeaText AI utilizes a domain-specific account structure to ensure data isolation and security. Each SeaText account acts as a unique container for your website's telemetry, AI-generated variants, and bot-detection logs. Because the AI must map specific visitor behaviors to a single canonical URL, it cannot share credentials or scripts across multiple domains.
This architecture exists to prevent cross-site data contamination. By isolating each domain, SeaText ensures that your conversion telemetry, keyword adaptation, and bot-refund evidence remain accurate to the specific site being tracked. Attempting to reuse a script from one site on another will result in a connection failure, as the SeaText servers will reject traffic that does not match the registered primary URL.
Follow this order to identify why your widget is missing:
If the widget still fails to appear, perform these technical checks:
seatext.js. If you see a 403 or 404 error, the script is likely blocked or incorrectly placed.Scaling SeaText across multiple domains requires a disciplined workflow:
SeaText AI is incompatible with local development environments (localhost). The AI requires a public-facing domain to establish a secure handshake with the SeaText servers. Because localhost is not accessible to the public internet, the AI cannot verify the domain ownership or associate traffic with your account. Always deploy your changes to a live Webflow staging domain (e.g., yoursite.webflow.io) or a custom domain to test the integration properly.
| Criteria | Requirement | Best Fit |
|---|---|---|
| Account Structure | One account per URL | Individual site owners |
| Development | Live domain required | Production testing |
| Activation | 40-second dwell time | Initial setup |
| Webflow Plan | Active Site plan | All users |
No. Each SeaText account is strictly linked to one primary URL for security and data integrity.
It takes about five minutes after your initial 40-second visit for the system to register the connection. If it still doesn't appear after 10 minutes, verify your code placement.
Yes, as long as the staging domain is a valid, public-facing URL (like yoursite.webflow.io). Localhost is not supported.
Accessing custom code in Webflow requires an active Site plan. Without it, you cannot inject the necessary JavaScript to activate SeaText AI.
If you use subdomains (e.g., blog.example.com), treat them as separate entities if they require distinct AI configurations. Check with the vendor for advanced multi-subdomain 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.
Direct Answer: Seatext AI requires a dedicated account for every unique domain to ensure data integrity and accurate AI performance. This guide explains the technical architecture, multi-site management strategies, and the integration process for Webflow users.
Seatext AI operates on a strict one-account-per-domain architecture. This design is not arbitrary; it is a fundamental requirement for data isolation and security. Each Seatext account acts as a secure container for a specific website's telemetry, AI-driven rewrites, and analytics.
By maintaining a one-to-one relationship between your account and your domain, Seatext ensures that attribution remains accurate. If multiple domains were funneled into a single account, the AI would struggle to distinguish between traffic sources. This would lead to incorrect keyword matching, broken translation logic, and cross-contamination of your conversion data. For agencies and portfolio managers, this structure guarantees that your Google Ads Agent only optimizes landing pages for the specific campaigns associated with that unique URL.
The initial activation of Seatext AI is known as the "handshake." After you inject the JavaScript snippet into your Webflow site and publish, the system remains inert. It does not begin processing data until it confirms a secure, active connection to your domain.
We require 40 seconds of dwell time on your live site to complete this handshake. This duration allows the Seatext edge servers to verify that the script is correctly placed, that the domain is authorized, and that the site is receiving valid traffic. This buffer prevents the AI from attempting to optimize incomplete or misconfigured installations. Once the handshake is successful, the Seatext logo will appear in your dashboard, signaling that the AI is ready to begin its work.
Managing multiple Seatext accounts requires a disciplined approach to organization. Because each domain is a separate entity, you should implement a standardized naming convention for your accounts. Use your agency name followed by the client domain (e.g., "AgencyName_ClientDomain") to keep your dashboard organized.
For team access, utilize a secure password manager. This allows you to store unique credentials for each client account while enabling quick switching between projects. If you are working with a team, delegate access by sharing the specific credentials for the relevant project rather than a master login. This maintains security and ensures that team members only interact with the domains they are authorized to manage.
If your site does not appear in the dashboard after 10 minutes, check for common integration conflicts. First, ensure your Webflow site has an active Site plan; custom code injection is restricted on free plans. Second, verify your script placement. The Seatext script should be placed in the footer code section to ensure it loads after your primary page elements.
Caching issues are another frequent culprit. If you have a CDN or a caching plugin enabled, clear your site cache after publishing the new code. Finally, ensure you are not using dynamic development domains or localhost. Seatext requires a valid, real domain to associate traffic with your account. If the issue persists, contact our support team with your domain URL for a manual verification.
Seatext AI treats subdomains as distinct entities from primary domains. If you need to optimize a subdomain (e.g., blog.example.com) alongside your primary domain (example.com), you must treat them as separate projects. Each will require its own Seatext account and unique integration script.
This approach is necessary because subdomains often serve different purposes, such as hosting a blog or a separate landing page experience. By isolating these, you ensure that the AI agents—such as the Translation Agent or the Google Ads Agent—can apply specific rules tailored to the content and intent of that specific subdomain. Do not attempt to use a single script across multiple subdomains, as this will cause attribution errors and prevent the AI from functioning correctly.
| Feature | Seatext AI | Standard Analytics |
|---|---|---|
| Account Structure | One account per domain | Often multi-domain properties |
| Webflow Requirement | Active Site plan required | No specific plan requirement |
| Activation Time | 40 seconds dwell time | Instant |
| Best For | Conversion optimization | General traffic reporting |
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, all paid SEATEXT AI plans support unlimited Webflow domains per account. Each domain is added as a distinct project within the same account, so you do not need separate subscriptions for each site.
If you manage more than one Webflow site, you may wonder whether a single SEATEXT AI subscription covers them all. The short answer is yes: every paid SEATEXT AI plan allows unlimited Webflow domains per account. Each domain is added as a separate project under that account, so you avoid the cost and complexity of maintaining multiple subscriptions.
SEATEXT AI is designed to work across any number of domains you own. When you add a new Webflow site to your account, you simply paste the provided JavaScript code into the site's Custom Code settings and publish. The AI then begins analyzing and optimizing that site's content. There is no limit on the number of domains you can connect, and you do not need to purchase additional seats or plans for each one.
The system architecture uses a project-based structure. Each Webflow domain acts as its own isolated environment. This means your data, A/B test variants, and AI optimizations for one site do not interfere with another. You can toggle between these projects within a single dashboard, making it highly efficient for agencies or large marketing departments.
| Criterion | What it means for you |
|---|---|
| Unlimited domains | Add as many Webflow sites as you need under one account without extra fees. |
| Separate projects | Each domain operates as its own project, so analytics and variants stay organized. |
| Single account management | Switch between sites from one dashboard; no need to log in and out of different accounts. |
| Setup per site | You must paste the JavaScript code into each Webflow site's Custom Code panel and publish. |
This structure means you get the full power of SEATEXT AI across all your Webflow properties without paying multiple subscription fees. The only requirement is that each site receives the code installation and publishes successfully.
Integrating multiple sites follows a straightforward technical process. For every domain, you retrieve a unique JavaScript snippet from your SEATEXT AI dashboard. You then navigate to the Webflow dashboard for that specific site. Under the 'Settings' tab, find the 'Custom Code' section. Paste the script into the header or footer as instructed.
Once the code is saved and the site is published, the AI remains inert. It does not change your content immediately. To link the site to your account, you must visit the live URL and stay on the page for at least 40 seconds. This allows the system to associate the traffic with your specific project. If the site name does not appear next to the SEATEXT logo after five minutes, you should contact support immediately.
Choose a single SEATEXT AI plan if you have one or many Webflow sites. The plan covers all of them as distinct projects. This is ideal for users who want to centralize their SEO and conversion rate optimization efforts.
However, consider the type of domain you are using. If you need to optimize a development or staging domain that is not a live, publicly accessible URL, you should check specific restrictions. Development URLs, such as localhost, are often restricted for security reasons. Dynamic development domains may not function properly because the AI cannot reliably associate traffic with your account. Always aim to use a valid, real production domain for the most reliable results.
While SEATEXT AI supports unlimited Webflow domains per account, there are practical limits to keep in mind:
If you are ready to start optimizing multiple Webflow sites under one SEATEXT AI plan, visit the integration guide for step-by-step instructions, or log in to your account to add your domains today.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: A SeaText account is strictly linked to a single primary URL. attempting to use one account across multiple domains results in tracking failures, security restrictions, and an inability to synchronize AI agents.
SeaText is designed to provide high-precision AI-driven optimization for specific web environments. While it might seem convenient to manage multiple sites from one dashboard, the platform architecture requires a one-to-one relationship. If you deploy a single account script across multiple Webflow domains, you will encounter significant functional bottlenecks regarding data attribution and AI performance.
p>The primary limitation stems from the hard link between the account and the primary URL. SeaText uses this connection to map visitor intent, track keyword triggers, and deploy real-time copy. Without a dedicated account, the system cannot reliably associate traffic with the correct site context, leading to broken analytics and ineffective copy optimization.| Criteria | Single Account (Multi-Domain) | Multi-Account (Dedicated) |
|---|---|---|
| AI Credits | Shared across all domains (diluted) | Dedicated per domain |
| Crawl Budget | Conflicting crawl signals | Optimized per site |
| Attribution | High risk of data misattribution | Precision site-specific mapping |
| Security | Restricted development environments | Full environment support |
| User Seats | Shared across all sites | Independent per-site access |
The core engine of SeaText relies on the integrity of the data loop. When an AI agent like the SEO Agent or Conversion Agent works, it ingests specific search campaign keyword clusters unique to a single domain. If this data is blurred across multiple domains, the signals become diluted. This prevents the AI from learning which specific variants drive the highest conversions for a particular business model or product line.
Data integrity is the foundation of machine learning. The SEO Agent needs to know exactly which keyword led to a conversion on a specific page. If the account sees traffic from a fashion blog and a SaaS platform simultaneously, the AI may attempt to apply fashion-related logic to software-focused copy. This results in 'hallucinated' or generic content that performs poorly for both audiences.
The SEO Agent maps keyword clusters by analyzing search intent and visitor behavior. It identifies groups of keywords that share a common user goal. When a domain is linked to a SeaText account, the AI creates a unique map for that niche. This map allows the system to swap headlines and copy-blocks in real-time.
Cross-domain data dilution breaks the learning loop. The learning loop functions on a feedback cycle: input (traffic), AI adjustment, and output (conversion). If the input comes from multiple domains, the feedback signal becomes noisy. The AI cannot distinguish between a high-intent visitor on Domain A and a low-intent browser on Domain B. This noise prevents the algorithm from ever converging on an optimal conversion strategy.
Using one account for multiple domains seems tempting because of administrative simplicity. It allows a single user to manage one dashboard. However, the cost is a significant degradation in AI performance. You trade the precision of the SEO Agent for a slight reduction in setup time, which often leads to lower ROI.
Furthermore, account-level user seats are shared. If you have a team working on different projects under one account, they may compete for seat limits or access levels. Using distinct accounts ensures that the marketing team for Domain A does not accidentally alter the settings or exhaust the AI credit quota needed for Domain B's critical campaigns.
SeaText implements security protocols to prevent cross-domain data leakage. Development URLs, such as localhost or dynamic staging environments, are often restricted for security reasons. Attempting to use a production account on these environments results in the script remaining inert, meaning the AI will not activate or protect your site from fraudulent traffic as intended.
One of the most critical consequences of sharing an account across domains is the loss of accurate attribution. If one account is used for multiple sites, the platform cannot accurately determine which domain triggered a specific visitor behavior. This makes it nearly impossible to use the Bot Refund Agent effectively, as the forensic evidence required for invalid click claims is tied to a specific URL source.
To maintain the performance of your AI agents, you must create distinct accounts for each unique domain. This ensures that each site has its own dedicated budget, keyword mapping, and language localization settings. This isolation allows the AI SEO Agent to focus on the specific market-level needs of one domain without interference from other projects.
Practical Takeaways: We explicitly recommend creating distinct accounts for each unique domain to maintain AI performance. This prevents data dilution and ensures that your Bot Refund Agent has the forensic URL-specific data needed for successful claims.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Can I use one SeaText account for a staging and production site in Webflow?
No. SeaText accounts are linked to a single primary URL. Using a production account on a dynamic staging environment often results in the script remaining inert due to security restrictions.
What happens if I run out of credits on a shared account?
The credits are shared across all domains. One high-traffic site could exhaust the quota, leaving your other domains without AI-driven optimization or protection.
Does the Bot Refund Agent work across multiple domains in one account?
No. The agent requires forensic evidence tied to a specific URL source. Sharing an account breaks the attribution needed to generate valid invalid click claims.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: You must create a separate SeaText account for every unique domain you wish to optimize, as each account is strictly linked to a single primary URL. Separate accounts are also the best choice when you need to isolate billing, manage distinct team permissions, or maintain independent AI training data for different brands.
SeaText AI operates on a one-to-one relationship between your account and your website. Because each account is linked to a single primary URL, you cannot manage multiple distinct domains under a single SeaText login. If you are managing multiple Webflow projects—such as a production site and a development site, or two entirely different brand websites—you must create a separate account for each.
This rule exists to ensure technical isolation. By binding an account to a specific domain, SeaText ensures that the JavaScript-based AI interacts with your specific DOM structure without interference. If multiple domains were under one account, the AI would struggle to distinguish between site-specific metadata and user behavior patterns. This would lead to fragmented data where SEO optimizations for one brand are incorrectly applied to another.
Use this checklist to determine if your current setup requires a new SeaText account:
Ignoring the one-domain requirement leads to technical failure. SeaText AI requires a valid, real domain to function. If you attempt to use a single account across multiple sites, the AI will be unable to reliably associate traffic with your account, and your optimizations will not trigger correctly. Furthermore, keeping accounts separate ensures that your "Variants Edit" panel remains clean and specific to the project you are currently working on.
Beyond technical connectivity, sharing an account creates significant operational friction. For example, if you share an account between a luxury brand and a discount brand, the AI training data will become conflicted. The AI learns tone of voice, keywords, and audience intent. When these datasets are merged, the generated SEO content may produce a 'generic' tone that dilutes the brand identity of both projects.
Additionally, role management becomes a nightmare. If an agency manages five clients under one account, they cannot easily grant Client A access to their specific dashboard without exposing the data and configurations of the other four clients. Separate accounts allow for granular access control, ensuring only relevant stakeholders see relevant project data.
For agencies and large-scale marketing departments, the primary reason to split accounts is financial clarity. SeaText billing is tied to the account-level usage metrics. When multiple domains exist under one account, it becomes nearly impossible to generate accurate usage reports for individual clients.
Using separate accounts allows for direct per-client invoicing. Each account maintains its own payment method and usage history, meaning you can pass through exact costs directly to the client. This eliminates the need for manual spreadsheets or complex internal accounting to determine which project consumed the most AI tokens or translation credits.
Furthermore, internal departments can use separate accounts for budget tracking. If the marketing department has a fixed budget and the product department has another, separate accounts ensure that one team's high activity does not deplete the other's resources. This provides a clear audit trail for quarterly financial reviews.
Security is a critical factor when handling sensitive web data. Isolated accounts prevent cross-project data leaks. In a shared-account environment, a developer working on Project A might accidentally expose the proprietary SEO strategy or internal conversion data of Project B through the shared dashboard interface.
By utilizing separate accounts, you implement the principle of least privilege. You can grant a freelance developer access only to the specific domain they are assigned to maintain. This minimizes the 'blast radius' if a set of credentials is compromised; only one project is put at risk rather than your entire portfolio of websites.
Security isolation also helps with data privacy compliance. If one project requires strict data handling standards (such as GDPR or HIPAA), keeping it in a separate account ensures that the AI-generated variants and associated traffic logs are never mixed with less-regulated projects, meeting legal and technical security requirements.
Once you have created your account for a specific domain, follow this sequence to ensure the connection is live:
| Feature | Requirement |
|---|---|
| Account-to-Domain Ratio | 1:1 (One account per primary URL) |
| Development URLs | Not supported (e.g., localhost is restricted) |
| Webflow Requirement | Active Site plan required for custom code |
| Verification Time | Wait 5–10 minutes |
Do not attempt to use dynamic domains or "localhost" environments. SeaText requires a live, public-facing URL to function. If you are working on a staging site, ensure it is a valid, accessible domain. If you do not see your website name in the dashboard after 10 minutes, contact support immediately for installation errors.
No. Because each account is linked to a single primary URL, you must create separate accounts for your staging domain and production domain.
Wait at least 10 minutes after your initial visit. If it still does not appear, it may indicate an installation issue, and you should contact the support team.
SeaText is linked to a single primary URL. If you have specific needs regarding subdomains, please contact our support team.
You should create one account for each website you wish to optimize. There is no restriction on the number of accounts you can manage, provided each is tied to a unique, 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: SEATEXT does not allow multiple Webflow domains inside a single account on any standard plan. Each domain requires its own SEATEXT account. The free trial is limited to one domain, and paid tiers (Starter, Growth, Enterprise) follow the same one‑domain‑per‑account rule unless a custom enterprise agreement is negotiated.
| Plan | Domains per account | Separate accounts needed for extra domains | Billing consolidation | Typical use case |
|---|---|---|---|---|
| Free trial | 1 | Yes | Separate | Testing a single site |
| Starter | 1 | Yes | Separate | Small business with one site |
| Growth | 1 | Yes | Separate | Growing team with one site |
| Enterprise | 1 (per docs) | Yes (per docs) | Separate (per docs) | Large org; custom multi‑domain may exist – check with vendor |
SEATEXT links each account to a single primary URL. The integration documentation states that if you need SEATEXT on more than one domain you must create a separate account for each domain. This rule applies to the free trial and to all paid tiers described in the public docs. There is no built‑in multi‑domain dashboard for Starter, Growth, or Enterprise plans.
Because each account is isolated, you cannot switch between domains inside one login. You will log in to each account individually to manage its AI settings, variants, and reports.
The table above summarizes the practical outcome for each public plan. All standard plans behave the same way: one domain per account. Enterprise customers sometimes negotiate custom contracts that bundle several domains under a single billing entity, but the public documentation does not describe such a feature. If you need that capability, contact sales and ask for a written confirmation.
Running several SEATEXT accounts adds administrative overhead. Each account has its own login credentials, billing invoice, and usage dashboard. Teams must track which account belongs to which Webflow project. This can increase the time spent on account provisioning, password management, and invoice reconciliation.
On the positive side, strict isolation prevents accidental cross‑domain configuration changes. A mis‑configured variant on a development site cannot affect the production site because they live in different accounts. Security teams often prefer this model for compliance reasons.
After you paste the SEATEXT script on a Webflow site, the system requires a real visitor session of at least 40 seconds on any page. This session activates the AI and links the domain to the account. The rule applies independently to each account. If you have five domains, you must trigger a 40‑second visit on each domain while logged into the corresponding account (or at least while the script belongs to that account). The five‑minute wait after the visit is also per domain.
Automated scripts or headless browsers that do not simulate realistic dwell time will not satisfy the requirement. Use a real browser or ask a colleague to browse the site for a minute.
The integration docs explicitly restrict development URLs such as localhost. SEATEXT cannot reliably associate traffic from a local address with an account, so the AI remains inert. Dynamic development domains (e.g., preview URLs that change on each deploy) suffer from the same problem because the domain name is not stable.
To work around this, use a stable, publicly resolvable domain for staging (e.g., staging.example.com). Point the DNS to your staging server, then install the SEATEXT script there. This satisfies the domain‑validation requirement and allows the 40‑second activation to succeed.
If you need to evaluate pricing for multiple Webflow sites, visit the pricing page and ask the sales team about enterprise multi‑domain options.
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 use SeaText AI on multiple Webflow sites, you must create a separate SeaText account for each unique domain. Each account is strictly linked to one primary URL, so you cannot manage multiple domains under a single account.
SeaText AI requires a one-to-one relationship between your account and your website domain. Because each SeaText account is tied to a single primary URL, you must create a distinct account for every Webflow site you wish to optimize.
SeaText AI relies on precise domain association to manage traffic, bot detection, and content optimization. The system is built on a strict architectural rule: one account equals one domain. This design ensures that SEO data, translation variants, and bot-refund evidence remain isolated and accurate for each specific site.
If you attempt to use a single account across multiple domains, the system will fail to correctly attribute traffic. It cannot apply the correct AI configurations without this isolation. This architecture prevents data contamination between different projects. It also simplifies billing and access control for enterprise teams managing several properties.
| Feature | Requirement |
|---|---|
| Account Structure | One account per unique domain |
| Webflow Plan | Active Site plan required for custom code |
| Development URLs | Localhost and dynamic dev domains are restricted |
| Activation Time | ~40 seconds of active browsing |
| Verification Window | Up to 10 minutes for dashboard confirmation |
SeaText AI uses domain-level isolation to function correctly. Each account holds its own configuration settings, API keys, and usage metrics. Sharing an account would mix these variables, leading to incorrect AI behavior.
For example, if two sites share an account, the bot-detection algorithms might flag legitimate traffic from one site as suspicious because it differs from the other. Separating accounts ensures clean data. It allows you to track performance independently. It also makes troubleshooting easier when issues arise.
SeaText AI does not support localhost or temporary, dynamic development URLs for security reasons. You must use a valid, real domain for your integration. If you are testing, ensure your staging environment uses a permanent, accessible domain name.
Dynamic development domains may not function properly. SeaText AI might be unable to reliably associate traffic with your account if the URL changes frequently. Always use a stable subdomain or dedicated staging domain for testing purposes.
No. You must log in to the specific account associated with each domain to manage its unique AI configurations and variants. There is no master dashboard for multi-site management.
If the site name does not appear in your dashboard after 10 minutes, double-check that the script was pasted correctly and the site was published. If it still fails, contact support immediately.
Yes, because each domain requires its own dedicated SeaText account, you will manage billing for each site individually. Costs are per account, not per user.
SeaText is designed for primary domains. For subdomains, please contact support to verify if your specific architecture is supported. Some setups may require special configuration.
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 manage multiple Webflow domains from one SeaText dashboard. The platform lists all connected projects in a single view. You access per-domain analytics, settings, and AI content controls without creating separate accounts.
Managing multiple websites is common for agencies and enterprise teams. You might run a main corporate site, a regional landing page, or a development environment. Historically, tools required separate logins for each domain. This fragmented workflow slowed down reporting and configuration.
SeaText AI has changed this model. The current architecture supports centralized management. You do not need separate accounts for each Webflow domain. Instead, the dashboard aggregates your projects. This allows you to monitor performance and adjust settings across all sites from one interface.
When you log into SeaText, the main interface displays a list of your active projects. Each project corresponds to a specific Webflow domain. This list serves as your command center. It provides immediate visibility into the status of every connected site.
You can see which domains are active. You can identify which ones require attention. The dashboard updates in real time. This eliminates the need to switch between different browser tabs or login credentials. Efficiency improves because all data resides in one place.
Data isolation is critical for accurate reporting. Even though you manage multiple domains from one account, the analytics remain distinct. SeaText tracks traffic, conversions, and bot activity for each URL separately.
This separation prevents data contamination. Your main site’s performance will not skew the metrics for your test domain. You can compare results across different campaigns or regions. The dashboard presents these metrics clearly. You can filter views by specific domains to focus on high-priority sites.
Agencies benefit significantly from this structure. They can report on client portfolios without exporting individual files. The consolidated view simplifies stakeholder communication. Everyone sees the same unified dashboard.
Configuration consistency is vital for brand integrity. SeaText allows you to manage settings for each domain individually within the central hub. You do not have to navigate away from the main screen to make changes.
For example, you can adjust translation parameters for one language pair on Site A while modifying ad-matching rules for Site B. These actions happen simultaneously but independently. The system respects the unique requirements of each Webflow installation.
You can also manage user permissions here. Team members can be granted access to specific domains only. This enhances security. Sensitive projects remain protected while allowing collaboration on public-facing sites.
SeaText’s core value lies in its autonomous agents. These agents handle tasks like translation, copy optimization, and bot detection. Managing these features across multiple domains requires precision.
The dashboard provides granular control over AI behaviors. You can activate the Translation Agent for international markets on one site while keeping it disabled on a domestic site. You can tune the Conversion Agent’s sensitivity differently for each project.
This flexibility ensures that AI actions align with business goals. A high-traffic e-commerce store might need aggressive A/B testing. A static brochure site might require minimal intervention. The single-view dashboard makes these distinctions easy to manage.
Understanding the technical capability is useful. Knowing when to apply it is better. Here are three common scenarios where this feature adds value.
Agency Portfolios: Marketing agencies often manage dozens of client sites. Using one SeaText account for all clients streamlines billing and oversight. Account managers can jump between client dashboards instantly. They can spot trends across industries without logging out.
Enterprise Regional Sites: Large companies operate in multiple countries. Each country may have a localized Webflow site. Centralized management ensures consistent branding and tracking. Teams can roll out global updates faster. They can monitor regional performance disparities easily.
Development and Production: Testing new features on a staging domain is standard practice. With SeaText, you can keep the staging site linked to your main account. This allows you to compare live traffic against test traffic. You can validate AI performance before pushing changes to production.
While the dashboard unifies management, certain technical constraints exist. Understanding these prevents frustration.
Installation Requirements: Each Webflow site still requires its own unique JavaScript snippet. You cannot use one code block for multiple domains. The script must be installed in the Custom Code section of each Webflow site. This is a security measure to ensure proper traffic attribution.
Domain Verification: SeaText requires valid, real domains. Development URLs like localhost are restricted. Dynamic staging domains may not function correctly. Always use a stable, registered domain for reliable tracking.
Activation Delay: After installing the script, there is a verification period. You must visit the site and stay for at least 40 seconds. Wait five minutes for the site name to appear in the dashboard. If it does not appear after ten minutes, contact 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.
Direct Answer: Using one SeaText account across multiple domains causes tracking failures, security restrictions, and an inability to isolate AI model training. Each domain is crawled and optimized independently, so sharing an account creates cross-domain content duplication risks and prevents accurate performance measurement.
You cannot use a single SeaText account for multiple domains. SeaText strictly links every paid account to one primary URL. Attempting to run the script on several sites from one login results in tracking errors, blocked access, and confused AI models that mix data from different brands. Each domain is crawled and optimized independently; AI models are fine-tuned per project so no cross-domain content duplication occurs. However, sharing the account itself prevents the technical isolation required for healthy SEO performance.
SeaText operates as an autonomous agent suite that rewrites pages in real-time. It does not just display static content; it actively modifies headlines, offers, and calls-to-action based on visitor intent. To do this safely, the system must know exactly which business owns the page.
If one account controlled ten different domains, the AI would not know which brand voice to use or which conversion goals to prioritize. The "Conversion Agent" needs to rewrite pages for specific enterprise accounts. The "Bot Refund Agent" needs to track ad spend for specific campaigns. Mixing these signals breaks the optimization logic. Each domain requires its own environment to ensure the AI remains contextually aware.
When you try to force one account onto multiple domains, you introduce several technical risks that hurt your search rankings.
SeaText tracks traffic by associating visits with a specific account ID. If you install the same JavaScript snippet from one account on two different websites, the analytics become useless. You will see traffic spikes that do not match your actual visitors. This makes it impossible to measure the true impact of your SEO efforts or calculate your Return on Ad Spend (ROAS).
SeaText enforces strict security protocols. Development URLs like localhost are restricted for safety reasons. Dynamic development domains often fail because the system cannot reliably associate traffic with your account. If you attempt to bypass these checks by using one account for multiple live domains, the script may be flagged as suspicious and deactivated. Your site will lose its AI enhancements without warning.
While SeaText generates unique variants, sharing an account can lead to accidental content overlap. The AI might apply similar translation patterns or copy variations across unrelated domains. Search engines penalize duplicate content. If Google sees identical text structures coming from the same source code but different domains, it may devalue your rankings.
SeaText uses fine-tuned AI models for each project. These models learn from the specific language, products, and audience of a single website. They are designed to optimize for one set of keywords and one brand identity.
If you share an account, you risk contaminating the model. The AI might start learning from the vocabulary of a competitor or a completely different industry if the data streams merge. This leads to irrelevant translations and poor conversion rates. Separate accounts ensure that the "Translation Agent" only learns the terminology relevant to your specific market.
Separating your domains into individual accounts has operational costs, but they are necessary for stability.
To avoid SEO penalties and ensure optimal performance, follow this diagnostic process for each new domain.
There are very few exceptions to the single-account rule. SeaText explicitly states you must create separate accounts for each domain. This includes production and development sites. Even if you own both, they require isolation.
Do not attempt to use one account for a staging site and a live site. The dynamic nature of development domains causes the AI to misinterpret traffic sources.
| Feature | Rule | Impact on SEO |
|---|---|---|
| Account Limit | One primary URL per account | Prevents data mixing and tracking errors |
| Script Installation | Unique JS code per account | Ensures correct attribution of traffic |
| AI Model Training | Fine-tuned per project | Maintains brand-specific relevance |
| Security Checks | Blocks dynamic URLs | Protects against invalid traffic |
| Webflow Integration | Unlimited domains in paid plans | Allows multi-site management under one brand |
No. Each domain requires its own dedicated SeaText account. This is a hard technical requirement to ensure data integrity and security.
If you start editing before the website name appears, the AI may not be fully connected. This can result in lost edits or incorrect content generation.
Subdomains are treated as distinct entities. You should verify with SeaText support if a subdomain counts as a new URL requiring a new account, as this affects tracking accuracy.
Run A/B tests within each individual account. Do not try to compare results across different accounts directly, as baselines and traffic sources will differ.
Each account requires a subscription. However, this ensures that each site gets dedicated support and accurate reporting. Shared accounts often lead to wasted spend due to poor targeting.
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 switch between Webflow domains in SeaText, you must log into the specific account tied to the target domain. There is no in-account project switcher; each domain requires its own dedicated SeaText account.
SeaText is built to provide high-precision AI-driven optimization. Unlike some platforms that allow multiple projects under a single login, SeaText operates on a strict one-to-one mapping. This means one SeaText account is linked to exactly one primary URL.
To switch between Webflow domains, you do not toggle an internal setting. Instead, you log into the specific account associated with the domain you wish to manage. This architecture ensures that the AI learning models for traffic patterns, content, and user behavior remain uncontaminated by data from other sites.
If you manage multiple Webflow sites, you will need separate SeaText credentials for each. To move between them, you must log out of your current session and log into the account tied to the target domain.
Managing multiple domains requires a specific workflow to ensure data integrity. Because the AI associates traffic directly with specific URLs, mixing data would lead to inaccurate analytics and failed optimization.
This structured approach prevents security issues related to dynamic development domains. Localhost and temporary staging URLs are restricted because the AI cannot reliably associate traffic with them.
The primary reason for the account-per-domain rule is data-driven accuracy. The SeaText AI learns from specific traffic patterns and site content. If data from two different domains were fed into one account, the AI would struggle to associate specific user actions with the correct URL.
Furthermore, this structure protects your security environment. Dynamic development domains are often restricted for security reasons. By requiring a valid, real-world domain, SeaText ensures that the telemetry collected is based on live, production-ready traffic.
Using separate accounts also allows for independent scaling. If you have a high-traffic ecommerce store and a low-traffic blog, keeping them separate allows the AI to optimize for the specific intent of each audience without one being skewed by the "noise" of the other.
Since there is no in-account project switcher, your workflow depends on how you organize your logins. Here are common scenarios and how to handle them:
If you manage Webflow sites for multiple clients, you should maintain separate sets of credentials for each. To switch from Client A to Client B, you must log out of the current dashboard and log in with Client B's credentials. This ensures you never accidentally apply configurations or view the wrong data set.
If you are moving a site from a staging environment to production, remember that the staging URL will not support SeaText. You must set up a new account for the production domain. Once the site is live on the real domain, you will log into that production-specific account to begin the AI-learning process.
If you are launching a new localized version of your site (e.g., a .com and a .co.uk), each domain requires its own account. This allows the AI to learn the specific cultural nuances and search behaviors of each region without interference from the primary market data.
While the separate-account model offers high data purity, it comes with operational trade-offs. The most significant limitation is the lack of a "global view." You cannot see the aggregate performance of all your domains in a single SeaText dashboard.
Another trade-off is the manual nature of switching accounts. If you manage dozens of domains, logging in and out can become tedious. However, this manual friction is a deliberate safeguard to ensure that AI-driven changes and traffic analysis are always applied to the correct domain-bound environment.
Additionally, remember that SeaText requires an active Webflow Site plan to access the custom code section. If a site is on a free Webflow plan, you cannot install the necessary snippet, and the integration will fail.
If your domain does not appear in your dashboard after following the setup, check these checklist items:
No, each domain requires its own dedicated SeaText account to maintain traffic association and security.
Dynamic or local development URLs (like localhost) prevent the AI from reliably associating traffic with your account. Real, valid domains are required for functionality.
Your website name will appear next to the SeaText logo at the top of the dashboard once the AI has successfully linked to your site.
If a domain is missing, ensure you are logged into the specific account associated with that domain. You cannot switch to a domain that is not linked to your current session.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Account-level settings manage global infrastructure like billing, team access, and API keys. Project-level settings control domain-specific SEO strategies such as crawl schedules, AI tone, target keywords, and content rules. This distinction allows agencies to manage multiple sites under one subscription while maintaining unique SEO identities for each.
In SeaText for Webflow, the distinction between account-level and project-level settings is essential. It separates global management from local execution. Account-level settings act as the foundation for your entire presence. They handle administrative tasks like billing, team membership, and API key management. In contrast, project-level settings are tailored to specific domains. They allow you to define unique SEO strategies for each site independently.
This hierarchy ensures you can manage multiple websites under one billing umbrella. Their SEO strategies do not bleed into one another. If you change an account-level setting, it affects everything you own. If you change a project-level setting, only that specific Webflow site is impacted.
| Criteria | Account-Level (Global) | Project-Level (Domain-Specific) |
|---|---|---|
| Primary Focus | Administration & Infrastructure | SEO Strategy & Content Execution |
| Key Features | Billing, Team members, API keys | Crawl schedule, AI tone, Keywords, Content rules |
| Impact Scope | Applies to all connected Webflow sites | Applies only to one Webflow site |
| Setup Effort | Set once per account | Configured per site/domain |
| Best For | Managing access and payment methods | Optimizing specific search performance |
| Flexibility | Low (Standardized across org) | High (Customized per brand voice) |
Choose account-level settings if you need to manage your subscription, add team members, or integrate tools via API.
Choose project-level settings if you want to fine-tune the AI voice, target keywords, or crawl frequency for a specific Webflow domain.
Account-level settings are the control center for your entire SeaText environment. These settings handle the 'business' side of your operation. This is where you manage your subscription plan and who has access to the dashboard. Because these settings are global, they are designed for consistency across all your projects.
When you configure your account, you are setting the environment in which all your projects operate. For example, adding an API key at the account level allows all linked projects to communicate with external tools without redundant setup. Similarly, inviting a team member at the account level grants them permissions to manage all the Webflow sites linked to that account.
Security is also managed here. You define who can view data and who can make changes. This prevents accidental configuration errors by unauthorized users. The account level ensures that every project starts with the same baseline security and connectivity standards.
Project-level settings are where the actual SEO work happens. Each Webflow domain you connect is treated as a distinct project. This allows you to run vastly different strategies for different sites. You might have one project for a professional blog with a formal AI tone. Another project might be for a creative portfolio using casual language.
Within the project, you define the technical parameters of the AI. This includes the crawl schedule—how often SeaText visits your site. You set target keywords you want to rank for. You also define specific content rules that govern how AI generates text. By isolating these settings, you ensure that the SEO efforts for your e-commerce store don't accidentally apply to your corporate landing page.
The AI tone is a critical component here. It dictates the personality of the generated content. A SaaS company might require technical precision. An e-commerce brand might prefer enthusiastic sales copy. These nuances are impossible to achieve if settings were global. Project-level control ensures brand integrity for every individual domain.
Choosing between global and granular configurations involves specific trade-offs. Understanding these helps you decide which approach fits your workflow.
While the separation of settings offers flexibility, there are important limitations to consider. These restrictions affect how you can deploy SeaText across different environments.
SeaText restricts the use of development URLs for security reasons. Domains such as localhost are not supported. This is because dynamic development domains may not function properly. SeaText might be unable to reliably associate traffic with your account during development phases.
You must use a valid, real domain for testing. If you need to use SeaText on multiple domains, such as a development domain and a production domain, you must create separate accounts for each. Each SeaText AI account is linked to a single primary URL. This limitation ensures data integrity and prevents tracking conflicts.
Account-level API keys facilitate communication between SeaText and your Webflow site. However, these connections are subject to rate limits. Excessive requests from multiple projects sharing the same API key could trigger throttling. It is important to monitor usage to ensure smooth operation.
Accessing custom code in your Webflow site requires an active Site plan. Without this, integration steps may fail. Additionally, after installing the script, you must visit or refresh your website several times. You must stay on your page for at least 40 seconds to activate the AI. This links the AI to your account securely.
After installation, wait at least five minutes until you see your website name displayed next to the SEATEXT logo. This indicates that your website is connected. If you do not see it after 10 minutes, contact support. Delays may indicate issues during installation on your platform.
Understanding these settings helps in specific scenarios. Here are detailed examples for different business types.
An agency manages three client Webflow sites. They use account-level settings to manage employee access. This ensures only authorized staff can view sensitive data. However, they use project-level settings to differentiate strategies. Client A ranks for 'local plumbing' with a trustworthy tone. Client B targets 'software SaaS' with a technical tone. This separation prevents brand confusion and optimizes each client's ROI.
A brand has a main US site and a new UK site. They keep the account-level billing the same. At the project level, they adjust the AI tone for British English spelling and cultural nuances. They also set a more aggressive crawl schedule for the UK site to keep product listings fresh daily. This granular control ensures local relevance without global overhead.
A SaaS company offers two distinct products: a CRM and a Marketing Tool. They treat each as a separate project. The CRM project targets enterprise keywords with a formal tone. The Marketing Tool project targets small businesses with a friendly tone. Crawl schedules differ based on update frequency. The CRM updates monthly, so it crawls less often. The Marketing Tool updates weekly, requiring frequent crawls. This efficiency saves resources while maximizing visibility.
To get started, follow this logical order of operations:
Does changing the AI tone in one project affect the others?
No, AI tone is a project-level setting. It only affects the specific domain where it is configured.
Where do I add new team members?
Team members are added at the account-level settings. This grants them access to all projects under that account.
Can I have different billing plans for different projects?
No, billing is account-based. All projects under one account fall under the same subscription tier.
What happens if I update the API key?
API keys are managed at the account level. Updating them ensures seamless integration across all your projects.
Can I use SeaText on localhost?
No, development URLs like localhost are restricted for security reasons. Use a valid, real domain instead.
How long does it take for a new site to connect?
Wait at least five minutes after installation. If it takes longer than 10 minutes, contact 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.
Direct Answer: No. Each SEATEXT AI account is linked to a single primary URL. To use different AI configurations for different Webflow domains, you must create separate accounts for each domain. This ensures strict isolation of training data and model settings.
Many marketers ask if they can manage multiple Webflow sites under one subscription while using distinct AI behaviors for each. The short answer is no. SEATEXT AI enforces a strict one-account-per-domain rule. Each account is linked to a single primary URL. You cannot assign different AI models or training data to multiple domains within one account.
This structure exists for security and tracking accuracy. It prevents data leakage between unrelated brands. If you run a high-tech SaaS site and a boutique lifestyle store, these entities require separate digital identities. They need separate AI environments to function correctly.
Below is a comparison of the two approaches. It highlights why the multi-account setup is necessary for diverse portfolios.
| Criteria | Single Account (One Domain) | Multi-Account Setup (Multiple Domains) |
|---|---|---|
| Account Limit | One primary URL per account. | One account per unique domain. |
| Model Isolation | Full control over one site. | Complete separation of logic and data. |
| Training Data | Specific to that single domain. | No cross-contamination between sites. |
| Security | Standard protection levels. | Higher security via isolated credentials. |
| Best For | Solo founders or single-brand agencies. | Agencies managing diverse client portfolios. |
To understand the restriction, you must look at how SEATEXT processes data. When you link a Webflow domain to your account, the system creates a specific project environment. This environment acts as a container for all AI-related settings.
Inside this container, you define the specific AI engine. For example, one domain might use a fast, lightweight model for a customer support chatbot. Another domain might use a more creative, complex model for generating blog copy. Because these settings are stored within the project ID, they do not "bleed" into other projects.
However, the source pack explicitly states that multiple domains require separate accounts. You cannot simply add five different domains to one account and configure them individually. Each domain must have its own login credentials and account structure. This ensures that the AI remains inert until activated on the correct site.
The AI model is only half the story. The training data is what makes the output useful. If you use the same training data for a law firm site and a bakery site, the AI will likely suggest legal jargon to a customer looking for a cake. Or vice versa.
By using separate accounts, you ensure that each business has its own knowledge base. You can feed specific product catalogs, style guides, and technical documentation to each account independently. This isolation is critical for SEO. It ensures your content remains highly relevant to specific search intents.
If you were allowed to mix domains in one account, the AI might struggle to associate traffic with the correct context. This could lead to generic messaging or irrelevant data processing. Separate accounts prevent this risk entirely.
Managing multiple accounts requires more administrative effort. You must log in separately to each dashboard. You must manage separate billing cycles. However, the benefits often outweigh these costs for agencies.
Consider the trade-offs carefully. A single-model approach works well for simple sites with identical brand voices. But it fails for diverse portfolios. If your domains target different industries, they need unique brand identities.
You gain full control by separating accounts. You can update the model for Domain A without impacting Domain B. You can adjust pricing plans for one client without affecting another. This flexibility is essential for growing businesses.
Users often try to bypass the single-domain rule by using subdomains or development URLs. This leads to errors. Development URLs like localhost are restricted for security reasons. Dynamic development domains may not function properly.
SEATEXT AI might be unable to reliably associate traffic with your account if you use invalid domains. Always use valid, real domains for installation. Ensure you have an active Site plan in Webflow to access custom code.
Another common pitfall is failing to activate the AI. You must visit or refresh your website several times. Stay on the page for at least 40 seconds. This activates the AI and links it to your account. Wait at least five minutes to see your website name displayed next to the SEATEXT logo.
A single-account strategy is sufficient if you only manage one brand. It simplifies billing and reduces login fatigue. However, if you manage multiple distinct brands, a single model is insufficient.
Different brands have different audiences. A B2B software company needs formal, technical language. A consumer fashion brand needs casual, trendy language. One AI model cannot effectively serve both purposes simultaneously.
Therefore, you should reconsider a single-model approach if your portfolio includes diverse industries. Separate accounts allow you to tailor the AI experience for each specific audience. This leads to higher conversion rates and better user engagement.
Imagine you run a high-tech SaaS site and a boutique lifestyle store. With separate accounts, you can give each its own AI model and training data. The SaaS site speaks in technical jargon, focusing on API documentation and enterprise features. The lifestyle store uses a warm, casual tone, highlighting product aesthetics and personal stories.
This separation ensures that visitors to the SaaS site receive precise, professional answers. Visitors to the lifestyle store feel welcomed and understood. Neither group is confused by irrelevant information. This clarity drives trust and sales.
To achieve this, you would create one SEATEXT account for the SaaS domain. You would create a second SEATEXT account for the lifestyle domain. You would then install the respective JavaScript codes on each Webflow site. This process is secure and maintains the integrity of your website's content.
To set up different AI models for your Webflow sites, follow these steps for each domain:
| Feature | Detail |
|---|---|
| Account Limit | One primary URL per account for security. |
| Model Selection | Configured per account/domain. |
| Data Isolation | Independent training bases per site. |
| Webflow Support | Requires active Site plan. |
| Activation Speed | Requires manual activation (40+ seconds). |
Yes. Each SEATEXT AI account is linked to a single primary URL. You must create separate accounts for each domain you wish to use.
No. Since each site has its own account, updating the model for Domain A has zero impact on the AI behavior of Domain B.
Yes. You can configure specific language parameters for each account. This allows you to target different global markets independently.
You must pay for each account separately. Pricing depends on the plan selected for each domain. There are no bundled discounts for multiple domains in the current structure.
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 includes unlimited domains on all paid plans with per-project AI tuning, while many competitors charge per domain or limit projects. This article explains the trade-offs and helps you decide if SeaText fits your multi-site needs.
SeaText offers unlimited domains on all paid plans, while many competitors charge per domain or limit projects. Here's how they compare.
| Criteria | SeaText | Competitor A (e.g., Surfer SEO) | Competitor B (e.g., Frase) | Competitor C (e.g., Clearscope) |
|---|---|---|---|---|
| Pricing model | Flat rate per account | Per domain or project | Per seat or domain | Per domain |
| Number of domains included | Unlimited | Limited (often 1-5) | Limited (often 1-3) | Limited (often 1) |
| Per-project AI tuning | Yes | Limited | No | No |
| Dashboard management | Single account, separate projects | Single dashboard | Single dashboard | Single dashboard |
| Best for | Agencies, multi-site owners | Single site focus | Single site focus | Enterprise single site |
Choose SeaText if you manage multiple sites and want unlimited domains; choose Competitor X if you need advanced content optimization for a single site.
SEO teams often manage many websites. These include client sites, brand variants, or regional versions. Each site needs unique content and optimization. Without proper support, costs rise quickly. You might pay per domain or project. This adds up fast for agencies. SeaText avoids this by offering unlimited domains. All paid plans include this feature. It simplifies billing and management. You do not need multiple subscriptions. One account handles everything. This reduces administrative work. It also lowers total cost of ownership. For growing teams, this flexibility is key.
SeaText links one account to one primary URL. To use it on multiple domains, you create separate accounts. Each account connects to a single site. This ensures accurate tracking and data. You cannot mix domains in one account. The installation process requires JavaScript code. You paste this into your website settings. For Webflow, this goes in Custom Code. You must publish changes to activate. The AI stays inert until activated. This protects your site integrity. You need an active account to install. Development domains like localhost are restricted. Use real domains for testing. After setup, wait five minutes. Your site name should appear. If not, contact support. This step confirms connection. It ensures data flows correctly.
Many competitors limit domains per plan. Surfer SEO often charges per project. Frase limits sites per seat. Clearscope restricts domains on entry plans. These limits force upgrades as you grow. SeaText does not have these caps. You get unlimited domains on paid plans. This saves money for multi-site teams. However, SeaText uses separate accounts per domain. Competitors often use one dashboard for all. This means SeaText users manage multiple logins. Some find this cumbersome. Others prefer isolated data. It depends on your workflow. Also, competitors offer more content audit features. SeaText focuses on real-time adaptation. Consider your priorities. If you need many sites, SeaText wins. If you need deep audits, check others.
Agencies benefit most from unlimited domains. They manage client sites regularly. Each client needs unique optimization. SeaText allows this without extra fees. You can test strategies across sites. This helps find what works best. E-commerce brands with regional stores also gain. They need localized content everywhere. SeaText supports 125 languages. This helps expand globally quickly. You translate pages automatically. No manual localization is needed. Marketing teams running ads see value too. SeaText rewrites landing pages in real time. It matches ad keywords instantly. This improves conversion rates. It lowers bounce rates too. For high-traffic sites, this is vital. It turns clicks into customers faster.
SeaText requires separate accounts per domain. This means multiple logins and dashboards. You cannot view all sites in one place. This is a trade-off for unlimited access. Some teams prefer unified reporting. Also, development domains are restricted. You cannot use localhost easily. This makes testing harder. You need a live URL first. The AI activates after 40 seconds. You must stay on the page. This ensures accurate data collection. If you leave early, it might fail. Support is available if issues arise. But initial setup takes time. Competitors offer faster onboarding sometimes. Also, SeaText focuses on conversion and ads. It is less about traditional SEO audits. Check if you need deep keyword analysis. Some tools specialize in that area. Know your needs before choosing.
Does SeaText offer a free plan?
SeaText offers a free trial. You can test agents before buying. Check pricing pages for details.
How do I migrate from another tool?
There is no direct migration tool. You install SeaText code manually. Export data from old tools separately.
Can I use SeaText on subdomains?
Yes, but treat each as a domain. You may need separate accounts. Check support for specific cases.
What if I need to change domains?
You create a new account. The old account stays active. Contact support for guidance.
Is SeaText good for small businesses?
Yes, if you have multiple sites. For one site, check other options. Compare features and costs.
How does pricing work?
Pricing is per account. Unlimited domains are included. Visit SeaText's pricing page to see which plan fits your multi-site needs.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Yes, you can move a domain between SeaText accounts by deleting the project from your source account and re-adding it to the target account. Note that historical analytics and AI training data are not migrated during this process.
The migration process is designed to ensure that only one account is controlling a specific domain at any given time. If you attempt to add a domain to a new account while it is still active in another, the connection will be blocked. Therefore, the process follows a strict sequence of de-linking from the source and re-linking to the target.
| Criteria | Manual Migration | New Account Setup |
|---|---|---|
| Data Retention | Historical data is lost | N/A (New start) |
| Setup Effort | Requires code removal/re-insertion | Standard installation |
| Best For | Changing ownership | New domain launches |
| Downtime | Minimal (minutes-based) | None |
To successfully move your Webflow-integrated domain, follow these specific steps. Ensure you have administrative access to both SeaText accounts before starting.
When you delete a project from a SeaText account, all associated data is permanently removed. This includes conversion reports, bot evidence, and AI-optimized variants. This data cannot be exported or imported into a new account. This is a critical decision point before you initiate the deletion.
Furthermore, there is no option to merge two accounts. If you are trying to consolidate domains, you must move each one individually and accept the fresh start. If you need to retain records for compliance or historical reporting, you must download all necessary reports from the source account before beginning the de-linking process.
Many users encounter issues because they skip vital steps in the migration process. Avoid these common pitfalls:
If your domain does not appear in your new dashboard after 10 minutes, check the following: First, verify that the Webflow site was successfully published after adding the new snippet. Second, ensure the snippet is placed correctly in the <head> or footer sections as instructed.
If the domain still fails to register, visit the site several times and stay on the page for at least 40 seconds. This triggers the AI activation script. If the issue persists beyond 15 minutes, you should contact the SeaText support team to check for account-level blocks.
No, SeaText accounts are independent. You cannot merge data or projects between them.
No. Removing or adding the SeaText JavaScript snippet does not affect your Webflow site uptime or design.
After installing the code and visiting your site, it typically takes about five minutes for the domain to appear. If it takes longer 10 minutes, contact support.
Yes, each SeaText account is a separate billing entity. Ensure your target account has the appropriate plan before migrating.
>For more details on managing your accounts and domain integrations, visit our official documentation.Learn more — Continue to the relevant page on the client website.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText AI is inactive if the script is missing from your page head, if no data appears in the dashboard after deployment, or if conversion metrics remain unchanged after 10 minutes.
If you suspect SeaText AI is not working on your Web site, the issue usually stems from a script failure or a synchronization delay. The most immediate signs are the absence of the SeaText script in your site's code, a total lack of activity data in your SeaText dashboard, or your website remaining static despite active traffic.
If you do not see your website name next to the SeaText logo within 10 minutes of publishing, the integration is likely not yet fully activated. This guide helps you diagnose the specific symptoms and fix the root cause.
| Symptom | Likely Cause | Action |
|---|---|---|
| No dashboard data | Script not installed or published | Check Webflow Custom Code settings |
| No site name in header | Activation period not met | Wait 10 minutes and refresh |
| Metrics are not moving | Development/Local domain used | Switch to a live production domain |
| AI content not updating | Inactive Site plan | Verify your account plan status |
To fix a connection issue, you must follow a specific diagnostic order. Not every error is a bug; some are simply results of how Webflow handles custom code or how AI activation triggers.
1. Presence Check: The first step is verifying the script actually exists on the frontend. Open your live site, use your browser's developer tools (F12), and search the <head> for 'SeaText'. If you find nothing, the script was not pasted correctly into the Webflow Custom Code section.
2. The Activation Window: If the script is present but no data shows, check the clock. SeaText AI requires a period to link your site to your account. If you do not see your website name next to the SeaText logo at the top after 10 minutes, the script is likely waiting for activation.
3. Domain Validation: Webflow users often test on .webflow.io staging. SeaText AI is restricted on these URLs for security reasons. If your URL is not a valid, production domain, the AI will remain inert and will not associate traffic with your account correctly.
When the AI fails to trigger, the cause usually falls into three categories. Understanding these helps you avoid the common mistake.
The most common hurdle is the Webflow publish process. In Webflow, pasting code does not make it live. If you save the settings but forget to publish, the SeaText script will never reach browsers.
Another cause is the account plan limitation. Accessing custom code in Webflow requires an active Site plan. If your account is on a trial or restricted tier, the script may load but the AI engine will not execute.
Finally, environment restrictions play a role. If you are using multiple domains—like development and production—you must create separate accounts for each.
If your symptoms indicate a break, follow these steps to bring the AI online. This process is secure and straightforward.
Once the AI is active, you may need to tune its behavior. If the AI is working but performing poorly, check your configuration settings.
You can use the 'Configuration' tool to adjust AI parameters. This is where you define how the AI handles visitor signals.
If you want to change copy, navigate to the 'Variants' panel in the left dashboard. Here you can select the URL and language you wish to edit.
There are specific scenarios where SeaText AI will not function. Knowing these prevents you from troubleshooting a 'broken' system that is actually working correctly.
Localhost: Development URLs such as 'localhost' are restricted for security reasons. The AI cannot function on local-only environments.
Staging Domains: As mentioned, dynamic domains (like .webflow.io) may not function properly. The AI requires a valid, production domain to associate traffic reliably.
Fast Scrollers: If a visitor bounces in under a second, the AI may not have time to trigger telemetry. The system requires at least 40 seconds of dwell time to ensure the session is linked to your account properly.
Proper integration ensures that your AI agents can work effectively. SeaText uses real-time data to match visitor intent. If the script is broken, you lose the ability to recover ad spend from bots.
nnA functional connection allows the AI to rewrite landing pages in 0ms. This increases conversion rates by matching the exact keyword. Without a stable link, your marketing efforts remain static and lead to lower ROI.
Wait at least 10 minutes after publishing. If your website name appears next to the SeaText logo by then, the connection is active.
No, dynamic or staging domains are restricted for security. You must use a valid production domain.
You must create a separate account for each domain. One SeaText account is linked to a primary URL.
Yes, accessing custom code in Webflow requires an active Site plan.
Ensure you have stayed on the page for at least 40 seconds and that you are not on a localhost or staging URL.
nThese 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.