Documentation / Settings
Settings › General.
Content types
Which content is translated, and what visitors see of a post or page that is not translated into their language yet.
- Translated?: Translate or Never (see Never translated).
- When it is not translated yet: Show it in the original language or Hide it in that language. A hidden post leaves menus, lists, search and the switcher in that language. Opened by its address, it either opens in the original language or is Not found (404).
A post counts as translated once every text of its own has a translation, machine or reviewed. Shared parts such as the header do not count. A post never opened in the translation editor is not translated yet.
Search
Find pages by their translated text: a visitor who searches in their own language finds a page by its translated words. The words of the original keep finding it either way. Switched off, search reads the original language only.
The index of translated text is written as you translate. Press Build the index again after adding or removing a language, or if search misses a page you know is translated. If the database server cannot make a full-text index, the words are read from the rows themselves: the same pages are found, slower on a large site.
Start over
Clears SwiftLing on this site and opens the first setup again, for example to choose another original language. The site keeps working in its original language while you set it up again.
| Choice | Removes |
|---|---|
| Remove everything | Every translation, the languages, the settings and the translation service with its key. Cannot be undone. |
| Keep the translations | Only the languages and settings; the translation service stays. Add a language again and its translations come back. |
It keeps your pages, posts, media and menus, the Switcher blocks, shortcodes and widgets you placed, and WordPress’s own language packs.
You must type a word to confirm. If you may want anything back, back up the database first. With SwiftLing Pro, Remove everything removes what Pro keeps too (currencies, glossary, settings of automatic translation, import).
Deleting the plugin removes nothing. Start over is the one way to remove what SwiftLing keeps.