What Pages Should You Exclude from Translation for SEO? A Practical Answer

Exclude pages that exist to serve one market or one step in your funnel: legal pages, privacy policies, terms of service, thank-you pages, and campaign-specific landing pages built for a single language. Keep those in the source language. That approach prevents duplicate-content confusion, hreflang mistakes, and translated legal copy that no lawyer approved.

Translation for SEO is a trade-off, not an all-or-nothing setting. A translated product page can win new customers. A translated thank-you page cannot rank, does not inform a buying decision, and may confuse the exact visitor you just converted.

Why exclusion matters

Search engines use language signals like hreflang to choose which version of a URL to show. When every URL on your site gets a machine translation, you create dozens or hundreds of alternate versions. Most are useful. Some are unnecessary. A few are harmful.

Harm usually comes in three forms:

• Wrong-language results: A search engine shows a French version of a thank-you page to an English user because the hreflang mapping is incomplete.
• Wasted crawl and index space: The search engine spends resources on pages that have little or no search demand.
• Conflicting legal meaning: A translated privacy policy or terms page says something different from the original, and you do not know it.

None of these problems come from translation itself. They come from translating without deciding which pages deserve a translated version.

Page types to evaluate first

Start with these five groups. They are not automatic never-translate rules. They are the first places to look.

1. Legal and compliance pages: Privacy policy, terms of service, cookie policy, refund policy, disclaimer, and accessibility statement. These pages are not written to rank. They are written to protect you. A machine translation can create a second contract that says something different.
2. Post-conversion pages: Thank-you pages, order confirmation pages, download-complete pages, payment success pages, and subscription welcome pages. They are usually noindex, they have almost no organic search intent, and a translated version can confuse a visitor who just acted.
3. Single-market campaign landing pages: City-specific offers, store-location pages, event registration pages, and limited-time promotions. If the campaign targets one audience in one language, translating it creates a version that no ad points to and no searcher looks for.
4. Internal and utility pages: Login, account dashboard, checkout, search results, admin pages, and 404 pages. These exist for function, not visibility. Translating them adds cost and maintenance without adding search value.
5. Time-sensitive pages: Webinar schedules, conference agendas, one-day sales, and expiring offers. By the time the translation is reviewed, the offer may be gone.

The decision criteria: use these questions first

Ask three questions for each URL:

1. Would someone in another language genuinely search for this page? If no one searches for it in the target language, exclude it.
2. Does a translated version create legal risk or obligation? If yes, exclude it unless a qualified person reviews and approves every translated version.
3. Does the translated page help someone buy, use, or trust your product? If only the source-language visitor can act, translate nothing.

Then check indexation. If the page is set to noindex, like checkout or thank-you pages, it does not belong in a translation effort aimed at SEO. You may still translate it for user experience, but you should not count it as an SEO asset.

These are defaults, not laws. The last row is the point of translation: pages that answer a question, describe a product, or help someone compare options are the pages that pull their weight in a new market.

Step-by-step decision process

1. Audit your URLs by template. Export posts, pages, and products, then group them by type.
2. Mark non-indexable pages. Thank-you, checkout, account, and internal pages should not participate in an SEO translation project.
3. Mark legal and compliance pages as review-required. Add them to your exclusion list unless legal signs off.
4. Apply the three questions above to each remaining group.
5. Exclude the URLs that fail. For translated URLs, add hreflang so search engines know the language versions belong together.
6. Monitor indexed pages and search performance. If a translated page never appears in results and never earns clicks, it is probably not worth keeping.

What the trade-offs look like in practice

Here are three examples to make the criteria concrete. They are hypothetical examples, not customer stories.

Ecommerce store: Product descriptions, size guides, and shipping FAQs are worth translating because shoppers search for them in their own language. Order confirmation and return confirmation pages are not worth translating because only a customer who already bought from you will see them.

SaaS business: Feature pages, pricing pages, and comparison pages help a buyer decide. Billing terms, data processing agreements, and security policies should stay in the source language unless your legal team reviews each translated version.

Local service business: A page for a free consultation in one city should remain in that city's language. A general services page that explains what you do and how to start can be translated for other markets.

How automatic translation changes the math

Automatic translation tools change the default. Instead of asking will I translate this page, the answer becomes yes, unless I exclude it. That default is useful for pages that produce real search value, but it means somebody has to set boundaries.

SEATEXT is built for WordPress and translates pages, posts, products, and headlines automatically. The product material says there are no page limits and no language limits, and it supports up to 125 languages. New website content is translated automatically. That is powerful for stores or sites that publish frequently.

Automatic does not mean uncontrolled. SEATEXT lets you edit translations, preserve brand voice, review key pages, and use A/B tested translation when you want to find the message that sells best in each market. You also choose the markets you want to enter. That control matters for legal pages and campaign pages, where your own judgment should override the automatic default.

Key facts

Scope and terminology

This guidance applies to websites that use automatic translation tools or agents and want to limit which URLs get alternate language versions. If you translate page by page with a human translator, the same criteria work, but you are already making these decisions manually.

• Excluded from translation: The original URL stays single-language. Search engines will not see an alternate language version for that URL.
• Hreflang: An HTML tag that tells search engines which language and regional version of a page to show to different users.
• x-default: The version search engines should show when no language or region matches the user.
• Localization: Adapting more than words. It includes currency, units, offers, and local expectations.
• Noindex: A way to keep a URL out of search results. Exclusion from translation is different from noindex; a page can be untranslated and still indexable in its original language.

Most translation tools have a setting for this. Weglot and TranslatePress both document URL or content exclusion options. The exact label varies, so look for exclude URLs, translate only certain pages, or do not translate.

Limitations: when this advice does not apply

There are exceptions to the exclusions above.

If your company actively sells in a country, some jurisdictions require translated privacy or consumer protection information. Do not exclude those pages automatically. Have a qualified reviewer create and approve the translated version.

If a thank-you page is also a referral page, such as a share-to-unlock offer, translation may help the visitor take the next step. Just remember that it is a user-experience decision, not an SEO decision.

If a paid campaign targets several languages and regions, the landing page should match the language of each ad. Exclude only when the campaign itself is single-market.

Most importantly, do not think of exclusion as hiding pages. A page can stay in its original language and still rank well in that language. The goal is to avoid creating weak alternate versions that nobody searches for and nobody approves.

Frequently asked questions

Why should I avoid translating legal pages?

Legal pages protect you. A machine translation can create a second set of obligations that say something different from the original. Legal pages also have almost no organic search intent, so the SEO upside is small.

What is the difference between excluding from translation and noindexing?

Excluding from translation means no alternate language version exists. Noindexing means the URL should stay out of search results entirely. You can exclude a page from translation and still let the original page be indexed and rank.

When should I translate a landing page?

Translate a landing page when real people in another language search for what it offers and can actually buy or use it. If the page is tied to a local offer or one event, keep it in one language.

How do I set exclusions in an automatic translation tool?

Check the tool's documentation for URL exclusion or page-level settings. Tools like Weglot and TranslatePress expose these options, and the exact labels differ. Add the URL patterns you identified in your audit.

Will a translated site be penalized for duplicate content?

When original and translated versions are clearly connected with hreflang, they are treated as language versions rather than duplicate content. The risk grows when hreflang is missing, navigation is mixed, or only part of a page is translated.

What does it cost to maintain excluded pages?

Excluded pages cost nothing in translation or review work. The real cost is the review time for the pages you do translate, especially legal, pricing, and campaign pages.

Should I exclude every page that does not rank?

Not automatically. A page might not rank in your source language but could rank in a new market. Judge the page by the demand in the target language, not by its current position at home.