How SeaText Integrates With Your Website: Implementation Steps, Control, and Verification
SeaText integrates by adding a single script to your site, then activating the Google Ads Landing Page agent (or other agents) to detect URL parameters from ad clicks and rewrite headlines, copy, offers, and...
SeaText connects to your website through a lightweight JavaScript snippet you paste once — typically in the <head> or via Google Tag Manager. After the snippet loads, you activate the Google Ads Landing Page agent (or other agents) from the SeaText dashboard. The agent reads the keyword parameter that Google Ads appends to your landing-page URL (for example ?keyword=office+space), matches it to a keyword list you approve, and rewrites the page content before the visitor sees it. You retain full control: every rewritten version appears in the dashboard for review, you can edit the AI output manually, add instructions for the model, or turn optimization off for any keyword.
How the Integration Works End to End
The integration has three moving parts: the snippet, the dashboard, and the agent logic. The snippet is a single <script> tag that loads asynchronously and adds less than 50 KB gzipped. It does not block rendering. Once present, it listens for page loads, extracts query parameters (UTM terms, gclid, custom keyword parameters), and sends them to the SeaText edge function. The edge function looks up the keyword in your approved list, fetches the pre-generated variant (or generates one on the fly if it's the first visit for that keyword), and returns a JSON patch that the snippet applies to the DOM — swapping headlines, body copy, offers, product blocks, and CTAs. The original page remains in your CMS unchanged; visitors see the personalized version only while the session matches an approved keyword.
Step-by-Step Implementation
- Create a SeaText account and open the dashboard. The dashboard is where you manage agents, keyword lists, and review rewritten copy.
- Copy the installation snippet. In the dashboard you'll find a unique
<script src="https://cdn.seatext.com/..." async></script>line. Paste it into your site's global<head>or add it through Google Tag Manager / Segment / Tealium as a custom HTML tag. The snippet works on any platform — WordPress, Webflow, Shopify, static HTML, React, Next.js, Vue — because it only reads the URL and mutates the rendered DOM. - Verify the snippet loads. Open your site with
?seatext_debug=1appended to any URL. The console will log "SeaText snippet loaded" and show the detected parameters. If you use a CSP, addhttps://cdn.seatext.comandhttps://api.seatext.comtoscript-srcandconnect-src. - Activate the Google Ads Landing Page agent. In the dashboard, toggle the "Google Ads Landing Page AI" agent to Active. This agent is purpose-built for paid-search traffic; other agents (Translation, Personalization, A/B Testing, etc.) can be activated independently.
- Connect your Google Ads account (optional but recommended). Linking lets SeaText pull your campaign/keyword structure automatically and suggest which keywords to personalize. You can also upload a CSV of keywords manually.
- Build your keyword list. For each keyword you want personalized, click Add keyword, enter the exact term (e.g., "short-term stay"), and approve the AI-generated rewrite. The dashboard shows a side-by-side diff: original vs. rewritten. Edit the rewrite if needed, add guidance like "emphasize flexible checkout", then save.
- Set traffic allocation. By default, 100% of matching traffic sees the rewrite. You can lower this to run a shadow test (e.g., 10%) while you monitor conversion data.
- Go live. Click Publish. The next visitor who clicks an ad for an approved keyword will see the tailored page.
Prerequisites Before You Start
- Admin access to your site's
<head>or tag manager. You need to paste the snippet once. - Google Ads campaigns using keyword insertion or explicit keyword tracking parameters. SeaText reads the keyword from the landing-page URL. If your ads use only
gclidwithout a keyword parameter, enable "Auto-tagging" in Google Ads and add{keyword}to your final URL suffix (e.g.,?kw={keyword}). - A list of keywords you actually bid on. Personalizing for keywords you don't bid on wastes review time and can confuse organic visitors.
- Content that can be swapped safely. The agent rewrites text nodes and attribute values (headlines, button labels, meta descriptions). It does not restructure HTML, move containers, or execute custom JavaScript. If your page relies on a rigid layout where copy length changes break design, set character-length constraints in the keyword settings.
- Consent for personalization under your privacy policy. The snippet sets a first-party cookie (
seatext_session) to maintain variant consistency during the session. Disclose this in your cookie notice.
What Gets Rewritten (and What Doesn't)
| Element | Rewritten? | Notes |
|---|---|---|
| Headlines (H1–H3) | Yes | Primary target; matches keyword intent. |
| Body paragraphs | Yes | Rewritten to reflect the search query. |
| CTA button text | Yes | e.g., "Book a tour" → "Reserve your short-term stay". |
| Offer blocks / pricing tables | Yes | Text inside cells; structure unchanged. |
| Meta title & description | Yes | Updated for SEO relevance on paid landing. |
| Navigation, footer, schema markup | No | Global site chrome is preserved. |
| Images, videos, PDFs | No | Media assets are not swapped. |
| JavaScript-rendered components (React, Vue) | Partial | Works if the component renders text nodes after hydration; may need a data-seatext-ignore attribute on dynamic widgets. |
Control & Verification
Every keyword you approve gets a version history in the dashboard. You can:
- Preview the rewrite on your live URL by appending
?seatext_preview=keyword-slug. - Edit the AI output directly in a rich-text diff view.
- Add instructions like "Use UK spelling" or "Mention 24/7 support" that the model follows on the next regeneration.
- Pause a single keyword without disabling the agent.
- Export all rewrites as CSV for compliance review.
To verify the integration is working in production, open an incognito window, click one of your own ads (or simulate with the exact final URL + keyword parameter), and confirm the headline changes. The dashboard's "Live view" panel also shows real-time sessions, the keyword matched, and the variant served.
Common Integration Scenarios
Scenario A: Single landing page, 50+ keywords
You run one generic landing page for a Google Ads campaign with 50 keywords. After snippet install, you activate the Google Ads agent, import the keyword list from Google Ads, and approve rewrites for the top 20 keywords by volume. The remaining 30 keywords fall back to the original page. Result: each high-volume keyword gets a tailored headline and offer; long-tail keywords keep the generic page.
Scenario B: Multiple landing pages, different campaigns
You have separate pages for "office space", "coworking", and "virtual office". Install the snippet globally. In the dashboard, create three keyword groups mapped to each page's URL path. Activate the agent. Visitors clicking "coworking" ads land on the coworking page and see coworking-specific rewrites; "office space" clicks see office-space rewrites on the office-space page.
Scenario C: Headless / SPA (Next.js, React Router)
Because the snippet runs on every route change (it listens to popstate and pushState), personalization works on client-side navigation. Add data-seatext-ignore to any component that manages its own copy via CMS API to prevent double-rewriting.
Limitations & When This Advice Does Not Apply
- No keyword parameter in the URL. If your ads use only
gclidand you cannot add a keyword parameter, SeaText cannot know which keyword triggered the click. Workaround: enable Google Ads auto-tagging and add{keyword}to the final URL suffix. - Heavy client-side rendering with no server-side text. If the entire page is built from JSON after load, the snippet may rewrite too late or miss elements. Use the
data-seatext-ignoreattribute or server-side render the critical copy. - Strict CSP without
https://cdn.seatext.comandhttps://api.seatext.com. The snippet will be blocked. Update your policy. - Pages behind login or paywall. The agent only works on public URLs Google can crawl and visitors can reach directly from an ad.
- Non-Google ad platforms without keyword parameters. The Google Ads agent expects Google's parameter format. For Meta, TikTok, or email, use the Visitor Source Rewrites agent instead (separate activation).
Key Facts
| Fact | Detail | Source |
|---|---|---|
| Installation time | Under 1 minute (single script tag) | S2 |
| Snippet size | < 50 KB gzipped, async, non-blocking | S2 |
| Keyword detection | Automatic from URL parameters (UTM, gclid, custom) | S1 |
| Rewrite scope | Headlines, body copy, offers, product blocks, CTAs, meta tags | S2 |
| Control features | Per-keyword approve/edit/pause, preview URLs, version history | S1 |
| Agent activation | Toggle per agent in dashboard (Google Ads, Translation, A/B Testing, etc.) | S2 |
| Session consistency | First-party cookie seatext_session | S1 |
| Debug mode | Append ?seatext_debug=1 to any URL | S1 |
| Preview mode | Append ?seatext_preview=keyword-slug | S1 |
| CSP requirements | Allow https://cdn.seatext.com (script-src) and https://api.seatext.com (connect-src) | S1 |
FAQ
Do I need developer help to install the snippet?
Usually not. Anyone with access to the site's <head> or Google Tag Manager can paste the one line. If you use a strict CSP, a developer must add the two domains to the policy.
Will the snippet slow down my page?
The script loads asynchronously, is under 50 KB gzipped, and executes after DOMContentLoaded. It does not block rendering or Core Web Vitals.
Can I use SeaText without Google Ads?
Yes. The Visitor Source Rewrites agent personalizes by referrer (Meta, email, organic, direct) instead of keyword. Activate that agent instead of (or alongside) the Google Ads agent.
What happens if the AI writes something inaccurate?
You review every rewrite before publishing. You can edit the text manually, add correction instructions, or pause the keyword. Nothing goes live without your approval.
Does SeaText change my CMS content?
No. Rewrites happen in the browser via DOM mutation. Your CMS, database, and source HTML stay exactly as they are.
Can I A/B test the personalized version against the original?
Yes. Set traffic allocation below 100% for any keyword (e.g., 50%) to run a split test. The dashboard reports conversions per variant.
Is there a free trial?
SeaText offers a free 1-month pilot for the Google Ads Landing Page agent. Activate it from the dashboard after installing the snippet.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.