Yes. Google recommends a different URL for each language version of a page, and it can't reliably find a Spanish version that only appears through a button, a cookie or the visitor's browser settings. Give each language its own address, link the pairs with hreflang, and keep each page in one language.
Does Google need a separate URL for each language?
It does, and Google says so in plain words. Its guide to managing multilingual sites reads: "Google recommends using different URLs for each language version of a page rather than using cookies or browser settings to adjust the content language on the page."
The reason is mechanical. The same guide explains that Googlebot usually crawls from the US, and that it "sends HTTP requests without setting Accept-Language in the request header." So a site that swaps to Spanish when it detects a Spanish browser shows Googlebot the English page, every time. The Spanish version never gets a chance to be indexed.
Picture a family law practice in Houston. Half its consultations happen in Spanish. Someone searches "abogado de divorcio en Houston" and the practice doesn't show up, even though its site has a Spanish toggle. To Google, that toggle opens nothing it can store.
Why doesn't a translate button count as a Spanish version?
Because most translate buttons don't create pages. They rewrite the page you're already on, in the visitor's browser, at the same address. There's nothing new for Google to crawl.
Google warns about this pattern directly: if you change content dynamically based on language settings, "Google might not find and crawl all your variations". The same page also asks you to avoid automatic redirects between language versions, because they "could prevent users (and search engines) from viewing all the versions of your site."
The second classic mistake is mixing languages on one page. A bilingual practice often ends up with an English paragraph followed by the Spanish one, stacked down the page. It feels inclusive. For Google it's a puzzle: it decides a page's language from what's visible, and it suggests "using a single language for content and navigation on each page, and by avoiding side-by-side translations."
One page, one language. Then link the two.
What is hreflang, and does it tell Google what language a page is in?
Hreflang is a small tag that tells Google which pages are translations of each other. It doesn't tell Google the language. Google's hreflang documentation is explicit: "Google doesn't use hreflang or the HTML lang attribute to detect the language of a page; instead, we use algorithms to determine the language."
Its multilingual guide says the same about code in general: "We don't use any code-level language information such as lang attributes, or the URL." That's why the visible text has to be really in Spanish. A tag can't fix a page that's half English.
What hreflang does is connect the pair, so a Spanish searcher lands on the Spanish page. Three rules cause most of the trouble:
- It has to go both ways. Google puts it bluntly: "If two pages don't both point to each other, the tags will be ignored." Each version also lists itself.
- The addresses must be complete. Google wants fully qualified URLs, with https, never a bare path like /es/.
- The codes must be real. The language comes first, in ISO 639-1. Google lists es-419, the code many people use for Latin American Spanish, among the ones it doesn't support. Plain es works, and so does es-US.
Then there's x-default, the fallback for visitors whose language you don't offer. Google says it "was designed for language selector pages and so it will work best with those." A two-language practice site can point it at the English homepage or at a page where people choose.
| Setup | What Google can see | Verdict |
|---|---|---|
| Spanish shown by browser language or cookie | Only the English page | Not indexable in Spanish |
| Translate widget at the same URL | Only the original page | Not indexable in Spanish |
| English and Spanish stacked on one page | One page in a mixed language | Confusing, avoid |
| Spanish pages at /es/ or es. subdomain, no hreflang | Both versions, unlinked | Works, but Google has to guess the pairing |
| Spanish pages at their own URLs, reciprocal hreflang | Both versions, paired | What Google recommends |
How often do real sites get hreflang wrong?
Often enough that I stopped assuming it's set up. In September we measured 343 professional service websites: therapy practices in the US, plus therapists, law firms, accountants, medical practices and small businesses in Spanish-speaking countries. Only 23 declared any hreflang on the pages we read.
Most of the rest are probably single-language sites, which don't need it. The interesting part is inside the 23. Nine of them listed fewer than two languages, so the tag couldn't pair anything. Two declared only x-default, and one used the value "1", which isn't a language code at all.
So even among the sites that tried, more than a third had a tag that does nothing.
How do you set this up on Squarespace or WordPress?
Squarespace. Its recommended path is the Weglot integration, in the Site Languages panel on version 7.1. The step that matters for search is the optional one: language subdomains, like es.yoursite.com. Squarespace's help says they "Automatically adds hreflang tags to make your site searchable in multiple languages." Without them, you get the language switcher but not the part that's built for search.
Watch the word count too. On Weglot's free plan, Squarespace says translations stop displaying above 2,000 words. When we measured our own site in October, it had about 50,200 words across 49 URLs, and a practice with a blog passes 2,000 fast.
You can also build it by hand, with a dropdown of pages per language. Squarespace's manual multilingual guide warns that this way "You can't have different domains or subdomains for different languages," and that some built-in text only displays in one language.
WordPress. A plugin like Polylang handles it. Its listing says the language "is either set by the language code in URL, or you can use a different sub-domain or domain per language." Either gives each translation its own address, which is the requirement.
On either platform, check the result yourself. Open your Spanish page, view the source (Ctrl+U), and search for hreflang. You should see the Spanish URL, the English URL and, ideally, x-default. The English page should list the same set, or Google ignores both.
If Google already shows the wrong version of a page, the problem may be the canonical tag, not hreflang. I covered how that works in indexed but not showing up on Google. And make sure your site answers at a single address first, as explained in www or non-www, so the pairs don't multiply.
Questions I get about this
Do my Spanish pages count as duplicate content?
No, as long as they're actually translated. Google's hreflang page says localized versions "are only considered duplicates if the main content of the page remains untranslated."
Will Google find my Spanish pages without hreflang?
It might. Google says it can still find alternate language versions on its own, but that it's usually best to point them out explicitly.
Should I translate the whole site or just the main pages?
Start with the pages people decide on: home, each service, fees, about and contact. A Spanish version of those, on their own URLs, does more than a machine translation of fifty blog posts. My guide to the pages a small business website needs is a good list to translate from.
Sources
- Google Search Central, Managing multi-regional and multilingual sites: https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites
- Google Search Central, Tell Google about localized versions of your page: https://developers.google.com/search/docs/specialty/international/localized-versions
- Squarespace Help, Creating a multilingual site with Weglot: https://support.squarespace.com/hc/en-us/articles/205809778-Creating-a-multilingual-site-with-Weglot
- Squarespace Help, Manually creating a multilingual site: https://support.squarespace.com/hc/en-us/articles/16552875658765-Manually-creating-a-multilingual-site
- WordPress.org, Polylang plugin listing: https://wordpress.org/plugins/polylang/
All pages were read on November 10, 2026. How we measured: the hreflang count comes from the homepage and up to three more pages of each of 343 sites, read with a script in September 2026; a site counts as declaring hreflang if any of those pages has the tag. If your practice runs in two languages and you want the setup checked page by page, that's part of the audit, or you can book a strategic fit call.

