A link alternate is an HTML (HyperText Markup Language) link relation that points search engines and browsers to another version of the same content. That version may target a different language, region, device, or format. Correct link alternate markup helps Google serve the right URL and reduces duplicate-content confusion across those versions.
Searchers who look up “link alternate” sometimes land on mainframe docs or CSS theme notes instead of web search engine optimization (SEO) guidance. Use HTML rel=“alternate“ to help search engines send people to the right language, region, or device version of your page. After that markup is in place, Bitly can help you create branded short links, manage redirects, and control mobile destinations so multi-market campaigns stay measurable and easy to accelerate.
Key takeaways
- A link alternate uses rel=“alternate“ to point to another version of the same content for language, region, device, or format.
- Hreflang pairs with rel=“alternate“ so search engines can match users to the correct language or localized market URL.
- Canonical and alternate tags solve different jobs: Canonical picks the preferred duplicate URL, while alternate describes legitimate variants.
- Implement alternates in HTML head links, HTTP headers, or XML sitemaps, and keep every version reciprocal.
- Bitly helps teams route and track multi-destination experiences with branded links, redirects, dynamic routing, and overrides for mobile deep links.
What a link alternate means in HTML and SEO
In HTML, a link alternate is a relationship declared with rel=“alternate“ on a <link> element. It identifies another representation of the current document. Google describes alternate URLs as device-specific or translated pages you can mark with hreflang or rel=“alternate“.
A link alternate isn’t a backup shortener, mainframe networking term, or link-in-bio product name. In plain terms, it tells crawlers and browsers that another URL provides the same content for a different language, region, device, or format.
The Mozilla Developer Network publishes documentation for the rel attribute. The HTML Living Standard definition of rel=“alternate“ locks the meaning browsers and specs share. With Google’s help docs, they treat alternate as a first-class relationship, not a soft hint in body copy.
| Attribute | Role | Example use |
|---|---|---|
| rel=“alternate“ | Declares another representation of the document | When identifying a language, device, feed, or format twin of the page |
| hreflang | Names the language or language-region of the alternate URL | hreflang=“es-MX“ for Spanish content aimed at Mexico |
| media | Limits when a device- or viewport-specific alternate applies | Legacy mobile site paired with a desktop URL |
| type | Names the MIME (Multipurpose Internet Mail Extensions) type of an alternate format | type=“application/rss+xml“ for an RSS (Really Simple Syndication) feed |
Alternate signals sit next to SEO-friendly URL structure. Each language or device version stays easier to maintain.
How rel=“alternate“ works with hreflang for language and region
Pair rel=“alternate“ with a proper hreflang implementation to map each language or language-region pair to its URL. Use this pattern for translated pages and same-language market variants, like Spanish for Spain versus Spanish for Mexico. Add an optional x-default URL for unmatched locales.
A typical head annotation looks like this, with a self-reference for the current page. Example destinations include https://example.com/ and https://example.com/mx/:
<link rel=“alternate“ hreflang=“en“ href=“https://example.com/“ />
<link rel=“alternate“ hreflang=“es-MX“ href=“https://example.com/mx/“ />
<link rel=“alternate“ hreflang=“x-default“ href=“https://example.com/“ />
You can implement the same relationships three ways with equal weight:
- HTML <head> links on each URL
- HTTP headers for non-HTML files like PDFs
- XML sitemaps with xhtml:link entries for every localized URL
Language values follow ISO 639-1 language codes. Region values use ISO 3166-1 alpha-2 country codes. You must include a language code; a region code alone is invalid.
Every URL in the set should point back to every other URL so annotations stay reciprocal.
One common mix-up is scope. World Wide Web Consortium (W3C) materials put hreflang on visible <a> elements for accessibility. SEO setups usually place rel=“alternate“ hreflang in the head, headers, or sitemaps so crawlers can map the full set.
After each market page exists, channel teams still need trackable campaign URLs. Bitly doesn’t write hreflang for you. We help send paid, social, and email traffic into the right locale page with various types of links you can brand, retarget, and measure.
Mobile, media, feeds, and other alternate link types
Beyond hreflang, rel=“alternate“ can point to device-specific pages, alternate formats such as RSS or Atom, or alternate stylesheets. Device and format twins matter most to marketers.
Separate mobile sites once used media queries on rel=“alternate“ pairs between desktop and mobile subdomain (m-dot) URLs. Most teams now prefer one responsive URL instead. Keep mobile alternate pairs only when device URLs stay separate.
Feeds use the same relation with a type attribute, such as rel=“alternate“ type=“application/rss+xml“ (and Atom), so readers can discover syndication endpoints. Alternate stylesheets remain a niche browser pattern, not a growth lever.
For growth teams, “alternate destination by context” maps to mobile deep linking and Bitly mobile links, not inventing HTML tags in Bitly. On paid Universal Links or Android App Links setups, set an alternate mobile path, interstitial, and install URL so app and web destinations stay intentional.
Link alternate vs canonical: How the tags work together
A canonical tag suggests the preferred URL among duplicates. Alternate describes valid language, region, device, or format variants. They work together when each job stays in its lane.
Large international sites often use self-referencing canonicals. Each locale page is canonical to itself while the full alternate set lists every language or market twin. That pattern prefers the Spanish-Mexico URL for that market without collapsing every locale into one global page.
If you treat every alternate as a duplicate to suppress, you can hide international or mobile versions you still need in search. Canonical consolidates true duplicates. Alternate advertises legitimate variants for the right audience.
| Topic | Canonical (rel=“canonical“) | Alternate (rel=“alternate“) |
|---|---|---|
| Purpose | Names the preferred URL among near-duplicates | Names another valid version of the content |
| Typical use | Parameter cleanup, printer pages, duplicate paths | Language, region, device, or format variants |
| Self-reference | Common: Page points canonical to itself | Common: Page includes itself in the hreflang set |
| Risk if misused | Wrong canonical can drop the URL you wanted ranked | Missing or one-way alternates confuse locale targeting |
For site architecture and parameter hygiene, cleaner paths help maintain consistent, SEO-friendly URL patterns across locales. Bitly serves short links, redirects, and tracking. WE don’t inject rel tags into your page head.
How to implement and validate alternate links
To ship clean alternate links:
- Choose one primary method
- Annotate every URL in the set
- Keep codes valid
- Validate in Google Search Console
XML sitemaps are a supported place to declare alternates. Incomplete HTML mixed with a partial sitemap set often causes errors.
Implementation checklist
- Inventory every language, region, and device URL that represents the same content.
- Choose one primary method among HTML head links, HTTP headers, or XML sitemap annotations.
- Add reciprocal rel=“alternate“ annotations and hreflang when relevant, across the full set.
- Include x-default when you maintain a fallback for unmatched locales.
- Submit or resubmit the sitemap that carries those URLs.
- Monitor “International Targeting” or hreflang-related reports in Search Console where available.
Five steps to ship a clean set
- Map each content piece to its live alternate URLs and owners.
- Normalize language and region codes before anyone ships markup.
- Publish reciprocal annotations with the method your CMS supports best.
- Crawl the set to confirm every page returns 200 and is indexable.
- Spot-check Search Console coverage after Google recrawls the URLs.
Validation tips
- Fix mismatched or invented language codes.
- Repair missing return links so A→B always includes B→A.
- Avoid alternates that point to redirected, soft-404, or noindexed URLs.
- Resolve conflicts where a canonical points away from the URL your hreflang set promotes for that locale.
Destination URLs change as campaigns, CMS migrations, and app releases move. Stable entry points matter as much as clean head tags. Use Bitly redirects when destinations change so shared campaign links keep working.
Route and measure multi-version destinations with Bitly
Bitly doesn’t replace hreflang markup. It helps you create, brand, route, and measure the URLs people click to reach those different versions, after they already exist. Technical SEO owns head, header, and sitemap alternates, while growth teams own link management into each version.
With Bitly products, you can:
- Create branded short links and custom domains that look consistent in every market.
- Redirect destinations when a locale page moves (on our Core tier plan and above).
- Apply dynamic routing by country or platform on our Growth tier plan and above, and by region or device on our Premium tier plan and above.
- Configure mobile deep links with overrides for the alternate mobile path, interstitial preferences, and install URLs.
- Attach uniform UTM (campaign tracking) parameters with our UTM builder.
- Review click analytics by country, city, device, and referrer so you can compare performance across channels.
That split keeps responsibilities clear. SEO teams annotate official alternates, and marketers ship trackable entry links into each annotated URL. You get to make the hard-to-measure measurable without having a short link platform rewriting your HTML headers.
UserEvidence reports a director-level marketer explaining how branded short links improved click-through rate and simplified campaign link management. Pair that clarity with accurate alternate markup to serve the right version in search. Then see which path performs in your channels.
Build cleaner multi-version link journeys
Link alternate markup tells systems which version is which. Disciplined routing and tracking tell your team which version performs. Audit annotations, keep canonical and alternate jobs separate, and standardize campaign entry links with branded Bitly Links.
Bitly is the marketing platform that helps businesses of all sizes see what’s working, simply and clearly. Annotate the variants search engines need, then measure clicks with Bitly Analytics, and quickly learn which path to grow.
Link your marketing. Get started for free to create branded, trackable links for each audience path.
Frequently Asked Questions
What is a link alternate?
A link alternate is a reference, usually via rel=“alternate“, to another version of the same content for a different language, region, device, or format. Search engines use these signals to serve the most appropriate URL.
What does rel=“alternate“ mean in HTML?
rel=“alternate“ marks a relationship between the current document and an alternate representation. Combined with attributes like hreflang, media, or type, it specifies language, device, or format variants.
Is hreflang the same as a link alternate?
Hreflang is the language or region code; rel=“alternate“ is the link relationship that often carries it. SEO implementations typically use <link rel=“alternate“ hreflang=“…“ href=“…“> in the head, HTTP headers, or sitemaps.
How is a link alternate different from a canonical tag?
A canonical tag points to the preferred URL among duplicates. A link alternate describes legitimate alternate versions you still want available for the right audience or device.
Do I need alternate links for a responsive website?
Responsive sites that serve one URL across devices often don’t need mobile rel=“alternate“ media pairs. You still need hreflang-style alternates when you publish distinct language or regional URLs.
Can Bitly create rel=“alternate“ or hreflang tags for my site?
Bitly doesn’t inject rel=“alternate“ or hreflang into your page HTML. Bitly helps you brand, redirect, dynamically route, and track the destination URLs those tags describe, including alternate mobile paths on supported deep link setups.
