Can You Exclude Certain Pages or Sections from Automatic Translation?

Why Excluding Pages from Automatic Translation Matters

Automatic translation is a powerful way to open your website to new markets. But not every page should be translated. Legal terms, privacy policies, checkout flows, and pages with sensitive or regulated content often need to stay in the original language. Translating them automatically can create legal risk, confuse customers, or break compliance requirements.

If you ignore this need, you might end up with a translated version of your terms of service that doesn't match your legal intent. Or a checkout page in a language your payment processor doesn't support. The cost of fixing these mistakes after the fact is much higher than setting up exclusions from the start.

How Automatic Translation Exclusions Work

Most translation platforms use one of three mechanisms to exclude content:

• URL patterns — You specify paths or URL fragments that should never be translated. For example, /legal/* or /checkout.
• CSS selectors — You target specific HTML elements by class, ID, or attribute. This is useful for excluding a single paragraph, a sidebar, or a banner.
• Meta tags or attributes — Some platforms respect translate="no" attributes or custom meta tags that mark content as untranslatable.

The exact implementation varies. Some platforms let you configure exclusions in a settings panel. Others require you to add a small snippet of code to your site. A few support both.

Main Options and Trade-Offs

When you decide how to exclude content, you're really choosing between three approaches:

1. Exclude by URL Pattern

This is the broadest approach. You exclude an entire page or a group of pages. It's simple to set up and easy to maintain. The trade-off is that you can't exclude just one section of a page — the whole page stays in the original language.

Best for: Legal pages, checkout, login, and any page that should never be translated.

2. Exclude by CSS Selector

This gives you fine-grained control. You can exclude a specific paragraph, a pricing table, or a testimonial block while translating the rest of the page. The trade-off is that you need to know your site's HTML structure and maintain the selectors as your site changes.

Best for: Pages where most content should be translated but a few elements must stay in the original language.

3. Exclude by Meta Tag or Attribute

This is the most precise approach. You mark individual elements as untranslatable directly in your HTML. It's great for one-off exclusions. The trade-off is that it requires editing your site's code, which may not be practical for non-developers.

Best for: Specific elements that appear on many pages, like a brand name or a legal disclaimer.

Decision Framework: How to Choose Your Exclusion Method

Use this simple decision rule:

1. Start by listing every page or section that must stay in the original language.
2. For each item, ask: Does the entire page need to be excluded, or just part of it?
3. If the whole page — use a URL pattern.
4. If just part of the page — use a CSS selector or meta attribute.
5. If you're not sure, start with URL patterns. They're the safest and easiest to manage.

Here's a practical example. Suppose you have a pricing page with a legal disclaimer at the bottom. You want the pricing table translated but the disclaimer to stay in English. You'd use a CSS selector targeting the disclaimer's class. If you have a separate terms page, you'd use a URL pattern to exclude the entire page.

Common Mistakes to Avoid

• Excluding too much. If you exclude your entire site, you lose the benefit of translation. Be selective.
• Excluding too little. Missing a legal page can create compliance issues. Review your site carefully.
• Using fragile selectors. If your CSS selectors depend on classes that change with each theme update, your exclusions will break. Use stable selectors or test after updates.
• Forgetting dynamic content. Some platforms translate content loaded via JavaScript. Make sure your exclusions cover those elements too.
• Not testing. After setting up exclusions, check the translated versions of your pages to confirm the right content is excluded.

Practical Scenarios

E-commerce Store

You want to translate product pages but keep checkout in English. Use a URL pattern to exclude /checkout and /cart. Keep the rest of the site translated.

B2B SaaS Company

You want to translate marketing pages but keep your help center in English. Use a URL pattern to exclude /help/*. Or use a CSS selector to exclude the help center's navigation if it's embedded on every page.

Legal or Financial Services

You want to translate your blog but keep all legal and compliance pages in English. Use URL patterns for /legal/*, /privacy, and /terms. This is the safest approach for regulated industries.

Limitations and When This Advice Doesn't Apply

Not every platform supports all three exclusion methods. Some only support URL patterns. Others only support CSS selectors. Check your platform's documentation before you start.

Some platforms don't support exclusions at all. If that's the case, you have two options: use a different platform, or manually manage translations for the pages you want to keep in the original language.

Also, exclusions don't prevent search engines from indexing translated versions of your pages. If you want to prevent indexing, you'll need to use noindex tags or robots.txt rules in addition to translation exclusions.

Key Facts at a Glance

Frequently Asked Questions

Can I exclude a single paragraph from translation?

Yes. Use a CSS selector or a translate="no" attribute on that specific element. This works on most platforms that support element-level exclusions.

What happens if I exclude a page but it's already been translated?

The existing translation usually stays in place. You'll need to delete the translated version manually if you want it removed. Some platforms automatically remove it when you add the exclusion.

Do exclusions affect SEO?

Exclusions prevent translation but don't prevent indexing. If you want to keep a page out of search results entirely, you'll need separate SEO controls like noindex tags.

Can I exclude content based on user language?

Some platforms allow conditional exclusions based on the visitor's language. This is less common. Check your platform's documentation for this feature.

How do I test my exclusions?

After setting up exclusions, switch your site to a translated language and visit the excluded pages. Confirm the content stays in the original language. Also check that the rest of the site still translates correctly.

What if my platform doesn't support exclusions?

You have two options: switch to a platform that does, or manually manage translations for the pages you want to keep in the original language. The second option is more work but can work for small sites.