Hreflang is the single most error-prone part of multilingual SEO. A wrong locale code, a missing return tag, a broken x-default — Google drops the alternate URLs from SERPs and your multilingual investment evaporates. Cogo Site generates every tag correctly, on every page, automatically.
What hreflang actually does (and why it breaks)
Hreflang is a hint attribute that tells search engines which locale and language version of a page to show in which region's results. Get it right and your English page shows on google.com, your Chinese version on google.com.hk, your Spanish version on google.com.mx — without duplicate-content cannibalization.
Get it wrong and the worst happens silently. Google ignores the alternate URLs entirely. Your Chinese page shows up on US searchers' queries and gets bounced. Your English page ranks in Hong Kong and tanks engagement. You see traffic fall but cannot trace why.
The most common breakage is incomplete bi-directional tags. If page A declares page B as its Chinese alternate, page B must declare page A as its English alternate. Miss one direction and Google ignores both. Other common mistakes: wrong locale codes (zh-tw vs zh-TW, fil-PH vs tl-PH), missing x-default, hreflang on canonicalized pages, and hreflang URLs that don't match canonical URLs exactly.
How Cogo Site handles hreflang for you
Every page Cogo Site publishes includes correct hreflang tags by construction. The locale is part of the URL (/zh-CN/, /es/, etc.), the canonical is locale-specific, the x-default points to the original locale, and every alternate declares every other alternate in both directions. You don't write the tags; you don't maintain them when content changes.
When you publish a new locale, all locales' hreflang tags regenerate to include it. When you unpublish a locale, the tags regenerate to remove it. There is no plugin to update, no sitemap to rebuild, no Search Console coverage report to chase.
Common hreflang mistakes Cogo Site prevents
Mistake 1 — Wrong locale code casing. Hreflang is case-sensitive (zh-CN, not zh-cn). Cogo Site uses ISO 3166-1 alpha-2 uppercase region subtags by spec.
Mistake 2 — Missing return tags. If /zh-CN/pricing links to /pricing as its EN alternate, /pricing must link back to /zh-CN/pricing as its ZH alternate. Cogo Site generates both directions atomically.
Mistake 3 — Missing or wrong x-default. The x-default tells Google which version to show when no locale matches the searcher. Cogo Site sets x-default to the original locale (usually English) by default.
Mistake 4 — Hreflang URLs that don't match canonical URLs. Google requires the hreflang URL to match the page's canonical URL exactly. Cogo Site derives both from the same source-of-truth route, so they cannot drift.
Mistake 5 — Hreflang on noindex pages. Pages blocked from indexing should not declare hreflang. Cogo Site omits hreflang automatically on noindex routes.
When you still need to think about hreflang
Cogo Site handles the mechanical parts. You still own the strategic parts: which locales to publish, which locale is the canonical source, whether to translate a page or keep it locale-specific. For most sites, the answer is publish the same pages in every locale. For some sites (commerce with locale-specific SKUs, legal pages with jurisdiction-only validity), the answer is selective translation.
For selective translation, Cogo Site's per-page locale visibility lets you mark a page as English-only or Chinese-only — hreflang will only declare alternates where the page exists in both locales. This keeps you from promising Google a Chinese version that does not exist.
What Cogo Site handles for you
Every page generates hreflang link tags for every published locale
Locale codes use correct ISO 3166-1 alpha-2 casing (zh-CN, es-MX, fil-PH)
Bi-directional return tags — no orphans, no asymmetry
x-default points to the original locale by default (configurable per site)
Hreflang URLs always match canonical URLs (same source-of-truth)
Adding or removing a locale regenerates all pages' hreflang atomically
Noindex pages automatically omit hreflang to avoid conflicting signals
Self-canonical, canonical to original, and canonical to localized are all supported
Frequently asked questions
What is hreflang and why does it matter for a multilingual website?
Hreflang is an HTML link attribute that tells search engines which language and region version of a page to show in which searchers' results. Without hreflang, Google may show the wrong locale to the wrong searcher (e.g., your Chinese page to a US searcher) — causing bounces and lost rankings. With correct hreflang, each locale version gets a fair shot at ranking for its target audience.
Does Cogo Site generate hreflang tags automatically?
Yes — every page Cogo Site publishes includes hreflang link tags for every published locale, with bi-directional return tags, x-default pointing to the original locale, and URLs that match canonical exactly. You don't write or maintain the tags; adding or removing a locale regenerates all pages' hreflang atomically. This is the core value of a hreflang-aware website builder.
What happens if I get hreflang wrong?
Google ignores incorrect hreflang. Symptoms are subtle: traffic to your alternate-locale pages falls without an obvious ranking drop, Search Console shows fewer indexed alternates, and engagement metrics (CTR, dwell time) on locale-specific landing pages decline. The most common mistakes are wrong locale code casing (zh-cn instead of zh-CN), missing return tags, missing x-default, and hreflang URLs that don't match canonical URLs. Cogo Site prevents all of these by generating tags from a single source of truth.
Can I set a specific locale as x-default?
Yes. By default Cogo Site sets x-default to the original locale (usually English, the first locale you published in). You can change the x-default locale per site in site settings. This is useful if your business is primarily non-English (e.g., a Chinese-first business that publishes an English version for international visitors) — you want searchers with no locale match to see the Chinese version, not the English.
Does hreflang work for region-specific locales like es-MX or zh-TW?
Yes. Cogo Site supports region-specific locale codes following the ISO 3166-1 alpha-2 standard — es-MX (Spanish Mexico), zh-TW (Chinese Traditional Taiwan), zh-HK, fr-CA, en-GB, etc. Region-specific locales help Google route searchers to the right version (Mexico Spanish vs Spain Spanish have different vocabulary, currency, and legal references). For most sites, language-only codes (es, fr, zh) are sufficient; region-specific codes are an upgrade when you have meaningfully different content per region.
We use cookies to enhance your browsing experience and analyze site traffic. By clicking 'Accept', you consent to our use of cookies. Learn more about our cookie policy
