Page management
SwiftLingo finds the pages on your website by itself and translates all of them by default. The Pages page shows what it found and lets you exclude what shouldn’t be translated.
Your pages
Section titled “Your pages”All Content Pages lists every page SwiftLingo knows about, with a status:
- Translated: translated into all your languages.
- Excluded: not translated; visitors see the original.
- Conditional: a rule excludes it for some languages only.
Search by URL or filter by status to find a page. Click Scan Pages to look for new pages right away.
Forget page removes a page and its translations from SwiftLingo, for example after you deleted it from your site. If the page still exists, SwiftLingo finds it again on a later scan. To keep a page untranslated, add a rule instead.
Translation rules
Section titled “Translation rules”Rules decide which pages are translated, by URL pattern.
- Click Add Rule.
- Choose an Action: Exclude from translation, or Force include.
- Enter a Pattern: an exact path such as
/privacy, or use*as a wildcard./account/*matches every page under/account/. - Optionally add a description, and under the advanced options pick the languages the rule applies to. Leave them empty to apply it to all languages.
- Click Add Rule.
Common rules
Section titled “Common rules”| Pattern | Action | Why |
|---|---|---|
/account/* |
Exclude | Personal account pages. |
/cart/*, /checkout/* |
Exclude | Keep checkout in one language. |
/admin/* |
Exclude | Your site’s back office. |
/blog/* for Spanish only |
Exclude | Translate the blog into every language except Spanish. |
Turn on Standard Exclusions in Settings › Website to skip common system paths such as /wp-admin and /admin without writing rules.
When rules overlap
Section titled “When rules overlap”Force include rules always win over exclude rules. That lets you make exceptions: exclude /blog/*, then force-include /blog/launch-announcement, and only that post is translated.