Managing languages in WPML is not only a matter of adding another option to a language switcher. On an existing multilingual WordPress site, a language can be hidden temporarily, removed from the active configuration or permanently deleted together with its translations. These actions have very different consequences, especially when the site contains important pages, posts, products, taxonomies or customized translation workflows.
This guide explains how to approach the WPML language lifecycle safely. You will learn when hiding a language is preferable to deleting it, how to add a regional custom language such as Swiss German, what to review before changing the default language and what to back up before destructive cleanup. The exact result can depend on the site’s content types, URL format, theme, plugins and translation workflow, so changes should be validated rather than assumed to be universal.
Hiding, Deactivating and Permanently Deleting a WPML Language
Visibility is not translation deletion
WPML separates language visibility from translation data. Removing or unticking a language in the active language list takes it out of the active site configuration, but it does not automatically delete its translations from the database. If the language is enabled again, the existing translations can become available once more.
This distinction matters when a translation is incomplete. A language can be unavailable to normal visitors and search-engine crawlers while logged-in editors continue working on it. In practical terms, hiding changes who can see the language; it does not erase the work already stored for that language.
When permanent removal is appropriate
Permanent removal is a separate, destructive process. Removing a language from the active list is only part of that process. WPML documents additional cleanup involving translated posts, pages and taxonomy terms, followed by handling remaining items in the Removed languages area.
Use permanent deletion only after the site owner confirms that the language is being retired rather than temporarily paused. Before proceeding, create and verify a restorable database backup. Do not assume that a language hidden from visitors has already been deleted, and do not delete translation records simply because the language is not currently published.
How to Hide a WPML Language Without Losing Translation Work
A reversible workflow for unfinished translations
Hiding is the appropriate starting point when translation work is unfinished, under review or temporarily unavailable to visitors. Use WPML’s language visibility controls to remove the language from the visitor-facing experience while preserving the translations in the database.
A practical workflow is straightforward:
- Identify the language that should not yet be visible.
- Remove it from the active visitor-facing language configuration.
- Allow logged-in editors to continue reviewing and editing the translations.
- Before re-enabling the language, check representative translated content and the language switcher.
This approach preserves the option to return to the existing translation work. It is different from permanent removal, where translated posts, pages and taxonomy terms are deliberately deleted. Communicate that difference clearly to clients and other site administrators so that a temporary visibility change is not mistaken for data cleanup.
How to Add a Custom Regional Language Such as Swiss German
Define the custom language metadata
WPML supports custom or country-specific languages. When the required regional language is not selected from the standard bundled language list, use the custom-language option and prepare the information required for its definition.
The documented setup includes:
- A locale code for the custom language.
- An English name and a native name.
- A flag used to represent the language.
- The language’s text direction.
Review this presentation before making the language available to visitors. The metadata affects how the language is identified in the site configuration and language switcher. Adding a custom language does not by itself mean that every translation workflow or automation feature will support it directly.
Map Swiss German for supported automation
WPML documents Swiss German as an example of a custom language that can be mapped to German. This mapping is relevant when automatic translation or spell checking is needed and the custom language is not directly supported by a translation engine.
Without mapping, WPML states that automatic translation and spell-check features are unavailable for the custom language. Mapping Swiss German to German provides a supported language reference for those functions, but it should not be treated as proof that generated wording is identical to regionally appropriate Swiss German. Review the output and the site’s language presentation before publishing it.
Changing WPML’s Default Language on an Existing Site
Review archive and fallback behavior
Changing the default language changes which language users see first. It can also affect archive listings when post types or taxonomies use fallback-to-default-language behavior. Existing posts retain their assigned language according to WPML documentation, but content that has not been translated into the new default language may be absent from archive listings under relevant fallback settings.
Before making the change, review the content that matters most to the site:
- Important posts and pages.
- Products and product-related content on a WooCommerce site.
- Taxonomies used by archives and navigation.
- Content coverage in the intended new default language.
- Language switchers and the first language shown to visitors.
Create a backup before changing the default language. For a substantial or business-critical site, test the change on staging where possible. Do not assume that custom integrations, cached URLs, sitemaps or external translation workflows will all update identically.
Check language URL configuration
Language-specific access paths should be reviewed alongside the default-language setting. WPML can use language directories, separate domains or subdomains, or a language parameter. Record which format the site uses before changing the configuration.
After the change, verify that visitors can reach the intended language versions through the expected paths. A setting change can be technically successful while still requiring review of internal links, redirects and other language-specific access points. The selected URL format is therefore part of the change assessment, not a detail to check only after a problem appears.
Backup and Pre-Deletion Checklist
What the backup should protect
Before permanently deleting a language, create and verify a restorable database backup. This is the minimum protection for translation records stored in the database and is particularly important because permanent language removal is destructive.
For higher-risk sites, consider a complete restorable site backup covering both the database and files. This is practical rollback protection for sites with WooCommerce content, custom post types, media, forms or customized integrations. The official WPML documentation does not prescribe one universal backup plugin procedure or host-specific restoration process, so confirm the method with the hosting or maintenance provider when necessary.
A backup is useful only if it can be restored. Test the restoration process where possible, or perform the deletion on staging first. Also record the current language, fallback, language-switcher and URL-related settings so that the post-change state can be compared with the original configuration.
Confirm the deletion scope
Do not begin destructive cleanup until the business owner confirms that the language is being retired permanently. Identify which translated posts, pages and taxonomy terms belong to that language, and distinguish them from content that should remain available in another language.
WPML’s documented removal process includes handling remaining items in the Removed languages area. Review that area as part of the cleanup rather than treating removal from the active list as the final step. If there is uncertainty about the scope, stop at hiding the language and preserve the translation data until the decision is clear.
Post-Change Testing for a Multilingual WordPress Site
Front-end and content checks
After hiding, adding, changing or removing a language, test more than the homepage. Use a representative set of content that reflects how the site is actually used.
- Pages and posts in the affected languages.
- Products and product-related content where WooCommerce is used.
- Taxonomies and archive listings.
- Menus, forms and search results.
- Language switchers and editor access to hidden translations.
After a default-language change, pay particular attention to archives and fallback behavior. After hiding a language, confirm that visitors cannot see it while the intended logged-in editorial workflow remains available. After permanent deletion, verify that the remaining active languages show the expected content and that no required translation was removed accidentally.
URLs, archives and multilingual output
Check language-specific URLs according to the site’s selected format: directories, separate domains or subdomains, or a language parameter. Review redirects and internal links where relevant, and confirm that representative pages and archives resolve through the intended paths.
Where applicable, also review multilingual SEO output, including language-specific access paths, canonical output and hreflang output. The research does not guarantee that every cached URL, sitemap, custom integration or external translation workflow will update identically. Treat these checks as site-specific validation, particularly when the theme, plugins, WooCommerce content or translation workflow has been customized.
The safest decision path is to hide a language when translation work should remain available, configure and map a custom regional language when the workflow requires it, and review content coverage, fallback behavior and archives before changing the default language. Permanent removal should follow only after explicit confirmation, a verified database backup and a clearly defined deletion scope. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.