The Custom section in langify can be used to translate text that cannot be translated out of the box. It's especially useful for the translation of third-party apps like page builders, review apps, search apps, and more — or other special cases where the translation is not natively supported by Shopify. Check out our third-party app integration list.


  • When using Custom Content, please make sure that langify is published as embedded app to your theme.
  • Custom Content translations should only be used if the text cannot be translated within any other section.


Since Custom Content translations have to be injected separately, an excessive amount can slow down the page. 

If there are too many added to a single subsection (like Global), it can cause rendering issues, depending on the amount of content on the page itself. As a rule of thumb please do not add more than 250 Custom Content translations per subsection.



Create a Custom Content Entry


To create a Custom Content, simply go to the Custom section in langify, and then:


  1. Choose a subsection.
  2. Create the Custom Content entry.
  3. Enter the original text that you want to translate.
  4. Click on Save — this will create a new translation field.
  5. Add your translations to the new field and save again.


Hint: Use the browser's Inspect tool by right-clicking on the text you want to translate and then selecting Inspect. This helps to find the correct text to create the Custom Content. Each text string needs its own Custom Content entry.



The Custom content can be found at the bottom of the menu and it offers several subsections as well


If you haven't added any Custom Contents in this section, then you'll find an Add New Custom Content button.

Otherwise, click on the three-dots icon in the upper right to find this option:


The "+ add new custom content" option will appear when clicking the three dots in any Custom subsection in langify



Subsections


The additional subsections are useful for organization, manageability, and performance. Each subsection also acts as a scope, controlling where each Custom Content entry is loaded — this keeps the speed impact as minimal as possible.


For example, a Custom Content added to Global will be loaded everywhere on your store. If you only need the translation on product pages, add it to the Product Pages subsection instead — it will then load exclusively on product pages.


The available subsections are:

  • Global — applied to all pages of your store
  • Frontpage — homepage only
  • Product Pages — all product pages
  • Collection Pages — all collection pages
  • Blog Pages — all blog pages
  • Article Pages — all article pages
  • Custom Pages — all custom pages
  • System Pages — all other pages (e.g.: cart, search, 404)
  • Global Strict Mode — applied to all pages of your store, but only client-side for text nodes and placeholder attributes. This is helpful if you need to ensure that no code-relevant text is translated.


If you're not sure what kind of subsection to use for your text, you can check the URL of the page where the text appears.

If the URL contains /products/, then this is a Product page. If it contains only /collections/, then it is a Collection page.



Individual Custom Content translations


You can create a more specified Custom Content for a single product, collection, article, or page in the respective item under the Custom tab. A translation added here is applied to this item only.

  1. Click on the item in langify, for example, a product, collection, or page.
  2. Scroll down to the Custom tab.
  3. Add your Custom Content and save.


Shows where to add an item-specific Custom Content inside langify


If there are multiple Custom Contents in the different subsections for the same original text, then the more specific translation will be used.


Limitations


There are some cases where Custom Content translations cannot be applied:

  • Content loaded via an iframe or shadowroot from an outside source.
  • Checkout pages, due to security reasons.
  • Notifications, and the new customer account pages, as these are handled separately from your theme.


If your Custom Content does not translate and you're not sure why, just let us know at support@langify-app.com and we will take care of the issue!



Technical


Out of the box, Custom Content translations are applied via JavaScript client-side, provided that langify is published as an embedded app to your theme. These translations are only applied to text nodes and placeholder attributes.


If you have added the langify Polyfill code to your theme, then Custom Content translations are additionally applied server-side via Liquid. Translations are applied to any text within > and <, or within quotes. This includes text nodes and all HTML attributes.


A special exception is Custom Content entries added in the Global Strict Mode subsection — they are always applied only via JavaScript and are ignored by the Polyfill code.