This page explains what the Language Version Builder does, how to manage version-specific hreflang tags for content that exists in multiple language editions, the step-by-step workflow, versioning mistakes that break hreflang, and how this builder differs from a general hreflang tag generator.
What is a language version builder?
A language version builder is a hreflang tool focused on managing discrete language versions of the same content. While a general hreflang generator treats every URL-language pair equally, this builder organizes your work around the concept of a "version" — a specific language edition of a page that may have its own publication date, its own editorial workflow, and its own URL.
This matters for content-heavy sites: news publishers, documentation platforms, SaaS knowledge bases, and e-learning portals. These sites often have an English source version, a Spanish version published two days later, a German version still in draft, and a French version awaiting review. The language version builder tracks which versions are live and ready for hreflang annotation and which should be excluded until publication.
The output is technically identical to any hreflang generator — HTML <link> tags, HTTP Link: headers, XML sitemap xhtml:link elements, and JSON-LD — but the input workflow is built around the editorial reality of maintaining multiple language versions of the same content.
How to use the language version builder
Follow this version-aware workflow:
- Identify the source version. Paste the URL of the primary language page — usually the original version that other translations are based on. Select its ISO 639-1 language code and optional ISO 3166-1 region code.
- Add each language version. For every translation, enter the URL, select the language-region code, and mark the version status: live, scheduled, or draft. Only versions marked as "live" are included in the generated hreflang set. Draft and scheduled versions appear in the interface for tracking but are excluded from the output.
- Set x-default. Designate the fallback URL. For version-managed content, this is usually the source-language version, since it is typically published first and stays live the longest.
- Review version coverage. The tool displays a version matrix showing which languages have live versions, which are in progress, and which are missing. This view helps editorial teams prioritize translations.
- Generate for live versions only. Click generate to produce the hreflang set for all live versions. The tool ensures reciprocity, self-reference, and ISO code validity within the live set. When a new version goes live, update its status and regenerate.
Common errors and how to fix them
Version-managed hreflang setups introduce a category of errors that flat hreflang generators do not encounter:
-
Including draft URLs in the hreflang set. If a German translation is not yet published, including its URL in the hreflang set sends Google to a 404 or a password-protected draft page. Google silently drops the annotation and may lose trust in your hreflang implementation over time. The tool prevents this by excluding non-live versions from the output automatically.
-
Forgetting to regenerate after publishing a new version. When the French version goes live but you do not update the hreflang tags on the English, Spanish, and German pages to include it, the French page has no reciprocal links. The tool tracks version status changes and highlights when a regeneration is needed.
-
Using different URLs for draft and live versions. Some CMS platforms serve drafts at a different URL path (like
/preview/fr/page) than the live version (/fr/page). If you accidentally enter the preview URL for a version marked as live, the hreflang set points to a URL that may not be publicly accessible. The tool flags URLs containing common preview path segments (/preview/,/draft/,/staging/). -
Mismatched source and translation content. If the English source version has been substantially updated but the Spanish translation still reflects the old version, the two pages are no longer true equivalents. This tool cannot inspect content, but it prompts you to confirm that each live version is current when you generate output.
-
Publishing versions without self-references. Some CMS integrations inject hreflang tags automatically but omit the self-referencing tag. The generated output from this tool always includes self-references, so deploying the full output from here avoids the issue.
How this tool is different
The language version builder treats hreflang as an editorial process, not just a technical one:
- Version status tracking. Each language entry has a live/draft/scheduled status. Only live versions enter the output. This prevents the common mistake of tagging pages that do not exist yet.
- Regeneration alerts. When you change a version's status from draft to live, the tool highlights that all other pages in the set need updated hreflang tags and offers to regenerate the full output.
- Version timeline view. A horizontal timeline shows when each version was marked as live, making it easy to see which translations lag behind the source. This is a planning aid, not just a tag generator.
- Partial-set generation. If your workflow requires deploying hreflang tags before all translations are ready, the tool generates a valid partial set from whatever versions are live today. As new versions launch, you incrementally expand the set.
For a workflow that does not require version tracking — where all language pages are already live — the hreflang tag generator is simpler and faster. For managing regional variants within a single language, see the multi-region tag builder.