A Step-by-Step Diagnostic Framework for Auditing Your Spanish Website's SEO

This diagnostic guide is written for two audiences: in-house marketing teams managing a bilingual or multilingual website, and business owners who launched a Spanish version of their site and haven't seen the traffic they expected.

Use this audit if any of the following apply:

• You added a Spanish version of your site in the last 12 months and organic traffic from Spanish-language queries is flat or declining.
• Your Google Search Console account shows impressions for Spanish queries but click-through rates are unusually low.
• You translated content from English to Spanish using a plugin or service, without significant editorial review.
• You're unsure whether your hreflang tags are implemented correctly — or whether they exist at all.
• You've noticed English pages ranking for Spanish-language queries, or vice versa.

This guide covers diagnostics, not fixes. For each problem area, we identify what to look for and what a healthy implementation looks like. Implementation guidance lives in our Spanish Website SEO Checklist.

One important note: the four diagnostic phases below are sequenced deliberately. Technical errors (hreflang and canonicals) should always be confirmed before you diagnose content or cannibalization issues, because a broken hreflang implementation can mask what looks like a content problem. Fix the foundation first, then re-evaluate everything else.

Hreflang is the HTML attribute that tells Google which version of a page is intended for which language and region. When it works correctly, Spanish speakers in Mexico see your es-MX page; Spanish speakers in Spain see your es-ES page; English speakers see your en or en-US page.

When it breaks, Google either ignores your implementation entirely or serves the wrong page to the wrong audience — both outcomes suppress rankings.

What to Check

• Missing return tags: Every hreflang implementation must be reciprocal. If your English page references your Spanish page, your Spanish page must reference your English page back. A missing return tag causes Google to discard the signal for that URL pair.
• Incorrect locale codes: The correct format is language-REGION (e.g., es-MX, es-ES, es-US). Common errors include es-mx (lowercase region), spanish (not a valid BCP 47 code), or using es when you intend to target a specific country.
• Self-referencing tags: Every page should include an hreflang tag pointing to itself. Missing self-references reduce implementation reliability.
• Inconsistent URLs: If your site uses trailing slashes inconsistently, hreflang tags using different URL formats for the same page will be treated as pointing to different resources.

How to Check

Use Screaming Frog (crawl → hreflang tab) or a dedicated hreflang validator to extract and cross-reference all hreflang declarations across your site. Export to a spreadsheet and look for any URL that appears as a reference target but doesn't have its own matching hreflang block. Those are your missing return tags.

In our experience working with bilingual sites, missing return tags are the single most common hreflang error — and they're often introduced when new pages are added without updating the corresponding language alternate.

Google Search Console includes an International Targeting report under the Legacy Tools section. This report has two tabs: Language and Country.

Language Tab

The Language tab confirms whether GSC has detected valid hreflang usage on your site. If your hreflang implementation is correct, you'll see a green checkmark. If you see errors, GSC will categorize them — common error types include "No return tag" and "Invalid language code." These errors correspond directly to what you should have found in Phase 1.

Country Tab

The Country tab is where many site owners make a consequential mistake. If you've set a country target (e.g., United States) at the domain or subdomain level in GSC, you're telling Google to prioritize that site for that country — even if the content is in Spanish.

This matters most for sites using subdomains or subdirectories for language separation:

• If es.example.com is verified as a separate property in GSC and has been set to target the United States, Spanish-language users in Mexico or Spain may not see it in their search results.
• If you're using a subdirectory structure (example.com/es/) and the root domain is targeted to the US, the subdirectory inherits that targeting — which may or may not align with your audience goals.

What Healthy Looks Like

For most bilingual US-based businesses serving both English and Spanish speakers domestically, the country target should either be set to United States for both properties or left unset, with hreflang handling regional differentiation. For businesses targeting Latin American markets or Spain specifically, the subdomain or subdirectory serving those audiences should either have its own GSC property with the appropriate country target, or rely entirely on hreflang.

Document the current state of every verified GSC property before making changes. Country targeting changes take effect quickly but can take several weeks to reflect in ranking data.

Translation at scale — whether machine-generated or outsourced at low cost — frequently produces content that Google evaluates as thin. The diagnostic question is not whether the content is in Spanish, but whether it provides meaningful, original value to a Spanish-speaking reader.

Signs of Thin Translated Content

• Word count below 300 on service or product pages: This alone isn't disqualifying, but pages under 300 words that are direct translations of longer English pages are flagged frequently in audits as under-optimized.
• Identical meta titles and descriptions, simply translated: If your Spanish meta tags are word-for-word translations of your English tags, you've missed an opportunity to optimize for Spanish query patterns, which often differ from literal translations.
• No Spanish-specific internal links: If your Spanish pages link back to English pages rather than to other Spanish pages, your internal link structure is fragmenting the crawl and sending mixed signals about the site's language architecture.
• Duplicate content across regional variants: If you have both es-MX and es-ES variants but the content is identical, Google may consolidate them — which can result in the wrong variant ranking in each market.

How to Diagnose

Crawl your Spanish URLs with Screaming Frog and export word counts. Cross-reference Spanish and English versions of equivalent pages using a similarity checker (Copyscape supports Spanish). For regional variants, compare the es-MX and es-ES versions of high-priority pages — if similarity is above 85-90%, consider whether the pages genuinely serve different audiences or whether consolidation is the more practical path.

Industry benchmarks suggest that pages with substantive, audience-specific content — not just translated text — tend to rank more consistently across Spanish-speaking markets. The degree of differentiation required varies by query type and competition level.

Cannibalization between Spanish and English versions of the same page happens when Google isn't confident which URL should rank for a given query — so it alternates between them, often ranking neither consistently.

How to Identify Cannibalization in GSC

In Google Search Console's Performance report, filter by query for a high-priority Spanish-language keyword (e.g., "abogado de inmigración en Miami"). Then look at which URLs are receiving impressions for that query. If you see both your Spanish URL and your English URL appearing in the same query report, you have a cannibalization signal worth investigating.

Repeat this process for your 10-20 highest-priority Spanish target queries. Export the results and flag any query where more than one URL is receiving impressions.

Common Causes

• Missing or broken hreflang: If Google can't determine the intended audience for each URL, it makes its own decision — which may not align with yours. This is why Phase 1 must come before this phase.
• Identical or near-identical page titles: If your English page title is "Immigration Lawyer in Miami" and your Spanish page title is "Immigration Lawyer in Miami — en Español," both pages are competing for English queries. Your Spanish page title should be "Abogado de Inmigración en Miami" — optimized for Spanish-language queries, not English ones.
• Canonicals pointing the wrong direction: If your Spanish page has a canonical tag pointing to the English equivalent, you've told Google the Spanish page is a duplicate — and it will be suppressed in favor of the English version.

When to Escalate

If you've corrected hreflang, set accurate canonicals, and optimized Spanish titles — and cannibalization is still present after 6-8 weeks — the issue is likely more systemic. At that point, a professional audit of your full URL architecture, crawl budget allocation, and internal linking structure is the appropriate next step.

This guide gives you the diagnostic framework. Whether you act on it yourself or bring in a specialist depends on a few concrete factors.

Handle It In-House If:

• Your site has fewer than 50 Spanish-language pages and a single language variant (e.g., only es-US or only es-MX, not both).
• You have access to Screaming Frog and a developer who can modify hreflang tags in your CMS or sitemap.
• The GSC International Targeting report shows no errors and your cannibalization check surfaces only 1-2 affected queries.

Request a Professional Audit If:

• You have multiple regional Spanish variants (e.g., es-MX, es-ES, es-US) and traffic is underperforming across all of them.
• You've made hreflang changes in the last 90 days and rankings haven't improved — this often indicates a deeper architectural issue that requires a full crawl and log file analysis.
• Your site uses a JavaScript framework (React, Vue, Next.js) where hreflang tags may not be rendering server-side — a crawl alone won't surface this.
• You have more than 200 Spanish-language URLs and no documented language architecture from when the Spanish version was built.

A professional audit typically surfaces issues that a self-audit misses — not because the methodology is different, but because pattern recognition across many multilingual sites changes what you look for and how you prioritize what you find.

If any of the escalation criteria above apply to your site, let our team audit your Spanish website before you invest further in content or link building on a broken foundation.