URL Shorteners and Redirects: Backlink Value Explained

Every link you hand to a publisher, newsletter editor or guest-post host forces a small choice that rarely gets discussed: paste the plain destination, paste a shortened address, or paste the wrapped link your campaign tool generated? For social and email teams those wrappers are useful, because they count clicks and label sources. For link builders they raise a sharper question. When a redirect sits between the publisher's page and yours, does the backlink still do its job?

Link builders feel this most, together with the social, email and paid-media colleagues who hand them links. The article explains what a redirect physically does, how Google describes permanent and temporary redirects, why a direct URL is the safer thing to give a publisher, and how to keep campaign measurement without polluting editorial links. You will find no search volumes, difficulty scores or "you lose this much value" percentages. Google publishes no such ratio, and an invented one would only mislead. Where a statement comes from Google's documentation, the text says so; where it is general working knowledge, it is labelled that way.

From Click to Destination: How Short and Tracking Links Behave

Start with the plumbing, because every later decision depends on it. The description in this section is general HTTP behaviour rather than Google documentation, so treat it as working knowledge and test any specific service yourself.

One click, two requests, several dependencies

A browser asks for the short address. The shortener's server looks the path up in its database and replies with a status code and a location header that names the real destination. The browser then makes a second request to that location. Two requests, two servers and two points of failure now sit where a plain link would have had one.

Three consequences follow. The link on the publisher's page points to the shortener's domain, not yours, so backlink tools and crawlers record that domain first. The life of the link depends on an account you may not control for years. And the status code the shortener picks, which you may never have chosen, decides how Google interprets the hop. The next section covers that last point in detail.

Campaign platforms go further than shorteners. They record the click, often set a cookie, sometimes choose a destination by country or device, and may append parameters on arrival. Email services commonly rewrite every link in a message to their own tracking address. A single click can therefore pass through an email service, a shortener and a campaign platform before reaching your page. Each layer is another request and another dependency. If you want to learn how to find and repair such chains on your own site, see redirect chains and loops: how to fix them. This article deals with the case where the chain starts on someone else's page.

Bots and people must see the same thing

Some tracking setups branch by country, language or device. That is fine in itself, but Google's spam policies (Opens in a new tab) define sneaky redirects as sending visitors to a different URL than the one they requested in order to show users and search engines different content, or to show users content that fails their needs. The same page treats site moves, page consolidation and redirecting signed-in users as legitimate. A branching rule is only safe when crawlers and people follow the same logic, so audit it before you rely on it.

The four setups side by side

The table is a way of thinking, not a verdict. Excellent and poor implementations exist in every row. The common thread is that each added step affects how reliable and traceable the link is, which matters more here than any claim about value.

What Google Says About Redirect Types

To judge the SEO effect you need Google's own wording. The points below come from the Search Central page on redirects and Google Search (Opens in a new tab).

Permanent or temporary: the signal each one sends

For a permanent redirect, Googlebot follows it and the indexing pipeline uses it as a signal that the target should be canonical. The page adds that permanent redirects should be used only when you are sure they will not be reverted. For a temporary redirect, Googlebot also follows it, but Google does not treat it as a canonical signal, and the source page may remain in search results.

For a backlink this distinction matters. A short link that answers with 301 or 308 tells Google plainly that the short address and your page are the same thing. One that answers with 302, 303 or 307 sends a weaker message, and Google may keep the short address as a separate page. The documentation gives no percentage of value that passes in either case. Statements such as "a 301 loses nothing and a 302 loses everything" are therefore unsupported.

Which methods Google reads most reliably

The same page lists redirect methods from most to least reliably interpreted:

In the documentation's own words, use JavaScript redirects only if you cannot do server-side or meta refresh redirects, because Google might never see them. Many click-tracking pages work through a small script. Giving such a page to a publisher as the link to your site adds uncertainty that a direct URL would avoid.

Alternate names, PageRank and a worked case

Google keeps track of both the old and the new address in a redirect. One becomes canonical according to the redirect type and the other becomes an alternate name. The documentation notes that alternate names can still appear in results when a query suggests people trust the old address more, and that old addresses tend to fade on their own after a site move. A short link showing up in search is unlikely in practice. The principle still holds: if you want the short address and your page to merge, a permanent server-side redirect is the clearest signal. That is a reading of the documentation, not a ranking promise.

The redirect page never uses the word PageRank. It frames everything as canonical selection. If you want the concept of how value travels between pages, link equity explained: how PageRank flows gives the background. What is documented is the canonical signal of each redirect type. What is not documented is the exact amount of value that crosses.

Fictional example: a stationery shop gives a blogger a link for a product roundup. To collect campaign numbers, the shop uses a shortener whose redirect is temporary. The blogger publishes the link. In the shop's backlink report the placement appears under the shortener's domain, and the shop's own page seems never to have received a link from that article. The example has no figures on purpose; it only shows how the decision plays out.

Reading the Redirected Links Already Pointing at You

You will not always control what a publisher used, and older campaigns may have left shortened links behind. This part is about reading those links systematically and requesting fixes where they matter.

Trace the destination, then classify the finding

Open the short address and follow it to the end. The network tab in browser developer tools, or a command-line tool, shows every step with its status code and location header. Record how many hops there are, what code each returns, what the final address is, and whether the final page answers with a 200.

Asking for a fix, and knowing when to skip it

Keep the message short, specific and free of pressure. Say the short address may stop working one day, that replacing it with the page address is safer for readers too, and paste the exact new URL. Offer no incentive. If anything of value is exchanged for a link change, the paid-link rules apply and the arrangement must be judged under them.

Not every redirect is a problem. If a publisher runs internal tracking and reaches you through a reliable single permanent hop, fixing it may not be worth the effort. Rank your list by the importance of the placement: a redirected link on a strong editorial page deserves attention before one on a weak page. This is a practical queue for your time, not a ranking formula.

A log that survives a team change

Record each case in a simple sheet: publisher, page address, the link as published, redirect type, number of hops, request date, reply and outcome. Later you can explain which links were refreshed, which are pending and which were deliberately left. Such a log helps most when an agency changes or a new team takes over.

The Case for Handing Publishers the Destination URL

The technical picture leads to a plain working rule: for editorial articles, sponsored posts and partner pages, give the publisher the clean, direct destination URL. This is not a Google rule. It is a way of removing uncertainty, and the reasons below support it.

Ownership and durability of the link

With a direct URL, the publisher's link points at your own domain. Backlink tools, Search Console and your colleagues all recognise it at a glance. With a shortener you see a third domain in the report and must decode the chain to learn where it ends. For a wider look at reading link data, see how to read a backlink profile and use link checkers.

Shortener accounts lapse, paid plans end and companies are sold. When that happens, short addresses can stop working, yet the publisher may keep the link on the page for years and you have no way to repair it. Hosting short addresses on your own domain reduces that risk because you control the redirect. For an editorial placement, though, the direct address remains the most durable option.

Attributes and the spam policy

For paid or sponsored placements Google asks for rel="sponsored"; user-generated links get rel="ugc" and other cases rel="nofollow". The rules are laid out in the guidance on qualifying outbound links (Opens in a new tab), which adds that links carrying these attributes are generally not followed. When a redirect is involved, it becomes hard to tell which behaviour belongs to the publisher and which to the intermediary. The wording requirements for paid placements are collected in sponsored posts with backlinks: the link spec.

Google defines link spam as links created primarily to manipulate rankings, and says paid links are acceptable when qualified with rel="nofollow" or rel="sponsored". A direct, qualified link is easy to defend. A paid link hidden behind an intermediary redirect is not, because it gives the impression that the real destination is being masked. Avoid any arrangement that could look that way.

Channels where a direct link is not possible

Some channels insist on their own tracking addresses. A newsletter platform wraps each link, and a social network may route links through its own shortener. In those places you cannot supply a direct URL, and that is normal. Such channels are mostly about traffic and visibility rather than backlinks. The rule applies where you are trying to earn a backlink: editorial articles, resource pages, co-created content and sponsored articles.

Fictional example: a small software company submits a guest article to an industry blog. The author box at the end names the company's clean home page address. In the company's own newsletter, by contrast, links go through the sending service's tracking address. The two links serve different purposes, one for a backlink and one for traffic measurement, and keeping them separate keeps the reports readable.

Final check before you send the link

• Is the address on your own domain and written in your preferred canonical form?
• Do the protocol and the www or non-www choice match your site's canonical usage?
• Does it carry a needless tracking parameter, and if so is there a clean version for the publisher?
• Does the page answer with a 200, or does it enter a redirect chain?
• For paid placements, has your expectation of rel="sponsored" been put in writing?

Measuring Campaigns Without Dirtying Editorial Links

Marketers want numbers and link builders want clean addresses. The two goals look opposed, yet a few habits satisfy both.

Parameters, duplicates and the URL structure guidance

Google's guidance on consolidating duplicate URLs (Opens in a new tab) uses a tracking-parameter address (its example is a click identifier) as a duplicate that should fold into the clean address. The page ranks the ways of naming a canonical from strong to weak: redirects and rel="canonical" are strong signals, sitemap inclusion is a weak one. It adds that redirects should be used when deprecating a duplicate page.

So a visitor arriving from a publisher on a parameterised address sees your page, but Google can notice that one page has several addresses. A self-referencing rel="canonical" on the target that names the clean address is the usual fix. The documentation also advises using absolute URLs and choosing either the HTML element or the HTTP header, not both.

The URL structure best practices (Opens in a new tab) recommend keeping parameters to a minimum and removing any that do not change the content. They list session IDs and referral parameters among the irrelevant parameters that spawn many duplicate URLs. They advise the equals sign and ampersand syntax, commas for several values, and discourage colons, brackets and double commas. They also say not to use fragments to change page content, since Google generally does not support them.

That document does not name tracking parameters directly. Blanket claims that UTM tags help or hurt SEO therefore do not come from it. What does come from it is the duplicate-URL risk of uncontrolled parameters, and the remedy: fewer parameters, a canonical declaration and a clean address.

Where the tracking can live instead

These approaches are not rules lifted from Google's pages. They are ways of reconciling the canonical and parameter principles with the need to measure, and the best choice varies with your analytics set-up and consent flow.

Short paths and channel matching

If campaigns need short addresses, building them as a path on your own domain is usually healthier. You choose the status code and no outside service can disappear under you. A permanent redirect suits an address you will keep, and a temporary one suits a short experiment, in line with Google's advice to use permanent redirects only when you are sure they will not be reverted. If the destination may change later, choosing a temporary redirect prevents a wrong canonical signal from forming.

In channels you own or pay for, such as ads, newsletters and social posts, tagged links are fine because the goal is measurement, not a backlink. In editorial placements, measure through referrer data and landing page analysis. Two needs, two channels, and neither spoils the other.

Fictional example: an online course provider wants to measure both a guest article on a learning blog and its own newsletter. In the guest article it supplies the clean course page address. In the newsletter it uses a tagged address. The course page carries a self-referencing rel="canonical". Visits from the guest article are tracked through the referring site entry in analytics. No shortener account is involved and the example has no figures.

Frequent Missteps

• Using a shortener for every editorial link: measurement gets easier, but the destination, lifespan and status of the link now belong to a third party.
• Ignoring the 301 and 302 difference: a temporary redirect carries no canonical signal, and leaving one where a permanent redirect belongs is a common oversight.
• Spreading tracking parameters without a canonical: one page ends up with many addresses in circulation.
• Giving a publisher a JavaScript click page: Google's documentation points to the risk that the redirect is never seen.
• Leaving the link attribute vague on a paid placement: put the rel="sponsored" expectation in writing.
• Building redirects that treat bots and people differently: this approaches the sneaky redirect definition and carries serious risk. If you branch by language or device, apply the same logic to crawlers and users.
• Tying the shortener account to one person: when they leave, access disappears and the published links cannot be repaired.
• Assuming a missing link in a report means no link: redirects can keep some tools from showing a link that exists.

Frequently Asked Questions

Does a Bitly link count as a backlink to my site?

A short link is a redirect step in front of your page. The publisher's page links to the short address, and your URL is reached only after the redirect. How much of the usual signal survives depends on the status code the shortener returns, and no one can promise a figure. Handing the publisher your destination URL removes that uncertainty.

What is the difference between a 301 and a 302 for link value?

Google says a permanent redirect (301 or 308) is a signal that the target should be canonical, while a temporary one (302, 303 or 307) is not treated as a canonical signal and the source page may stay in results. Google does not publish a percentage of value passed either way, so keep expectations modest.

Is it a problem to give a publisher a link with UTM parameters?

Google treats a tracking-parameter address as an example of a duplicate URL that should consolidate into the clean one, and it recommends a rel="canonical" on the target. Even so, an editorial placement is neater with a clean address, with measurement handled on your side.

Do JavaScript redirects pass link value?

Google tells site owners to use JavaScript redirects only when server-side or meta refresh redirects are not possible, and warns that rendering can fail so the redirect may never be seen. That makes them a poor foundation for a backlink.

What should I do when my backlink report shows a redirected link?

Trace where it actually lands, note the status codes and the number of hops, then ask the publisher politely to swap in the direct URL. Not every redirected link needs fixing, but extra hops and third-party services that can expire carry avoidable risk.

Conclusion

Shortened URLs and tracking redirects are not forbidden; they have a cost. Each intermediate step ties the link to a third-party service, makes the trail harder to follow and depends on the right redirect type being chosen. According to Google, a permanent redirect is a canonical signal and a temporary one is not, and a JavaScript redirect is a last resort. Because no ratio of value passed has been published, treating any of this as a ranking guarantee would be a mistake.

The practical outcome is simple. For editorial articles, sponsored posts and partner pages, give publishers the clean, direct URL. Handle measurement through referrer data, canonical tags and short paths on your own domain, and keep tagged links for channels you own or buy. Classify the redirected links you already have by status code, ask politely for fixes on the ones that matter and log the work. Stay away from hidden, conditional or misleading redirects in every case.

If you want editorial placements with direct, qualified links, you can review the backlink packages at Akua Adforce; scope and terms are written on the product page.