How to Fix Hreflang Errors on an English-Spanish Business Website

Website layout sketches and a tablet arranged on a desk with teal and orange design swatches
Language: English | Español

To fix hreflang errors on an English-Spanish business website, give every translated page its own indexable URL, connect each language pair with reciprocal hreflang annotations, and use a self-referencing canonical on each page. Then verify that both URLs return a successful response, contain genuinely localized content and remain accessible without automatic language redirects.

Hreflang does not improve rankings by itself. It helps Google understand which localized version may be more appropriate for a searcher. Google’s localized-page documentation permits HTML, HTTP-header or sitemap implementations. Choose one method that your team can maintain consistently.

Diagnose the problem before changing WordPress

SymptomLikely issueWhat to inspect
English URL appears for Spanish queriesMissing, incorrect or incomplete hreflang clusterSource code on both pages
Spanish page is excluded from indexingWrong canonical, noindex directive or redirectCanonical, robots directives and HTTP status
Only one side references the otherNo return annotationBoth members of the page pair
Language changes without changing the URLCookie or browser-language deliveryURL structure and redirect rules
Spanish page contains mostly English textIncomplete localizationMain content, navigation, forms and metadata

Implementation sequence

1. Create a stable URL for each language

Use separate crawlable URLs, such as /services/example/ and /es/servicios/ejemplo/. Google recommends distinct URLs instead of relying only on cookies or browser settings. Keep a visible language switcher so visitors can choose their preferred version.

2. Localize the complete page

Translate and adapt the title, main copy, headings, calls to action, form labels, confirmation messages and relevant navigation. Spanish search intent may require different terminology or examples; replacing words mechanically is not enough. The business name, services, pricing and contact details must remain factually consistent.

3. Add reciprocal hreflang annotations

For pages aimed at English- and Spanish-speaking audiences in the United States, a basic HTML-head implementation can look like this on both versions:

<link rel="alternate" hreflang="en-US" href="https://example.com/service/" />
<link rel="alternate" hreflang="es-US" href="https://example.com/es/servicio/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/service/" />

Each page must reference itself and its counterpart. Use fully qualified HTTPS URLs. The optional x-default entry identifies a general fallback page.

4. Correct the canonical tags

The English page should normally canonicalize to itself, and the fully translated Spanish page should canonicalize to itself. Do not point every Spanish page to its English counterpart; that creates conflicting localization and canonical signals.

5. Set the document language

Use <html lang="en-US"> on English pages and <html lang="es-US"> on U.S. Spanish pages when those tags accurately describe the content. The W3C language guidance explains that the HTML language attribute supports content processing and accessibility, but it does not replace hreflang.

6. Remove crawl and redirect conflicts

  • Confirm that both URLs return HTTP 200 responses.
  • Remove unintended noindex directives.
  • Do not block either language directory in robots.txt.
  • Avoid forcing users or crawlers to another language solely from their browser setting.
  • Include indexable language URLs in the appropriate XML sitemap.

Common mistakes

  • Using es-US on one page and es inconsistently elsewhere.
  • Generating hreflang for untranslated or nonexistent URLs.
  • Leaving old staging domains, HTTP URLs or redirected URLs in annotations.
  • Adding tags through multiple plugins, creating duplicate or conflicting clusters.
  • Translating the header and footer while leaving the main page in English.

What to verify after publishing

  1. View the rendered source of both URLs and confirm an identical hreflang cluster.
  2. Check that every alternate URL loads directly and uses the expected canonical.
  3. Inspect both pages in Google Search Console for indexability and Google-selected canonicals.
  4. Test the language switcher, forms, telephone links and conversion tracking.
  5. Recheck after template, translation-plugin or sitemap updates.

Corrections may require recrawling, and hreflang remains a signal rather than a command. Google can still select another URL based on its indexing systems.

To request a bilingual website review, send your English and Spanish page URLs to CyberTek Group. Include the affected pages and the language-selection problem you want reviewed.

If your bilingual WordPress site produces conflicting language or canonical signals, CyberTek Group can review its architecture through our web design and development services. You can also explore additional implementation checklists in our business resource center.

Related ArticlesArtículos relacionados