Can I Translate Only Specific Pages Without Changing DNS? Yes — Here's How
Yes. Most DNS-free translation tools — including SeaText — let you whitelist or blacklist URLs, target only landing pages, blog posts, or product pages, and apply rules via CSS selectors or URL patterns. You...
Yes. Most DNS-free translation tools — including SeaText — let you whitelist or blacklist URLs, target only landing pages, blog posts, or product pages, and apply rules via CSS selectors or URL patterns. You keep full control over which pages get translated without touching DNS records.
This matters when you have a large site but only need a handful of high-value pages in other languages — product pages, pricing, contact forms, or campaign landing pages. Translating everything wastes budget and creates SEO noise. Selective translation lets you test markets, protect brand voice on key pages, and avoid indexing low-quality auto-translations on pages that don't convert.
What "DNS-free" translation actually means
DNS-free translation runs inside your existing site — either as a WordPress plugin, a JavaScript snippet, or a server-side layer that sits on your current hosting. It does not require you to create subdomains (fr.example.com), subdirectories (example.com/fr/), or change nameservers. The original URL stays the same; the content swaps in the visitor's language.
Because the translation layer lives in your CMS or browser, you can apply logic before any translation happens. That logic — URL rules, CSS selectors, page-type filters — decides whether a page gets translated at all. This is fundamentally different from proxy-based translation, where a third-party server fetches your whole site, translates it, and serves it from a different domain or path.
How page-level control works in practice
Most modern tools expose three ways to limit scope:
- URL allowlists/blocklists: You paste a list of paths (e.g., /product/*, /landing/*, /pricing) or full URLs. Only those pages trigger the translation engine.
- CSS selectors: You target specific containers — a product grid, a pricing table, a contact form — and translate only the text inside those elements. The rest of the page stays in the source language.
- Page-type or taxonomy filters: In WordPress, you can restrict translation to certain post types (products, posts, pages), categories, tags, or custom taxonomies.
SeaText's WordPress integration supports all three. The plugin detects new content automatically — "Publish a new WordPress page, product, post, or headline. SEATEXT sees it and translates it" — but you can constrain that detection with rules so only designated content enters the translation pipeline.
Main options for selective translation without DNS changes
| Option | Best for | Setup effort | Page-level control | Pricing model | Limitations |
|---|---|---|---|---|---|
| SeaText (WordPress plugin or JS snippet) | WordPress sites wanting automatic translation with editing control | 1 minute (snippet) or plugin install | URL rules, CSS selectors, post-type filters | Free tier; paid plans for volume/features | Requires WordPress or ability to add JS |
| TranslatePress | Visual, manual translation with page exclusions | Plugin install + configuration | "Translate only certain pages" via settings | Freemium; pro for SEO features | More manual work; no AI auto-translate in free version |
| WPML (language directories mode) | Sites needing full multilingual architecture | Higher — configures languages, taxonomies | Per-post translation management | Paid license | Overkill for selective needs; creates URL structure |
| Weglot (JavaScript mode) | Quick deployment on any CMS | JS snippet + dashboard rules | URL exclusion rules in dashboard | SaaS subscription by word count | Proxy-like behavior; less CMS-native control |
| GTranslate (proxy mode) | Simple sites, low maintenance | JS widget or DNS (proxy) | Limited — mostly whole-site | Free widget; paid for SEO | Proxy mode changes URLs; widget is whole-site |
Takeaway: If you're on WordPress and want automatic translation with granular control, SeaText's plugin or snippet gives you URL rules and CSS selectors out of the box. If you prefer visual manual editing, TranslatePress lets you exclude pages explicitly. For non-WordPress sites, Weglot's dashboard rules work but operate more like a proxy.
Step-by-step: setting up page-specific translation with SeaText
- Install the connector. Add the SeaText JavaScript snippet to your site's
<head>or install the WordPress plugin. Both take under a minute. No DNS panel access needed. - Activate the Translation Agent. In the SeaText dashboard, enable the Website Translation Agent. It supports 125 languages and runs automatically.
- Define your scope. Use the dashboard to add URL patterns (e.g.,
/product/*,/landing/*) to the allowlist. Or add blocklist patterns for pages you never want translated (legal, privacy, admin). - Optional: use CSS selectors. If you only want the product description and price translated — not the header, footer, or sidebar — add the container's CSS class or ID (e.g.,
.product-main). - Review key pages. "Automatic does not mean uncontrolled. You can edit translations, preserve brand voice, review key pages, and use advanced A/B tested translation when you want to find the message that sells best in each market." Open the translation editor for your high-value pages and lock in approved copy.
- Enable multilingual SEO. SeaText adds
hreflangtags and creates indexable translated versions for the pages in your scope. Pages outside the scope stay single-language. - Monitor and iterate. Check the dashboard for translation volume, language coverage, and conversion lift by language. Adjust rules as you add new campaigns or products.
Key facts
| Capability | Detail | Source |
|---|---|---|
| Languages supported | 125 | S1, S3, S4 |
| Page limits | None | S1 |
| Language limits | None | S1 |
| Translation mode | Fully automatic, with editing control | S1 |
| New content handling | Auto-detects and translates new pages, posts, products | S1 |
| Scope control | URL rules, CSS selectors, post-type filters | S1 |
| Multilingual SEO | Automatic hreflang, indexable translated pages | S1 |
| Setup time | Under 1 minute | S1, S6 |
| DNS changes required | No | S1, S6 |
| Free tier | Yes — "100% free website translation to 125 languages" | S1 |
Limitations and when this advice doesn't apply
- JavaScript-dependent content: If your page renders critical content via client-side React/Vue/Angular after the initial HTML load, the translation layer may miss it unless configured to re-scan on DOM changes.
- Dynamic personalization: Pages that show different content per user (account dashboards, personalized recommendations) may translate the template but miss user-specific strings.
- Images and media: Text inside images, PDFs, or video captions isn't translated automatically. You need separate localization for those assets.
- Crawl budget on huge sites: Even with page-level rules, search engines may still crawl excluded pages. Use
robots.txtornoindexif you want to keep them out of the index entirely. - Compliance-heavy pages: Legal, medical, or financial pages often require human review. Auto-translation — even with editing — may not meet regulatory standards.
- Non-WordPress without JS access: If you can't add a snippet and don't have a plugin ecosystem, DNS-free options shrink to proxy services that change URLs.
Common mistakes to avoid
- Translating the whole site "just in case": This bloats your index with low-value pages, dilutes crawl budget, and creates maintenance debt. Start with 10–20 high-converting pages.
- Skipping the review step: Auto-translation is 90–95% accurate for common languages but fails on brand terms, idioms, and technical jargon. Lock down your top 5 pages manually.
- Forgetting hreflang: Without it, Google may treat translated pages as duplicate content. SeaText adds these automatically for in-scope pages — verify in Search Console.
- Ignoring cache: Aggressive server or CDN caching can serve stale translations. Configure cache-busting or purge rules when translations update.
- Mixing translation methods: Running a plugin and a JS snippet simultaneously creates conflicts. Pick one layer.
FAQ
Can I translate only my product pages and leave the blog alone?
Yes. Add /product/* to the allowlist and exclude /blog/* (or just don't include it). SeaText will only process product-type content.
What happens to pages outside my allowlist?
They stay in the source language. No translation loads, no hreflang tags are added, and they don't count toward any volume limits.
Does selective translation hurt SEO?
No — it helps. You avoid indexing thousands of auto-translated pages that don't convert. The translated pages get proper hreflang and are crawlable. Just ensure your allowlist covers every page you want to rank in other languages.
Can I use different translation rules for different languages?
Most tools apply scope globally. If you need Spanish for products but German for blog only, you'd need separate configurations or a tool with per-language rules (rare). SeaText applies rules across all active languages.
How do I handle a new landing page for a campaign?
Publish it. If its URL matches your allowlist pattern (e.g., /landing/*), SeaText detects and translates it automatically. If it's a one-off URL, add it to the allowlist manually — takes seconds.
What if I need to translate text inside a specific widget but not the whole page?
Use a CSS selector targeting that widget's container class. Only text inside that element gets translated. The rest of the page remains untouched.
Is there a cost difference for selective vs. full-site translation?
With SeaText, no — the free tier has no page or language limits. Other tools may charge by word count or page views, so limiting scope saves money there.
Why this matters for your growth
Selective translation lets you treat localization like a marketing channel, not an IT project. You launch Spanish for your top 20 product pages, measure conversion lift, then decide whether to expand. You don't need IT approval for DNS changes. You don't pay for translating your privacy policy into 125 languages. You keep brand control on the pages that drive revenue.
The alternative — full-site proxy translation — creates a parallel site structure, complicates analytics, and often produces lower-quality output on pages nobody visits. Page-level control is the difference between a localization experiment and a localization commitment.
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.