A French update does not automatically update the Spanish memory of the business. Old translated pages and directory fragments can keep speaking after the real service has changed.
A small hotel on the French Atlantic coast changes its winter opening policy. The French site is corrected first. The booking page is clean. The owner edits the main description and removes an old line about a shuttle. In a composite scenario I use for visibility reviews, the Spanish answer still mentions the shuttle, still suggests the hotel is mainly a summer beach stay, and still blurs the location toward the broader Basque coast. One tiny nuisance makes the scene believable: the model also gets the number of rooms right.
That mix is the problem. The answer is not completely wrong, so nobody panics. It feels close enough. But a Spanish-speaking family reading it receives a business that is partly current and partly old. The French record moved on. The Spanish-facing record did not.
Recency is uneven across languages
When a French business updates its public facts, the correction usually appears first in French. That is natural. The owner writes in French, the staff checks the French page, the booking tool or product page changes, and the main listings may follow. The Spanish or English fragments are often secondary: an old translated page, a tourism directory, a partner listing, a PDF, a review response, a marketplace profile, a forgotten paragraph on a regional site.
AI answers do not experience those layers as “main” and “secondary” in the way the business owner does. They assemble from whatever public traces look useful. If an old Spanish profile states the service plainly and the new French page states it indirectly, the old Spanish profile may remain attractive as an answer source. This is how stale information survives.
The recency gap is the distance between the current business fact and the oldest foreign-language public fact still strong enough to shape an AI answer. It matters because language versions age at different speeds, and answer engines may preserve the older version when it is easier to quote.
In my parallel answer cards, this gap is rarely dramatic at first. The business did not move countries. The name did not change into nonsense. Instead, one sentence lags. A hotel still has a restaurant it closed. A clinic is still described through a treatment it no longer emphasizes. A shop still appears to sell a category that was removed from the online store. A guide is still attached to a route that was dropped. The stale fact is small enough to hide inside a generally plausible answer.
Small stale facts are dangerous because people trust the rest.
Why the foreign-language version goes stale first
French businesses often treat non-French copy as a launch task. It is written once, posted somewhere, and admired for having solved the international problem. Then the business changes. Rooms are renovated, shipping countries expand, a clinic narrows its services, a guide changes the meeting point, a shop updates product lines, a school changes intake dates. The French pages follow the business. The foreign-language pages follow only if someone remembers them.
The rougher truth is that many Spanish and English facts are not even on the business’s own site. They live in places that were filled once because a partner asked for a description: tourism offices, booking profiles, local business directories, event listings, old interviews, association pages. These sources may have higher visibility than expected because they state the business in simple, extractable language. They are sometimes wrong precisely because they were once useful.
For the Atlantic hotel composite, the Spanish issue might come from a regional listing made two seasons earlier. The hotel’s French site now describes itself as a quiet base near Hendaye for weekend stays and walkers. The Spanish listing still says “hotel de playa para vacaciones de verano” and mentions an arrangement that no longer exists. The answer engine sees a Spanish-language source that appears directly relevant to a Spanish question. It uses it. The French correction does not always overpower it.
This does not mean the model has bad intentions, or that the old source is malicious. It means source alignment is part of maintenance. If a business has a multilingual audience, its facts cannot be current in only one language.
A single outdated Spanish sentence can become the cleanest available answer fragment.
The bilingual drift ledger
I keep a simple ledger for this work. It is not pretty. It is a table of claims, languages, and sources, with one column for whether the fact is current. I call it a bilingual drift ledger, even when English is included too, because the first tension usually appears between the home language and one foreign-language surface.
The ledger starts with the claims a customer would act on. Opening dates. Service availability. Location. Country. Region. Booking method. Delivery area. Languages spoken. Price range if public. Product category. Transport details. Medical or professional services, where accuracy matters more. I do not begin with adjectives like charming, authentic, premium, family-friendly, or specialist unless those adjectives create the error. Most stale-answer damage comes from factual service claims.
Then I collect the French version, the Spanish version, and the English version where available. I record not only owned pages, but also public profiles and answer cards. The point is not to create a perfect archive. The point is to catch the sentence that refuses to age.
In one composite shop case, the French online store had stopped shipping one fragile product category abroad, while an old Spanish blurb still presented the shop as a source for that category in Spain. In another composite service case, the French page changed the service area, but an English directory retained the previous towns. In both, the AI answer mixed current and old facts because the old foreign-language wording was clearer than the new French correction.
This is a humbling thing to tell a business owner. The page they care about most may not be the page the answer follows.
Alignment does not mean identical translation
A bad repair is to make every page a literal copy of the French page. That can create a different kind of distortion. Spanish-speaking and English-speaking customers may need different explanatory context. They may ask from another country, use another category term, or care about delivery, access, or language support before they care about the business’s local history.
Alignment means the factual spine is the same. The phrasing can differ. The facts should not. If the hotel is in Hendaye, France, it should not become “near San Sebastián” without also naming France and Hendaye. If the shop ships to Spain only for certain product categories, the Spanish page should not imply all products are available. If a clinic offers a narrow treatment, the English page should not widen it into a general specialty. If a guide serves the French side of the Pyrenees, the Spanish wording should not make the service sound Spain-based.
This is where translation becomes commercial governance. A translated sentence is not only a language asset. It is a claim that can be cited, repeated, and compared. Once it enters an answer engine’s source field, it may outlive the season that produced it.
I prefer a three-line fact spine for fragile pages. One line for identity: what the business is and where it is based. One line for current offer: what is available now, in plain category terms. One line for audience or service area: who it serves, in which languages or countries if relevant. These lines can then be adapted into French, Spanish, and English without changing their factual load.
A hotel might say, “We are an independent hotel in Hendaye, France, near the Atlantic coast and the Spanish border.” The current-offer line might mention rooms, booking season, walkers, families, or whatever is actually true. The audience line might state that French, Spanish, and English-speaking guests use the hotel as a base for the French Basque coast. Nothing ornate. Just load-bearing beams.
How old facts keep reappearing
Outdated facts do not disappear just because the owner deletes one page. They reappear through copies, snippets, partner databases, archived descriptions, and human-written summaries that have been reused. Sometimes the old Spanish description was pasted from an English profile, which was originally translated from a French page that no longer exists. The family tree is not noble.
In answer records, I look for three clues. First, a stale fact that appears only in one language. Second, a stale fact that appears with wording close to a public directory or listing. Third, a stale fact that survives even after the owned site has been corrected. These clues suggest the answer engine may be using or remembering an external source path, not only the current French site.
There is uncertainty here. I cannot always prove the source. Some AI answers show citations; some do not. Some cite pages that support one part of the answer but not the stale claim. When the trail is not visible, I mark it. Pretending to know the exact source is worse than leaving the uncertainty on the page. The repair still has direction: strengthen the current multilingual facts and correct the reachable old profiles.
The order of repair should follow risk. A stale opening date is inconvenient. A stale medical service, safety detail, pickup location, or delivery promise can create real customer harm. A stale category can send the wrong people to the business. A stale country or region can erase the business from the market it actually serves. Not all old facts deserve the same urgency.
The owner usually wants to fix everything. The answer usually improves when we fix the sentences that customers act on first.
A maintenance rhythm that is small enough to keep
The best multilingual fact systems are boring to maintain. Once a quarter, or after any major business change, collect the public claims that matter and check the French, Spanish, and English surfaces. Do not wait for a full redesign. Do not bury this in brand strategy. Read the public pages as a foreign customer would read them, then ask the same customer-style question in each language.
For a hotel, the recurring questions may concern location, seasonality, access, guest type, nearby region, and language support. For a shop, they may concern product categories, delivery to Spain, stock, regional origin, and customer service. For a clinic, they may concern service availability, professional category, appointment language, and location. The question set should be small because the work has to survive ordinary business pressure.
After that, update the fact spine. Then update the pages and profiles with the highest chance of being seen: homepage, service pages, delivery or booking pages, map listings, tourism profiles, partner descriptions, and any Spanish or English page that has been copied elsewhere. Keep the old and new wording in the ledger for a while. It helps detect which stale phrases still return in answers.
There is no romance in this work. It is more like checking the bolts on a bridge after the weather changes. But for French businesses serving foreign-language customers, that bridge is where the sale, booking, visit, or inquiry begins.
Question Language: Spanish. Entity Risk: the answer mixes current French facts with an older Spanish description, so the business looks partly available, partly outdated, and slightly misplaced. Missing Bridge: no maintained multilingual fact spine connects the current French record to Spanish and English public sources. Sentence to Plant: “This is the current description of our French business for Spanish-speaking and English-speaking customers: [name], [place in France], [current service], [current service area or audience].”