Multilingual Website Creation Diary - Day 33] Website Setup Complete!

The project exceeded the initial schedule by three days.

All website setup issues have been resolved. Although I'm a complete novice in development, I believe it's best to avoid frequently altering the default settings when initially creating a website.

Especially for multilingual websites, posts are published 50 times more, so if you publish a post incorrectly or make a mistake, you can't undo the changes to each category, tag, and post.

Therefore, wanting to quickly expose blog posts, registering the sitemap in Search Console first and tinkering with the website structure and plugin installations can negatively impact the website. Absolutely don't do that.

Thus, sitemap submission should be done after all site settings are complete. It's recommended to pre-publish one or two posts and submit after all settings are finalized.

This is because if Google's search bot visits once and then returns, and the post's permalink has changed, or key settings such as the website title or tags have been modified, it causes confusion. Ultimately, if the website structure changes frequently, the Google bot won't visit often.

Therefore, the sitemap should be submitted only after the site creation is complete and there are no further changes needed.

It's best to limit modifiable aspects to those related to posts. For example, this includes the post title or content. Deleting pages that have already been requested for indexing is also not recommended. It's good to remember that a stable website is more beneficial for search exposure.

Nevertheless, I want to document the parts where I made mistakes. I think this can be considered a form of self-reflection.

Initially, I placed the hosting server in Indonesia. In the Asian region, I could choose from India, Indonesia, and Singapore. I thought it was best to set the server closest to the website operator's location, so I chose Indonesia without much thought. However, the GTranslate plugin's server was located in France. The distance between the servers caused a delay in the translation process.

Every time I published a post, I had to go to the translated page and press Ctrl + F5 to complete the translation. For pages that weren't translated in one go, I had to refresh multiple times.

Furthermore, a bigger problem was that the first page and category preview pages of each language's website weren't being translated. To solve this, I had to access Hostinger and clear the cache every time I published a post. However, I felt this would negatively impact the CDN (Content Delivery Network), and ultimately decided to change the server hosting location.

Kodee is Hostinger's AI robot consultant.

Although they advise that server changes can take up to 4 hours, in my case, since the website was recently created, I only had 3 websites, and the number of posts and pictures was small, it only took about 10 minutes.

For reference, the list below shows the countries where Hostinger has servers by continent.

• Europe: France, Lithuania, Germany, United Kingdom
• Asia: India, Indonesia, Singapore
• North America: United States
• South America: Brazil