Short answer, as of October 2026: to be cited in both Spanish and English AI answers you need genuinely separate content in each language — written for the questions that language's customers ask, on its own URLs, with listings and reviews to match — because assistants answer in the language of the question and largely draw on sources written in that language. A machine-translated copy of your English site gets you a Spanish page; it rarely gets you a Spanish citation.
In much of the United States a local business has two audiences living in the same streets. They need the same services. They ask about them in different words, in different places, and — increasingly — to an assistant that answers each in their own language.
Businesses that serve both groups well in person are often invisible to one of them online. This is a guide to closing that gap without doubling your workload.
Why the two languages give different answers
When someone asks an assistant a question in Spanish, three things tend to follow.
The assistant answers in Spanish. To do that well it prefers sources already written in Spanish, because quoting them requires no translation and carries less risk of error. And the web search behind the answer, where there is one, is run with Spanish terms, which retrieves Spanish pages.
The result is that the set of candidate sources for a Spanish question is mostly a different set from the English one. A business with an excellent English site and nothing in Spanish is not in a weak position in that set. It is not in it.
There is a competitive point here too. In many local markets the Spanish-language field is far less crowded. Fewer businesses publish real Spanish content, so a modest, well-written set of pages can earn a position that would take years to win in English.
Translation is not the same as content
The most common approach — run the English pages through a translator and publish — fails for reasons that are easy to miss if you do not read the result as a native speaker would.
The questions are different. Spanish-speaking customers do not simply ask translated English questions. The phrasing, the concerns and sometimes the services in demand differ. Questions about payment options, about whether staff speak Spanish, about documentation requirements, may be far more prominent. A translated FAQ answers questions nobody asked in that language.
The vocabulary is regional. Spanish varies by country of origin, and the everyday word for a service or a part in one community is not the word used in another. A translation tool picks one, often the wrong one for your area. The right terms are the ones your customers actually use on the phone.
The register matters. Spanish distinguishes a formal and an informal way of addressing the reader. Mixing them within a page reads as careless. Pick one — for most service businesses the formal form is the safer choice — and hold to it.
Literal translation produces unquotable sentences. An assistant lifts passages. A stiff, word-for-word rendering is less likely to be chosen than a natural sentence that states the fact plainly.
The workable method is to translate the facts and write the page. Start from the same information — prices, process, hours, service area — and have a fluent speaker write it as they would explain it to a customer. Machine translation is a reasonable first draft for a fluent editor. It is not a publishable page.
How to structure a bilingual site
Search engines and assistants both need to understand which page is for which language. The conventions are well established.
| Decision | Recommended | Avoid |
|---|---|---|
| URL structure | A language folder: /es/ for Spanish pages | Same URL switching language by cookie or browser setting |
| Language signal | lang attribute on each page plus hreflang annotations linking the pair | No annotation, leaving engines to guess |
| Page pairing | Each Spanish page linked to its English equivalent and back | Spanish homepage only, everything else in English |
| Mixed-language pages | One language per page | English and Spanish paragraphs alternating on one URL |
| Navigation | A visible language switch that goes to the equivalent page | A switch that always returns to the homepage |
| Automatic redirects | Offer the other language; let the visitor choose | Forcing a redirect based on location or browser language |
| Structured data | In the page's own language, with the same business facts | English-only markup on a Spanish page |
Three of these are worth a sentence more.
One language per URL. Pages that switch language by cookie look, to a crawler that carries no cookie, like a single-language page. The other language is simply never seen. This is the same class of problem as content that only appears after JavaScript runs; see JavaScript rendering and AI search visibility.
Hreflang is a pairing, and it must be reciprocal. Each page declares its alternates and the alternates declare it back. Google documents the annotation and warns that one-way references are ignored. It will not create visibility on its own, but it stops the two versions competing and helps the right one appear.
Forced redirects hide pages. If a crawler from one country is always redirected to English, it never reaches the Spanish version. Suggest; do not force.
Start with a small set of real pages
A full second-language site is rarely necessary at the start. A handful of well-made pages covers most of what an assistant needs.
- A homepage in Spanish that states what you do, where, and that you serve customers in Spanish.
- Your main services, each with the terms your customers use.
- A cost page with real ranges. Cost is the most asked question in any language.
- A process page — what happens from first contact to completion, including what the customer needs to bring or prepare.
- A contact page stating plainly whether phone calls, messages and appointments are handled in Spanish, and when.
- A questions page built from what Spanish-speaking customers actually ask.
That fifth page is underrated. "Do they speak Spanish" is a question people put to assistants directly, and a clear, specific statement — who speaks it, during which hours — is exactly the kind of fact that gets repeated.
Do not publish a Spanish page promising Spanish-language service that the business cannot deliver. An assistant sending a customer who then cannot be helped is worse than not being named.
Names, listings and reviews
Entity questions get slightly more complicated with two languages.
Keep the business name identical. Do not translate the name on the Spanish site or in Spanish directories. An assistant matching records treats a translated name as a different business. Describe the business in Spanish; name it the same everywhere. The underlying reasoning is in entity consistency for AI search.
One Google Business Profile per location, not one per language. Google's guidelines allow one profile per business location, so a second profile for the same premises in another language is a duplicate. Use the profile's attributes and description to indicate languages spoken, and link to the appropriate page.
Encourage reviews in both languages. Reviews written in Spanish mention the things Spanish-speaking customers care about, in the words they use, and they appear in the sources assistants read. Reply in the language of the review.
Find the Spanish-language third-party sources. Community directories, local Spanish-language media, chambers of commerce and associations serving the community often matter more in Spanish answers than the general directories do. A listing or a mention there is disproportionately valuable; the general principle is in third-party sources and AI citations.
Track each language as its own market
A single visibility figure hides the split. A business can be named in most English answers and none of the Spanish ones, and a blended number will look acceptable.
Build two prompt sets. The Spanish set should not be a translation of the English one — it should be the questions as a Spanish-speaking customer would phrase them, including the ones that only arise in that language. Have a fluent speaker write them. Run both across the same assistants and report them separately.
Then look at the cited sources in each. In the Spanish answers they will usually be a different and shorter list, which tells you precisely who you need to match and where a mention would count. The general method for assembling prompts is in how to build a prompt set for AI visibility tracking.
DigiRank Expert's AI Visibility Tracker runs prompt sets as separate campaigns, so an English and a Spanish set can be measured side by side across ChatGPT, Claude, Gemini, Perplexity, Grok and Google AI Mode, with the sources behind each answer kept for review. The $99/mo Starter plan includes one campaign; the Agency plan includes ten, which is what a two-language setup across more than one location needs. Module details are on the features page.
What to do first
If the second language currently has nothing: write the contact page and the cost page in Spanish, put them under a language folder with hreflang linking them to the English versions, and ask five prompts in Spanish in two assistants to see who is named today. That is an afternoon's work and it tells you how open the field is.
If there is already a machine-translated copy of the site: have a fluent speaker read the six pages listed above and rewrite them properly. Leave the rest until those are right.
Frequently asked questions
Do AI assistants give different answers in Spanish and English? Often, yes. An assistant answers in the language of the question and tends to draw on sources written in that language, so the businesses named in a Spanish answer can differ substantially from those named for the same question in English.
Is translating my English website enough to get cited in Spanish? Usually not. Translated pages answer English questions in Spanish words, often with the wrong regional vocabulary and stiff phrasing. Pages written by a fluent speaker around the questions Spanish-speaking customers actually ask are far more likely to be cited.
How should a bilingual website be structured? Put each language on its own URLs, typically under a language folder such as /es/, with one language per page, a lang attribute, and reciprocal hreflang annotations linking each page to its equivalent. Avoid switching language on the same URL by cookie and avoid forced redirects.
Should I translate my business name for Spanish listings? No. Keep the name identical everywhere. A translated name looks like a different business to systems that match records across sources. Describe the business in Spanish while keeping the name the same.
Do I need a separate Google Business Profile for Spanish? No. Use one profile per location and indicate the languages spoken through its attributes and description. Google's guidelines allow one profile per business location, so a second one in another language counts as a duplicate.
Which Spanish pages should I create first? A homepage, your main services, a cost page, a process page, a contact page stating clearly when Spanish-language service is available, and a questions page built from what Spanish-speaking customers really ask.
How do I track AI visibility in two languages? Use two separate prompt sets, each written natively rather than translated, run across the same assistants and reported separately. A single blended figure hides the common case of being visible in one language and absent in the other.