🌍 Building an SEO-Ready Bilingual Portfolio
From Long-Term Intent to Real Execution with AI Agents
From my first, second, until my third portfolio website, I always had the same intention:
I wanted to build a bilingual portfolio website — Indonesian and English.
Not for aesthetics.
But because I knew early on:
if I wanted my work to be read outside Indonesia, language would be the first barrier.
The problem was always the same:
➡️ complex
➡️ time-consuming
➡️ SEO + multi-language felt overwhelming
And eventually, that intention was always postponed.
Until AI Agents became part of my workflow.
🎯 Purpose of This Article
This is not a surface-level SEO tutorial.
This article is:
-
a real technical note
-
a practical experience
-
a set of architectural decisions
-
and a collection of hard-earned lessons
about how daffathan-labs finally became:
-
🌐 a bilingual website (ID / EN)
-
🔍 SEO-ready
-
🤖 largely built and configured with the help of AI Agents
🧠 The Classic Problem of Developer Portfolios
Every time I tried to build a bilingual portfolio, the problems were repetitive:
-
routing became more complex
-
content duplication increased
-
fear of SEO duplicate content
-
sitemap management became harder
-
maintaining two languages was exhausting
Honestly, for a solo engineer, the effort never felt proportional.
That’s why my previous portfolios were always:
-
single-language
-
locally focused
-
fast to finish
🤖 The Turning Point: AI Agents in the Workflow
Once AI Agents matured, my approach changed completely.
AI was no longer just for:
- writing content
But also for:
-
structuring the system
-
generating boilerplate
-
validating configurations
-
accelerating iteration
At that point, I realized:
This long-standing intention finally made sense to execute.
🏗️ Bilingual Architecture in Daffathan Labs
The core structure is simple, but disciplined:
/id
/articles
/projects
/services
/en
/articles
/projects
/services
Each language:
-
has its own URL
-
is not a client-side toggle
-
does not rely on query parameters
-
is fully SEO-friendly
This decision matters.
🌐 Routing & Locale Handling
The approach used:
-
Next.js App Router
-
[locale]dynamic segment -
language dictionaries
With this setup:
-
search engines understand language context
-
users are never confused
-
the URL structure stays consistent
Most importantly, AI Agents help maintain consistency across languages.
🔍 SEO: More Than Meta Tags
SEO in this project goes far beyond:
-
title
-
description
It includes:
-
canonical URLs
-
modern robots.txt handling
-
dynamic XML sitemaps
-
consistent URL structures
-
content parity across languages
Interestingly,
both sitemap and robots configuration were fully generated by AI Agents,
then manually reviewed and refined.
🗺️ Modern Sitemap (Without Physical Files)
The sitemap in daffathan-labs:
-
is not written manually
-
is not stored as a static file
-
is generated via Metadata Routes
It includes:
-
all Indonesian pages
-
all English pages
-
articles
-
projects
For search engines, what matters is not the file itself, but that it is:
-
valid
-
fetchable
-
consistent
🤯 Lessons from Google Search Console
One important lesson:
Google Search Console is not real-time.
Sometimes:
-
the sitemap is valid
-
accessible in the browser
-
but still marked as error
This is normal.
The real mistake is:
-
panicking
-
re-submitting repeatedly
-
changing structure without clear reasons
The right approach: ➡️ configure it correctly once, then let Google do its job.
🌍 Why a Bilingual Portfolio Matters
Because my goal is clear:
-
not only local recruiters
-
not only Indonesian traffic
-
but global relevance
With a bilingual portfolio:
-
technical articles reach a wider audience
-
projects are easier to understand
-
positioning moves to the next level
This is not about “looking international.”
It’s about opening wider opportunities.
🚀 The Role of AI Agents in This Project
Being fully transparent:
-
bilingual structure → AI-assisted drafting
-
SEO checklist → AI-generated baseline
-
sitemap logic → AI-assisted design
-
English content → AI-assisted adaptation
Still:
-
final decisions remain human
-
AI is an accelerator, not a replacement for understanding
🧾 Conclusion
Now I can confidently say:
An SEO-ready bilingual portfolio is no longer a dream.
With:
-
the right architecture
-
modern tooling
-
and AI Agents integrated into the workflow
what once felt too complex for a solo developer
is now reasonable and scalable.
And daffathan-labs is the living proof.
📌 Website: https://daffathan-labs.my.id
📌 Experiments & repositories: https://github.com/daffa09