A multilingual site needs more than a language switcher. Search engines should be able to identify which French, English and Spanish URLs represent the same content for different audiences.
Identify genuine equivalent pages
Only connect pages that answer essentially the same need. A French technical guide should not point its English hreflang to an unrelated service page. When a translation does not exist, do not invent an alternative URL or link to the homepage as though it were equivalent.
Give every language its own URL
Use distinct, stable addresses for the French, English and Spanish versions, such as language folders. Content, headings, metadata and internal navigation should match the selected language. Confirm that routes return real pages rather than silent fallback translations.
Build reciprocal language groups
Each equivalent should list the full set of language alternatives, including itself, with valid hreflang codes. References should be reciprocal. Check spelling, HTTP status and canonical destinations; one incorrect slug can break a group.
Coordinate hreflang with canonicals
A translated page generally needs a canonical pointing to its own language URL when it is an intended independent version. Canonicalising all translations to French can conflict with the purpose of offering language-specific pages. Review redirects and regional variants separately.
Prioritise translation quality
Duplicating French text under English and Spanish routes does not create meaningful translations. Localise titles, body content, calls to action, image alternatives and links. Technical terms should remain accurate, and the intended reader should be able to follow every instruction.
Check a complete language cluster
Open one article in all three languages, inspect the alternate links, validate canonical output and follow the language switcher. Check that links to related articles stay in the selected language whenever translations exist. Repeat after SQL imports.
Frequently asked questions
Can hreflang point to a page that has not been translated?
No. Only declare genuine, accessible equivalent pages.
Do translated pages need separate canonical URLs?
Normally yes, when each is intended to be indexed as a real language variant.
Related guides on Concepty
- Article and BlogPosting structured data: practical value and limitations
- Dynamic XML sitemap: how new database pages are discovered
- PrestaShop redesign and search visibility
For a specific implementation or compatibility question, explore Concepty services or contact Concepty.