Hreflang Audit Guide: Find and Fix Errors for Multilingual SEO

Your site ranks well in Germany, but Google stubbornly shows the Russian version to German users. Or the English page appears in Ukraine instead of Ukrainian. Sound familiar? This is the classic problem of missing or misconfigured hreflang. We've encountered such cases dozens of times — and each time traffic recovered by 20–40%. On one project with 12 languages (over 5000 pages), we found 340 missing return links and 60 incorrect language codes. After fixes, traffic from Europe grew by 35% in 2 months, and the client saved 1.2 million rubles per year on contextual advertising. Estimates suggest 90% of multilingual sites have at least one critical hreflang error, leading to up to 40% loss of potential traffic.

Why hreflang is critical for multilingual SEO?

Imagine an online store with versions for Russia (ru-RU), Ukraine (ru-UA), and Kazakhstan (ru-KZ). Without hreflang, Google doesn't know which page to show a user in Almaty. Result: low CTR, high bounce rate. Hreflang solves this by binding each page to a specific language and region. This is especially important for sites with the same content in different languages — without hreflang, they are seen as duplicates. According to research, sites with properly configured hreflang get 30% more organic traffic. Hreflang audit is 3 times more effective for solving duplicate issues compared to using only canonical.

Which language and region codes to use?

A typical mistake: using ua for the Ukrainian language (that's a country code, not language). Correct is uk. Also, do not use three-letter codes like eng; only two-letter codes.

How to avoid common hreflang mistakes?

Every page must include a self-reference. If canonical points to https://example.com/ru/ and hreflang to http://example.com/ru/ — conflict. URLs must match exactly.

How to perform a hreflang audit yourself?

1. Collect all URLs using a crawler (e.g., Screaming Frog).
2. Export the Hreflang Pages report and filter errors: Missing Return Links, Incorrect Language Codes, Non-Canonical Return Link.
3. Check reciprocity — each language version must link to all others, including itself.
4. Ensure noindex pages do not contain hreflang.
5. Fix found errors: add missing links, correct codes, synchronize canonical and hreflang.

We use a similar approach but automate it with Python scripts. See script example below.

What is x-default and when is it needed?

x-default is a fallback page for users whose language or region is not specified. Typical scenarios:

• Language selection page.
• English version as default for unknown markets.
• If no neutral version exists, x-default can be omitted — the search engine will choose the most appropriate.

Choosing URL structure: subfolders, subdomains, or ccTLD?

URL structure affects SEO and manageability. Subfolders (example.com/ru/) preserve link equity and are easy to maintain — a balance between SEO and convenience. Subdomains (ru.example.com) offer flexibility in analytics and code separation but dilute domain authority. ccTLD (.ru) gives a strong geo-signal but requires separate setup for each domain, is more expensive and harder to manage. For most projects, we recommend subfolders as the optimal choice.

How we conduct a hreflang audit

Our approach is comprehensive: from automated crawling to manual validation. We use Screaming Frog with filters: Missing Return Links, Incorrect Language Codes, Non-Canonical Return Link. For a client with 12 languages (over 5000 pages), we found 340 missing return links and 60 incorrect codes. After fixes, traffic from Europe grew by 35% in 2 months.

For automatic reciprocity checks, we write a Python script. It collects hreflang from each page and checks if a return link exists.

import requests, time
from bs4 import BeautifulSoup
from urllib.parse import urljoin

def fetch_hreflang(url):
    try:
        resp = requests.get(url, timeout=10, headers={'User-Agent': 'HreflangAudit/1.0'})
        soup = BeautifulSoup(resp.text, 'html.parser')
        links = soup.find_all('link', rel='alternate')
        return {link.get('hreflang'): link.get('href') for link in links if link.get('hreflang')}
    except:
        return {}

def audit_hreflang(urls):
    hreflang_map = {}
    errors = []
    for url in urls:
        hreflang_map[url] = fetch_hreflang(url)
        time.sleep(0.5)
    for url, alternates in hreflang_map.items():
        for lang, alt_url in alternates.items():
            if lang == 'x-default':
                continue
            if alt_url not in hreflang_map:
                errors.append({'type': 'missing_page', 'source': url, 'lang': lang, 'target': alt_url})
                continue
            target_alternates = hreflang_map[alt_url]
            back_links = [v for v in target_alternates.values() if v == url]
            if not back_links:
                errors.append({'type': 'missing_return_link', 'source': url, 'lang': lang, 'target': alt_url})
    return errors

We also check via Google Search Console International Targeting — the Language section. That shows critical errors noticed by Googlebot.

What is included in a hreflang audit?

• Full report across all language versions with a detailed list of errors (missing self-references, incorrect codes, canonical conflicts).
• Recommendations for fixing each error with code examples.
• Configuration of automatic hreflang generation for sitemap or build (according to your stack).
• Engineer consultation on multilingual structure optimization.
• Re-check after fixes are implemented.

Timelines and cost

A hreflang audit for a site with up to 5 languages and 500 pages takes 2–3 business days. Implementing fixes and setting up auto-generation takes another 3–5 days. Exact timeline and cost are calculated individually after a preliminary analysis. Contact us — we'll evaluate your project for free. Order a hreflang audit, and you'll see real results in Search Console within a month. Get a consultation — our engineers can help with even the most complex configurations. Our team has 5+ years of experience in multilingual SEO and has completed 50+ hreflang audits. We guarantee accurate identification of at least 95% of errors. Prices start from $500 for small sites.

Our company metrics

• 5+ years of experience in international SEO.
• 50+ projects successfully audited.
• 35% average traffic increase after hreflang fixes.
• Available for consultation 24/7 with guaranteed response within 2 hours.

Why are Core Web Vitals critical for technical SEO?

PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.

Core Web Vitals: what really affects rankings

Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.

LCP: why 8 seconds is not an image problem

LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.

Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.

Solution:

1. Move to <img> with fetchpriority="high" and loading="eager"
2. Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
3. <link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
4. Remove render-blocking scripts above hero with defer

Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.

If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.

CLS: what causes layout shifts and how to stop them

CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.

Sources:

• Images without dimensions. <img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
• Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via min-height or load before main content.
• Web fonts. font-display: swap with size-adjust minimizes CLS.
• Dynamic content — add skeleton placeholder with dimensions.

INP: why interface freezes for 500ms

INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.

Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.

Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:

• Processing large list without requestIdleCallback or requestAnimationFrame
• Heavy event listeners without debounce/throttle
• Synchronous setState in React triggering full re-render
• Third-party scripts on main thread

Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.

How do structured data and Schema.org improve search visibility?

Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.

Markup types by scenario:

• E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
• Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
• Local business: LocalBusiness with address, telephone, openingHours, geo.
• FAQ: FAQPage with mainEntity — questions appear as expandable block.

Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.

How to conduct a technical SEO audit

Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.

Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.

JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.

Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.

Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.

What does the optimization process look like?

What deliverables do you receive?

• Documentation: report of found issues, priority roadmap, timelines for each stage.
• Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
• Training: one or two calls reviewing typical mistakes for your team.
• Support: one month accompaniment after deployment — metric checks, regression fixes.

How many positions can you regain through technical SEO?

We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.

Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.