Bilingual Websites: Structure, Hreflang and Content

• Give each language its own pages, such as a Spanish folder.
• Hreflang tags tell search engines which pages are translations of each other.
• Each language version should point its canonical tag to itself.
• Let visitors choose their language instead of redirecting them automatically.
• Keep each page in one language, not side-by-side translations.
• Have fluent people review translations before publishing.

This guide covers structure, hreflang and canonical tags, language switchers, redirects, one language per page, translation quality, forms, content management and launch checks. Put plainly: give each language its own pages, tell search engines how they connect and have a fluent person review every page.

Separate pages for each language. Not one page that changes by cookie or browser setting.

Folders are simplest. For example, a Spanish folder alongside the English site.

Subdomains or separate domains. Work too, but are harder to manage.

Matching pages. Each English page has a Spanish match where it matters.

What they do. Tell search engines which pages are versions of each other in different languages.

Each page lists all versions. Including itself.

Return links. If the English page points to the Spanish page, the Spanish page must point back.

A default. An "x-default" version for visitors whose language isn't covered.

Where to put them. In the page code, server headers or the sitemap.

Each version points to itself. The Spanish page's canonical tag points to the Spanish page.

A common mistake. Pointing Spanish pages to the English version tells search engines to ignore them.

Easy to find. Usually at the top of every page.

Go to the matching page. Not back to the Spanish home page.

Name languages in their own language. "English" and "Español."

Don't redirect by guessed language. Browser settings and locations often guess wrong.

Search engines need access. Automatic redirects can stop them from seeing every version.

Suggest instead. A small banner offering the other language is fine.

Search engines read the visible text. Google decides a page's language from its content.

Avoid side-by-side translations. Mixed pages confuse visitors and search engines.

Translate everything visible. Menus, buttons, forms and image text.

Write natively. As covered in bilingual marketing beyond translation.

Review machine translation. Google's spam policies flag automatically translated pages published without human review.

Keep facts identical. Prices, hours, terms and claims match across languages.

Spanish as a channel. As covered in what changes when Spanish is a channel.

Translated menus and footers. Not English menus on Spanish pages.

Spanish forms and confirmations. As covered in Spanish landing pages.

Booking, chat and payments. In Spanish too, as covered in website integrations.

Event pages. Both languages where your audience needs them, as in event landing pages.

Stores selling abroad. The same care applies, as in selling to Latin America.

Link versions in your editing system. So editors see which pages match.

Update both. A price change in English means a change in Spanish.

Clear owners. Who writes and reviews each language, as covered in website content management.

Hreflang tags valid. Every page lists all versions and links back.

Canonical tags correct. Each version points to itself.

No automatic redirects. Search engines can reach every version.

Spanish pages in the sitemap. And reachable through links.

Moving or rebuilding later. As covered in moving hosts or domains.

Spanish pages in search results. For Spanish searches.

Traffic by language. And where it comes from.

Conversions by language. Forms, calls and bookings.

Wrong-language visits. Visitors switching right away.

Hreflang errors. In search tools.

Choose folders or another structure, map English pages to Spanish matches and decide who writes and reviews each language.

Build Spanish pages with native writing, add hreflang and self-canonical tags, translate menus, forms and tools and add a language switcher.

Run launch checks, fix hreflang errors and track Spanish search visibility and conversions by language.

Astra Results Marketing builds English and Spanish websites that search engines and visitors understand. We give each language its own pages, set hreflang and canonical tags correctly, avoid automatic redirects and have fluent writers create and review every page.

Engagements begin with a bilingual site review through our website development team.

Related reading

• Website Development: From Brief to Launch Day
• Bilingual Marketing Beyond Translation
• Spanish Landing Pages for Miami Campaigns

Give each language its own pages, such as a Spanish folder, rather than one page that changes by cookie or browser setting.

Tags that tell search engines which pages are translations of each other. Each page lists all versions, including itself, and every version links back.

To the Spanish page itself. Pointing it to the English version tells search engines to ignore the Spanish page.

No. Guesses are often wrong and can block search engines. Offer a clear language switcher or a small suggestion banner instead.

As a draft only. Google's spam policies flag automatically translated pages published without human review, so have fluent people review every page.

Check Spanish search visibility, traffic and conversions by language, and fix hreflang errors reported in search tools.

Ready for a bilingual website that works in both languages? Astra Results Marketing builds English and Spanish websites with separate pages, correct hreflang and canonical tags, clear language switchers and human-reviewed content. ▸ CALL (786) 321-2866 · ▸ REQUEST YOUR CONSULTATION