When agencies go bilingual, the default answer is two sites: a Spanish one and an English one. Separate installs, logins, menus, SEO. And somewhere in the weekly routine, someone pays that cost forever.
The real cost of “two sites”
Every front-page change has to be redone. Every listing update lands twice. Every new agent bio exists in two places that quietly drift apart. After a few months, the Spanish site is a month behind and search engines have two half-maintained versions to choose from.
That’s not a bilingual strategy. That’s a maintenance tax you pay every week because nobody wanted to stop and choose a better model.
One site, both languages
A multilingual system keeps one source of truth and publishes it in both languages. A listing updated in English is immediately current in Spanish. Clean /en/ and /es/ URLs tell search engines exactly which version to show a buyer from Vancouver or a homeowner in Puerto Vallarta. Hreflang is handled. Your team feeds one system.
The first build costs a little more than a single-language template drop. The second year of operation is where it pays for itself — every single week.
The pattern we use
For most real estate and destination builds: English at the root, Spanish at /es/, TranslatePress handling the pairing, and copy written native per language rather than machine-flipped. Same install, same design system, same hosting. One site that serves two markets because your market is bigger than one language.
This post is one of two on bilingual WordPress. Next: why the site you build should outlast the agency you build it with.