Menu Close

Polylang core settings. Permalinks, language detection, synchronization, string translation

In fact, the first thing you need to do after setting up a polylang is to set the language. The reason should be preceded by such things as URL modifications, synchronization, and a Detect browser language system that connects the actual visitors to the language page, It is because there are functions.

Of course, the basic settings are very good, so there is no big deal to use without touching, but each one is essential and useful, and if you know how to use it, you can actually use it to construct a site translation system. Let's go.

    URL modification - URL modifications

It is a menu to set the unique address of the translation (Permalink).

  • The language is set from content - the language is determined by its content
  • I do not want to create a permalink of the translation. Unless you have a specific reason to do so, you do not need to select this menu to detect and navigate pages based on the visitor's language, and to improve SEO and expose it to search engines.

  • The language is set from the directory name in pretty permalinks - created as a subdirectory
  • Like the category, set the URL to a subdirectory of the main address. This is the default setting, and it is the most recommended method. It is an effective way to let people know that they are translations of the same content, not a sub-domain, not a hosting or server configuration, and not a search engine independent site.

    If you add an English translation in this way, it is implemented as follows

    example.com/
    example.com/post/
    
    example.com/en/
    example.com/en/post/
    
  • The language is set from the subdomain name in pretty permalinks - Create subdomain
  • Set the translation URL to a subdomain. In order to be represented as a subdomain in a multi-site, you have to touch the server or hosting settings, and there are places where there are multiple or not. I do not know how many plug-ins are supported. It is complicated in various ways such as being issued with a wild card.

    Therefore, creating a sub-domain URL of a translation is disregarded unless a large menu such as a blog, news, or product page is shared on a site. If you set it as a subdomain, it is implemented as below.

    example.com/
    example.com/post/
    
    en.example.com/
    en.example.com/post/
    
  • The language is set from different domains - Set in another domain
  • Set the translation's unique address in another domain. It is a menu that literally implements the subdirectory, not the domain, but the different languages in different domains.

    When you select it, you will get a text form to enter the domain for each language you set in Polylang, and enter the desired domain. I have not thought about what I need in some cases, but it seems to be very cumbersome in terms of cost. If you set it up, you can implement it like this.

    ko = example-ko.com/
    en = example-en.com/
    

      Detecting browser language - Detect browser language

    By default, the setting is on. It is a simple but really core function. When this feature is turned on, the site is switched to the language that the user actually uses in the user's browser, and hreflang is set for each country, so the SEO optimization of the Google search engine is done.

    Redirecting users to your own language is a great feature, but it's a useful feature that is optimized not only for users, but also for search engines and bots.

      Synchronization Options - Synchronization

    It is a menu to set the information to be shared between translations. For example, if you turn on Published date here, the same date will be applied when you write in Korean and upload an English translation.

    It's a really handy feature, but if you upload a translation when the tag is not translated, there's the inconvenience that the original tag will disappear. The menus that can be synchronized are shown below.

  • Taxonomies - Classification settings, such as categories
  • Custom fields - Custom fields
  • Comment status - Comment state
  • Ping status
  • Sticky posts - Sticky posts
  • Published date - Date published
  • Post format - Post format
  • Page parent - Top Page
  • Page template - Page template
  • Page order - Page order
  • Featured image - Thumbnails, Thumbnails
  • WPML Compatibility mode (WPML Compatibility), which synchronizes media synchronization, Strings, etc., Tools to remove data when polling is deleted, and Paired feature which can be used in Polylang Pro. slugs, and slugs.

      String translation - String translations

    In addition to the contents of the body or page, translate strings such as site title or category name. There is a text form that allows you to translate object texts on the site, not content, and how to translate the translitable strings into each language when you enter the menu.

    It is a very convenient, intuitive and essential feature for building a complete multilingual site, but it has the disadvantage that the strings that can be recognized and translated are limited. This pointPolylang Strings translations Add custom string translationYou can add a string to be translated or customize it as suggested in.

    Comment (Information not required)

    Posted in All, Wordpress

    이메일 구독 - Email Subs

    최선을 다해 직접 만든 콘텐츠만 공유합니다.
    We share the best content we have created.