Google has clarified its Business Profile naming rules by adding repeated bilingual names and script transliterations to the examples of content that is not permitted in the business-name field. Search Engine Roundtable identified the wording change on August 10, 2026 and compared it with the previous guidance.
The policy may look narrow, but it directly affects tourism, healthcare, real estate, restaurant, education, and export-oriented businesses that serve multilingual audiences. Many profiles place a local-language name next to an English translation or repeat the same name in another script. Google's current wording says that a repeated translation or transliteration should not be added to the name merely to show both versions, even when the alternate form appears on physical signage.
What changed?
Business Profile quality guidelines have long required the name field to reflect the name used consistently in the real world. Phone numbers, slogans, business hours, service areas, and category descriptions do not belong in it. The current text adds another explicit group: repeated business names in another language or script.
A business should not write its name in Latin characters and immediately repeat the same name in another alphabet. A Turkish and English version joined by a dash can also be risky when the second phrase is only a translation added for discoverability. Google does not list every country and language combination. The underlying principle is one consistent business identity in the name field.
This text-free Fark Studio illustration contrasts one verified business identity with a duplicated language layer compressed into the same field. It is not a Google interface.
There is an important nuance. Google is not saying that a business name can never contain words from two languages. A formally registered brand may genuinely use a bilingual construction, or multiple terms may be permanent parts of the identity. The clearer risk is adding a second translation, pronunciation guide, or search phrase next to the primary name when it is not the consistent business identity.
Who is affected?
Hotels, tours, restaurants, and experience providers are a first group because they often add English wording for international visitors. The same pattern appears in medical tourism, property, schools, clinics, and cross-border services. Multi-location retailers and franchise networks should review their name inventory as well.
The operational risk grows for agencies and large networks. A disputed name on one profile may be corrected quickly, but a bilingual naming pattern pushed to hundreds of locations can multiply verification, suspension, and name-change requests. Franchise teams need evidence that central naming rules match local real-world use.
Local SEO teams should avoid the wrong conclusion. Removing an English phrase from the name does not make the business invisible to every English-language search. Categories, services, products, descriptions, reviews, the website, and localized content provide other signals. Using the name field as a keyword container was already risky.
What is confirmed and what remains uncertain?
The official help page now lists repeated bilingual names and script transliterations among disallowed name examples. The broader rule that the profile must reflect a consistent real-world identity remains in place. Search Engine Roundtable's comparison indicates that these examples were newly added to the text.
Google has not published a universal enforcement date, the share of profiles that will be reviewed, or a detailed exception table. Businesses with formally bilingual legal names, franchises, and companies that use different official names in different markets still need case-specific evidence.
Do not edit every location in a panic. Changing a profile name can trigger re-verification in some situations. Multi-location brands should collect evidence first and test the workflow on a small representative group before a bulk change.
What should businesses do now?
1. Export every location. Put the profile name, country, language, branch, and verification status in one inventory.
2. Flag repeated structures. Isolate names that repeat the same identity in two languages, scripts, parentheses, or pronunciation forms.
3. Preserve real-world proof. Store signage, website, invoice, registration, and brand-guideline evidence for the primary name.
4. Separate keyword additions. City, service, phone, slogan, and category terms added to the name are a different policy problem and should be cleaned independently.
5. Move language support to the right surfaces. Use localized landing pages, services, products, posts, and customer-facing content. Do not make the name field a translation database.
6. Stage multi-location edits. Test whether a name change triggers verification or unexpected visibility movement before updating the complete network.
7. Review agency permissions. Prevent an unapproved bulk edit from changing hundreds of profiles at once.
8. Prepare an appeal file. If the official name is genuinely bilingual, gather registration, signage, and corporate-source evidence before support is needed.
This Fark Studio flow moves from profile inventory through evidence collection and risk classification to a staged update.
Where should teams wait?
Do not change an entire estate based only on one secondary headline. The official guidance confirms the rule, but the enforcement schedule and all edge cases are not documented. A company with a genuinely bilingual trade name should evaluate its own evidence and support options first.
Do not attribute every short-term ranking movement after an edit to this wording change. Local results depend on proximity, category, competition, reviews, websites, and freshness. Without a clean change log, the cause is difficult to establish.
Fark Studio perspective
Google's direction is clear: the business-name field should represent one verifiable identity, not function as a multilingual keyword surface. Multilingual discovery belongs in localized content and a coherent website architecture.
At Fark Studio, local SEO, SEO, and corporate web share one location inventory. Cleaning profile names should not stop international users from reaching the right language, service, and location page.
If you need to audit a multi-location profile estate for policy risk and organic visibility, Fark Studio can build the local SEO plan.
Sources
Google Business Profile Help, Guidelines for representing your business on Google, current official documentation, checked August 10, 2026. Primary source for the business-name rules.
Search Engine Roundtable, Google Business Profiles Disallows Repeated Bilingual Names & Script Transliterations, August 10, 2026. Secondary radar source comparing the new and previous wording.
