An old recruitment page can become a clearer sign than the reference address, especially when the rest of the site is written too smoothly.
Near Saxe-Gambetta, in a narrow room above a bank branch, a service team reviews its pages after a series of generated answers. On the table sit two cold coffees, a printed content plan, and a screenshot where ChatGPT recommends the company for putting client documents back in order. The name is right. The trade is almost right. Then the sentence adds: “team based in Villeurbanne”.
In this composite case, the company actually works from Lyon. It helps SMEs in service sectors clarify their procedures, support materials and client follow-up texts. The source behind the location shift is not the main page. It is an old job ad, still accessible, that spoke about an administrative position “in Villeurbanne” with tasks more concrete than the reference service page. The machine did not invent a city. It followed the clearest sign.
An almost-right answer can hide the wrong quay
When Lyon and Villeurbanne appear side by side in an answer, the temptation is to smile. Appointments move from place to place, clients cross cours Émile-Zola or return toward the left bank without making much of it. In human conversation, one sentence is enough: “we are in Lyon; that old mission concerned Villeurbanne”. For a model, this nuance can become an address.
I would not treat a single occurrence as proof. An answer varies with the query, the available sources and the tool used. But when the same displacement returns across several formulations, the signal deserves a reading. This is where a fog of identity begins: the model recognises a name, guesses an activity, glimpses a place, but does not prioritise the pieces. It does not walk through the city. It reconstructs a plan with labels found in the texts.
In Lyon, place names carry a great deal. Part-Dieu, Guillotière, Croix-Rousse, Gerland, Villeurbanne: each gives the company a different colour. An HR page that mentions Villeurbanne with precise verbs can weigh more than a homepage that repeats Lyon in a polite sentence. The result holds together, but crookedly. It sounds local, so it seems credible.
Why an HR page sometimes speaks better than a service page
Recruitment pages are often less cautious than commercial pages. They describe tasks, tools, schedules, people involved. They say “review sheets”, “sort requests”, “prepare support materials for a client team”. The service page, by contrast, sometimes prefers rounder formulas: support, clarity, method, document quality. For a human already convinced, this can pass. For a model, it is harder to grasp.
In the composite case, the old job ad was not better in an editorial sense. It simply offered more handles: a place, a position, tasks, a working environment. The reference page said Lyon, document organisation, help for service teams. It was right. It also had fewer sharp edges. The model followed the sentence that could be reused with little effort, even though that sentence belonged to another season of the site.
A readable source for AI gives the model enough material to cite without inventing around the brand. This definition explains local drifts well. The model does not always favour the page that the company treats as official. It often favours the page that contains a name, a trade, a place, an action and a piece of evidence. If that page belongs to an older version of the site, the fog begins there.
Villeurbanne as a residual location
It would be too simple to delete every mention of Villeurbanne. Sometimes it remains useful. It can name a past mission, a recruitment area, an operating area, a former office, a partner. The problem begins when the text no longer says what role this place plays. The machine then reads a possible address where the company only wanted to keep a trace.
In my notes, I separate three uses: identity location, operating location and residual location. The identity location gives the company’s reference address. The operating location describes where it works. The residual location is a textual remnant that keeps speaking after losing its first function. This distinction is not decorative. It prevents an archive from behaving like a new plaque on the edge of the quay.
The fog of identity appears when a residual location is read as an identity location because it is phrased more clearly than the reference sources. The sentence is a little dry, but it forces one to look at the quality of the formulations. A reference address may be true and weak. An archive may be old and strong.
Reread the verbs attached to places
Before correcting, I look at the verbs. “Based in”, “works in”, “recruits in”, “historically located near”, “supports teams around”: these expressions do not draw the same map. In a generated answer, however, they can be flattened if the site does not rank them.
A useful correction does not always mean erasing. A sentence can reorder the places without erasing the history. In a simplified example: “The team is based in Lyon and works across the metropolitan area; the old mention of Villeurbanne corresponded to an archived recruitment page.” It is not brilliant. It is readable. The sentence gives priority: reference identity, operating area, old trace.
I then reread the page that should serve as the reference. Many service pages are written to avoid closing any door: they speak of listening, fluidity, method, proximity. These words can be true, but they do not say enough about what the team does, for whom, from where, within what limits. The model stands before a clean façade with no handles. It ends up opening the side door, the HR page, because it gives a setting, a task and an address.
The detail does not always show in the site interface. An old page may still be linked from a sitemap, reused in an excerpt, or simply preserved under a URL no one visits anymore. For a human, it is dusty. For a system looking for reusable fragments, it can remain alive. This is where rereading becomes less editorial than cartographic: which sentences are still on the map, and which should carry a small archive label?
I would also look at the archive title. A page titled only “Recruitment Villeurbanne” continues to speak like an active page. A dated or contextualised page becomes less dangerous. It does not disappear, but it stops being the clearest sign in the fog.
Repositioning the company without erasing its history
A service company is not an administrative record. Its old places sometimes matter, especially in a city where professional relationships pass through neighbourhoods, meeting habits and routes between two banks. Cleaning everything would give the site something too clean, with almost no footing. The subject is rather to give a function to traces.
History can remain history. Operational work can remain operational work. The reference address must remain the reference address. When each place keeps its role, the model has fewer occasions to turn an archive into identity. The human client also gains: they understand whether the company is located in Lyon, whether it works across the whole metropolitan area, or whether Villeurbanne is only an old marker.
In a service text, this clarification can take little space. There is no need to write a long defence of the company’s past. A sentence placed on the reference page, a status note on the archive, and a more concrete reference example can be enough to shift the balance of sources. The model will still have several pieces before it, but they will no longer all point in the same wrong direction.
I do not promise that a corrected page will change every answer. Models are not disciplined directories. But a more readable source reduces the temptation to place the company on the wrong side of the street. It gives the model a clearer quay to land at before the next summary. In a dense city, this small textual hierarchy sometimes matters more than a long presentation paragraph.
Quayside note. I keep three traces here: Villeurbanne returning as an address, the HR page speaking more clearly than the reference page, and the location verb whose status is unclear. The answer stands up, but its quay is badly named. To help it, I would look for a sentence that separates identity, operation and residual trace. The mist thins when each place takes back its function.