Almost every property management company in a market with Spanish-speaking renters says the same three words on the phone. Se habla español. Almost none of them say it anywhere a renter can read it before calling, and the handful that try do it with a widget that drops a translate dropdown in the corner and produces nothing a search engine can find, nothing a lease can rely on, and nothing that survives the next template update. There is a version of this that works. It is smaller than a translated website, it is legally more careful than most vendors will tell you, and the audience it reaches is measurable rather than assumed.
The audience is countable, so count it
Spanish is spoken at home by 44.9 million people in the United States according to the American Community Survey, which makes it the most common language other than English in American households by a wide margin. That number alone does not justify a translation budget, because most of those speakers also read English comfortably. The number that does is the one underneath it. Migration Policy Institute tabulations of the 2020 to 2024 five-year ACS put 27,139,643 US residents aged five and over as speaking English less than very well, which is 8.6 percent of that population, and 17,218,782 of them, roughly 63 percent, speak Spanish.
Then layer the tenure data on top, because that is what turns a language statistic into a leasing one. The Census Bureau's Housing Vacancy Survey put the second quarter 2026 homeownership rate at 65.0 percent nationally, 74.5 percent for non-Hispanic White alone householders, and 48.1 percent for Hispanic householders of any race. Read the Hispanic figure the other way around and a majority of Hispanic households in the country, 51.9 percent, are renting. Against roughly a quarter of non-Hispanic White households. The renter pool is not evenly distributed across languages, and neither is your vacancy.
None of that tells you about your market, which is the only one that matters. Before you translate a single page, pull three things: the share of households in your metro speaking Spanish with limited English, which the Census publishes at the place level; the calls your leasing line already fields in Spanish, which your staff can count in a week; and the Spanish-language queries already reaching your site in Search Console. If all three come back near zero, the honest answer is that the money belongs somewhere else on the site.
What the national numbers actually say
44.9M
People who speak Spanish at home, the most common non-English language in US households
17.2M
Spanish speakers who report speaking English less than very well, 63 percent of all limited-English residents
48.1%
Hispanic homeownership rate in Q2 2026, against 74.5 percent for non-Hispanic White householders
Sources: US Census Bureau American Community Survey language use tables; Migration Policy Institute tabulations of the 2020 to 2024 ACS five-year estimates; US Census Bureau Quarterly Residential Vacancies and Homeownership, second quarter 2026, Table 7.
Where the legal line actually sits
No federal law requires a private management company to publish a Spanish version of its website. Anyone telling you otherwise is selling translation. What exists is narrower and more specific, and it is worth knowing precisely, because the risk is not in failing to translate. It is in translating selectively, or in making a promise the office cannot keep.
HUD's Office of General Counsel issued guidance on 15 September 2016 on how the Fair Housing Act applies to limited English proficiency. Its position is that LEP is not itself a protected class, but that language and national origin are close enough to be treated together, so a housing decision made on the basis of limited English can be analysed as national origin discrimination. The guidance names the obvious failures: an advertisement stating that all tenants must speak English, or a policy of turning away applicants who are not fluent. It also sets out the three-step discriminatory effects test, asking whether a policy produces a disparate effect, whether it serves a substantial, legitimate, nondiscriminatory interest, and whether a less discriminatory alternative exists. Housing providers that receive federal financial assistance carry separate language access obligations under Title VI on top of all of that.
Then there is state contract law, which is where a website promise becomes a document problem. California Civil Code section 1632 requires a business that negotiates primarily in Spanish, Chinese, Tagalog, Vietnamese or Korean to deliver a translation of the contract in that language, with every term and condition, before it is executed. Leases and rental agreements are named in the statute. The obligation continues through the tenancy, so material changes including rent increases have to be translated too, and failure to comply lets the other party rescind. If your Spanish page produces a Spanish-speaking applicant and the negotiation happens in Spanish, in California the lease follows. Check your own state before you assume it does not.
Four ways to put Spanish on a site, and what each is worth
This is the decision that determines everything downstream, and most companies make it by accident, because a plugin was easier to install than a page was to write. The difference between the options is not quality of translation. It is whether the Spanish version exists at a URL.
| Approach | Own URL | Findable in search | Safe for lease documents | What it is actually for |
|---|---|---|---|---|
| The browser’s own translate | No | No | No | It already exists and costs you nothing. Treat it as the floor, not a strategy, and make sure your pages do not break when it runs |
| A JavaScript translate widget | No | No | No | Looking like you did something. It swaps text on the same URL, so there is no Spanish page for Google to rank and nothing to link to |
| Machine-translated /es/ pages, shipped as-is | Yes | Yes | No | A first draft that got published. Fine for a neighborhood description, wrong for anything stating a fee, a deadline or a screening criterion |
| Reviewed /es/ pages on real URLs | Yes | Yes | Yes | The only version that earns search traffic, survives a compliance question and reads like a person wrote it. Machine draft plus a human pass is the affordable route |
What Google needs, in its own words
Google's international documentation is unusually direct about this. Use different URLs for each language version rather than cookies or browser settings to adjust the content language. It lists three acceptable structures, subdirectories such as example.com/es/, subdomains such as es.example.com, and country-specific domains, and says URL parameters are not recommended. For a property management company operating in one country, the subdirectory is the obvious answer: cheapest to set up, inherits the authority of the domain, and no extra DNS or hosting to maintain.
The same documentation tells you to avoid automatically redirecting users from one language version to another, because it can stop both people and crawlers from reaching every version, and it warns that changing content dynamically based on browser settings may leave Google unable to crawl all the variations. That single sentence is the case against the widget. Add hyperlinks between the language versions instead, and put that link somewhere consistent rather than in the footer.
On hreflang, three things decide whether it works at all. It can be declared in link elements, HTTP headers or an XML sitemap, and the methods are equivalent. Every version has to point at every other version including itself, because if two pages do not both point at each other the annotations are ignored. Codes use ISO 639-1 for the language with an optional ISO 3166-1 Alpha 2 region, so es and es-mx are valid and a bare region code is not. Add x-default for the version that should catch everyone else. One detail worth knowing before you worry about duplicate content: Google treats localized versions as duplicates only when the main content itself remains untranslated, so translating the template while leaving the body in English is the case that actually causes trouble.
Translate six pages, not forty
The reason most Spanish sections die is that somebody scoped the whole website, priced it, and shelved it. The version that ships covers the pages where a renter has to understand something exactly, and stops there. Listing search and the listing page, so the unit, the rent and the availability date are unambiguous. Application requirements and fees, which is the page that generates the most phone calls in any language. The apply page itself, or at minimum a Spanish walkthrough of the English form if your software will not localize. Maintenance request submission, because a resident describing a leak should not have to translate first. Contact, with the hours somebody Spanish-speaking is actually there. And the resident FAQ covering rent payment, late fees, notices and lease renewal.
Your blog is not on that list and does not need to be. Neither is the about page, the owner services funnel, or the team bios, unless you are also pursuing Spanish-speaking owners, which is a separate decision with a separate audience and should be made on its own evidence rather than folded in for tidiness.
Seven steps to a Spanish section that works
Measure your own demand first
Census place-level language data for your metro, a week of tallying Spanish calls at the leasing line, and the queries already in Search Console. Three cheap inputs that tell you whether to build this at all, and which market to build it for.
Choose a subdirectory and commit to it
Everything under /es/. Not a parameter, not a subdomain you will forget to renew, and never a widget that leaves the URL unchanged. Google names the subdirectory as the low-maintenance option and rules out parameters outright.
Scope the six decision pages and ignore the rest
Listings, application requirements and fees, the application itself, maintenance requests, contact, and the resident FAQ. A finished six-page Spanish section beats a forty-page one that never launches.
Machine draft, human pass, every time
Translation software gets you 90 percent of the way for a fraction of the cost, and the last 10 percent is where fees, deadlines and screening criteria live. A bilingual staff member reviewing the draft is usually cheaper than an agency and better at your local usage.
Wire hreflang in both directions and add x-default
Every page points at its counterpart and at itself. Unreciprocated annotations are ignored outright. Use es or es-mx, never a bare region code, and pick the declaration method (link element, HTTP header or sitemap) you can maintain without remembering to.
Never auto-redirect, and put the language link in the header
Automatic redirection by browser language is explicitly discouraged and it traps both users and crawlers on one version. A visible link on every page, in the same place, in the language it switches to.
Make the promise true after the click
If the page says se habla español, somebody has to answer in Spanish during the hours you published, the application confirmation has to arrive in Spanish, and in California the lease has to follow under Civil Code 1632. A Spanish page in front of an English-only office is worse than no Spanish page.
The bottom line
More than 17 million people in the United States speak Spanish and report speaking English less than very well, and the group they sit inside rents at a far higher rate than the national average. That is a real gap between who is searching and what most management websites are readable by. Closing it does not take a translated website. It takes six pages at real URLs under /es/, a human read on the machine draft, hreflang pointing both ways, no automatic redirect, and an office that can answer in the language the page promised. Do less than that and you have a dropdown in the corner that nobody finds and nothing can rank. Do that much and you have pages that show up in Spanish searches, get sent between family members over text, and hold up when somebody asks what the application fee actually was.
