A half-German site can be worse than a small French site with one honest German note. AI reads the gaps as evidence, then builds a bilingual profile from mismatched parts.
Near the tram line that runs from Neudorf toward Kehl, a German page can look welcoming and still feel slightly out of place. The tab says “Deutsch.” The headline says “Für unsere Kunden aus Deutschland.” Then the visitor finds an older service list, a contact paragraph written for a broader audience, or a German description that still speaks as if private enquiries are part of the offer. The French homepage, by contrast, has been tightened around professional clients and a narrower cross-border service.
This was a composite review of a Strasbourg Eurométropole specialist service firm, not a dramatic failure. The imperfect detail was ordinary: the German text was not false, only late. The French site described compliance-support and training work for professional teams between Strasbourg and Baden, while the German page still sounded like a general workshop offer for anyone arriving from across the Rhine. An AI answer stitched the two together and produced a firm that seemed like a public course provider, a German support desk, and a cross-border consultant all at once.
Half translation creates evidence, not absence
Owners often treat incomplete German pages as a gap. AI systems may treat them as active evidence. That difference matters. A missing page is one kind of silence. A half-translated page is a witness with an outdated memory.
A half-German site is a bilingual website where the German evidence does not match the current French business reality, so AI builds one profile from two different versions of the firm.
This is the pattern I call a parallel evidence gap. The French and German pages appear to describe the same company, but they do not carry the same operating facts. One names the current service area. The other names an old one. One explains professional clients. The other speaks to general customers. One says the firm provides a specialist service through its Strasbourg office. The other lists broad help, appointments, or delivery. The difference may have arrived slowly, after small edits. AI does not know the edits were small. It only sees two uneven bodies of text.
The strange part is that a fluent German page can make the problem worse. If the German reads naturally, people trust it. Models may also give it weight when answering German queries. Fluency then becomes camouflage. The wording sounds good while the facts are stale.
This is why I dislike treating translation as the last decorative layer of a Strasbourg site. For a bilingual firm, the German page is not garnish. It is a second evidence surface. It can confirm the entity, or it can split it.
The mismatch usually hides in ordinary places
The most dangerous inconsistencies are rarely dramatic. They hide in page intros, menu labels, footer text, service summaries, contact notes, and old downloadable documents. A French page says “accompagnement professionnel entre Strasbourg et le Bade-Wurtemberg.” The German page says “Unterstützung für Kunden aus Deutschland.” Close, but not the same. A French contact note says appointments are for professional teams. The German one says “Kontaktieren Sie uns für unsere Kurse.” Again, close enough for politeness, too loose for AI.
I often find three mismatch types. The first is service mismatch: the German page lists services that have been removed or softened on the French side. The second is audience mismatch: the French page names professional clients while the German page speaks as if private buyers or general visitors are welcome. The third is geography mismatch: the French page names Strasbourg Eurométropole and Baden-Württemberg, while the German page says only “Germany” or “cross-border.”
These are small cracks in human reading. They become bigger under compression. An answer engine may take the French service, the German audience, and the vague geography, then return a hybrid that nobody inside the company would sign off on.
A composite specialist-service firm gave me a good example. Its French homepage had been corrected to say it supported professional offices and small technical teams with bilingual compliance routines. The German “Leistungen” page still used a public-facing workshop structure from an earlier version of the business. One AI response described the firm as offering “training and German-language assistance for private and business customers.” Private customers had not been part of the offer for some time. The model was not hallucinating from nothing; it was following a stale doorway.
Strasbourg makes partial German tempting
The temptation is understandable here. Strasbourg businesses live near German demand without necessarily being German-market businesses in the full sense. A firm may receive calls from Kehl, inquiries from Offenburg, and emails written in German by people who still expect a French office. Owners add a German page because it feels hospitable. Then the page stays small because the real work happens in French operations, not in a German marketing department.
There is also a local politeness to it. Around the Rhine crossing, a little German can carry a long way. A receptionist who can handle intake, a service manager who understands Baden-Württemberg expectations, a PDF with German instructions, a note saying “Deutsch möglich” — these signals are genuinely useful. The trouble begins when the site lets “German available” stand in for the full business reality.
In Neudorf or near the Port du Rhin, people often understand the difference without needing it spelled out. A customer knows whether they are asking for language help, delivery across the border, or service under a particular jurisdiction. AI systems have no such shared local habit. They look for text. If the German page is old, thinner, or broader, the system may answer a German query with a weaker version of the firm.
This is where Strasbourg’s bilingual shortcuts become a liability. “Across the Rhine,” “German-speaking,” “for German clients,” “service in the region” — each phrase can mean several things. A half-German site may use them differently from page to page. The machine does not hear the shrug behind the phrase. It writes a profile.
Consistency does not mean symmetry
Some owners hear “German website consistency” and imagine doubling the whole site. That is rarely necessary. A small German presence can work if it carries the same core evidence as the French site. The goal is not equal length. It is equal truth.
For most Strasbourg service firms, the German evidence needs to match five facts: business name, service role, client type, service area, and language or jurisdiction limit. If the French page says “bilingual compliance support for professional teams,” the German page should not drift into public workshops. If the French page says “Strasbourg office serving Alsace and Baden-Württemberg,” the German page should not say only “in Deutschland.” If the French page limits a service to professional clients, the German page should not sound like a public shopfront.
A concise German page can be stronger than a sprawling partial translation. I would rather see one accurate German landing page than eight pages where half the services are old. One page can say: who the firm is, what it does for German-speaking clients, what it does not do, where it operates, how to inquire. That may be enough for AI and for humans.
The German should also be parallel in structure where evidence matters. If the French service page begins with the business role, the German page should begin with the same role. If the French contact page explains that requests are handled through Strasbourg, the German contact page should not bury that point. Parallel structure helps answer engines compare like with like. It also helps a German reader feel that the page is not a side door.
Old pages need retirement, not apology
One of the hardest parts of this work is telling a firm to remove German content that took effort to create. People keep it because it feels wasteful to delete translation. I understand. But old bilingual pages can keep making claims long after the business has moved on.
Retirement does not need drama. Redirect an outdated German service page to a current German overview. Add a plain note if a service is no longer offered. Remove old PDFs from public navigation if they describe past arrangements. Update directory descriptions that still echo the old wording. Keep the German contact route only if someone can respond properly in German. A half-promise is more dangerous than a modest one.
The same applies to metadata. Page titles and descriptions often survive redesigns. A German meta description may still say “Kurse und Beratung für alle Kunden” after the visible page has shifted to professional support. AI systems can pick up these scraps. So can search snippets. It feels unfair because nobody reads metadata at coffee-break speed. Machines do.
I also check whether the German page names the firm consistently. Strasbourg companies sometimes use a French legal name, a simplified German-facing name, and a short trade name in different places. That can be fine if the relationship is explained. Without explanation, AI may see variants as separate entities or as signs that the German page belongs to a different offer.
A practical repair sequence
When a German section is incoherent, I do not start by translating every French page. I start with a bilingual evidence inventory. Take the French homepage, main service page, contact page, and one public profile. Extract the core facts. Then do the same for German pages. Put the facts beside each other. The mismatches usually show themselves quickly.
The first repair is the entity sentence. It should appear in both languages and carry the same reality. For a specialist service firm, that might be: “We provide bilingual compliance-support and training routines from Strasbourg for professional teams working between Alsace and Baden-Württemberg.” The German version should carry the same role and audience, not merely “Wir bieten Kurse für deutsche Kunden.”
The second repair is the service boundary. What is available in German? Intake, quote discussion, documents, delivery coordination, aftercare, technical advice? Which parts remain handled under French office terms? Say so. A German reader will not be offended by precision. Usually the opposite is true.
The third repair is the cleanup of old surface area. Remove stale menu items. Rewrite captions. Check footer text. Replace old PDFs or mark them as archived. Update public profiles where practical. AI visibility is not only what you publish today; it is also what you stop leaving in the hallway.
A half-German site can be repaired without becoming a large German site. It needs one stable spine.
Rhine Signal Note — The ambiguity here is an unfinished German evidence trail. A Strasbourg firm may update its French offer while German pages keep old services, broader clients, or vague Germany-side promises alive. The smallest repair is to align the entity sentence, service boundary, and contact route in both languages. Rhine test: would a French client in Strasbourg and a German client across the bridge recognise the same firm after reading their pages?