Can I limit what parts of my site are translated?

Yes, with GlobalLink GO you have many options to control what does and does not get translated. You can even hide original content from appearing on a translated page, or show content only on a translated page and not on the original source page.

There are three main ways to manage what should and shouldn't be translated on your site:

    • Individual words and phrases are best managed using the Glossary.
    • Content blocks and components are best managed using a CSS class.
    • Entire pages and your site map as a whole are best managed using the Project Scope.

In this article, we'll focus on Project Scope, which can be found in your dashboard under Project Settings.

Default Settings

Project Scope comes with three default settings.

  1. Everything

Every page of your site that has the JavaScript injection in the <head> will display a language selector and will be translated on demand.

This is the simplest and most comprehensive Project Scope setting. Everything is included in scope by default and any new page that appears on your site will automatically be translated.

  1. Exclude

Everything except the pages you specifically exclude from scope will be translated.

This setting lets you choose specific pages that you might not want to be translated. But any new pages that appear on your site will be in scope by default and will be translated, unless you specifically exclude them.

  1. Include

Nothing but the pages you specifically include in scope will be be translated.

Include mode means that only the pages you specifically opt in will be translated. This setting is generally not recommended, since it requires the most manual intervention on your part to ensure content is translated. Any new page that you create on your site will not be translated by default, unless you specifically add that page to scope.

Using the Page Tree

When you create a project, we will scan the domain you entered and generate a folder-based page tree of your site, which you can view in Project Settings -> Project Scope. As pages are added and removed from your site over time, the page tree will be updated to reflect that periodically.

If your default setting is either Exclude or Include, you can use this page tree to intuitively manage what pages are in and out of scope for your project.

When you drill down in the page tree, you can select a URL and choose whether to include or exclude that URL itself, or that URL and any sub-pages ("children") under it, or just the sub-pages (children) only and not the page itself (the "parent").

When you make an exclusion or an inclusion, a "regex" (regular expression) rule is generated and will appear below.

For example, if you wanted to exclude from scope your Terms & Conditions which appear on the page www.example.com/terms-and-conditions, you would select that page and click "Exclude Page". A regex rule is generated that will say:

Exclusion Rule

URL path is exactly | "/terms-and-conditions/" | ^/terms-and-conditions/?$

Understanding how regex works will be very helpful in making sure your scoping rules are properly implemented, but the UI is designed to be intuitive and does not require a knowledge of regex.

Related Articles