A business decides to add Spanish to its website, usually because a meaningful share of its customers speak it, and often because staff have been translating on the phone for years already.
That is a good reason. The failure comes afterwards. Six months later the English pages have moved on, the Spanish pages have not, and the site is publishing two versions of the business that disagree. The Spanish-speaking customer is now reading last year's prices and a service the business stopped offering.
Marque & Heir treats translation as a scoped, reviewed, and maintained commitment. What follows is that method for local businesses across the United States.
Decide how much of the site is in scope
Translating everything is rarely the right answer, and it is almost never the right first answer.
Start from what a Spanish-speaking customer needs in order to act: what the business does, where it works, how to make contact, what happens next, and how price is arrived at. That is usually four or five pages.
Then ask the harder question: what happens after they make contact. A translated contact page that leads to an English-only conversation is worse than no translation, because it invited someone in and then could not serve them. If nobody at the business speaks Spanish, translating the site is the second job, not the first.
Settle who is translating, and who is reviewing
There are three routes, and they are not equivalent.
Automatic translation. Fast and free. Also unreviewed, and it makes confident mistakes — particularly with trade terms, measurements, and anything idiomatic. Published unreviewed on a commercial site, it will eventually say something the business did not mean.
A translator. Accurate and paid for. The right answer for the pages that matter.
A bilingual member of staff. Often the best result, because they know the trade words customers actually use locally, which a general translator may not. It is also work, and it should be treated as work rather than a favour squeezed between jobs.
Whichever route, name a separate reviewer who reads the finished Spanish and confirms it says what the business means. The translator and the reviewer should not be the same person, for the same reason nobody proofreads their own writing well.
Regional variation is worth a decision too. The Spanish spoken by customers is not uniform, and a translation done in a register that feels foreign to local readers reads as imported. Ask the reviewer to check for that specifically.
Do not translate what should not be translated
Some things stay as they are: the business name, product and brand names, licence and registration numbers, and anything quoted from an official document.
Other things need conversion rather than translation — a phone number written for one audience, an address format, a date. And some things need a decision: if the business publishes terms or a policy, a translated version may or may not be the version that governs. That question goes to qualified review before either version is published, and until it comes back, mark it HOLD.
Give the two versions separate addresses
Each translated page should have its own address, and each should link plainly to the other. A visitor should be able to see that a Spanish version exists and reach it in one action, and the same in reverse.
Avoid the pattern where a script swaps the words in place with no change of address. It makes the Spanish version hard to link to, hard to share, and hard for search engines to treat as a page in its own right.
Say which language a page is in, in the page itself, so that assistive software and browsers read it correctly. A Spanish page marked as English is read aloud with the wrong pronunciation, which is a small technical detail with a large effect on whoever is listening.
Decide the upkeep rule before launch
This is the part that decides whether the project succeeds a year from now.
Write down: who updates the Spanish pages when the English changes, how they find out a change happened, how long they have, and what happens if they cannot.
Then pick a discipline and hold it. The two workable ones are: change both or change neither, or mark the Spanish page with the date it was last reviewed so a reader can see its age. The unworkable one is to change English freely and get to the Spanish later.
A smaller translated section that stays current is worth more than a complete one that goes stale. Scope the work to what the business can actually maintain.
Expect the phone to change
If the translation works, the business will get calls from people who expect to be answered in Spanish. Decide in advance who takes those calls, what happens when they are unavailable, and what the voicemail says.
Also decide what happens with forms. An enquiry written in Spanish needs someone who can read it and reply. Plan that before the form goes live, not after the first one arrives.
What honest translation avoids
No claim that the business offers Spanish-speaking service unless it does. No translated review or testimonial that was not given in that form. No automatically translated legal or safety wording published without review.
And no assumption that translation is a search tactic. It is a service to customers who speak the language. Whether it changes anything in search results is not something anyone can promise, and it is the wrong reason to do it.
What this work does not include
It does not include providing interpreters, translating documents the business is legally required to provide in a particular form, or certifying a translation. Where a translation carries legal weight, that goes to qualified review.
If a business is weighing this and wants to know what it would be taking on, the free business check can look at what is public now and mark which pages a Spanish-speaking customer would need in order to act, and which of those change often enough to need a maintenance rule.