Build an equivalence map before adding tags
Start with one resource that genuinely has multiple language editions. Record the final URL and language of each edition in a small mapping table. Read the pages to confirm that they serve the same resource and task. A language homepage is not a substitute for a missing translation of a specific article.
Separate translation availability from intended future work. Include only editions that exist and can be checked. Keep each resource’s mapping distinct so a shared template does not accidentally point every article to the same pair of destinations. Record who maintains the mapping when pages are renamed or translations are withdrawn.
Choose one manageable implementation method
Google supports alternate-language annotations in HTML, HTTP headers or sitemaps and treats these methods as equivalent. Choose a method the team can maintain consistently. For an HTML implementation, place the alternate link elements in the page head and use fully qualified destination URLs.
Each edition should include itself and its alternate editions. Check the return relationship: when the English page names the Arabic edition, the Arabic page should name the English edition too. Google may ignore a nonreciprocal relationship. Do not confuse these annotations with a visible language-switch link; review the metadata and the user navigation separately.
Generate the set from a single resource record
Store the resource identity, language codes and URLs together and generate the same alternate set for both editions. Validate codes against the official documentation rather than guessing a country abbreviation. Keep optional regional targeting out of the mapping unless the content and intended audience justify it.
Review the actual generated head, not just the template source. Confirm that the URLs are the current destinations and that neither edition silently redirects to an unrelated resource. Check canonical consistency separately: declaring an alternate language does not itself decide which duplicate URL should be canonical.
Illustrative example: one guide in two languages
Suppose a fictional maintenance guide exists at https://example.com/en/maintenance/ and https://example.com/ar/maintenance/. The mapping contains en for the first address and ar for the second. Both pages publish those two alternate entries, including their own address. The example demonstrates the relationship and is not a claim about a deployed customer website.
During review, the Arabic page is found to name an old English slug. The editor corrects the resource mapping and rebuilds both editions, then checks the emitted sets again. The fix is complete only when the published addresses and return links agree; editing a row in an unpublished configuration does not prove the live pages changed.
Validate each pair and retain the evidence
For each resource, compare the complete alternate sets, request the destinations and read their main content. Record the checked URLs, response behavior and any mismatch. A successful HTTP response alone cannot confirm that the destination is the right translation. Test a renamed page and a resource with no translation to catch template assumptions.
Save the mapping and check date, and repeat the review when editions are added or removed. An SEO audit can help discover inconsistent tags, but language equivalence still requires editorial review. Hreflang communicates relationships; it does not guarantee indexing or that every search will display the preferred edition.