Project · Conversational messaging platform
Fifteen country subdomains, and the case for not building them
Gupshup was early into international expansion and the plan on the table was a separate subdomain for roughly fifteen countries. It is a common instinct and it is usually the expensive answer. Fifteen subdomains means fifteen authority profiles to build independently, and most of them stay thin for years.
The problem
The team wanted market specific presence and the obvious route looked like country subdomains. The trouble is that subdomains do not inherit authority automatically. Every one of them starts near zero and needs its own links, its own content investment and its own patience. For a company still establishing itself globally, that spreads a limited budget across fifteen fronts at once.
There was a second problem underneath it. Market pages that target overlapping languages compete with each other unless the relationships between them are declared properly. Without hreflang the wrong market page surfaces in the wrong country, and the fix after launch is far more expensive than the decision before it.
Not how many markets do we want, but how many authority profiles can we afford to build and maintain. That reframing changes the architecture.
What I did
- Set the international SEO direction, including the case for consolidating authority rather than splitting it across country subdomains.
- Implemented hreflang, so language and market versions declared their relationships to each other rather than competing.
- Worked on page structure and design alongside the content, since international architecture is not only a tagging exercise.
- Established the on-page patterns each market version would follow, so new markets could be added without redesigning the system.
FIGURE 1
Diagram: subdomain sprawl versus a consolidated subfolder structure
Draw this, do not screenshot it. 1600 x 900.
Where it landed
The platform today runs three language versions on subfolders rather than fifteen country subdomains, with reciprocal hreflang across all versions and x-default pointing at the primary English page. It is the consolidated architecture rather than the sprawl.
Have a migration coming up?
The cheapest time to fix a migration is before it ships. Twenty minutes on a call will tell you whether yours is at risk.
Typical reply time: within one working day