GarantLead
A URL for each version
If the same URL changes language according to the browser, a search engine may not discover every translation. On our initial websites, Spanish and English depended on a later JavaScript change. The replacement structure uses /cs/, /es/ and /en/, with the correct text already in HTML. Each page can be opened and shared directly.
Canonical and hreflang have different jobs
A canonical URL identifies the preferred version among duplicate pages. hreflang connects language versions. A Spanish translation should not automatically canonicalise to Czech: the pages serve different audiences. Language references should be reciprocal and include the current page. Czech uses cs, not the country code cz.
Translate the intent and review the details
Word substitution is not enough. A Spanish business owner may search “diseño web para autónomos”; a Czech owner, “tvorba webu pro řemeslníky”; an English speaker, “websites for tradespeople”. These are wording examples, not search-volume data. Review titles, descriptions, alternative text, form errors and receipts as well. Prices and terms should still describe the same offer.
A check before publishing
Open each version without relying on browser-language changes. Check that the selector leads to the equivalent translated content and no page returns an error. Review internal links, metadata and sitemap inclusion. After publishing, use Search Console, when available, to observe which versions Google discovers and indexes. Correct structure supports the process but does not guarantee indexing or rankings.