International SEO and Hreflang: How to Serve the Right Language to the Right Searcher, Starting With Spanish in Texas

Language or country: settle which problem you have before touching code

Google splits the subject in two. A multilingual site offers content in more than one language. A multi-regional site targets users in different countries. Some sites are both. The distinction decides almost everything that follows, and most small businesses guess wrong about which one they are.

A plumbing company in El Paso with English and Spanish pages serves one country in two languages. That is a multilingual site, and it needs no country domains at all. A store in Houston that ships to Mexico, prices in pesos and quotes Mexican delivery times is multi-regional, because the offer itself changes at the border. The first needs good translation and clean annotations. The second needs separate versions of prices, policies and stock.

The market is not small. The Census Bureau's 2017 to 2021 language tables found that 22% of Americans age 5 and older spoke a language other than English at home, and about 61% of them spoke Spanish. Our San Antonio AI search page has the local figures for one Texas city.

ccTLD, subdomain or subfolder: Google's trade-offs side by side

Google's guide to managing multi-regional and multilingual sites lays out four ways to give each version its own address. It does not crown a winner. It lists costs, and the costs are what a business should weigh.

For a US business adding Spanish, a subfolder is our default, and it is a practice, not a Google rule. One domain means one Search Console property, one set of links and reviews pointing at it, and one site to maintain. A ccTLD earns its cost only when a business truly operates in another country. Google also treats some vanity country endings, such as .tv and .me, as ordinary generic domains, so a clever domain does not make you local anywhere.

Changing structure later is a site move with every redirect that implies. If you are already on subdomains and want subfolders, plan it like a migration, with the old-to-new map our redirects guide describes, or have our website migration team build and test it.

How Google works out who a page is for, and what it ignores

Owners often assume a setting somewhere tells Google their target country. It used to exist. Search Console's International Targeting report is deprecated, and Google says country targeting was judged to have little value and is no longer supported. It keeps supporting hreflang. Everything else Google reads from the site and the web around it.

Google decides a page's language from its visible text. That has a blunt consequence: a page with Spanish navigation wrapped around English paragraphs is an English page. Keep the lang attribute correct anyway, because screen readers use it to choose pronunciation, which is an accessibility job our ADA compliance work checks.

The crawler detail matters most for sites that guess a visitor's language. Google's page on locale-adaptive pages says Googlebot's default IP addresses appear to be in the USA and that it sends requests without an Accept-Language header. A site that silently swaps languages by browser setting may show Google only the English version, forever.

Hreflang, line by line, with examples that validate

Hreflang tells Google that several URLs are versions of the same page for different languages or regions, so it can show the right one. Google's localized versions documentation, updated September 2026, accepts three equivalent methods: link elements in the head, an HTTP Link header (useful for PDFs), or entries in the XML sitemap. Pick one. Google says using all three gives no extra benefit.

For a home page in English and Spanish, both pages carry the same three lines in their head: <link rel="alternate" hreflang="en" href="https://example.com/" />, then <link rel="alternate" hreflang="es" href="https://example.com/es/" />, then <link rel="alternate" hreflang="x-default" href="https://example.com/" />. The x-default line names the fallback for searchers whose language matches none of your versions.

• Every version lists every version, including itself. The set is identical on each page.
• Return links are mandatory. Google's words: if two pages don't both point to each other, the tags will be ignored.
• Use full URLs with https. A relative path such as /es/ is not accepted.
• Language comes first, as an ISO 639-1 code. A region is optional, as an ISO 3166-1 two-letter code: es-US, es-MX, en-GB.
• A region alone is invalid. Writing mx tells Google nothing, and be means Belarusian, not Belgium.
• Some popular codes do nothing. es-419, the code for Latin American Spanish, is not supported, and reserved codes such as UK and EU have no effect. Use en-GB, not en-UK.

Where the tags come from on common platforms

Hand-typed hreflang breaks the first time someone adds a page. Let the platform write it. Next.js generates the tags from the alternates.languages field in page metadata and can add them to a generated sitemap. Shopify says its automatic hreflang tags are on by default for every store and recommends subfolders for most. On WordPress, the multilingual plugins WPML and Polylang both say they write hreflang automatically. Whatever writes them, open the page source and count: two languages plus x-default should give three lines on each version.

Six ways hreflang quietly fails

Hreflang does not raise rankings. Google describes it as a way to point users to the most appropriate version of a page, and the documentation never calls it a ranking signal. When it breaks, nothing dramatic happens. The wrong version simply keeps showing up, which is why these mistakes survive for years.

Duplicate content worries are mostly misplaced here. Google says localized versions are only considered duplicates if the main content stays untranslated. A US page and a UK page in near-identical English are the exception: annotate them with hreflang and pick a preferred version as Google advises.

Translation gets you words; localization gets you customers

A translated page says the same thing in another language. A localized page says what a customer in that market needs to hear: the words people really search, prices in the right currency, a phone line someone answers in that language, forms that accept the names and addresses people have. Most bilingual sites stop at the first and wonder why the second never calls.

• Research the searches in the language itself. Translating your English keywords gives you dictionary Spanish, which may not be how people search for the service. Google Keyword Planner lets you set the language and location for ideas.
• Keep one language per page. Google warns against side-by-side translations and against translating only the menus while the content stays in one language.
• Edit machine translation with a fluent human. Google's spam policies list automated transformations such as translating among the techniques behind scaled content abuse. Your own pages, carefully edited, are not the target. Thousands of unedited pages could look like it.
• Translate the trust, not just the copy. Reviews, guarantees, licensing and the about page persuade in any language. A Spanish service page that links to English-only proof loses the reader at the moment of decision.
• Staff the promise. If the page says se habla español, the person who answers the phone must.

AI tools have made a first draft cheap, and our guide to AI for writing covers how to use them without embarrassment. Fluency is still the expensive part, and the part customers notice.

Spanish pages for a Texas business: the build, in order

Here is the sequence we would follow for a hypothetical HVAC company in San Antonio adding Spanish. It is practice built on Google's rules, sized for a site of a few dozen pages.

1. 1

   Choose the pages that sell

   Start with the home page, the main service pages, the contact page and the service area pages. A Spanish blog can wait. Ten complete pages beat a hundred half-translated ones.

2. 2

   Put them in a subfolder

   Mirror the English structure under /es/, with Spanish slugs if you like. Keep one Search Console property and watch the /es/ folder with a page filter.

3. 3

   Write and edit the copy in Spanish

   Translate from the English, then have a fluent speaker who knows the trade rewrite it for how local customers talk. Check every price, phone number and form label.

4. 4

   Add hreflang and canonicals

   Each pair gets en, es and x-default annotations, and each page names itself as canonical. Add both versions to the XML sitemap, as our XML sitemaps guide describes.

5. 5

   Add a visible language switch

   A link at the top of every page to the matching page in the other language, not to the other home page. No automatic redirects.

6. 6

   Check what Google stored

   Run a Spanish URL through URL Inspection in Google Search Console and confirm the selected canonical is the Spanish page itself, not its English twin.

Your Google Business Profile and listings matter as much as the site for local searches; the map pack guide covers them. Spanish questions to AI assistants are a related case, covered on our San Antonio GEO page and checkable with the free AI visibility check.

Measuring a second language, and when to hand it off

Give the new pages three months before judging them. In Search Console, filter Performance by pages containing /es/ and watch impressions first, clicks second. In GA4, record calls and forms from the Spanish pages as their own key events so the language that brings work is visible. Our SEO KPIs guide shows how to fold those numbers into a one-page monthly report.

Hreflang decides which version Google shows. Only the page decides whether anyone calls.

Most of this is within reach of an owner with a fluent colleague and a free afternoon a week, especially on a platform that writes the tags. Hire help when the site has hundreds of pages, when country versions with their own prices are involved, or when a restructure means redirects. The free site audit flags common technical faults, and the technical SEO checklist and the rest of the SEO guide cover the ground around this page.

On sites DataCram builds, the Athena CMS agent Harmonia drafts Spanish versions for a person to approve. On any site, Spanish pages can sit inside our SEO programs, which start at $625 a month, with most local businesses between $625 and $2,250, per the SEO pricing page.