Correct hreflang implementation helps search engines identify which language or regional version of a page to show. Each equivalent page should reference itself and its alternatives using valid language codes, absolute URLs and reciprocal annotations.
It does not translate content, replace canonical tags or guarantee rankings. Its job is to reduce mismatches, such as someone in the UK seeing your US pricing page, while keeping genuinely equivalent pages connected.
1. Decide which pages need language or regional targeting
Start with your audience and content, not a list of countries you hope to rank in. Hreflang is useful when you publish equivalent pages in different languages, or regional versions of the same language with meaningful differences.
For example, an Islamabad software business might maintain English and Urdu service pages. An international retailer might need separate English pages for the UK and UAE because delivery terms, availability and prices differ.
- Language targeting: use en for English and ur for Urdu, without limiting either language to one country.
- Regional targeting: use en-PK, en-GB, en-US or en-AE when the content specifically serves those markets.
- Multiple languages within one country: use en-PK and ur-PK when both versions specifically address customers in Pakistan.
A single English page serving customers worldwide usually does not need regional duplicates. Creating four identical versions with different country names adds maintenance work without necessarily improving search visibility.
Build a mapping sheet with one row per page family. Include its purpose, language, region, canonical URL and equivalent URLs. Match service pages to service pages and products to the same products, not to whichever translated page happens to exist.
2. Set stable URLs, codes and canonical rules
Subdirectories, subdomains and separate country domains can all support hreflang. For many small and medium-sized websites, subdirectories such as /en/, /ur/ and /en-gb/ are easier to maintain within one CMS. Your choice should reflect publishing workflows, infrastructure and market requirements.
Before adding annotations, establish these rules:
- Use supported codes. Language codes generally follow ISO 639-1, with optional ISO 3166-1 Alpha-2 country codes. English for the UK is en-GB, not en-UK. A country code alone is insufficient.
- Use complete URLs. Every annotation needs an absolute address, including HTTPS and the correct hostname.
- Keep targets accessible. Referenced pages should return HTTP 200, allow crawling and be indexable. Avoid redirects, error pages and noindex URLs.
- Align canonical signals. Distinct regional or translated pages intended for indexing should normally canonicalise to themselves, not all point to the English homepage.
- Choose one URL format. Keep trailing slashes, hostname preferences and letter case consistent with your canonical URLs.
Canonical tags identify a preferred URL among duplicate or near-duplicate pages. Hreflang identifies language and regional relationships. If every regional page canonicalises to one global URL, search engines may consolidate the pages you intended to serve separately.
If your CMS cannot manage these relationships reliably, review its template and localisation capabilities before launch. SEOISB’s web development service is listed at /services-web-development.
3. Build complete, reciprocal page groups
The central rule of hreflang implementation is reciprocity. If your UK service page references the equivalent UAE page, the UAE page must reference the UK page. Each page should also include itself in the group.
Consider a hypothetical website with these equivalents:
- en-GB: https://example.com/uk/web-development/
- en-AE: https://example.com/ae/web-development/
- en-PK: https://example.com/pk/web-development/
- x-default: https://example.com/choose-region/web-development/
All four pages should expose the same four-member group. The x-default address is an optional fallback for users whose language or region does not match a listed alternative. Here, it opens a service-specific region selector rather than dropping visitors onto an unrelated homepage.
Without a selector, x-default can point to an appropriate global version. It is not another language code, and adding it does not force search engines to display that page.
Do not invent equivalents for missing translations. If a product exists only in the UK catalogue, leave it outside any unavailable regional relationship. Linking it to the UAE category page gives search engines an inaccurate equivalence signal.
Avoid forced location redirects that prevent users or crawlers from accessing alternatives. Offer a visible language or region switcher and let visitors retain their choice.
4. Choose one delivery method and automate it
Search engines support hreflang through HTML head annotations, HTTP response headers and XML sitemaps. Choose the method your team can generate, inspect and maintain consistently. Using all three offers no inherent search advantage and creates more opportunities for conflicting data.
- HTML head annotations: suitable when your CMS can generate alternate link elements in each page’s head. Prefer server-rendered output rather than relying solely on browser-side JavaScript.
- HTTP headers: useful for non-HTML resources, such as translated PDF documents. The server supplies alternate URLs through Link response headers.
- XML sitemaps: useful for large catalogues with structured translation records. Each listed URL needs its complete alternative set, including itself, using the supported XHTML namespace.
Use a shared content identifier to connect equivalents. For example, one service record can hold separate English, Urdu and Arabic URLs. Generate annotations from those records rather than guessing relationships from matching slugs.
Make publication status part of the logic. A draft translation should not enter the group until its public URL is indexable. When editors unpublish or move a page, update the remaining members automatically.
Assign ownership too: developers maintain generation rules, editors confirm equivalent content, and the SEO team validates crawlability and search signals.
5. Test before launch and monitor changes
Validate hreflang implementation with a crawler that reports language annotations, response codes, indexability and canonical targets. A spreadsheet review alone cannot reliably detect template-wide errors.
Use this release checklist:
- Inspect at least one complete group from every major template, including products, services and articles.
- Confirm self-references, return links, valid codes and absolute URLs.
- Check that every target returns 200 and has no conflicting canonical or indexing directive.
- Test missing translations, renamed slugs and removed products.
- Verify that mobile and desktop visitors can reach every language version.
- Crawl the full production site after deployment and compare errors with the pre-launch baseline.
Use Google Search Console to inspect representative URLs and monitor performance by country and page. Look for the intended regional URLs receiving relevant impressions, but do not treat a single manual search as proof: location, device and personalisation can change results.
Allow time for recrawling rather than expecting an immediate switch. Include localisation checks in ongoing technical maintenance; SEOISB’s package options are available at /seo-packages.
Frequently asked questions
Does hreflang improve rankings directly?
It is not a ranking boost. It helps search engines select an appropriate alternative, while content quality, relevance, accessibility and other SEO factors remain important.
Can English and Urdu pages use different layouts?
Yes. Layouts can differ, including right-to-left presentation for Urdu. The pages should fulfil the same purpose, and their language annotations must remain reciprocal.
How often should hreflang be checked?
Check it after migrations, template changes and localisation releases. For actively updated sites, include a crawl in your regular monthly technical review.
Request a free SEO analysis from SEOISB, part of HA Technologies in Blue Area, Islamabad, at /request-a-free-seo-analysis to identify multilingual indexing and localisation issues.