Pre-Launch Checks for an English Website: Hreflang and Canonical URLs
Tuohai editorial guide · Reviewed and published October 5, 2026. The worksheets are blank working templates, not client results.
An English website that loads and has a language switcher has not necessarily passed multilingual launch QA. The switch may lead to the wrong page, the English canonical may point to Chinese, or the versions may lack reciprocal annotations.
Start with page relationships, then check hreflang and canonical URLs. Hreflang describes language or regional variants; canonical expresses a preferred representative URL. Installing a multilingual plugin does not replace page-level checks.
Map the pages before checking tags
Create a mapping of each Chinese product or guide to its corresponding English page. They should cover the same main object and task, not merely use different languages.
If a Chinese model page links to an English product directory, the language switch loses the specific object. Mapping every inner page to the English homepage is not completed translation pairing. Mark missing translations as unavailable rather than creating a false relationship.
An English-only site with no alternative language or regional versions does not need an invented hreflang group. With partial translation, connect only existing corresponding pages. Regional versions should serve real user tasks and have a maintenance plan, not exist merely as near-duplicate country-keyword pages.
Confirm targeting before selecting codes. Generic English may use en; genuinely targeted US or UK versions may use en-US or en-GB. The language code uk does not mean English for the UK. Select appropriate Chinese language, script, or region codes where needed.
Google's localized-version guidance explains that hreflang identifies localized variants, but neither hreflang nor HTML lang is used by Google to detect page language. An English tag does not make mostly Chinese content a completed English page.
Record final public URLs, not preview hosts, old paths, or temporary parameter addresses. Keep HTTPS, host choice, and trailing-slash conventions consistent with the selected canonical version.
Check version relationships and canonical preference separately
Verify self-reference, reciprocal links, and fully qualified URLs. The English page should list itself and its Chinese counterpart; the Chinese page should return the same relationship. A one-way annotation is not a pass. Google requires complete alternate URLs, not relative paths.
This fictional example represents two language versions of one product. It is not production configuration. Both pages contain the same alternate annotations, while each canonical points to its own language version.
<!-- Chinese page -->
<link rel="canonical" href="https://example.com/zh/part/">
<link rel="alternate" hreflang="zh" href="https://example.com/zh/part/">
<link rel="alternate" hreflang="en" href="https://example.com/en/part/">
<!-- English page -->
<link rel="canonical" href="https://example.com/en/part/">
<link rel="alternate" hreflang="zh" href="https://example.com/zh/part/">
<link rel="alternate" hreflang="en" href="https://example.com/en/part/">
If English content is intended for independent search visibility, pointing every canonical to Chinese sends conflicting signals. Google's canonical guide recommends a same-language canonical when using hreflang, or the best substitute when none exists. Check complete Chinese and English pages individually rather than merging languages through a sitewide template.
For near-duplicate URLs in the same language, resolve canonical preference before designing regional relationships. Canonical is a signal, not an instruction Google must follow. A declared URL is not proof of Google's selected canonical.
Use x-default for a genuine fallback when language or region does not match, commonly a language selector. It is not mandatory for every English site and does not replace specific language relationships.
Inspect live output, sitemaps, and internal links
Do not stop at the configuration screen. Inspect returned pages. With HTML implementation, annotations belong in a valid head. Check response headers too, especially for a canonical that contradicts HTML. Review duplicate plugin output for inconsistencies.
Google supports HTML, HTTP headers, and sitemaps as equivalent hreflang methods. Choose the method the team can maintain. Adding all three does not strengthen search performance; existing multiple implementations need consistency checks.
Check that target URLs work. A 404, redirect chain, login page, or non-indexable preview is not a normal public target. For pages intended to be publicly indexed, check status, final URL, robots rules, and noindex separately. Record intentional exclusions without forcing access open.
Navigation, language switches, and sitemaps should use the confirmed canonical URLs. A new canonical with old navigation links creates avoidable inconsistency. Test important templates and individual pages; a tidy mapping sheet does not prove the whole site is correct.
You can test code and mapping in preview without removing preview protection. After launch, separately verify production responses, declarations, and search state. Configuration accepted, deployed, Google-selected canonical, and indexed are different states. A request for inspection is not indexing completion.
Original English-launch worksheet
This is a blank page-level checklist. Retain the URL, timestamp, and evidence for each result; template acceptance does not establish every page passed.
| Check | Acceptance condition | Page result |
|---|---|---|
| Page correspondence | Same main object and task | Pending |
| Language and region | Code matches content and actual targeting | Pending |
| Self-reference | Page lists its own version | Pending |
| Reciprocal annotation | Counterpart returns the relationship | Pending |
| Full URL | Confirmed final absolute address | Pending |
| Canonical | Clear same-language preference, no conflict | Pending |
| Actual response | Available target, not error or preview | Pending |
| Output consistency | HTML, headers, and sitemap agree | Pending |
| Links and switching | Navigation uses correct addresses | Pending |
| Environment and later state | Preview protection retained; indexing checked separately | Pending |
Send missing counterpart content to the content owner and redirects or conflicting declarations to development. Do not pair unrelated topics just to make the checklist pass.
FAQ
Does an English-only site need Chinese hreflang?
No. Declare a relationship when the corresponding version exists. Empty tags and invented URLs do not replace translation.
Should both languages canonicalize to Chinese?
Not by default. Check same-language canonicals for complete English content intended for independent visibility. Similar regional variants require separate assessment.
Does a passed hreflang check guarantee indexing?
No. It verifies part of the configuration, not crawling, Google's acceptance, indexing, or ranking.
Conclusion
Confirm page pairs, reciprocal annotations, self-reference, and same-language canonicals. Then inspect responses, sitemaps, and links. Resolve missing pages and conflicts before recording production state. The website audit entry (Chinese) supports scope discussion, not an indexing guarantee.
Official sources
Sources checked on October 5, 2026. The sample domain does not represent a deployed website.