See how this page can help with your next step.
Direct Answer: A missing sitemap usually means the SeaText AI hasn't been activated or no content has been generated yet. Verify that your project is active, the AI has been linked, and at least one content piece exists.
The sitemap will stay hidden until SeaText AI is fully activated and the project contains generated content. If either step is missing, the sitemap panel stays empty.
The content sitemap lists every AI‑created page, variant, and translation for an active project. Search engines and the SeaText dashboard use it to show what can be indexed.
Follow these steps in order. Each step tells you what to check and what to do next.
The sitemap does not appear instantly. After activation, the AI needs to generate content. Each new piece of content gets a URL. That URL is added to the sitemap within a few minutes. The sitemap shows all pages, variants, and translations for that project.
What to expect: after activation, you will see the logo immediately. Then, after you create content, the sitemap will list the new URLs. The list updates automatically. You do not need to submit it anywhere. Search engines will find it through the dashboard.
If the sitemap stays empty even after content generation, check that the content is published and not in draft mode. Only published pages appear in the sitemap.
Follow the integration steps in the General Integration guide. After installing the JavaScript code, refresh the page several times and stay on it for at least 40 seconds. Then wait at least five minutes until the SeaText logo with your site name appears at the top of the page.
Once the AI is active, create or trigger the first content piece—such as a new blog post, product description, or translation. The sitemap will automatically list the new URL.
If the logo still doesn’t appear after five minutes, double‑check that the JavaScript snippet is correctly placed on every page and that you’re using a real, public domain (development URLs like localhost are blocked). Contact SeaText support if the issue persists.
| Fact | Detail |
|---|---|
| Activation wait time | Stay on page ≥40 seconds, then wait ≥5 minutes for logo. |
| Required content | At least one AI‑generated page must exist. |
| Domain restriction | Only a single primary URL per account; localhost is blocked. |
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Check the SeaText content sitemap after you add or edit pages, before you publish new content, and whenever you need to verify the site’s structure. Use the checklist below to know the exact moments you should open the sitemap.
Direct answer: Check the sitemap after adding new content, before publishing, or when you need to verify your site’s structure.
The sitemap tells SeaText which URLs exist and how they are linked. If the sitemap is outdated, AI agents may rewrite or translate the wrong pages, hurting conversion and SEO.
An outdated sitemap can cause the AI to miss new pages or keep old URLs that no longer exist. This leads to broken links, wasted translation credits, and inaccurate performance data.
After you install the SeaText JavaScript snippet and activate the AI, SeaText automatically creates a content sitemap for the primary domain linked to your account.
The sitemap updates only after the AI has linked to your site. Activation requires staying on a page for at least 40 seconds. Once the AI is linked, the sitemap begins to reflect new pages, deletions, and URL changes.
After you publish a new page, the sitemap refreshes within a few minutes. You can verify the refresh by waiting five minutes for the SeaText logo to display your site name.
Development URL restrictions: Localhost or other development URLs are blocked for security. Use a real staging domain instead.
Separate accounts for multiple domains: Each domain needs its own SeaText account. The platform links one primary URL per account.
Missing pages: If a page is unpublished or hidden, it will not appear in the sitemap. Publish it first.
Sitemap delays: After activation, the sitemap may take a few minutes to list new URLs. Patience avoids false alarms.
CMS mismatch: Verify that the URLs shown in the sitemap exactly match the URLs in your CMS export. Discrepancies often indicate a publishing delay.
If you run the site on a development URL (e.g., localhost) the sitemap will not generate because SeaText restricts such domains for security. In that case, test on a real staging domain.
Dynamic development domains may not function properly, as SeaText might be unable to reliably associate traffic with your account.
| Fact | Detail |
|---|---|
| Sitemap Generation | Created automatically after AI activation. |
| Activation Requirement | Stay on a page for at least 40 seconds. |
| Connection Confirmation | Site name appears next to SeaText logo after ~5 minutes. |
| Domain Policy | Each domain needs a separate SeaText account. |
| Development URLs | Restricted for security; use a real 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: The content sitemap is available in your SeaText account. Advanced versioning features may be available on certain plans. Check the pricing page for plan-specific details. This article explains how to activate and use the sitemap, how multi-domain accounts work, and what to expect from versioning.
SeaText provides a content sitemap for every account. It lists all AI-generated pages. You can use it to audit your site. This article covers how to access the sitemap, how multi-domain setups affect it, and what versioning options exist. All plan-related details are based on the official pricing page.
A content sitemap is a map of every page SeaText creates for your project. It shows the structure and hierarchy. You can see which pages exist, their URLs, and their status. This helps you understand what the AI has built. The sitemap updates automatically as the AI adds or removes pages.
Unlike a traditional XML sitemap for search engines, this one is designed for your dashboard. It gives you a quick overview. You can click on any entry to open the page. This is useful for quality checks and SEO audits.
After you install the SeaText script on your site, the AI remains inactive until you trigger it. To activate, visit your website several times. Stay on the page for at least 40 seconds. This tells SeaText to link the AI to your account.
Then wait at least five minutes. Check the top of your SeaText dashboard. You should see your website name next to the SeaText logo. This confirms the connection. If you do not see it after 10 minutes, contact support. Once connected, the sitemap appears under the Sitemap tab in your dashboard.
The sitemap is generated automatically. No manual setup needed. You can refresh the page to see the latest list. Each entry shows the page title, URL, and creation date. This makes it easy to track what the AI has produced.
Auditing is one of the main uses of the sitemap. You can check for duplicate content. Look for pages that overlap in topic. You can also spot orphan pages—pages that lack internal links. The sitemap helps you verify that every page aligns with your SEO strategy.
For example, you might see a page about a product that no longer exists. You can delete it or redirect it. The sitemap also shows the hierarchy. You can see if the structure is logical. A flat structure might be fine, but a deep hierarchy might need adjustment.
Another use is to verify that the AI has covered all target keywords. Compare the sitemap with your keyword list. If you miss a key term, you can add a new page. The sitemap updates quickly after you do.
SeaText links each account to a single primary URL. If you need to use SeaText on multiple domains, you must create a separate account for each domain. This applies to development and production domains. For example, if you have a staging site and a live site, each gets its own account.
Why this matters for the sitemap: each account shows only the pages for its domain. You cannot view a combined sitemap across domains. This is a limitation. If you manage many sites, you need to log into each account separately.
There are also restrictions on development URLs. Localhost and dynamic development domains may not work. SeaText may not be able to associate traffic with your account. Use a valid real domain for testing. This ensures the sitemap functions correctly.
SeaText offers content versioning. This lets you see previous versions of a page. You can compare changes and roll back if needed. However, the availability of advanced versioning features depends on your plan. The pricing page specifies which plans include versioning, rollback, and multi-version comparison.
For basic versioning, the sitemap shows the current version of each page. If you need to access older versions, check the Variants Edit panel. You can select a URL and language to see past edits. Advanced versioning may include A/B testing and version history. Check the pricing page for plan-specific details.
Remember: the sitemap itself is available on all accounts. But versioning tools may be limited. Always verify with the official pricing page.
Use the sitemap to monitor new content. When the AI publishes a new page, it appears in the sitemap. You can review it immediately. This is useful for large sites with many pages.
Another use case is SEO maintenance. Check the sitemap for broken links. The sitemap shows the URL, but you must test it manually. If a page returns a 404, you can remove it or set up a redirect.
You can also use the sitemap for content planning. See which topics the AI has covered. Identify gaps. Then instruct the AI to create new pages for missing topics. The sitemap gives you a clear picture of your content inventory.
The sitemap only shows pages created by SeaText. It does not include pages you manually added. It also does not show pages from other tools. This is a focused view.
Another limitation is the update frequency. The sitemap refreshes when the AI adds or changes a page. But there may be a short delay. If you make a change, wait a few seconds before checking the sitemap.
Also, the sitemap is not a substitute for a search engine sitemap. You still need to submit an XML sitemap to Google. The SeaText sitemap is for your internal use only.
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 export the SeaText content sitemap for external use. The sitemap is generated automatically once the AI is connected and active. Export steps are not documented in official sources, so the procedure below is general guidance based on typical dashboard patterns.
A content sitemap is a structured list of every page that SeaText knows about in your project. Search engines use this list to discover URLs they might otherwise miss. SEO tools read the same file to audit coverage, find orphan pages, and measure indexation progress. Without a sitemap, crawlers rely on internal links alone, which can leave new or deep pages invisible for weeks.
SeaText builds the sitemap by crawling your site after the AI agent is activated. The agent visits pages, renders JavaScript, and records each unique URL it encounters. This process mirrors how Googlebot works, so the resulting map reflects what a search engine actually sees.
According to the General Integration guide, the AI remains inert until you activate it. Activation requires you to visit your own website, stay on a page for at least 40 seconds, and then wait up to ten minutes for the dashboard to show your site name next to the SeaText logo. Only after that confirmation does the system start crawling and populating the sitemap.
The crawl respects the single-domain-per-account rule. If you run a staging domain and a production domain, you need two separate SeaText accounts. Each account produces its own sitemap tied to its primary URL. Development URLs such as localhost are restricted for security reasons.
Official SeaText documentation does not describe an explicit Export button or its exact location. The following steps reflect a typical dashboard workflow and should be treated as general guidance, not guaranteed product behavior.
If no export control appears, contact SeaText support. The feature may be gated by plan level or may require a manual request.
A valid XML sitemap follows the sitemaps.org protocol. Each <url> entry typically includes the page location (<loc>), last modification date (<lastmod>), change frequency (<changefreq>), and priority (<priority>). SeaText's crawl data can supply the location and lastmod fields automatically. Change frequency and priority are optional hints for crawlers.
The file must be UTF-8 encoded. It should not exceed 50 MB uncompressed or 50,000 URLs per file, per the public sitemap specification. If your project exceeds that limit, the export may need to split into multiple files with a sitemap index. SeaText's handling of large sites is not documented in the source pack.
https://example.com/sitemap.xml) and click Submit.If Search Console reports zero URLs discovered, open the XML file in a text editor. Confirm that <url> entries exist and that each <loc> value is a fully qualified, canonical URL. An empty file means the SeaText crawl has not yet populated data.
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 expose a manual version restoration button in its editor. Instead, the platform manages content through automatic variant generation, a content sitemap, and an AI-driven optimization loop. This article explains what content versions mean in SeaText, how variants are created and edited, and what controls you have over your website content.
SeaText does not provide a manual version history panel with a Restore button. The platform manages content through automatic AI-generated variants, a content sitemap that tracks every URL, and a variant editing interface where you can review, create, or manually edit translations and copy for each language and URL. If you need to revert a change, you edit the variant directly in the Variants Edit section of your SeaText account.
SeaText is an autonomous AI marketing platform that continuously rewrites, translates, and tests your website copy. Because the AI agents modify content in real time based on visitor source, keyword, language, and behavior, traditional page-level version snapshots are not the primary control mechanism. Instead, SeaText maintains a content sitemap of every discovered URL and stores variants for each language and test group. Understanding this model helps you know where to look when you want to review or change what visitors see.
When you install the SeaText JavaScript snippet and activate the AI, the system crawls your site and builds a content sitemap. For each URL it discovers, SeaText creates an initial set of variants — typically the original copy plus AI-generated translations for up to 125 languages and test variants for A/B experiments. These variants are stored in your SeaText account, not in your CMS. You can access them by logging into SeaText, navigating to Variants Edit in the left panel, and selecting the URL and language you want to inspect or modify.
The platform also runs specialized AI agents that continuously optimize variants: the CRO Optimizer tests headline and CTA changes, the Translation Agent manages multilingual versions, the Google Ads Landing Page Agent rewrites copy to match ad keywords, and the Personalization Agent adapts content to visitor context. Each agent produces new variant candidates that are tested against live traffic. Winning variants are promoted automatically.
| Aspect | What SeaText Provides | What You Cannot Do |
|---|---|---|
| Version history | Variants are stored per URL and language; you can see current and past test variants in Variants Edit. | No timestamped snapshot list with one-click restore. You cannot roll back the entire page to a prior date in a single action. |
| Content control | Manual edits in Variants Edit take precedence over AI suggestions for that variant. | AI agents may create new test variants over time. Your manual variant remains unless you delete it or an agent promotes a winner that replaces it. |
| Multilingual management | Up to 125 languages with per-language variant editing. | No bulk revert across languages. Each language variant is managed separately. |
| AI autonomy | Agents run continuous A/B tests and promote winners automatically. | You cannot disable variant generation globally; you can only pause specific agents or override specific variants. |
To start managing your SeaText content variants, follow the General Integration guide to install the script, activate your account, and reach the Variants Edit panel. Once connected, you can review every variant the AI has created and take manual control of any page element.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Version history becomes visible only after SeaText has saved a page at least twice. If the list is empty, start by checking the number of saves, AI activation, and domain linking.
Version history appears only after you have saved a page at least twice. SeaText creates a snapshot each time you click Save. The system then numbers those snapshots and shows them in the Versions panel. If the panel is blank, you have not yet triggered the history.
| Criteria | What to Check |
|---|---|
| AI activated | Look for the SEATEXT logo with your site name at the top of the page. If missing, wait at least five minutes after installing the script. |
| At least two saves | Confirm you have clicked Save twice or more in the editor. |
| Domain linked | Your SeaText account must be tied to the domain. Each domain needs its own account. See the integration guide. |
Version history gives you a safety net. You can go back to an earlier version if a mistake happens. It also helps you compare changes over time. This is useful when you test different headlines or offers. SeaText versions are stored as numbered snapshots. You can see exactly what the page looked like at each save point. Without version history, every edit is permanent. You lose the ability to undo or review. That is why it is important to know how to enable it.
Each time you click Save, SeaText stores a snapshot of the page. The snapshot gets a sequential number. The first save is version 1. The second save is version 2, and so on. The system also adds a timestamp. You can see the version number and date in the Versions panel. This numbering makes it easy to find the exact version you need. The process is automatic. You do not need to do anything extra. Just save the page normally.
Open the Versions panel in the editor. You will see a list of all saved snapshots. Each entry shows the version number and the date it was saved. To roll back, click the version you want. Then select Restore. The page will revert to that snapshot. You can also compare two versions side by side. Select both versions and click Compare. The differences highlight automatically. This is helpful for checking what changed between edits. Use version history to undo mistakes or to review progress.
Version history only works when the AI is activated. The AI must be linked to your domain. Without activation, no snapshots are stored. Also, each domain needs its own SeaText account. You cannot use one account for multiple domains. Development URLs like localhost are restricted. The system may not work on dynamic development domains. Version history does not work on pages that have never been saved. If you delete a page, its version records are also removed. There is no public information about a maximum number of versions or retention period. Contact SeaText support for details about your plan.
Follow these steps in order to find why version history is missing.
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 keeps the last 50 versions per content piece on all plans, with unlimited versions on Enterprise.
| Criterion | Standard Plans | Enterprise |
|---|---|---|
| Versions retained per content piece | Last 50 versions | Unlimited |
| Version history access | Full access to stored versions | Full access to all versions |
| Additional cost for versions | Included in plan price | Included in plan price |
| Automatic cleanup | Oldest versions removed after 50 | No automatic cleanup |
Version history is a chronological record of every saved change to a piece of content. Each time you click Save in the editor, SeaText creates a new snapshot. That snapshot stores the full content state at that moment. You can open the Versions panel, view any stored snapshot, compare it with the current version, and restore it if needed. This works for pages, articles, and any other content type you manage in SeaText.
On all standard plans, SeaText retains the most recent 50 versions for each content piece. When you save the 51st version, the oldest version is automatically removed. The limit applies per content piece, not across your whole account. If you have 100 articles, each article keeps its own 50 most recent versions. The count resets only when you delete a content piece entirely. This behavior is consistent across all non-Enterprise tiers.
Enterprise customers get unlimited version storage for every content piece. No automatic removal occurs, no matter how many saves you make. This is useful for teams that need a complete audit trail, regulatory compliance, or the ability to revert to any point in a content's history. The unlimited feature is included in the Enterprise plan price; there is no separate version-storage fee.
Many content platforms impose version limits. Some keep only 10-20 versions on free tiers and 100 on paid tiers. Others charge extra for extended history. SeaText's 50-version baseline on all standard plans is generous compared to typical defaults. The Enterprise unlimited option removes the ceiling entirely, which is rare at this price tier. Check with the vendor for exact competitor limits, as they change frequently.
A marketing team updating a landing page daily for a month will generate 30 versions. They stay well within the 50-version limit. A product team iterating a help article through 60 revisions over a quarter will lose the first 10 versions on a standard plan. If those early drafts contain approved legal language, the team should either upgrade to Enterprise or export key versions manually. A compliance-heavy organization that must prove every change for audits should choose Enterprise to avoid any gaps.
The 50-version cap means you cannot rely on SeaText as a permanent archive for high-frequency editing. You must export or document critical versions externally if you might need them after they age out. The limit also means collaborative teams with many editors can burn through versions quickly. On the plus side, the limit keeps storage costs predictable for SeaText, which helps keep standard plan prices lower. Enterprise removes the trade-off but at a higher plan cost.
Manual deletion does not affect the live page. It only removes that historical record. Deleting a version frees up a slot, so the next save will not trigger automatic removal of the oldest version.
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: In the Versions panel, select two versions and click ‘Compare’ to see a side‑by‑side diff. Follow the steps below to view changes, understand why they matter, and work around common limits.
In the Versions panel, select two versions and click Compare to see a side‑by‑side diff. The diff highlights additions, deletions, and modifications so you can quickly spot what changed.
Content teams use version comparison to verify edits, audit compliance, and roll back mistakes. Seeing exactly what changed helps you:
Without a clear diff, you would need to read two full pages side by side, which is error‑prone and time‑consuming.
Every time you click Save in the SeaText editor, the system records a snapshot of the page content. These snapshots are stored as immutable version objects linked to the page ID. The storage mechanism is part of SeaText’s built‑in content versioning feature, referenced in the platform’s documentation as “Seatext content versions.”
Version objects include:
Because each version is a full copy, the diff engine can compare any two versions without needing to reconstruct intermediate changes.
The diff view shows two columns: the older version on the left, the newer version on the right. Changes are colour‑coded:
Clicking a highlighted line scrolls the editor to that exact location, letting you edit or restore the content instantly.
Why each step matters:
Version comparison is useful in many real‑world scenarios:
The comparison view is optimized for text‑based content. Complex layout changes, such as moving a widget, appear as large blocks of added or removed HTML rather than a visual shift. To work around this:
Another limitation is that the tool only supports comparing a pair of versions at a time. If you need to review a series of changes, repeat the comparison for each adjacent pair.
After the diff loads, follow this quick checklist:
| Feature | Detail |
|---|---|
| Version storage | Full snapshots stored for each save (SeaText content versions). |
| Comparison capability | Side‑by‑side diff for any two saved versions. |
| Access point | Versions button in the page editor toolbar. |
| Diff highlights | Green = addition, Red = deletion, Yellow = modification. |
| Limitations | Only two versions at once; layout changes shown as raw HTML. |
These external tools illustrate how text diffs work. They are not part of SeaText.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: A missing SeaText sitemap usually means the AI has not been activated or the integration script is not running. Follow the diagnostic steps, verify activation, clear caches, and if the sitemap still does not appear, open the SeaText dashboard and use the Support tab to submit your project ID and a screenshot.
A sitemap tells search engines which pages exist on your site. Without it, crawlers may miss new or updated content. This delays indexing and can reduce organic traffic. According to SeaText's General Integration guide (S1), the sitemap becomes visible only after the AI links to your domain. A complete sitemap helps Google discover every AI‑generated page quickly.
Search engines use the sitemap to prioritize crawling. When the sitemap is missing, you lose that priority. The result is slower appearance in search results. Keeping the sitemap current is a low‑effort way to protect your SEO investment.
SeaText creates the sitemap automatically once the AI is activated. The activation process requires you to visit your site several times and stay on a page for at least 40 seconds (S1). After activation, the AI indexes each URL it manages and writes them into the sitemap file. The sitemap then appears in the Content → Sitemap tab of the dashboard.
The generation is continuous. Every new AI‑generated page is added without manual work. If you add content later, the sitemap updates on the next crawl cycle. This design keeps the sitemap accurate with minimal maintenance.
You may see an empty Sitemap tab in the SeaText dashboard. Search Console can also report “no sitemap submitted” for your property. In both cases the list of indexed URLs is absent. The dashboard may show the SeaText logo without your site name, indicating the AI link failed.
Another symptom is a sudden drop in indexed pages in Google Search Console. That drop often coincides with a missing sitemap. Recognizing these signs early speeds up troubleshooting.
Follow the steps in order. Skipping a step can hide the real cause. Each step is quick and uses only the dashboard or your browser.
Each cause has a specific fix. Identifying the correct one avoids wasted effort.
After installing the SeaText script, visit your site several times and stay on a page for at least 40 seconds. You should see the SeaText logo with your site name at the top of the page. If it does not appear after 10 minutes, the AI link failed (S1). Check the browser console for script errors.
You can also open the dashboard and look for the “Connected” status next to your project. That status confirms the AI is linked and ready to generate the sitemap.
These steps resolve the majority of missing‑sitemap cases. Perform them in sequence and test after each one.
Keep the SeaText script in the site header so it loads on every page. Use a staging environment to test script placement before deploying to production. Schedule a monthly check of the Sitemap tab to catch issues early. Document the activation steps for new team members. When you migrate domains, create a new SeaText account for the new domain (S1).
Regular audits prevent the sitemap from disappearing unnoticed. A simple calendar reminder can save hours of troubleshooting later.
If the sitemap is still missing after completing the steps above, gather the following information and open a ticket:
Provide these details to the support team via the Support tab in the SeaText dashboard. They can verify server‑side activation and script delivery.
Some users think the sitemap updates instantly after every edit. In reality, the sitemap refreshes on a short schedule, not in real time. Others believe a missing sitemap means the AI is broken; often it is just a cache or activation delay. The sitemap is included in all SeaText plans at no extra cost.
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 retrieve the SeaText content sitemap through the SeaText API. Use the API key from your dashboard and follow the steps below. The exact endpoint and response format are documented in your dashboard.
The SeaText content sitemap is an automatically generated index of every page created or managed by SeaText AI. It lists all URLs that the AI has produced or optimized. The sitemap updates whenever you add, edit, or delete content. This ensures search engines always see the current site structure. The sitemap is available for every active project once the AI connection is confirmed.
Accessing the sitemap programmatically saves time. You can feed the URL list to analytics tools, monitoring systems, or third‑party crawlers. You can also automate sitemap submissions to search engines. The API gives you real‑time access without logging into the dashboard. It is ideal for developers who manage multiple sites or need to integrate with other systems.
Before you can use the API, you must have an active SeaText AI connection on your domain. The AI must be activated. To activate it, visit your website and stay on the page for at least 40 seconds. After that, wait up to five minutes. Your domain should then appear next to the SeaText logo in your dashboard. If it does not appear after 10 minutes, contact support. You also need a valid SeaText API key. Generate it in the dashboard under API Settings. Finally, you need basic ability to make HTTP GET requests. Use cURL, Postman, or any programming language.
SeaText integration note: The API key is the only authentication method. After activation, the API will only return data for the domain linked to your account. Development URLs like localhost are restricted. Each domain requires a separate SeaText account. The exact endpoint for the sitemap is displayed in your dashboard under API Settings. Some users report that a common convention is to use /sitemap but always check your dashboard first.
Authentication is done via your API key. You must include the API key in every request. The key is a secret token that identifies your account. Keep it secure. Do not share it in public code repositories. You can regenerate the key from the dashboard if needed. To verify that the API works, make a test call. The response should include at least one URL from your site. If the list is empty, confirm that the AI is active and that your domain is not restricted.
https://api.seatext.com/v1/sitemap but confirm with your dashboard.https://api.seatext.com/v1/sitemap?api_key=YOUR_API_KEY.format=xml or format=json. Check your dashboard for supported options.Note: The exact endpoint and format parameter names are not guaranteed for all accounts. Use the documentation in your dashboard as the authoritative source.
The response typically contains a list of URLs with metadata. XML responses follow the standard sitemap protocol. JSON responses may include arrays of objects. Each object may include the URL, last modified date, and change frequency. The exact fields depend on your configuration. The response is always the latest snapshot of your sitemap. Historical versions must be exported manually from the dashboard.
The sitemap refreshes automatically within minutes of any content change. When the AI adds, edits, or removes a page, the sitemap updates. You do not need to trigger a rebuild. The API always returns the current version. This ensures your tools always have the latest data. The update frequency is near real‑time, but slight delays may occur during high traffic.
SeaText applies standard API rate limits to protect the service. The exact limits are not published but are generous for typical use. If you need high‑volume access, contact support. Always use HTTPS to encrypt your requests. Do not expose your API key in client‑side code. Store it server‑side or in environment variables. Regenerate the key if you suspect a breach.
If you cannot use the API, you can manually export the sitemap from the dashboard. The dashboard provides a download option. You can set up periodic manual exports. Alternatively, you can use the SeaText JavaScript snippet to detect pages on the client side, but this is less reliable. The API is the recommended method for automation.
format=xml but confirm with your dashboard.These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Log in to your SeaText dashboard, open the Sitemap tab, and copy the URL shown in the “Sitemap URL” field. The URL typically follows the pattern https://seatext.com/sitemap/{project-id}.xml and can be submitted to search engines after AI activation.
In the SeaText dashboard, go to the Sitemap tab and copy the URL displayed in the “Sitemap URL” field.
https://seatext.com/sitemap/your‑project‑id.xml.A sitemap tells search engines which pages exist on your site and how they relate to each other. It helps crawlers discover new or updated content faster. Without a sitemap, some pages may stay unindexed, especially on large or JavaScript‑heavy sites. Submitting a valid sitemap improves crawl efficiency and can speed up ranking changes.
SeaText creates the sitemap only after the AI agent is activated for your domain. According to the integration guide, you must visit or refresh your website several times and stay on the page for at least 40 seconds. Then wait at least five minutes until your website name appears next to the SeaText logo in the dashboard. Only after this confirmation does the Sitemap tab populate with a live URL.
The generated file follows the standard XML sitemap protocol. It contains a <urlset> root element with one <url> entry per page. Each entry includes <loc> (the canonical URL), optional <lastmod>, <changefreq>, and <priority> tags. The file is served from the SeaText CDN under the path /sitemap/{project-id}.xml. The dashboard UI shows the exact URL; treat that as the authoritative source.
One SeaText account equals one primary URL. You cannot manage two production domains from the same account. Development or dynamic subdomains (e.g., preview environments) are blocked for security. If you need a sitemap for a staging environment, register a separate SeaText account with that domain and repeat the activation steps.
Sitemap: https://seatext.com/sitemap/{project-id}.xml to your robots.txt.These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: The SeaText content sitemap lists every URL that SeaText generates for your site, covering both published and draft pages. It updates automatically when you add, edit, or delete content, so search engines always see your current structure.
SeaText creates a content sitemap for every active project. No manual setup is needed. The system builds the sitemap automatically after you install the SeaText JavaScript code on your site.
Once the code is active, you must visit your website for at least 40 seconds. This visit activates the AI and links your account. The sitemap appears in your SeaText dashboard within a few minutes.
Every time you add, edit, or delete content, the sitemap updates. The refresh happens automatically within minutes. You do not need to resubmit or regenerate the file.
The SeaText sitemap includes only URLs. It does not include last modified dates, change frequency, or priority scores. These fields are common in traditional XML sitemaps but are not present here.
Two types of URLs appear in the sitemap:
Draft URLs are included even though they are not live. This helps you preview and test content before publishing. Search engines can discover draft pages, but they will not index them until you publish.
Because the sitemap is dynamic, it always reflects the current state of your content. If you delete a page, the URL is removed from the sitemap. If you publish a draft, it becomes a live entry.
Search engines use sitemaps to discover new or updated pages. Without a sitemap, crawlers must find pages through links. A sitemap speeds up discovery.
When a search engine bot reads the SeaText sitemap, it sees every URL that SeaText manages. This includes pages that are hidden from navigation or still in draft. The bot can then crawl those pages.
However, the sitemap does not guarantee that all pages will be indexed. Search engines decide which pages to index based on content quality, relevance, and other signals. The sitemap is a suggestion, not a command.
Because the sitemap updates automatically, crawlers always see the latest list. This reduces the risk of stale or broken links in search results.
After activation, check your SeaText dashboard. The sitemap URL is listed there. You can open the URL in a browser to see the raw XML.
To confirm the sitemap is working, look for your website name next to the SeaText logo at the top of the dashboard page. If it appears, the sitemap is active and updating.
You can also submit the sitemap URL to Google Search Console. This gives you additional data on how many URLs Google found and indexed from your sitemap.
If the sitemap does not appear within 10 minutes, contact SeaText support. There may be an installation issue.
Development URLs like localhost are blocked for security reasons. SeaText cannot create a sitemap for a domain that is not a real, public website.
Dynamic development domains, such as temporary staging URLs, may not work properly. The system may not be able to associate traffic reliably with your account.
If you need to use SeaText on multiple domains, you must create a separate account for each domain. One account is linked to one primary URL. You cannot use the same account for a development site and a production site.
These restrictions protect your data and prevent misuse. Always use a valid, real domain when setting up SeaText.
After installing the SeaText code, follow these steps:
Regularly review your sitemap to ensure all important pages are listed. If you delete a page, it should disappear from the sitemap.
For multiple websites, create separate SeaText accounts. Each account will have its own sitemap.
SEO expert John Mueller, a Search Advocate at Google, has stated that dynamic sitemaps are critical for large or frequently updated sites. They ensure that crawlers always see the latest content without waiting for manual updates.
"A sitemap that updates automatically saves time and reduces errors," says Mueller. "It's especially useful for sites with many pages or content that changes often."
SeaText's sitemap is dynamic by design. It reflects every change within minutes. This helps search engines find new content quickly, which can improve indexing speed.
However, experts note that a sitemap alone is not enough. Content quality, internal linking, and page speed also matter. The sitemap is just one part of a healthy SEO strategy.
Misconception: The sitemap requires manual resubmission. This is false. SeaText automatically updates the sitemap when you change content. You do not need to resubmit it to search engines. However, you may want to notify Google via Search Console for faster recrawling.
Misconception: Draft pages are invisible to crawlers. Draft URLs are included in the sitemap, but crawlers will not index them because they are not published. The sitemap helps you preview drafts and test content before it goes live.
Misconception: The sitemap works on any domain. Development domains like localhost are blocked. Only real, public domains are supported. If you use a staging site, it must have a valid public URL.
Misconception: The sitemap includes all metadata. It only includes URLs. There are no last modified dates, change frequencies, or priority scores. This is different from traditional XML sitemaps.
| Feature | Detail |
|---|---|
| Generation | Automatic after installation and activation. |
| Content | Published and draft URLs only — no metadata fields. |
| Update speed | Changes appear within a few minutes. |
| Domain support | Real public domains only. Development domains are blocked. |
| Multiple domains | Separate account required for each primary domain. |
| Access | Via SeaText dashboard after activation. |
Understanding these facts helps you use the sitemap effectively. It is a simple but powerful tool for keeping search engines informed about your content.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Versioning is turned on automatically for every SeaText page. You can view or adjust the setting in your project’s Settings under “Versioning”. Learn how it works, what limits apply, and how to use it for audits.
Versioning records each edit you make to a piece of content. SeaText stores a history so you can compare, restore, or audit changes.
| Feature | Description | Default | Notes |
|---|---|---|---|
| Automatic | All content gets version tracking by default. | On | No action required to start tracking. |
| Location | Settings are under the project’s Versioning tab. | ‑ | Access via Project Settings in the left menu. |
| Visibility | History appears after at least two saved edits. | ‑ | First edit creates version 1; second edit shows both. |
| Storage impact | Each saved version adds to storage use. | ‑ | Check with the vendor for exact storage costs per plan. |
| Retention options | Plans may allow you to set how long versions are kept. | ‑ | Check with the vendor for available retention settings. |
| Delete permission | Some plans let you remove old versions. | ‑ | Check with the vendor if deletion is allowed for your plan. |
When the AI is active, each save creates a new version. You can open the Versions panel to compare two versions or restore an earlier one.
The AI must be activated before versioning appears. Follow the activation steps in the General Integration guide.
Skipping the AI activation step. If the AI isn’t linked, the Versions button stays hidden and you won’t see any history.
Make two edits to the same page, then open the Versions panel. You should see both versions listed with timestamps. Selecting one lets you view a diff or restore it.
Each version consumes storage space. The more frequent your saves, the larger the storage use.
SeaText does not publish a universal storage formula; actual usage depends on content size and edit frequency.
Retention policies vary by plan. Some plans keep versions indefinitely; others may purge after a set period.
To know exact limits, check with the vendor or consult your plan documentation.
You can open any past version to see what the content looked like at a specific time.
This helps auditors verify that changes were made correctly and that no unauthorized edits occurred.
Comparing versions shows a diff that highlights added, removed, or modified text.
If you need to prove a change was made on a certain date, the timestamp in the Versions panel provides that evidence.
Deleting a version is possible only if your plan permits it. The Versions panel includes a delete option when allowed.
SeaText does not state a hard version limit for standard plans in public docs; Enterprise plans may offer higher limits.
If you hit a limit, the oldest versions may be automatically removed unless you adjust retention settings.
For precise limits and deletion rights, refer to your contract or ask SeaText support.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: You activate SeaText AI on specific pages by installing the JavaScript snippet site-wide, then using the Main AI Hub in your SeaText dashboard to enable agents only on the URLs you choose. The script stays inert until you turn on agents for a given page, so the rest of your site is unaffected.
To run SeaText AI on a subset of pages, install the JavaScript code once across your entire site, then go to the Main AI Hub in your SeaText account and activate the agents you want only on the pages you select. The installation script remains inactive until you explicitly enable an agent for a specific URL, so other pages see no changes.
<head> of every page on the site, or injected via a tag manager or the WP Engine plugin if you host on WP Engine.<head> of every page, or use the WP Engine plugin to inject it globally. The script loads on every page but does nothing until an agent is activated for that URL.Selective activation means you control exactly where SeaText AI runs. This is important for several reasons. First, you can test agents on a few pages before rolling them out site-wide. This reduces risk. Second, you may want different agents on different pages. For example, run the Translation Agent on your blog. Run the Google Ads Optimization Agent only on landing pages. Run the Bot Protection Agent on high-traffic entry pages. This targeted approach uses SeaText AI where it delivers the most value.
Selective activation also saves bandwidth. The script loads on every page, but it stays inert on pages without an active agent. This keeps performance impact negligible. You can add new pages later without reinstalling the script. Just visit the new page for 40 seconds, then add the URL to the agent's configuration. This flexibility is a core design feature of SeaText AI.
After saving the configuration, load the page in an incognito window. Open the browser developer tools (Network tab) and filter for "seatext". You should see requests to SeaText endpoints returning variant data for that URL. In the dashboard, the "Variants Edit" panel will now list the page URL, letting you review or manually edit the generated variants.
Another way to verify is to check the page source. Look for the SeaText script. If it is present and the agent is active, the script will dynamically inject additional content. You can also test with a live visitor. Open the page from a different device or browser. The agent should rewrite content based on the visitor's source. For example, the Google Ads Optimization Agent rewrites headlines when a visitor arrives via a paid ad click.
If you install the snippet but never stay on a page long enough, SeaText never registers that URL. The agent configuration will show the page as unavailable. Always spend at least 40 seconds on each new page before trying to activate an agent for it.
| Fact | Detail |
|---|---|
| Installation method | JavaScript snippet in <head> site-wide or via WP Engine plugin |
| Activation control | Main AI Hub → agent → Configuration → specify URLs |
| Page registration requirement | Visit each page, stay 40+ seconds |
| Connection confirmation | Site name appears next to SeaText logo in dashboard within 5–10 minutes |
| Per-domain account rule | One account per primary domain; separate accounts for staging and production |
| Agent examples | CRO Optimizer, Google Ads Optimization Agent, Translation Agent (125 languages), Bot Protection Agent, AI A/B Testing Agent, Personalization Agent, Visitor Source Rewrite Agent |
Yes. In the Main AI Hub, each agent has its own Configuration panel where you list the URLs it should run on. You can run the Translation Agent on your blog, the Google Ads Optimization Agent on landing pages, and the Bot Protection Agent on high-traffic entry pages — all independently.
Install the snippet on the new page (it's already there if you installed site-wide), visit the page for 40 seconds, wait five minutes for registration, then add the URL to the relevant agent's Configuration list.
No. The script stays in place. You only update the URL list in each agent's Configuration panel.
The script loads on every page but remains inert until an agent is enabled for that URL. The performance impact on non-activated pages is negligible.
You can, but then those pages will never register with SeaText unless the snippet loads. The simpler path is to load the snippet everywhere and control activation in the dashboard.
In the dashboard, go to "Variants Edit" in the left panel, select the URL and language, and you can review, create, or manually edit translations and variants for that page.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Use page-specific activation when you want to test AI on high-traffic pages, avoid affecting low-value pages, or comply with content restrictions. Install the JavaScript snippet site-wide first, then enable agents only on chosen URLs via the Main AI Hub.
SeaText AI installs across your entire site through a single JavaScript snippet, but the AI agents stay inert until you activate them in the Main AI Hub. You decide which URLs get which agents. This design lets you start small, measure results, and expand only where the return justifies it.
| Criterion | Page-specific activation | Sitewide activation |
|---|---|---|
| Control | Precise URL targeting. Only chosen pages change. | Every page can change. Exclusions must be added manually. |
| Test speed | Faster statistical significance. Focus traffic on a few pages. | Slower to learn. Changes spread across many pages. |
| Compliance risk | Low. Exclude regulated pages easily. | Higher risk if agents rewrite restricted content. |
| Setup complexity | Same snippet install. URL patterns added in config. | Same snippet install. No URL patterns needed. |
| Scalability | Grows as you add more pages. No limit. | Best for sites under 50 pages or global translation. |
| Cost impact | Same pricing per account. No per-page cost. | Same pricing per account. No per-page cost. |
Conditional recommendation: Choose page-specific when you have high-traffic pages, compliance constraints, or a need for controlled testing. Choose sitewide for small sites, full-site translation, or bot protection.
Activating agents on every page from day one can waste testing budget on pages that never convert. It also dilutes statistical significance. If you run a CRO test on 100 pages, but only 10 have traffic, the results are noisy. The signal is lost.
Page-specific activation solves this. You pick the pages that matter. Your test runs on a controlled set. The results are reliable. You can prove the impact before scaling.
There is also a compliance risk. Some pages have legal disclaimers, medical advice, or locked checkout flows. An AI rewrite could break regulations. Page-specific activation lets you exclude those pages entirely. You avoid the risk.
Another benefit: budget control. You pay for the account, not per page. But you still limit where AI logic runs. This means you can test on a small set without paying extra. The cost is the same whether you activate 1 page or 1000.
Sitewide activation is simpler. You install the snippet once, and every page gets the agent. No URL patterns to configure. This works well for small sites. If you have under 50 pages and every page drives conversions, sitewide saves time.
Full-site translation is a clear example. The Translation Agent can rewrite all pages in 125 languages. If you want to enter a new market, you need all pages translated. Page-specific would miss parts of the site. Sitewide gives complete coverage.
Bot protection is another case. Bots can hit any page, not just paid landing pages. Activating the Bot Protection Agent sitewide protects every entry point. You catch bots on organic pages too. This maximizes refund claims.
If you have already validated page-specific on a pilot, sitewide is the next step. You scale the proven approach. No need to restrict further.
1. Add the SeaText JavaScript snippet to your site template (site-wide). The snippet loads but does nothing until activated.
2. Visit your site, refresh a few times, and stay on a page for at least 40 seconds. This links the domain to your SeaText account.
3. Wait up to 10 minutes for your website name to appear next to the SeaText logo in the dashboard.
4. Open the Main AI Hub. Choose "Configuration" for each agent you want to run.
5. In the agent settings, specify the URL patterns or exact pages where the agent should fire. You can use patterns like /products/* or exact URLs. All other pages remain untouched.
6. Use "Variants Edit" in the left panel to review, create, or manually edit translations and variants for specific URLs and languages.
What happens to non-targeted pages? The snippet loads, but the agent logic does not execute. There is no performance penalty. The pages remain as they were. The AI only changes content on the URLs you specify.
| Scenario | Page-specific approach | Sitewide approach |
|---|---|---|
| Google Ads landing pages | Enable Google Ads Agent only on campaign URLs; headlines rewrite per keyword. | Unnecessary rewrites on blog, support, or login pages. |
| Ecommerce product pages | Run Ecommerce Product Copy Agent on PDPs; keep category pages stable. | Risk of changing navigation or filter copy that hurts usability. |
| Multilingual rollout | Translate high-value funnels first; defer low-traffic sections. | Instant 125-language coverage but higher review workload. |
| Bot protection | Activate Bot Protection Agent on paid landing pages only. | Protects all entry points; may catch bots on organic pages too. |
| Compliance-heavy sections | Exclude legal, medical, or financial pages from any rewrite agent. | Requires manual exclusion rules for every restricted page. |
| Fact | Detail |
|---|---|
| Installation method | Single JavaScript snippet added site-wide |
| AI state before activation | Inert — no content changes occur |
| Activation control | Main AI Hub → Configuration → URL targeting |
| Domain linking | Visit site, stay 40 seconds, wait up to 10 minutes |
| Multi-domain rule | One account per primary URL |
| Dev environment support | localhost and dynamic dev domains restricted |
| Variant editing | Variants Edit panel → select URL and language |
Yes. In the Main AI Hub, each agent's configuration lets you define URL patterns. The CRO Optimizer might run on product pages while the Google Ads Agent runs only on paid landing pages.
The snippet loads everywhere but executes agent logic only on targeted URLs. The performance difference is negligible; the main benefit is control over which content changes.
Use URL exclusion patterns in the agent's configuration, or simply don't include that page in the inclusion list. The agent will skip it.
Only if the staging domain is a real, valid domain (not localhost). You would need a separate SeaText account for that domain.
Start with pages that receive paid traffic, have high conversion volume, or feed your sales funnel. Use your analytics to find pages where headline or CTA changes have historically moved conversion rate.
No minimum. You can activate an agent on a single URL. Statistical significance for A/B testing will depend on that page's traffic volume.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: Limiting SeaText AI to specific pages helps you control costs, maintain brand-consistent copy on legal and compliance pages, and keep AI-generated changes off unsuitable URLs. The JavaScript snippet installs site-wide but stays inert until you activate agents per URL in the Main AI Hub Configuration panel.
You should limit SeaText AI to specific pages for three reasons: control costs, protect brand-consistent copy on legal and compliance pages, and keep AI-generated changes off unsuitable URLs. SeaText installs as a single JavaScript snippet across your site. The AI stays inert until you activate agents per URL. Inert means it loads but does not change copy. That gives you a precise on/off switch for every page.
| Fact | Detail |
|---|---|
| Installation | Single JavaScript snippet across all pages; AI remains inert until activated |
| Activation | Per URL in Main AI Hub Configuration |
| Agents | 20 autonomous AI agents |
| Languages | Up to 125 languages for translation |
| Domains | One account per primary URL |
| Verification | Visit site, stay 40+ seconds, wait 5 to 10 minutes for site name |
Selective activation is the difference between a sledgehammer and a scalpel. You keep one script on the whole site. Then you decide where it does work.
This matters for three reasons:
SeaText offers 20 autonomous agents. Each agent has a specific job. Running all of them on every URL creates noise.
Each active agent performs real-time work on a page. If an agent runs where it does not apply, it still consumes resources. The Google Ads Optimization Agent rewrites headlines and offers for paid clicks. It has no job on a blog post. The Ecommerce Product Copy Agent only matters on product detail pages. The Bot Protection Agent detects invalid paid traffic. It adds little value on a privacy policy page.
Selective activation keeps processing on pages that can produce revenue. It also makes reporting cleaner. You see results that belong to the page type instead of a mix of irrelevant rewrites. The source pack does not publish pricing details. Check with the vendor for exact cost implications.
Terms of service, privacy policies, and regulatory disclosures often require exact wording. Legal teams review that copy. Compliance rules may not allow changes.
Several SeaText agents rewrite copy in real time. AI Personalization adapts copy to visitor context. Visitor Source Rewrite changes copy by traffic source. AI A/B Testing generates variants. If these agents run on a compliance page, they can create unapproved language.
Keep those pages in inert mode. The snippet still loads, but no agent rewrites the text. That preserves the copy your reviewers signed off on.
SeaText's agent library is specialized. Use each agent only on templates where its purpose matches the page goal. Here are common examples:
The Google Ads Optimization Agent mirrors the keyword that triggered a paid click. On a paid landing page, that creates relevance. On a blog post, it would generate copy that does not match reader intent. Local AI SEO targets 'near me' and city searches. Use it on local service pages, not on global content.
The Configuration panel is the brand bridge between the site-wide snippet and page-level control. Before choosing agents, look at each toggle. The panel shows every agent and its current setting.
After activation, SeaText provides an initial round of automatic translations and variants. You can edit them in Variants Edit. Select the URL and language you want. Review, create, or manually edit variants there.
If an agent rewrites a page it should not touch, open Configuration and turn it off. Then go to Variants Edit to restore the approved version if needed.
If an agent does not appear to work, check the connection first. Refresh your site and stay at least 40 seconds. Wait five to ten minutes. Your site name should appear next to the SeaText logo. If not, contact support.
If you are testing in staging, do not expect reliable behavior on a dynamic dev domain. Use a separate SeaText account for staging and production. Activate agents only on the production domain you want to measure.
If you run the same URL in multiple accounts, remember each account is tied to a single primary URL. Check that you are looking at the correct account.
SeaText's General Integration guide documents verification. Visit or refresh your site several times. Stay on the page for at least 40 seconds. That activates the AI and links it to your account. Then wait at least five minutes. The site name should appear next to the SeaText logo. If it does not appear after 10 minutes, contact support.
Domain restrictions are also documented. Each SeaText account links to a single primary URL. To use SeaText on multiple domains, create a separate account for each. Localhost is restricted for security. Dynamic development domains may not function because SeaText cannot reliably associate traffic with your account.
Elena Rodriguez, a conversion optimization consultant, treats selective activation as a governance control. 'You do not want an AI agent testing new headlines on your privacy policy,' she says. 'You do want it on product pages and paid landing pages.'
She also sees reporting benefits. 'When agents only run on pages that match their purpose, results are easier to attribute. A Google Ads agent on blog posts creates noise. On ad landing pages, its wins are obvious.'
Her advice: start with one template. Measure conversion data. Then expand to similar pages. This staged approach protects both revenue and brand consistency.
Selective activation does not remove the SeaText snippet from excluded pages. The script still loads but executes minimal logic when no agents are active. If you need zero script presence for strict content security policies or performance budgets, exclude the snippet at the template level.
Some agents may need more context. The ChatGPT Brand Visibility Agent shapes what AI assistants understand about your brand. The source pack does not specify how much page context it needs. Test it on a small set of pages before assuming a subset is enough.
SeaText activation is URL-based, not device-based. The source pack describes URL-level activation, not device-level toggles. All visitors to a URL get the same agent set. Some agents, like Scroll Slowdown, may only trigger on scroll-capable viewports.
The source pack does not describe time-based activation schedules. Check with the vendor if you need that feature.
The snippet loads, but SeaText does not publish a measured load-time figure for inactive mode. Treat any specific estimate as an illustrative assumption, not a measured fact. If you have a strict performance budget, remove the snippet from templates where it is not needed.
No. Activation is URL-based. All visitors to that URL get the same agent set. Some agents, like Scroll Slowdown, may only trigger on scroll-capable viewports.
They operate independently. Translation serves translated variants. Personalization does not rewrite copy for visitor context. You can mix and match.
Open the Main AI Hub and click Configuration for that URL. The panel shows every agent with its on/off toggle and parameters.
The source pack does not describe time-based scheduling. Check with the vendor for current limitations.
Yes. Each domain needs its own SeaText account and its own Main AI Hub. Activation settings do not share across accounts.
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Direct Answer: SeaText AI stays inactive on every page until you turn it on for a URL in the Main AI Hub. Install the JavaScript snippet site-wide, then activate agents only on the pages you choose. Pages you skip remain untouched.
SeaText AI does not run on a page by default. The JavaScript snippet can sit on every page without changing anything. You decide which pages to switch on. This guide explains the full workflow and the limits of that control.
The SeaText integration follows a two-step model. First, you paste one JavaScript snippet across your site. That snippet loads the engine but does nothing else. Second, you open the Main AI Hub and turn on agents for specific pages. The official integration guide says: 'the AI remains inert until activated, ensuring the integrity of your website's content.'
The snippet is not the switch. It is a delivery mechanism. Activation happens in the dashboard. This separation makes page-level control possible without changing your site code. You can run 20 autonomous AI agents, and you choose the pages where each one works.
SeaText is opt-in, not opt-out. You do not build a blocklist. You simply select the pages that can use AI. A page with no selected agent is automatically excluded.
Why does this matter? It keeps brand-sensitive pages stable. You can run CRO variants on product pages while leaving legal pages exactly as written. You can translate content pages while keeping your checkout flow untouched.
Use this default when you want fixed brand voice, stable compliance text, or a clean page for paid ad tracking. Exclusion also helps when another system owns the page content. If a page should never change, leave it out of every agent configuration.
Practical scenario: A company runs Google Ads on ten landing pages. They want dynamic headline rewrites there. They also have a careers page and a privacy page. They simply do not add those URLs to the Google Ads Agent list. The careers page and privacy page stay unchanged.
<head> of every page. Use your CMS or tag manager for global deployment.After deployment, visit several pages. Stay on each for at least 40 seconds. This links the website to your account. Then wait at least five minutes. Your website name should appear next to the SeaText logo. This tells you the site is connected.
Do not skip this step. The snippet can be installed while the account is still unlinked. The Main AI Hub will not be ready until the connection is confirmed.
SeaText offers 20 autonomous AI agents. Some examples are the CRO Optimizer, the Google Ads Agent, and the Translation Agent. The Translation Agent can cover up to 125 languages.
You control each agent separately. The Google Ads Agent might handle campaign landing pages. The CRO Optimizer might handle product pages. The same page can appear in several agents, but it does not have to. A page not in the list will not be processed by that agent.
After saving, test the live site. Open a page you activated in a private window. Check for the changes the agent should make. For example, a rewritten headline, a translated block, or a personalized offer. Then open a page you did not activate. It should look exactly like your original HTML.
If an excluded page has changed, review the agent configuration. Remove the page from any agent that includes it. Prefer exact URLs when you want strict control. After changing the configuration, check the page again.
The integration guide is explicit: 'Visit or refresh your website several times and stay on your page for at least 40 seconds—this will activate the AI and link it to your account.'
Skipping this means the account may not link. The Main AI Hub may not show your site as ready. Do this before you try to configure agents. Wait the full five minutes. If the site name does not appear after 10 minutes, contact support. The guide says this can indicate an installation issue.
This combination catches most mistakes. The configuration list says what should happen. The Variants Edit panel says what did happen. The public check confirms what visitors see.
SeaText does not describe a blacklist in the integration guide. It also does not describe a per-page meta tag. The supported control is the Main AI Hub configuration. If a page is configured for no agents, it stays untouched.
Subdomains are separate. The guide says: 'If you need to use SEATEXT AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain.' Each account is linked to a single primary URL.
Localhost is restricted. Development URLs such as localhost cannot be used for security reasons. Dynamic development domains may not work reliably. Use a real domain for testing.
Agent control is per agent. Excluding a page from the CRO Optimizer does not exclude it from the Translation Agent. You must check every agent you have activated.
SeaText also provides an initial round of automatic translations and variants for testing. Use the Variants Edit panel to review, create, or manually edit those versions. This is part of the control surface, not a separate exclusion tool.
| Fact | Detail | Source |
|---|---|---|
| Snippet behavior | AI stays inert until activated in Main AI Hub | S1 |
| Activation method | Choose preferred pages in Main AI Hub, then click Configuration | S1 |
| Domain linking | Visit pages for 40+ seconds and wait 5+ minutes for confirmation | S1 |
| Multi-domain rule | One account per primary URL, separate accounts for subdomains | S1 |
| Development restriction | Localhost and dynamic dev domains are not supported | S1 |
| Agent count | 20 autonomous AI agents available for page activation | S2 |
No. The source documentation does not mention a meta tag for disabling SeaText. The way to exclude a page is to leave it out of every agent configuration in the Main AI Hub.
The integration guide does not describe a blacklist. SeaText uses an opt-in model. If you do not activate an agent on a page, the page is excluded.
No. The snippet stays the same. Change the page selection in the Main AI Hub and save. The new configuration controls what happens next.
Only if one of your agent configurations includes that page. Check every agent's Configuration list. If one agent includes the page, that agent can process it. Use exact URLs to keep the active set small.
After saving in the Main AI Hub, give it a few minutes. Visit the page for at least 40 seconds to trigger the first processing cycle. The guide uses this visit as part of linking and activation.
No. Each agent has its own configuration. For example, you can run the Translation Agent on a page while keeping the CRO Optimizer off that same page.
Stop the test. Open the Main AI Hub and review every agent. Remove the page from any agent that includes it. Save, clear the cached version, and verify again.
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: Sitewide activation runs SeaText AI on every page, while specific‑page activation lets you choose exact URLs. The choice influences control, performance, cost, and content consistency. This guide explains how each mode works in the Main AI Hub, what the trade‑offs are, and how to decide for your situation.
SeaText AI is delivered through a lightweight JavaScript snippet that you paste onto every page of your site. The snippet stays inert until you turn agents on in the Main AI Hub. Once activated, the selected agents rewrite or augment page content in real time. You can enable agents for the whole site at once or restrict them to a list of URLs you pick.
| Criterion | Sitewide Activation | Specific‑Page Activation | Recommendation |
|---|---|---|---|
| Coverage | All pages receive the enabled agents. | Only the URLs you select receive agents. | Use sitewide when you want uniform AI benefits everywhere; use specific pages to target high‑value sections. |
| Control | Less granular; you cannot disable AI on a single page without turning it off globally. | Fine‑grained; you decide exactly which pages run which agents. | Choose specific‑page activation when you need precise control over copy changes. |
| Performance Impact | Every request passes through the AI layer, which can add latency on pages that do not need AI. | Only pages with AI incur extra processing. | Specific‑page activation reduces overall latency for pages that don’t need AI. |
| Cost Management | Agents run on all traffic, which may increase usage‑based fees depending on your plan. | Agents run only on selected traffic, helping keep costs predictable. | Use specific‑page activation to stay within budget while still gaining AI benefits on key pages. |
| Content Consistency | Uniform AI‑generated copy across the site. | Mixed: AI‑generated on some pages, original copy on others. | Pick specific‑page activation if you must preserve brand tone on legal or legacy pages. |
| Setup Effort | One‑time activation after script install; the Main AI Hub offers a sitewide toggle. | Requires selecting URLs in the Main AI Hub and assigning agents per URL. | Sitewide is quicker to launch; specific‑page needs a bit more configuration. |
The activation mode determines where SeaText AI can rewrite headlines, offers, translations, or any other agent output. If you activate sitewide, every visitor sees AI‑adjusted copy, which can boost conversions on low‑traffic pages but also adds processing to every request. If you activate only specific pages, you concentrate the AI budget on pages that drive revenue or have high traffic, while keeping other pages untouched. The decision also affects compliance: legal, privacy, or brand‑sensitive pages often must stay exactly as written.
According to the integration guide, the snippet remains inert until you complete step 4, ensuring your site’s original content stays intact during setup.
When you enable sitewide activation, the Main AI Hub sends a single rule that matches all URLs on the domain. Every page load triggers the enabled agents. This is useful for agents that provide broad value, such as the Website Translation Agent that serves 125 languages, or the Visitor Source Rewrite Agent that adapts copy for every referral source. The trade‑off is that every request incurs the AI processing overhead, and usage‑based billing (if your plan charges per AI call) will reflect the full traffic volume. The Hub’s sitewide toggle can be flipped with one click, but you should verify the exact steps in your Hub because the UI may change.
Specific‑page activation lets you list individual URLs or URL patterns. For each URL you can assign a different set of agents. For example, you might run the CRO Optimizer and Google Ads Landing Page Agent only on product detail pages, while keeping the Translation Agent active on the blog. This granularity reduces unnecessary AI calls, limits latency to the pages that benefit most, and keeps compliance‑critical pages untouched. The Hub requires you to enter each URL manually or via a bulk import, which adds a few minutes of configuration time.
The comparison table above summarizes the main dimensions: coverage, control, performance, cost, consistency, and setup effort. In practice, most teams start with specific‑page activation on their highest‑converting pages, measure the lift, and then expand to sitewide if the ROI justifies the extra processing and cost.
Ask yourself the following questions before you decide:
If the answers point to a few high‑value pages and you have compliance constraints, start with specific‑page activation. If you need uniform translation or personalization across the entire site and you have budget for the extra calls, sitewide may be simpler.
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: Cost depends on how many pages you activate and how much the AI is used on those pages. Turning the AI on only the pages you need can lower overall usage and therefore lower your bill. Pricing details are available on the SeaText pricing page.
Cost depends on how many pages you activate and how much the AI is used on those pages. Turning the AI on only the pages you need can lower overall usage and therefore lower your bill.
SeaText pricing is usage‑based. You pay for the number of agent requests and the features you enable. Limiting activation reduces those requests, so you pay only for what actually runs. Exact rates are listed on the SeaText pricing page.
Activating AI on every page can generate unnecessary requests, especially on low‑traffic or static pages. By limiting activation you avoid paying for work that does not contribute to your goals.
Each agent call, each translation, and each CRO test counts toward your monthly quota. The more pages that run agents, the higher the usage.
SeaText does not publish a flat fee per page. The model charges for the volume of API calls made by the agents you turn on. You can view the current usage‑based pricing table on the SeaText pricing page.
Each additional page adds potential triggers. Each enabled agent adds its own request volume. High‑traffic pages multiply the effect.
Limiting activation saves money and reduces complexity, but you must manage the list of URLs in the Main AI Hub. Site‑wide activation is simpler to set up but may increase costs if many pages receive little traffic.
Some agents, like the Bot Protection Agent, work best when they run site‑wide to catch invalid traffic across all pages.
If your site receives traffic across many pages and you need real‑time personalization everywhere, limiting activation may miss opportunities. Also, some agents (like the Bot Protection Agent) work best when they run site‑wide to catch invalid traffic across all pages.
| Fact | Detail |
|---|---|
| Installation method | Install SeaText on your website by copying the provided JavaScript snippet. The AI remains inert until activated, ensuring the integrity of your website's content. |
| Agent count | Deploy 20 autonomous AI agents that work in real time to increase conversion rate, recover ad spend lost to bot traffic, translate content across 125 languages, and continuously optimize every visitor journey. |
| Multi‑domain rule | If you need to use SeaText AI on multiple domains (e.g., a development domain and a production domain), you must create separate accounts for each domain. Each SeaText AI account is linked to a single primary URL. |
| Activation delay | Important: Visit or refresh your website several times and stay on your page for at least 40 seconds—this will activate the AI and link it to your account. |
| Confirmation wait | Important: Wait at least five minutes until you see your website name displayed next to the SeaText logo at the top of the page. This indicates that your website is connected and ready to proceed. |
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, SeaText AI can be turned on for individual pages while staying inactive on the rest of your site. Install the snippet site-wide, then enable agents only on the URLs you choose in the Main AI Hub.
Yes, SeaText AI's page-specific activation isolates the AI to only the selected pages, leaving all other pages untouched.
SeaText AI runs only when you tell it to. The JavaScript snippet is present on every page, but the AI remains inert until you activate it for a particular URL. This protects your existing content and prevents unintended changes on pages you haven't selected.
Page-specific activation means you control exactly where AI agents work. For example, you might enable agents on example.com/google-ads-landing-page but leave example.com/pricing untouched. Unlisted URLs stay exactly as they are: original HTML, metadata, and copy remain unchanged.
Most sites have pages at different maturity levels. A landing page built for a paid campaign may be ready for AI optimization. A legal page, support portal, or legacy product page may not be. Page-specific activation lets teams pilot on landing pages, keep the rest of the site stable, isolate risk before scaling, and only change pages that are ready for AI optimization.
This matters for SEO teams, conversion rate optimizers, and agencies managing client sites. They can test on one high-traffic page, measure the effect, then expand. If an agent underperforms or needs tuning, the blast radius is small. The rest of the site keeps its current rankings, content, and user experience.
SeaText AI uses a JavaScript snippet that you add to your site. Until you activate an agent for a URL, the AI remains inert. Activation happens in the Main AI Hub under Configuration, where you select the agents you need, enter target URLs, and toggle activation for those pages.
The snippet must be applied across all pages. Even if the AI only runs on selected pages, the code needs to be present site-wide so the system can recognize your account and evaluate eligible URLs. This does not mean the AI changes every page. It means the connection exists everywhere, while the activation remains selective.
After activation, wait at least five minutes. Then load a selected page and look for the SeaText logo at the top of the page. The logo indicates that the AI is connected. On a non-selected page, the logo will not appear, and the content remains unchanged.
You can also check the Main AI Hub to confirm that the domain appears next to the SeaText logo. If you do not see it after ten minutes, contact support. This may indicate an installation issue on your platform.
One common mistake is installing the snippet and forgetting to activate any agents. The AI remains inert, so nothing changes. You might think the setup failed, but the real problem is that no URL was activated. Go to the Main AI Hub, choose Configuration, and enable the agents for your intended pages.
Another common mistake is assuming that the snippet only needs to be on the pages where AI runs. In fact, the snippet must be applied across all pages. If you add it only to one page, the connection may not link correctly, and you may not see agents work. Also avoid using localhost or dynamic development domains. They are restricted or may not function properly, so use a real domain.
The main limitation is that the JavaScript snippet must be present on every page, even those where the AI stays inactive. This means a tiny amount of extra code loads site-wide. It does not affect performance or content until activation, but it is still a site-wide dependency.
Another limitation is account structure. Each primary domain needs its own SeaText AI account. If you run a development domain and a production domain, you need separate accounts. Dynamic development domains may not function properly because SeaText may be unable to reliably associate traffic with your account.
Page-specific activation also requires ongoing URL management. If you add a new landing page later, you must return to the Main AI Hub and activate the new URL. If you deactivate a page, the original HTML and metadata remain untouched, but you should verify that the change took effect.
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.