Our Work / Custom Software
Custom Software Full case study

Multilingual Visa Information Portal

Malaysia Visa Advisory Information services · Malaysia

"Serving English and Chinese-speaking audiences from one site — with accurate content, reliable translation management, and an SEO foundation strong enough to rank for both."

EN / ZH
Bilingual
WPML
Translation mgmt
SEO
Structured
CWV
Core Web Vitals pass
Technology stack
WordPress
CMS — content management
WPML
Multilingual — EN/ZH content parity
LiteSpeed Cache
Performance — Core Web Vitals
On-page SEO
Schema, hreflang, meta structure
Client
Malaysia Visa AdvisoryInformation services · Malaysia
Industry
Immigration & VisaB2C information portal
Services delivered
Custom SoftwareWeb development · SEO · CMS
Languages
English & ChineseFull content parity, WPML
The challenge

Two audiences. Two languages. One site that had to serve both without compromise.

Malaysia Visa Advisory helps both English and Chinese-speaking visitors navigate the Malaysian visa application process. Their previous site was English-only, with no clear content hierarchy, slow page load times, and no structured data — effectively invisible in search results for Chinese-language queries despite that audience making up a significant portion of their actual traffic.

Adding a second language to an existing WordPress site is straightforward. Adding it properly — with full content parity, correct hreflang configuration, a manageable editorial workflow for the team, and a structure that doesn't confuse search engines — is considerably harder. Done wrong, bilingual sites can end up with duplicate content penalties, inconsistent URLs, and a translation layer that breaks every time the site is updated.

The brief was clear: build a bilingual portal that serves both audiences without compromising either. English and Chinese versions should be content-equivalent, fast, correctly structured for search, and maintainable by a non-technical team after handover.

Our approach

Architecture first. Content second. SEO baked in from the start.

We designed the multilingual architecture before writing a line of code — mapping the content structure, deciding on URL patterns for each language version, configuring hreflang correctly across all page types, and establishing the editorial workflow for how translated content would be created, reviewed, and published before any content went in.

Bilingual Content Architecture
WPML configured with language-specific URL patterns, language switcher placement, content parity mapping across all page types, and a translation workflow the editorial team could operate independently after training.
WPMLURL structureContent parityHreflang
On-Page SEO Framework
Title tag and meta description structure for both language versions, canonical URLs to prevent duplication, schema markup (Organization and FAQPage), and internal linking architecture designed around the most valuable visa information queries.
Meta structureSchema markupCanonicalInternal links
Performance Optimisation
LiteSpeed Cache configured for both language versions — page caching, browser caching, CSS/JS minification, lazy image loading, and CDN-compatible setup. Core Web Vitals benchmarked and resolved before launch.
LiteSpeed CacheImage optimisationCWVMinification
CMS & Editorial Workflow
Custom editorial documentation, role-based CMS access for the translation team, and a post-handover support period ensuring the team could add, update, and translate content without developer dependency.
CMS trainingRole accessEditorial guide
How we delivered it
01
Content audit & architecture
Sitemap review · URL structure · WPML planning
02
Design & build
Custom theme · Responsive layouts · Language switcher
03
SEO & performance
Meta setup · Schema · Hreflang · LiteSpeed · CWV
04
Content migration
English content · Chinese translation · Parity check
05
Launch & handover
Go-live · CMS training · Editorial workflow documentation
The SEO decision

Hreflang done right. Not just added.

Hreflang is one of the most commonly misconfigured elements in bilingual WordPress sites. The tag tells search engines which version of a page to serve to which audience — but it has to be implemented consistently across every page, in both the HTML head and the XML sitemap, with correct language and region codes.

We implemented hreflang at the WordPress template level, so every page — including dynamically generated archive pages and individual visa-type content pages — carries the correct bilateral annotation automatically. New pages added through the CMS inherit the correct hreflang configuration without requiring manual intervention.

We also configured separate XML sitemaps for each language version and submitted them individually to Google Search Console — giving the search engine a clean, unambiguous signal for both the English and Chinese content sets.

SEO architecture
English (en-MY)
Primary language · /en/ URL prefix
Chinese (zh-MY)
Secondary language · /zh/ URL prefix
Hreflang
Bilateral annotation on every page type
Separate XML Sitemaps
Per-language submission to Search Console
New CMS pages inherit correct hreflang automatically
The outcome

One portal. Two languages.
Built to rank in both.

EN / ZH
Full bilingual content parity across all pages
Every page exists in both English and Chinese with equivalent content, correct hreflang tags, and proper language-specific URLs — serving both audiences without compromise.
WPML
Translation managed independently by the editorial team
The team can add new content, create translations, and update existing pages entirely through the CMS without developer involvement. The editorial workflow is documented and the team was trained at handover.
SEO
Full on-page and technical SEO coverage from day one
Title structure, meta descriptions, canonical URLs, schema markup, internal linking, and hreflang configured correctly across both language versions — not retrofitted after launch.
Fast
Core Web Vitals passing at launch
LiteSpeed Cache, image optimisation, and asset minification configured before go-live. Core Web Vitals benchmarked and resolved during testing — not left as a post-launch problem.
Start a project

Have a similar challenge? Let's talk.

Book a free 30-minute consultation with Jack. We'll tell you honestly whether your project is a fit for what we do — and what a realistic build would look like for your business.

JC
Jack Chang
Director, Trendtive Digital Sdn Bhd
Your consultant for this session
Book your free consultation
Trendtive Digital · 30 minutes · Microsoft Teams
30 minutes · Free · No obligation
Format: Microsoft Teams
With: Jack Chang, Project Director — Trendtive Digital
What we'll cover
Your business and the specific challenge you're trying to solve
Whether your project is a fit — and which service approach applies
Realistic scope, timeline, and CAPEX or OPEX engagement model
No credit card · No commitment · Response within 24 hours