Why Exclude Pages from Translation: Legal, Brand, and Cost Reasons
Excluding specific pages from translation helps you avoid legal compliance risks, preserve campaign-specific messaging, prevent low-quality machine translation on sensitive content, and reduce translation costs. It gives you control over which content appears in...
You exclude pages from translation when the risk of automatic translation outweighs the benefit of multilingual coverage. Legal pages, active ad landing pages, pricing tables with region-specific terms, and brand-critical copy often need human review or must stay in the original language to remain accurate and compliant.
Legal and compliance pages need human control
Privacy policies, terms of service, cookie notices, and regulatory disclosures carry legal weight. A machine translation can change the meaning of a clause, expose you to liability, or violate local law that requires the original language version. Courts and regulators often treat the source-language document as the authoritative version. Keeping these pages untranslated — or flagging them for certified human translation — protects you from disputes and fines.
Active campaign landing pages must match the ad promise
When you run paid campaigns, the landing page headline, offer, and call-to-action must mirror the keyword and ad copy that brought the visitor. Automatic translation can drift from the exact promise, lowering conversion rates. SEATEXT's Google Ads Landing Page Agent rewrites pages in real time to match each keyword; translating those same pages through a generic layer can break that alignment. Excluding campaign pages lets the personalization agent work without a translation layer interfering.
Pricing, checkout, and legal terms vary by market
Prices, currencies, tax rules, shipping restrictions, and contractual terms differ across countries. A translated pricing page that shows the wrong currency or omits a required tax disclaimer creates checkout errors and support tickets. Excluding pricing and checkout pages from automatic translation forces you to build proper localized versions with correct data, rather than relying on a language swap that leaves the numbers wrong.
Brand voice and high-stakes copy deserve human review
Homepage hero statements, taglines, and flagship product descriptions carry disproportionate brand weight. Machine translation often flattens tone, misses cultural nuance, or chooses the wrong register. SEATEXT notes that "automatic does not mean uncontrolled — you can edit translations, preserve brand voice, review key pages" (S1). Excluding your most visible pages lets you invest human editing budget where it matters most, while the rest of the site translates automatically.
Technical and performance pages break when translated
Documentation with code samples, API references, configuration files, and embedded scripts often break when run through a translation engine. Variable names, command syntax, and JSON keys become garbled. Developers copy-paste these snippets; a translated code block causes immediate errors. Excluding technical documentation preserves usability for the audience that actually reads it.
Cost control for high-volume, low-value content
If you publish hundreds of blog posts per month but only 10% drive international traffic, translating everything wastes budget. Excluding low-traffic, low-conversion pages — or setting a traffic threshold before translation activates — focuses spend on content that actually reaches buyers. SEATEXT's model translates "every WordPress page, post, product, and update automatically" with "no page limits, no language limits" (S1), but you still choose which languages to activate and which sections to exclude.
User experience: don't show broken translations
A partially translated page — where navigation, footer, and sidebar are localized but the main content stays in English — confuses visitors. It signals low quality. If you cannot translate a section well, excluding it entirely and showing a language-switcher notice is more honest. Visitors can then choose the source language or a fully translated alternative.
Definition: what "exclude from translation" means
Excluding a page means the translation system skips that URL entirely. The page serves in its original language regardless of the visitor's detected language. The language switcher may still appear, but selecting another language either keeps the page in the source language or redirects to a fallback. This differs from "no-index" (hiding from search) or "block translation of a text fragment" (inline exclusion).
Key facts
| Factor | Detail | Source |
|---|---|---|
| Translation scope | Up to 125 languages, automatic for new content | S1 |
| Control features | Edit translations, preserve brand voice, review key pages, A/B test translations | S1 |
| Activation | One-minute WordPress install, no page or language caps | S1 |
| Campaign alignment | Google Ads Landing Page Agent rewrites pages per keyword in real time | S3, S5 |
| Conversion impact | Up to +60% more international customers via Translation Agent | S6 |
| Bot protection | Recovers up to 20% of ad spend lost to bot clicks | S6 |
Common scenarios where exclusion makes sense
- Legal/compliance: Privacy policy, terms of service, GDPR/CCPA notices, industry-specific disclosures.
- Active paid campaigns: Landing pages tied to specific Google Ads, Meta, or TikTok campaigns where keyword-to-page match drives conversions.
- Pricing and checkout: Pages with currency, tax, shipping, or regulatory terms that differ by country.
- Technical documentation: API docs, code tutorials, SDK references, configuration guides.
- Brand-critical copy: Homepage hero, tagline, flagship product narrative, founder letter.
- Low-value archive: Old blog posts, press releases, event pages with no international traffic.
Limitations and when this advice does not apply
Exclusion is not a substitute for proper localization. If a market is strategic, you need human-translated or professionally localized versions of legal, pricing, and brand pages — not just exclusion. Exclusion also does not solve SEO for that language; the page will not rank in the target language's search results. If you exclude a page, consider adding a language-switcher banner that links to the source-language version or a manually localized alternative.
Terminology
- Source language: The original language of your website content.
- Target language: A language you translate into for visitors.
- Automatic translation: Machine translation applied site-wide without per-page human review.
- Controlled translation: Automatic translation with edit, review, and A/B test overrides (SEATEXT model).
- Exclusion rule: A configuration that tells the translation engine to skip specific URLs, paths, or content blocks.
FAQ
Can I exclude only part of a page?
Yes. Most translation platforms let you wrap a block in a data-no-translate attribute or use a CSS class to skip a fragment — like a price table or code snippet — while translating the rest of the page.
Will excluded pages still appear in the language switcher?
Typically yes. The switcher shows all enabled languages. When a visitor selects a language for an excluded page, the system either serves the source-language version or redirects to a fallback URL you define.
Does excluding a page hurt SEO in that language?
Yes. The page will not have a translated URL, hreflang tag, or localized content, so it will not rank for queries in the target language. Only exclude pages you do not need to rank internationally.
How do I decide which pages to exclude?
Audit by traffic, conversion value, legal risk, and brand sensitivity. Start with legal, pricing, active campaign landing pages, and technical docs. Add low-traffic archive content if translation volume drives cost concerns.
Can I re-enable translation later?
Yes. Exclusion rules are reversible. When you have budget for human review or a certified translation, remove the exclusion and the next automatic cycle will translate the page.
What if I need a page translated but not the navigation?
That is the inverse problem: translate a specific page while keeping global elements in the source language. Most systems handle this by translating the page content but excluding the header/footer via template-level rules.
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.