Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
English (US)
US English (US)
FI Finnish
  • Home
  • Builder.io

How to build a multilingual blog with Builderio?

Learn how to build your own blog quickly and easily with Builderio with this guide!

Written by Petro Mäntylä

Updated at March 25th, 2026

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • AI Commerce
    Administration homepage Customer relationships Orders Order management Categories Quotation tool Products Configurations Modules Local regulations and taxes Front page FAQ -työkalu Tools Box Additional functions Svelte
  • Akeneo
  • Builder.io
  • Algolia
  • Google
  • Partners
  • Tuki
+ More

Table of Contents

Step 1: Create a new Model Step 2: Define Required Fields Step 3: Set up dynamic preview (Options) Step 4: Manage categories and page structure Summary

Creating a blog with the Builderio content creation tool makes content management easier and minimizes manual work. You can automate the listing of blog articles, eliminating the need to manually add new articles to the lists. The category structure can also be implemented dynamically using separate codes and integrations, which significantly speeds up maintenance.

Below are step-by-step instructions for building a blog, the most essential settings, and tips for further development. 


1) Create a new Model

  1. Go to Builderio and select the new model creation view.
  2. Give the template a name : Blog article (exactly this spelling, without any extra characters).
    • Note: The name must be exactly “Blog article” (in English), as even one incorrect character will prevent it from working.

2) Define fields (Fields)

Go to the Fields tab of the template and add the following fields. Note A and B depend on whether you support multiple languages on your blog.

A) For monolingual stores, make them mandatory
B) For multilingual stores, remove their enforcement

  • title : Article title
  • handle : The end of the article's URL (slug) without special characters and without any prefixes, e.g. “new-location-opened”. The link will not work if the URL contains any special characters other than a hyphen.
  • image : The main image for a blog article, which can be used on the article page and in category views.
  • date : Publication date, which can be used to sort blogs.
  • blurb : A short preview text that appears in blog listings and, if necessary, in search results (SEO benefit).

If you need more fields (for example, longer description text), you can create them. Your integration partner can add the necessary logic on the backend.


3) Set up dynamic preview for domains

  1. Open the “ Blog article ” template settings and go to the “ Options ” tab.
  2. Set the dynamic preview URL to match the web address and blog structure. Image below.
  3. This will allow you to preview each article via its own URL.
const rawPath = targeting.urlPath || '';
const path = rawPath.startsWith('/') ? rawPath : `/${rawPath}`;
const language = locale || ''

switch (language) {
    case 'et-EE':
        return "https://veronashelters.ee" + path
    default:
        return "https://turvakauppa.com" + path
}

5) Check the settings

  • The unique identifier must be exactly “blog-article.” A single character error will break the functionality.
  • Public readable must be turned on. Otherwise the article will not be visible.


In a multilingual store: Go to your account's main settings ( https://builder.io/account/space ) and check that Locales contains the same locales as the Hreflang value on the Domains page of the online store's MyStore , e.g. "fi-FI". Case is important for Builderio.


In a multilingual store: In case of errors, the integration partner should check that CloudFront is forwarding the same locale, for example “ et-EE ”, as the Domain settings in the control panel. Builderio needs the locale before AI Commerce backend responds, so the locale is retrieved from the X-Forwarded-Locale header of the web request.


In a multilingual store: Go to Advanced Settings and make sure that “Allow targeting to multiple URLs” is enabled. If this setting is not enabled, you will not be able to add URLs in different languages to Preview later.


5) Creating articles

Make sure that the URL targeting uses only one WHERE clause, and that all language options you use are included. You decide what the URL is in different languages. The exact same spelling should be in the “ handle ” (NOTE! Without the path).

 

Make sure you have filled in at least the Title and Handle in different languages, otherwise the article will not work! Multilingual stores do not fill in the Default option at all. Builderio has intended it for monolingual stores.

NOTE! Do not add a path to the “ handle ” section. It should be just the address of the page, such as “spring-security-check”.


6) Categorization

  • AI Commerce supports automatic categorization of Builderio articles using the GraphQL interface. Your UI integration partner can activate this feature if you wish.

Summary

Creating a blog in Builderio consists of building a new blog article template, defining required fields, and setting up a dynamic preview (preview URL). It is important to get the settings right once to avoid hunting for errors in the future.

builderiolla create blog

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • How to create families and variant families in Akeneo?
  • How do you activate a Klarna invoice?
  • How does Lemonsoft customer account synchronization work?
  • Group products
  • How to view a product's transaction history in the AI Commerce dashboard?

Copyright 2026 – AI Commerce Cloud.

Knowledge Base Software powered by Helpjuice

Expand