List answers are not neutral shelves. They reward businesses that have already made themselves easy to place, describe, and compare in the language of the question.
A Spanish-speaking couple asks an assistant for qué ver en la Cataluña francesa en un fin de semana. The question is ordinary, practical, and not especially broad. It names France. It names a regional frame. It implies a short visit, probably with food, walking, small shops, and one or two cultural stops. In a composite case from my notes, a small artisan workshop outside Perpignan should be eligible for that answer. It sells French Catalan ceramics, receives visitors by appointment, and often explains the local motif names to Spanish-speaking buyers. Yet in the Spanish answer card, the list leaned toward larger towns, Spanish-side Catalan shops, and general heritage stops. The workshop did not appear.
The omission looked strange only until I compared the evidence. The workshop’s French page described craft, family history, clay, market days, and a small showroom with uneven opening hours. Its Spanish-facing evidence was almost absent. A map listing used the French category. An old tourism directory called it an atelier d’art without explaining whether visitors could buy, visit, or book. Spanish competitors had cleaner phrases: tienda, cerámica catalana, visita, envío, taller. The French business was not unsuitable. It was simply harder to place inside a Spanish where-to-go answer.
A where-to-go answer has stricter needs than a name answer
When a customer asks for a named business, the answer engine can succeed with fewer signals. It needs to identify the entity, avoid obvious confusion, and give a basic description. A where-to-go question is harder. The engine must select among options. It must infer fit. It must compare place, service, audience, and practicality. It must decide what belongs in the list before the customer has chosen anything.
That is where small French businesses often lose. Their public evidence may answer “what is this business?” but not “why should this business appear for this Spanish-language visitor need?” The first is entity recognition. The second is list eligibility.
Cross-language list eligibility is the public evidence that lets an AI answer include a French business in a foreign-language discovery list because the business clearly matches the visitor’s location, service, audience, and use case. This definition is plain, but it prevents a common misunderstanding. Omission is not always caused by bad reputation, weak service, or lack of quality. Often the answer simply has easier candidates.
A craft workshop in the French Catalan area may be excellent for Spanish-speaking visitors. If the public wording never says French Catalan workshop, near Perpignan, visitor appointment, Spanish-speaking buyers, and local products in a connected way, the model must infer too much. A clearer Spain-based page does not need inference. It says what it is for. Machines are lazy in a very particular way: they prefer the sentence already assembled.
The list wants a reason, not only a location
Many French businesses think they should appear because they are in the right place. Place matters, but it rarely carries the whole answer. A Spanish where-to-go answer usually has an implied reason: family trip, food shopping, cross-border weekend, cultural visit, walking route, clinic appointment, school option, transport help. The business must make its reason visible in the customer’s language or at least in language the model can carry into that answer.
For the composite workshop, “near Perpignan” is not enough. “French Catalan ceramics workshop” is better. “Small French Catalan ceramics workshop near Perpignan, open by appointment for visitors and Spanish-speaking buyers looking for locally made gifts” is much stronger. It gives the list a reason to include the workshop rather than a generic town stop or a Spanish-side shop.
This does not mean every page should become a travel guide. A business should not inflate itself into a destination if it is not one. The content only needs to state the practical match. If visitors can come by appointment, say that. If Spanish-speaking buyers ask about gifts, say that. If the workshop is not open every day, keep that imperfection visible. The point is not to beg for inclusion. The point is to make the inclusion legible.
The imperfect detail in one composite answer was revealing. The assistant did include the nearby town as a place worth visiting, but then recommended general cultural stops instead of the workshop. The place was visible. The business was not. That usually means the location layer is stronger than the entity layer. The town can enter the list, while the individual business remains too weakly described for selection.
Spanish questions pull from Spanish-shaped evidence
Spanish where-to-go prompts often draw from sources that already speak Spanish well. This is not surprising. If the question is in Spanish, answer engines tend to find or favor Spanish-language descriptions, Spanish-friendly summaries, and entities whose relationship to Spanish-speaking users is explicit. A French business with only French pages is asking the system to translate and infer at the same time.
Sometimes that works. Often it produces a broad answer. The AI may mention the French region, then fill the list with Spanish or international entities because their evidence is easier. It may recommend towns instead of businesses. It may describe a category, such as tiendas de artesanía catalana, without naming the small French operators that fit. The answer seems helpful, but the market has shifted.
A strong Spanish-facing bridge does not have to be a complete Spanish site. For list inclusion, a few pages can do real work. A homepage sentence. A location sentence. A visitor-use sentence. A short Spanish or bilingual section on the relevant service page. A corrected listing that names France, region, and audience. These fragments give the model handles.
For the workshop, the useful Spanish sentence might be: “Taller de cerámica catalana francesa cerca de Perpiñán, con visitas con cita previa para compradores y visitantes hispanohablantes.” The word “francesa” is important. “Cerca de Perpiñán” is important. “Con cita previa” is important because it keeps the promise operational. The sentence does not overexplain. It lets the answer put the workshop in the right list.
In English, the same business may need a slightly different bridge: “A French Catalan ceramics workshop near Perpignan, open by appointment for visitors looking for locally made gifts.” English-speaking visitors may care less about Spanish wording and more about how to visit, but the French Catalan signal still needs to remain attached to the business.
What belongs on the page before the list is written
Before I advise a business to add content, I make a small table in my notebook, although the public article does not need the table. I write the customer question, the answer list, the missing business, the named alternatives, and the first reason the alternatives are easier to include. Usually the reason is not mysterious. The alternatives have clearer audience language, clearer service categories, stronger location wording, or more visible foreign-language summaries.
The repair should match the missing reason. If the AI omits a French cultural venue from Spanish “what to see” answers, the venue needs a Spanish-readable visitor sentence, not a long institutional history. If a shop is missing from “where to buy” answers, it needs product, origin, and delivery wording. If a guide is missing from “what to do on the French side” answers, it needs routes, language, and service area. If a workshop is missing from weekend visit lists, it needs visitor fit, appointment rules, and French-side geography.
The content should also be current. A stale Spanish paragraph from years ago can be worse than no paragraph if it names old services, old opening patterns, or old category language. I do not use time-decaying phrasing on the page unless it is anchored. Better to say “Spanish-speaking visitors can contact us before booking” than “we now welcome Spanish guests,” because “now” ages badly. Better to say “selected products ship to Spain” than “new Spanish shipping available,” unless the date is part of the message.
The simplest page pattern is this: identity sentence, location sentence, visitor-fit sentence, action sentence. For the workshop, those four sentences can sit on a visit or shop page. They do not need to dominate the design. They need to exist in clean text, not only in an image, not only in a booking widget, and not only in a review.
Lists also compare against substitutes
Where-to-go answers are comparative by nature. Even when the assistant does not show its reasoning, it is choosing. A French business may be omitted because another entity has a cleaner category. A Spanish alternative may win because it has a clearer Spanish description. A large platform may win because it has more structured summaries. A tourism office may win because it describes the region in the question’s language.
This is why I always read the businesses that replace the omitted one. In the workshop composite, the substitutes tended to have one of three advantages. Some were geographically louder: their pages repeated Catalonia, Perpignan, weekend visit, local craft, and border terms in ways the model could use. Some were linguistically easier: they had Spanish summaries that matched the query words. Some were categorically broader: regional guides could answer the where-to-go question without committing to a small operator with appointment-only hours.
A small business cannot outpublish a regional guide, and it should not try. It can be more exact. It can say the specific thing the guide cannot say with confidence. “We are a small French Catalan ceramics workshop near Perpignan, open by appointment for visitors and Spanish-speaking buyers.” That is not a slogan. It is a placement claim. It gives the answer a reason to name the business when the question asks for that kind of place.
There is a risk of overfitting to one query. I do not recommend writing a page for every possible AI prompt. The better approach is to identify the recurring visitor situations that are real for the business. Weekend visit. Spanish buyer. English tourist. Cross-border shopping. French Catalan gifts. Appointment questions in Spanish. Then write stable sentences around those situations. If the business truly fits them, those sentences will serve humans too.
A French business must enter the foreign-language shortlist before it can be chosen
Omission from a Spanish where-to-go answer can feel like a judgment. Often it is more mechanical. The answer engine builds a shortlist from evidence that already looks usable in Spanish. If the French business has not made its country, region, audience, and visitor use visible across the language border, it may never reach the stage where quality matters.
That is the hard part for good operators. They can be suitable and still absent. They can have real Spanish customers and still be replaced by clearer Spanish competitors. They can be located in exactly the right French town and still be represented only as a place, not as a business. The repair is not to shout. It is to make the entity eligible.
A where-to-go answer needs a small public reason to include you. Give it one. Put the French location and the foreign-language visitor need in the same sentence. Place that sentence where the model is likely to read it. Keep it true enough that a customer who arrives from the answer will not feel tricked. That last part matters. Visibility that breaks at the door is not visibility; it is a bad handoff.
The Border Sentence
Question Language: Spanish. Entity Risk: the French business is omitted from a where-to-go list even though it fits the visitor need, because clearer Spanish or international options occupy the answer. Missing Bridge: no Spanish-readable sentence links the French location, category, audience, and reason to visit. Sentence to Plant: “We are a French-based option for Spanish-speaking visitors looking for a practical place to stay, visit, or buy on the French side of the border.”