Google and local search
Translating the hours is useful. Inventing a second suite in Spanish is a split NAP.
Language is not a second shop. Hours and the phone must not drift. Hreflang is not a SKU we fake if we have not shipped it. Visible bilingual copy still has to share one NAP. A shop that wants a Spanish page and is about to change the phone "for that audience." One entity. Two languages. Zero doorway cities.
If you show Spanish and English, keep the same name, address, and phone in both. Match Google Business Profile. Translate hours, not the suite number. Do not create city clones per language. BizzitPro is $12 a month. We do not invent an hreflang SKU we have not documented.
Who this is for
A shop that wants a Spanish page and is about to change the phone "for that audience." If that is not you, a different Bizzit guide will fit better, do not force this URL.
The actual answer
Language is not a second shop. Hours and the phone must not drift. Hreflang is not a SKU we fake if we have not shipped it. Visible bilingual copy still has to share one NAP. One entity. Two languages. Zero doorway cities. The short version is still the one in the box at the top of this page. The rest of the article exists so you do not have to guess the limits.
Do this in order
Lock NAP first. Then translate the offer. Then check hours in both places.
- Lock NAP in one card
- Translate hours and the offer
- Keep the phone identical
- Match GBP
- Skip a second URL per suburb and language
What not to do
Do not publish a different address in translation. Do not stuff cities into the Spanish H1. That is the usual way a useful page turns into a doorway, a fake comparison, or a brief Cipher cannot honor.
How this shows up on Bizzit
Tell Cipher the languages you actually staff. A fake translation of a fake suite is two lies.
GBP is usually one profile
Do not create a duplicate listing for "the Spanish shop." Answer Q&A in the language asked if you can. Keep hours identical.
Limits
Do not publish a different address in translation. Do not stuff cities into the Spanish H1.
Limits and caveats
Do not publish a different address in translation. Do not stuff cities into the Spanish H1.
If a sentence would require a competitor SKU we have not verified, or a statistic we did not measure, it does not belong here.
What to do after you read this
If this page answered the query, open Create with the nouns from your own business, not a slogan. If it did not, you are probably in the wrong cluster: go back to the blog hub or Google and local search. Do not spin a second URL for a synonym. One intent per page is the whole point of this library.
Tools that actually do this job
These are public pages. Use them when the job is this job. They are not a second product you have to buy.
Questions people actually ask
Does Google want two GBPs?
Not for two languages of the same shop. Follow their help. One place.
Hreflang?
If we have not shipped it as a SKU, we will not document it as one. Visible bilingual copy can still exist.
Who answers the phone?
Hours should reflect who can speak which language, without splitting NAP.
Pro?
Unlimited Cipher to fix a drifted translation. Still not a ranking buy.