What Is the SeaText Content Sitemap? A Practical Guide
The SeaText content sitemap is a dashboard feature that appears during installation across supported platforms. It sits alongside "SeaText content versions" and helps the AI understand your site structure so agents can rewrite, translate,...
Direct Answer
The SeaText content sitemap is a menu item shown in the SeaText installation flow for WordPress, Shopify, BigCommerce, and other platforms. It appears next to "SeaText content versions" in the dashboard. Its purpose is to give SeaText's AI agents a structured view of your site's pages so they can match content variants, translations, and personalization rules to the right URLs.
SeaText does not publish a public XML sitemap file at a fixed URL like /sitemap.xml. Instead, the content sitemap is an internal index built after you install the snippet and visit your pages. The agents use that index to know which pages exist, how they relate, and where to apply keyword-matched rewrites, translations, or bot-protection logic.
Where You See It in the Dashboard
During installation on any supported platform, the SeaText setup page lists two links under the platform-specific instructions: "SeaText content versions" and "SeaText content sitemap." Both appear after you paste the JavaScript snippet and before you activate agents.
- Source S1 (general install page) shows the pair under "General / Custom" platform.
- Source S8 (BigCommerce integration) lists them in the step-by-step integration section.
Clicking either link opens a SeaText dashboard view. The content versions view lets you see and approve AI-generated text variants. The content sitemap view shows the discovered URL structure.
How the Content Sitemap Gets Built
- You add the SeaText snippet to your site (via plugin, script manager, or theme file).
- You visit several pages and stay at least 40 seconds per page (SeaText's activation requirement).
- SeaText crawls the visited pages, follows internal links, and records each unique URL, title, and content blocks.
- The dashboard populates the content sitemap with that discovered structure.
- Agents (Google Ads, Translation, Personalization, Bot Protection) reference the sitemap to decide where to act.
If you add new pages later, SeaText detects them on the next visit and updates the sitemap automatically.
Why It Matters for Each Agent
| Agent | How It Uses the Content Sitemap |
|---|---|
| Google Ads Optimization | Maps each campaign keyword to the exact landing page URL so rewrites hit the right page. |
| Website Translation | Knows every translatable page, including dynamically added posts and products, so no page is missed. |
| Visitor Source Rewrite | Routes referral traffic to the best-matching page based on URL patterns in the sitemap. |
| Bot Protection | Tracks which URLs receive paid clicks and correlates session evidence per page. |
| ChatGPT Brand Visibility | Feeds the FAQ/schema generator with a complete page inventory so AI answers cite real URLs. |
Content Versions vs. Content Sitemap
The two links serve different purposes:
- Content versions = the library of AI-generated text variants (headlines, CTAs, product descriptions) awaiting your approval or already live.
- Content sitemap = the structural map of URLs that tells agents where those variants can be applied.
Think of the sitemap as the "where" and versions as the "what." Both are required for agents to work safely at scale.
How to Access and Verify Your Sitemap
- Log in to app.seatext.com after installation.
- In the left navigation, choose "Content sitemap" (or click the link on the install page).
- Review the list of discovered URLs. Confirm key pages (home, product, landing, blog) appear.
- If pages are missing, visit them manually for 40+ seconds, then refresh the sitemap view.
- Use the search/filter box to find specific paths or patterns.
SeaText does not expose a public XML file you can submit to Google Search Console. The sitemap is for internal agent coordination only.
Limitations and What the Source Pack Does Not Cover
- No documented API to export the sitemap as XML, CSV, or JSON.
- No stated crawl frequency, depth limits, or handling of JavaScript-rendered routes.
- No guidance on excluding staging, admin, or parameterized URLs from the sitemap.
- No SLA for how quickly new pages appear after publication.
- No mention of multi-domain or subdomain handling in a single sitemap view.
If you need any of the above, contact SeaText support directly.
Key Facts (From Source Pack Only)
| Fact | Source | Excerpt |
|---|---|---|
| Content sitemap appears in the general install instructions | S1 | "Seatext content versions Seatext content sitemap" |
| Content sitemap appears in BigCommerce integration steps | S8 | "Seatext content versions Seatext content sitemap" |
| Installation requires visiting pages for 40+ seconds to activate AI | S8 | "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." |
| Each SeaText account links to a single primary URL | S8 | "Each SEATEXT AI account is linked to a single primary URL." |
| Multiple domains require separate accounts | S8 | "If you need to use SEATEXT AI on multiple domains… you must create separate accounts for each domain." |
Practical Scenarios
Scenario 1: Launching a Google Ads Campaign
You create 50 keyword-specific ad groups. After installing SeaText, you open the content sitemap to verify every landing page URL exists in the index. Missing pages mean the Google Ads agent cannot rewrite them. You visit each missing page once, wait 40 seconds, and confirm they appear.
Scenario 2: Adding a New Language
You activate the Translation agent for Spanish. The agent reads the content sitemap to know which pages to translate. If your blog has 200 posts but only 150 show in the sitemap, the remaining 50 stay untranslated until you visit them or SeaText discovers them via internal links.
Scenario 3: Auditing Bot Protection Coverage
You suspect bot traffic on a specific campaign landing page. In the content sitemap you locate that URL, then check the Bot Protection agent's evidence report for that exact path. The sitemap ensures you're looking at the right page.
Terminology Quick Reference
- SeaText snippet
- The JavaScript code you paste into your site's
<head>or via a platform integration. - Agent
- An autonomous AI workflow (Google Ads Optimization, Translation, Personalization, Bot Protection, ChatGPT Visibility, etc.).
- Content versions
- The set of AI-generated text variants for headlines, CTAs, product copy, etc., shown for approval.
- Content sitemap
- The internal URL index SeaText builds from visited pages; used by agents to target actions.
- Primary URL
- The single domain tied to one SeaText account; subdomains and additional domains need separate accounts.
FAQ
Is the SeaText content sitemap the same as an XML sitemap for Google?
No. It is an internal dashboard view for SeaText agents. It is not served at /sitemap.xml and cannot be submitted to Google Search Console.
Can I export the content sitemap to audit my site structure?
The source pack does not document an export feature. You can manually copy URLs from the dashboard view, but there is no supported API or download button.
How often does the content sitemap update?
SeaText updates it when you (or any visitor with the snippet active) visit a page. There is no published crawl schedule.
What happens if I have a single-page application (SPA) with client-side routing?
The source pack does not address SPA handling. SeaText likely relies on the snippet firing on each route change. Test by visiting each route and checking the sitemap.
Can I exclude staging or admin URLs from the content sitemap?
No exclusion controls are documented. The practical workaround is to avoid visiting those URLs while the snippet is active, or use a separate SeaText account for staging.
Does the content sitemap support multiple languages or regional subdirectories?
It lists every discovered URL, including /es/, /fr/, etc. The Translation agent uses that list to know which pages already have translations and which need them.
What should I do if the content sitemap stays empty after installation?
Visit your homepage and key pages for at least 40 seconds each. Wait five minutes, then refresh the dashboard. If the site name still doesn't appear next to the SeaText logo, contact support (Source S8).
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText Can Help
SeaText installs in under a minute on WordPress, Shopify, BigCommerce, Webflow, and 200+ other platforms. Once the snippet is active, the content sitemap builds automatically as you browse your site. Agents then use that map to rewrite landing pages for each Google Ads keyword, translate every page into 125 languages, personalize copy by referral source, detect bot clicks, and feed ChatGPT a complete FAQ schema — all from one dashboard.
Limitations to know: each account covers one primary domain; staging or additional domains need separate accounts. The content sitemap is internal — you cannot export it as XML for Google. If you need crawl controls, exclusion rules, or API access, ask support before scaling.