Phoenix and Tucson both carry large Spanish-speaking populations, and most local business sites never acknowledge it.
I check language settings on every site I audit. English is usually the only option, even in neighborhoods where a large share of residents speak Spanish at home. One language, one version of the business, no second door in.
The Market Already Here
Arizona is not a bilingual market by accident. Spanish has been spoken in parts of Phoenix, Tucson, and the towns along the border for generations, not a decade.
A business serving that market in English only is not missing a market. It is missing a part of the one it already has.
I do not think every business needs a full Spanish site. Most never ask the question at all. The ones that do usually ask it too late, after a competitor already answered it.
What Machine Translation Misses
Running a page through a translator fixes the grammar and loses the person.
A literal translation of a tagline can read stiff or formal in a way nobody actually talks. Arizona's Spanish-speaking community draws heavily from Mexican Spanish, so word choice built for Spain or for a generic translation tool can land oddly here. A price, a warranty, a service name, all of it can come out technically correct and still feel off to the person reading it.
The fix is not a better translation tool. It is a bilingual person who reads the page before it goes live, the same way you would proofread a brochure before it goes to print. One pass. One real reader. That is the whole fix.
How Engines Read Language Signals
A Spanish page needs its own URL and a language tag in the page's HTML. A banner that swaps visible text on click is not the same thing.
I have not seen anything published by Google, OpenAI, or Perplexity describing exactly how a Spanish page is weighed against its English twin. What I can say is that the structural basics still apply. The page has to be a real, separate, crawlable page for either a search engine or an AI tool like ChatGPT to treat it as its own answer.
A toggle that swaps text with JavaScript and never changes the URL gives a crawler one page with two states, not two pages. Same address. Two different businesses trying to speak through it.
Which Pages Actually Need It
Not every page is worth translating. Trying to translate all of them usually means none of them get done well.
- The homepage and the pages for services people search for in Spanish, like limpieza or remodelacion.
- The Google Business Profile description and services list, since a Spanish listing supports it directly.
- The contact page, so a Spanish-speaking buyer can reach someone who can help them in that language.
Everything else can wait. A thin, mistranslated page the business cannot maintain works against it. A handful of pages a bilingual person actually wrote works for it. Fewer pages, done right, beats a full site nobody keeps current.
The Profile Side Matters Too
A Spanish page nobody can find does nothing. Pair it with a profile that says the same thing in both languages.
Google Business Profile does not need any setup to receive a review written in Spanish. That already happens on its own. People write in whatever language they think in, and the profile just holds it.
I read those reviews specifically. They often say something the English ones never do. A detail about a crew member. A note about how a quote was explained. Small things, but they tell you who the business is actually reaching.
When Skipping It Is Fine
If a business has no Spanish-speaking staff and no plan to serve Spanish-speaking customers, a Spanish page is a liability, not an asset. It promises a conversation the business cannot actually have.
A bilingual page should match the business behind it. A business that already serves Spanish-speaking customers by phone and in person, with nothing written down anywhere, is the clearer case worth fixing. The conversation already exists. The page is just catching up to it.
I would start with the page that answers the question a Spanish-speaking buyer is already asking somewhere else, on the phone or at the counter. That is usually one page, not ten.
Keeping a business's name, services, and prices consistent across languages is the same discipline covered in our post on entity consistency, pointed at a new surface. That work is part of what I build inside an SEO / AEO / GEO Foundation engagement.