A customer calls and asks if anyone there speaks Spanish. Another fills out your contact form with a few words of English and a lot of questions. You start to wonder whether Spanish versions of pages like your services and contact page would win those people, or whether it would become one more thing you pay for and never use.
You do not have to guess. Your own calls, your Search Console data and the Census Bureau's language numbers can tell you in about ten minutes whether Spanish pages have a job to do.
Sometimes the answer is yes. Sometimes it is not yet, and that is a real answer too.
Key Takeaways
Spanish-speaking customers already contacting you, Spanish demand in your service area, or a Spanish page that removes a real barrier to booking. Google does not require every page to exist in every language.
A widget changes the text a visitor sees. Real Spanish pages have their own URLs such as /es/, a Spanish language tag, hreflang links to their English twins, and a language switcher.
Begin with the service, contact and booking pages that bring calls and forms, have a fluent Spanish speaker review every page, and measure Spanish calls and forms before going further.
When does a Spanish version of your website pay off?
Add Spanish pages when one of three things is true. Spanish-speaking customers already call, text, fill out forms or leave reviews. Your service area shows meaningful Spanish-language demand. Or a Spanish page would remove a real barrier, such as a booking form a customer cannot read.
Google does not require every page of a site to exist in every language, so a focused set of accurate pages is a legitimate first step. No general U.S. rule requires every private small-business website to publish Spanish. Sector, contract, funding or state rules can differ, so confirm those with qualified counsel or the relevant regulator.
Your answer will land on one of three decisions:
| Decision | It fits when | First step |
|---|---|---|
| Not yet | Spanish contacts are rare, Search Console shows no Spanish searches, or no one on your team can answer in Spanish | Log Spanish inquiries for a few months and keep improving the English pages |
| A small set of reviewed Spanish pages | Some Spanish contacts and searches show up, and at least one person can reply in Spanish | Translate the pages that bring calls and forms, then count Spanish calls and forms |
| A fuller rollout | Demand is clear, a Spanish response process works, and someone owns upkeep | Extend to the remaining service, policy and FAQ pages |
Ask any web design vendor to price the first two before you hear about a full bilingual rebuild. A proposal that can say "not yet" is one you can trust when it says "now."
How can you check Spanish demand in ten minutes?
Four checks, in this order, give you a usable read. Each one answers a different question: whether Spanish speakers already find you, whether they already reach you, whether you can answer them, and whether they live nearby.
- Open Search Console, choose Performance, set the date range to the last three months, and scan Queries for Spanish words and phrases such as "en español."
- Count the Spanish-language calls, texts, forms, appointments and reviews from the last month.
- Check whether your staff can answer those contacts in Spanish.
- Look up the American Community Survey language data for your service area. Table B16001 shows the language spoken at home and how well residents speak English.
The Census Bureau's language-at-home release and its ACS data portal are the places to start. Keep two limits in mind. ACS data describes residents, not guaranteed buyers. And the Search Console Performance report shows only searches that surfaced your existing site, so an English-only site can understate Spanish demand.
Is a translation button the same as a Spanish version?
A translation widget changes the text a visitor sees, and that can help someone read one English page. It usually does not create a stable Spanish page for each service. There is no separate Spanish URL to rank, no Spanish page title for Google to read, and nothing in your analytics that separates Spanish visitors from the rest.
Google also announced that its Website Translator widget would no longer be supported beginning October 1, 2026, with users of automatic translation pointed to the Cloud Translation API. A button can serve as a temporary reading aid. It is a weak foundation for a plan.
| What matters | Translation button | Real Spanish pages |
|---|---|---|
| Own address for each page | Usually not | Yes, such as /es/services/ |
| Spanish title and description | Usually not | Written and reviewed by a person |
| Language declared in the code | Not guaranteed | lang set to es |
| Google can connect the English twin | No | Yes, through hreflang |
| Measured on its own in Search Console | No | Yes |
Google's own guidance on translated results says Search may show machine-translated titles and snippets, but it does not host the translated pages. A page on your site that has its own URL can be crawled, indexed, linked and measured.
What does Google need to treat your pages as Spanish?
Google recommends a separate URL for each language version, such as /es/, instead of switching language with cookies, browser settings or automatic redirects. Its multilingual guidance gives the reason: Googlebot usually crawls from the United States without an Accept-Language header, so a version that only appears for certain browsers may never be seen.
Four pieces make a Spanish page readable to Google and to your visitors:
- Its own URL: Spanish pages live at addresses such as /es/ so they can be crawled, linked and measured on their own.
- A language tag: Set html lang to es on each Spanish page. The W3C requires the language of a page to be programmatically determinable, which lets browsers and screen readers pronounce the text correctly.
- hreflang links: These connect each Spanish page to its English equivalent. Google's localized versions guide covers the annotations and the sitemap option.
- A visible language switcher: Let visitors choose, and avoid redirecting people by a guess about their language.
Each page should use one main language for its visible text. The same guidance lists subdirectories, subdomains and country-specific domains as options, so a separate Spanish domain is not required. A subfolder such as /es/ is often the simplest to keep up.
One limit matters here. Hreflang connects equivalent pages. It does not translate them, and it does not guarantee rankings or traffic. Our search engine optimization work covers the crawlable URLs, internal links and measurement that Spanish pages need.
How do you put your website in Spanish, step by step?
The question people type in Spanish is "¿cómo poner en español una página web?" The answer is to build real pages rather than add a button. If the ten-minute check shows demand, the order of work is short and repeatable.
- Pick the pages closest to a customer's decision as your first translations.
- Have a qualified native or highly fluent Spanish speaker write or review each page, including titles, descriptions and button labels.
- Publish each page at its own URL under /es/.
- Set the language tag to es and add hreflang links between each pair of pages.
- Add a clear language switcher on every page.
- Add Spanish pages to your sitemap, then check in Search Console that they appear.
- Track Spanish calls and forms so you can judge the result.
Spanish page titles and descriptions deserve the same care as the English ones. Our guide to writing page titles and meta descriptions applies in either language. Our web design team builds the page structure, the switcher and the language markup so you are not wiring them by hand.
Which pages come first, and who checks the Spanish?
Translate the pages closest to a customer's decision. A visitor who reads your Spanish service page and then lands on an English contact form has been stopped at the last step. This order follows the path from reading to contacting.
| Order | Pages | Why |
|---|---|---|
| 1 | Main service pages that bring calls or forms | They start the decision |
| 2 | Contact, booking, quote, location, hours, payment and policy pages | They finish it |
| 3 | FAQs that answer buying objections | They remove doubt |
| 4 | Business Profile description and service details, where Spanish support is real | They match what people see on Google |
Google's help for your Business Profile covers how to edit your description and service details. Only add Spanish there if you can answer in Spanish.
The first reviewer should be a qualified native or highly fluent Spanish speaker who knows your business, your industry's terms and your customers. Ask the reviewer to check meaning, tone, regional vocabulary, legal wording, calls to action, phone numbers, forms and page titles. Do not publish machine output without that review. Your homepage and the experience and trust signals on it are the English pages to match in Spanish.
What makes a Spanish version of a website fail?
These failures are a practical triage list, ordered by how much damage they do to a customer's path, not by a measured ranking. Each one is fixable, and several have nothing to do with the website itself.
- Unreviewed machine translation: Service or legal wording published without a fluent reader. Fix it with human review of every page.
- A half-translated path: The homepage is Spanish, but contact, booking or pricing stays in English. Translate the whole path from first page to form.
- Missing technical signals: Pages without stable URLs, language tags, internal links or hreflang. A small job on a simple site, larger on a custom setup.
- No one to answer in Spanish: Spanish copy with nobody ready for the call or message. That is an operations job: assign a person or provider and set response hours.
- Stale pages: Hours, prices or policies change in English only. Add the Spanish page to your update routine.
- No measurement: Traffic counted but not Spanish calls, forms, appointments or sales. Add a lead-source field and track the events.
Upkeep is the quiet cost. A small, accurate Spanish section serves visitors better than a large one the business cannot maintain, and two versions of a site mean two sets of updates.
Is your Spanish plan ready?
Pick an answer to begin.
1. A translation widget is installed on your English pages. What does that give you?
2. What does hreflang do?
3. Census ACS data shows many Spanish speakers in your service area. What does that tell you?
Frequently Asked Questions About a Spanish Version of Your Website
Do I need a Spanish website if some customers speak Spanish?
Not automatically. Check your customer inquiries, Search Console queries and the ACS language data for your service area. If the evidence supports it, start with the pages that bring calls and forms.
How do I put my website in Spanish?
Build real Spanish pages at their own URLs, such as /es/, reviewed by a fluent speaker. Set the language tag to es, link each page to its English twin with hreflang, and add a language switcher.
Is a translation widget enough?
A widget can help a visitor read an English page for a while. It does not give you stable Spanish URLs, Spanish page titles or pages Google can index as Spanish, and Google's Website Translator widget was announced to end support on October 1, 2026.
Do I need hreflang for Spanish?
Google recommends hreflang when you have separate language versions. It helps Google connect equivalent pages. It does not translate them or guarantee rankings.
Should I translate every page?
No. Start with service, contact, booking, policy and FAQ pages, then expand based on use and on how much upkeep you can handle.
Who should review the Spanish?
A qualified native or highly fluent Spanish speaker who understands your business, your industry and your customers.
The Bottom Line
Add Spanish when your calls, your Search Console data or your service area give you a reason, and say "not yet" when they do not. If the evidence is there, build real Spanish pages on their own URLs, with a language tag, hreflang links and a switcher. Start with the pages that bring calls and forms, and have a fluent reader check every one. A translate button can help someone read a page, but it does not take the place of those pages.
A small set of reviewed pages, with Spanish calls and forms counted, tells you whether to grow the project. You spend on what the data supports and you stop paying for pages nobody uses.
If you want help turning your numbers into a plan, Web Leveling can sort out which pages to build first and what the switch should look like. Our web design team builds Spanish pages with the right URLs and language markup, and if the numbers say not yet, we will tell you that. We work with small and medium businesses across the country and overseas. Send us your Spanish call and search numbers, and we will help you decide.
Terms
Words used in this post
Tap a term to see what it means.
hreflang. A tag that tells Google which page is the Spanish or English twin of another page.
Language tag. The lang setting in a page's code that declares its language, such as es for Spanish.
Translation widget. A button or plugin that changes the visible text on a page without creating new pages.
ACS. The Census Bureau's American Community Survey, which reports language spoken at home by area.
Search Console. Google's free tool that shows the searches and pages that bring people to your site.
Language switcher. A visible link or menu that lets a visitor move between English and Spanish pages.
