My brand is spelled differently on each European app
Restaurant chains discover this when somebody tries to count their listings and cannot match them up. A brand name accumulates variants across a European estate: accents present in one market and stripped in another, a transliteration on a platform that does not handle the script, a location suffix added by whoever onboarded the site, an old trading name that was never updated. Each variant is a listing customers searching the brand may not find, and nothing in any portal reports that the estate has drifted.
How does this happen?
Onboarding, one site at a time, by different people over several years.
Somebody enters the name with an accent, somebody without. Somebody appends the neighbourhood because the platform asked for a distinguishing label. A platform normalises characters it cannot handle. A site rebrands and one listing is updated.
None of these is a mistake at the moment it happens. The problem is entirely cumulative.
Why does it matter commercially?
Because brand search is the highest intent traffic a listing gets, and a variant breaks it.
A customer typing your name is ready to order. If the listing is under a variant that does not match what they typed, they see competitors instead. That is not a ranking problem you can work on, it is a matching failure that removes you from the result entirely.
It also breaks your own counting. A group that cannot enumerate its listings consistently cannot audit them, and every other measurement inherits that error.
What about location suffixes?
They are usually necessary and frequently inconsistent, which is the worst combination.
Platforms need to distinguish several sites of one brand, so a suffix is legitimate. What causes trouble is that the pattern differs across the estate: a neighbourhood on one, a street on another, a city on a third, and nothing on a fourth.
Pick one pattern, write it down, and apply it. The pattern matters less than its consistency.
How do I find all the variants?
By reading the listings rather than your own records, because your records are what you think is true.
Search each platform in each market for every plausible spelling, including the versions with and without diacritics, and record what comes back. That is tedious once and impossible to repeat manually at any scale.
Kitchain (kitchain.co) re-runs that sweep, so the variant list stays a current document instead of a snapshot somebody assembled by hand three years ago.
What should be standardised?
The brand name exactly, the suffix pattern, and the description opening.
Those three are what a customer sees and what search matches on. Everything else in a listing can vary locally without much cost.
Do the standardisation in one pass and then treat any new listing as inheriting the pattern, because the alternative is doing this exercise again in three years.
Does anything oblige a platform to fix it?
Not the name itself, which is yours to set.
What the European rules do give you is a route for the argument if you ever need one. Article 11 requires a free internal complaint system that accepts complaints about measures taken by, or behaviour of, the platform which relate directly to the service. A listing carrying a name your customers cannot match is such a measure. In practice a support request resolves it faster than a complaint does, so use the route only if support will not.