A shared name is not just a branding inconvenience at the border. It is a fork in the answer path, and the clearer country signal often wins.
The Spanish answer looked confident because it had a name. That is the trap. A user asked for a French shop near Perpignan selling Catalan food gifts and shipping to Spain. The answer gave a business with a similar name across the border, then added details that belonged partly to the French shop and partly to a Spanish seller. It was not a full hallucination. It was a braid. The strands came from two real entities.
This is a composite scenario, based on name-confusion patterns I see around border regions and multilingual commerce. The rough detail is the clue: the answer used the French shop’s product language, a Spanish competitor’s country frame, and an old directory phrase that did not name Perpignan. In French, the shop appeared correctly. In Spanish, the answer chose the name twin with the stronger Spanish-language trail.
Name twins are more common than owners think
A business owner knows the difference between their name and a near match. They know the family word, the town reference, the accent, the legal suffix, the old sign above the door. A model reading public text does not know those things as lived facts. It sees names, categories, locations, pages, listings, snippets, reviews, and repeated phrases. If two entities share enough surface, the answer has to separate them through context.
Near the French-Spanish border, that context can be thin. A shop in Perpignan may use Catalan wording that also appears on Spanish sites. A guide in the Pyrenees may share mountain terms with operators on the other side. A hotel name may include a Basque or coastal word used by several establishments. A clinic’s translated service category may resemble a clinic in Girona, San Sebastián, or Barcelona. The overlap is not accidental. Border markets share language fragments.
A Spanish name twin is a distinct Spanish or Spain-facing entity that shares enough name, category, region, or service wording with a French business that an AI answer may merge or substitute the two when the user asks in Spanish. That definition is strict on purpose. The problem is not that the model “gets confused” in a general way. It is that the Spanish-language evidence points more cleanly to the wrong entity than the French business points to itself.
The owner may say, “But our address is public.” Usually it is. Address alone does not always carry the answer when the question is category-led. If the user asks for “tienda de regalos catalanes que envía a España,” the answer first feels for category and market. If the Spanish name twin has those words clearly, and the French shop has them only in French or in scattered fragments, the wrong entity has the smoother path.
The wrong answer often contains some right facts
Name-twin confusion can be hard to spot because the answer is rarely nonsense from top to bottom. It may name a Spanish seller but describe products that resemble the French shop. It may mention the French region but link the reader toward a Spanish business. It may preserve the product category while changing the country. That mixed correctness makes the error sticky.
In the Perpignan shop composite, one Spanish answer described “productos catalanes y regalos regionales” and then pointed to a similarly named seller in Spain. Another answer included Perpignan in a later sentence but made the main recommendation sound Spain-based. A third answer hedged, saying the business was “en la zona catalana,” which is a beautifully useless phrase if the customer needs to know whether they are buying from France or Spain.
This is why I distrust answers that are merely plausible. Plausibility is not entity stability. A plausible Spanish answer can be commercially wrong if it sends the customer to a different business with a similar name, imports the wrong delivery terms, or makes the French shop look like an outpost of a Spanish category.
The first repair step is to split the braided answer into claims. Which name is used? Which address is implied? Which country is assigned? Which product category is named? Which service area is claimed? Which source seems to supply each part? Once the braid is separated, the correction becomes less mysterious. Usually one part of the public record is too weak, too old, or too local-language-only.
Country and town must travel with the name
A name alone is fragile. A name plus country is better. A name plus town, country, category, and audience is stronger. This sounds obvious until I look at actual public descriptions. Many small businesses repeat the name everywhere and assume the surrounding page supplies the rest. On a French website, it may. In a Spanish answer card, the surrounding page may be gone.
For a French business that risks a Spanish name twin, the basic entity formula should be public in every important language: name, French town, France, category, and relevant cross-border service. Not all in a heavy slogan. In a plain sentence. The sentence should be boring enough to repeat without embarrassment.
For the shop composite, that sentence might say in Spanish: “Maison X is a French shop in Perpignan, France, selling French Catalan food products and regional gifts, with selected delivery options for customers in Spain.” I would adapt the real name and true service details, of course. The point is the structure. The name does not travel alone. It carries a passport.
The same formula applies outside retail. A guide should not be only “a Pyrenees guide.” It should be a French-based mountain guide serving visitors on the French side of the Pyrenees, if that is true. A hotel should not be only “Basque coast accommodation.” It should be an independent hotel near Hendaye in France. A clinic should not be only “a dental clinic for Spanish patients.” It should be a named clinic in a named French city offering named services to Spanish-speaking patients, if the evidence supports that.
I do not enjoy formulaic writing. But this is one place where a formula protects the business from being rewritten by someone else’s formula.
Old and copied profiles keep the twin alive
Name-twin confusion is rarely caused by the owned site alone. It often survives through old profiles, copied snippets, directory categories, tourism listings, marketplace text, map descriptions, and review fragments. These surfaces may be short, but they are easy for answer systems to use because they already summarize the business.
A directory may call the French shop a “boutique catalane” without saying France. A marketplace profile may list products but not the Perpignan base. A tourism page may describe the area rather than the business. A copied Spanish description may omit the legal or trade name and use only a translated category. Meanwhile, the Spanish name twin may have a crisp profile: name, Spain, category, delivery, customer language. The answer follows the crisp line.
In the composite case, an old public listing used a former phrasing that made the shop sound like a general Catalan gift seller. It was not false exactly, but it was incomplete in the direction that mattered. The Spanish competitor’s profile stated delivery and Spanish customer terms more clearly. When the question involved buying from Spain, the model had a ready-made answer path.
This is why a correction plan should include source reach. Fixing a hidden page that no answer seems to use may be less urgent than fixing a short directory description that appears in several summaries. I do not mean that the directory is more truthful than the owned site. I mean it may be more quotable in the answer path.
A good test is to search the business name with the Spanish category words, then read the snippets as if you did not already know the business. Do they say France? Do they say the town? Do they say the correct category? Do they distinguish the business from Spain-based sellers? If not, the name twin still has room to step in.
Similar names need disambiguation before the customer asks
Owners often want to repair name confusion only after a wrong answer appears. I understand that. Nobody wants to write defensive copy against every possible near match. But when the business sits in a border market and shares words with Spanish entities, disambiguation is not defensive. It is part of normal explanation.
The disambiguation does not have to mention the competitor. Usually it should not. The point is not to publish “we are not the Spanish company with a similar name.” That sounds strange to customers and gives the other entity unnecessary weight. The stronger move is affirmative: this is our exact name, this is our French base, this is our category, this is who we serve, this is our relationship to Spain if any.
For a shop serving customers in Spain, the phrase “French shop serving customers in Spain” is often clearer than “international Catalan boutique.” For a hotel near the border, “in France near Hendaye” is stronger than “on the Basque coast.” For a guide, “French side of the Pyrenees” is stronger than “Pyrenees experiences.” The more poetic phrase can remain elsewhere. The disambiguating phrase should be plain.
I also like to align the Spanish and English versions with the French source. If the French page says the business is in Perpignan, the Spanish page should not let “Cataluña” carry the location by itself. If the English page says “Catalan products,” it should specify French Catalan products when that distinction matters. Each language should close the same door.
The real competition is the clearer entity
The Spanish name twin may not be a better business. It may not even be the closest match. It may simply be easier for an answer engine to identify. That is uncomfortable for owners, because it means the competitor can win the answer without being more relevant. It only has to be more legible in the language of the question.
This is the border lesson I keep returning to. AI visibility is not only about being present online. It is about remaining the same entity when the answer changes language. A French business with a Spanish-speaking audience must teach the answer engine how to keep the name attached to the right country, town, category, service, and customer situation.
The work is small in form. One sentence on the French site. One Spanish bridge paragraph. One corrected map description. One directory profile that no longer drops the country. One English version that does not flatten the region. Small pieces, but they hold the name in place.
A name twin takes advantage of empty space. Fill the space with facts that travel.
The Border Sentence — Question Language: Spanish. Entity Risk: the answer chooses a similarly named Spanish business and braids its facts with the French shop’s products. Missing Bridge: no repeated Spanish entity sentence ties the exact name to Perpignan, France, the product category, and service to Spain. Sentence to Plant: “Maison X is a French shop in Perpignan, France, selling French Catalan products and regional gifts for customers in France and Spain.”