Short-link SEO — myths and facts about redirects
Do short links hurt SEO? Pass link equity? Get penalised by Google? The honest answers about short-link SEO, with citations from Google's own documentation.
Short link SEO is the most over-mythologised corner of the redirect world. The five-minute version: a properly-configured short link is SEO-neutral. It doesn't hurt your rankings, it doesn't help them, and Google has been saying this on the record since at least 2016. The destination URL is what gets indexed and ranked. The redirect is invisible to search results. There's no penalty for using a shortener, no "15% link equity loss per hop" tax, and no secret signal that distinguishes a bit.ly link from a direct one in PageRank. What can hurt SEO is misconfiguration — chained redirects, JavaScript-only redirects, redirect loops, mixed-protocol hops — and that's true of any redirect, not specifically of short links.
This post goes through the seven big short-link SEO myths in order, refutes each with the actual source it comes from, walks through the cases where short links genuinely affect search performance (mostly indirectly, through click-through rate on social platforms), and gives a checklist for when short links are the right SEO answer rather than a neutral one. By the end you'll know which redirects pass authority, which Google statements are misquoted online, and what to do with the rel=canonical and rel=nofollow questions that always come up.
The myth list, refuted in order
Before the long version, the short version. Here's the full list of short link SEO claims floating around, ranked by how often they show up in client questions: Skim the short-links documentation alongside the refutations below if you want the slug-picker, destination-type, and custom-domain workflow in one place while the SEO claims get unpacked.
Each one in turn below.
Myth 1: "Short links hurt SEO"
The most common version of the claim is some variation of: search engines treat redirects as a downgrade signal, so any URL that goes through a shortener loses ranking power. This is wrong, and it's wrong in a specific way that's worth understanding.
Search engines crawl your short link. The shortener responds with a 301 or 302 status code and a Location: header pointing at the destination. The crawler follows it. The destination URL is what enters the index. The short URL doesn't compete for rankings because it's not a destination — it's a router.
Google's own documentation on URL redirects is explicit: "Permanent redirects (301)... pass full ranking signals." Temporary redirects (302) historically had a more complicated story, but Gary Illyes confirmed in 2016 that 302s also pass PageRank when used persistently. We covered the trust mechanics of branded shorteners in why your domain beats bit.ly; the SEO mechanics are even simpler — there is no SEO penalty.
The mechanism people imagine — that the redirect step "leaks" authority — doesn't exist in the algorithm. Pages get authority from inbound links pointing at them. If those links point at lnks.work/k/abc and that 301-redirects to yourbrand.com/spring, the destination accumulates the equity. Whether the inbound link's anchor text was on a short URL or on a direct URL is irrelevant; the destination is the URL that ranks.
So short links are SEO-neutral when configured right. They become SEO-positive only indirectly — through the click-through-rate lift that branded short links produce on social and email channels, which we covered in detail in the branded short link argument.
Myth 2: "302 redirects don't pass any authority"
This one comes from old SEO advice — pre-2016 — that said 301 was the only redirect type that passed PageRank. The advice was always slightly wrong, and Google has since said so explicitly.
The current Google position, articulated by John Mueller in multiple Search Central office hours and reflected in the Search Central redirect documentation: both 301 and 302 redirects pass ranking signals. The semantic difference is what they signal to the index, not whether equity flows through:
- 301 tells the crawler "the destination has permanently replaced the source; index the destination."
- 302 tells the crawler "the source is the canonical URL; the destination is a temporary stand-in."
In practice, when a 302 has been in place long enough that the search engine concludes it isn't actually temporary, Google starts treating it like a 301 — indexing the destination and forwarding equity. The conversion happens around 6 months in most observed cases, though Google doesn't publish exact thresholds.
This matters because most short-link platforms default to 302. The 302 default exists for reasons we walked through in the URL shortener guide — primarily that 301s cache aggressively in browsers, which makes editing destinations later much harder. The 302 keeps the short URL re-fetchable on every click, which is what enables dynamic short links to actually be dynamic. The trade-off is that, in theory, 302s are slower to consolidate authority on the destination — but in practice the timeline is months, not forever, and the trade-off is worth it.
Myth 3: "Google penalises link shorteners"
The strongest version of this claim says Google has a manual or algorithmic flag for shortener domains and downranks pages that link through them. This is not true and has never been true.
The evidence: Google itself ran goo.gl, the Google URL Shortener, from 2009 to 2018. The product had hundreds of millions of active short URLs and was integrated into Google Maps, AdWords, and Google's own search-result snippets. Google would not have run an in-house shortener for a decade if shorteners were algorithmically penalised — they would have been penalising their own infrastructure.
What Google does penalise is deceptive redirect chains — sites that use shorteners to cloak malicious destinations, redirect-loop schemes designed to confuse crawlers, and JavaScript-based redirects that show one URL to users and another to bots. These are spam tactics that exist independently of shorteners. A reputable shortener doing standard 301/302 redirects to a legitimate destination is not in this category.
The actual nuance: Google's link spam policies call out "sneaky redirects" as a violation. The word "sneaky" is doing the work — the violation is intent to deceive, not the existence of a redirect. A short link from bit.ly/abc to your product page is not sneaky; a short link that shows Googlebot one destination and human users another is. The category boundary is whether you're trying to hide the destination from a specific audience.
Myth 4: "rel=canonical fixes everything"
A common follow-up to the redirect question: "but if I add a rel=canonical to the destination page pointing at the original URL, doesn't that solve any short-link SEO confusion?" Mostly, but with a critical caveat people miss.
rel=canonical is a hint to Google about which URL among several near-duplicates should be treated as the primary version. It's documented as a hint, not a directive, in Google's canonicalization docs. Google considers the canonical tag alongside other signals — internal linking patterns, sitemap entries, redirect chains, content similarity — and picks whichever URL the totality of signals supports. If the short URL is a redirect (which is the normal case), the canonical hint isn't relevant because the short URL never gets indexed as a destination in the first place.
Where canonical matters for short links is the unusual case where the shortener returns a 200 status with HTML content rather than a 301/302 redirect — for example, a frame-based shortener or an interstitial page. In that case the short URL could compete with the destination in the index, and a canonical tag on the interstitial page pointing at the destination is the right fix. But this is a misconfigured shortener, not the standard case.
The takeaway: if your shortener does HTTP redirects (which all reputable ones do), rel=canonical is irrelevant for the short URL itself. The destination's canonical tag matters for that page's own indexing across other near-duplicates (e.g., session-ID variants, http vs https), but the short link is not part of that conversation.
Myth 5: "Each redirect hop loses 15% link equity"
This is one of the longest-running zombie claims in SEO. It originates from an offhand comment Matt Cutts (Google's then-head-of-webspam) made in 2008 about how PageRank flows through redirects. The "15% loss per hop" number was extrapolated from his comments by a third party and then repeated for fifteen years in SEO blog posts.
Cutts himself debunked this in 2013, and John Mueller has reiterated it multiple times since: there is no fixed percentage loss per redirect hop. The actual algorithmic behaviour is that PageRank flows through redirects with the same dampening factor as any other link traversal, which is built into how PageRank works generally and isn't redirect-specific.
What is true: long redirect chains hurt SEO indirectly. Googlebot has a crawl budget per site — a rough cap on how many requests it'll make to your domain in a given window. Every redirect hop is a request. A chain that goes short.url → tracker.url → middle.url → final.url consumes four requests where one would have done. For a small site this is fine; for a large site with millions of URLs and a constrained crawl budget, redirect chains starve other URLs of crawl attention.
The fix: keep redirect chains to one hop. Short URL → destination, done. If your stack has analytics infrastructure that adds an interstitial redirect (some click-tracking layers do this), evaluate whether the analytics value justifies the crawl budget cost. For most sites it does; for sites with crawl budget constraints it might not.
Myth 6: "rel=nofollow on shortened outbound links blocks all credit"
A subtler claim, mostly affecting people running content sites who use shorteners for outbound affiliate or sponsored links. Until 2019, rel=nofollow was a strict directive — Google interpreted it as "do not pass PageRank through this link" and that was that.
In September 2019, Google changed the policy. rel=nofollow became a hint rather than a directive. The same change introduced two more specific hints: rel=sponsored (for paid links) and rel=ugc (for user-generated content). All three are now hints — Google may or may not pass equity through them based on broader signals.
The practical implication for short-link SEO: if you're shortening outbound links from your content (affiliate links, sponsored links, anything that needs rel=sponsored) and applying nofollow attributes through the shortener's link rendering, those attributes still need to be on the original <a> tag in your HTML, not on the short URL. The nofollow attribute lives on the anchor element, not on the destination URL. Shortening the URL doesn't change whether nofollow is present.
The 2019 change also means there's no SEO advantage to not using nofollow on legitimate sponsored links anymore. Skipping the attribute doesn't pass more authority because Google now treats the absence as one signal among many; it just creates risk that a manual review classifies your unmarked sponsored links as a link scheme violation. Mark sponsored links as such and let the algorithm sort it.
Branded short links on your own domain — with proper 301/302 redirects, no chained hops, no SEO weirdness.
See the lifetime tierMyth 7: "Branded short-link domains can rank in Google"
The contrarian myth: if you set up a branded short-link domain (go.yourbrand.com), the domain itself accumulates SEO authority and can compete in search results. This is partly true and mostly misleading.
What's true: a domain that's been around for years, has established trust, and serves consistent content can build search authority. Branded short-link domains are domains, so they can in principle accumulate signals.
What's misleading: branded short-link domains serve only redirects. Search engines don't index redirect-only URLs because there's no content to index — the destination is what enters the SERP. So the branded short-link domain itself doesn't appear in search results for content queries.
The narrow case where branded short-link domains do rank: navigational queries. Someone searches "yourbrand short link" and the domain appears as a navigational result alongside your main site. This is real but rare and only relevant if your brand is well-known enough that people search for it by name. For 99% of small businesses, the branded short-link domain is invisible in search and that's fine — it's a redirect surface, not a content surface.
The infrastructure-ownership question is more relevant than the ranking question. We covered that thread in owning your link infrastructure — the value of a branded domain is independence from a third-party shortener, not search visibility.
What actually hurts SEO when you use short links
The myths are myths. The real risks, in priority order:
Chained redirects. A short URL that redirects to a tracker URL that redirects to the final destination is two hops. Three hops is bad. Anything beyond three is a problem — Googlebot stops following redirect chains around 5 hops (the limit varies by crawler) and the destination doesn't get crawled at all. Audit your redirect chains; collapse them to one hop wherever possible.
Mixed-protocol redirects. A redirect that goes from HTTP to HTTPS is fine if it's one hop. A chain that goes HTTP → HTTPS → another HTTPS is wasteful. The browser still has to make multiple requests, the crawl budget gets eaten, and TLS handshakes add measurable latency.
JavaScript-based redirects. A short URL that returns a 200 status with HTML containing window.location = '...' is a JavaScript redirect. Googlebot can execute JavaScript, but it's slower and more error-prone than following an HTTP redirect. JavaScript redirects also break for any user-agent that doesn't run JS — including some social-media crawlers that fetch link previews. Stick to 301/302 server-side redirects.
Redirect loops. A short URL that redirects to a destination that redirects back to the short URL. Sounds absurd, happens regularly when domain configurations get crossed. Check your stack; loops kill SEO and user experience equally.
Slow redirect servers. A short URL on a server that responds in 2 seconds adds 2 seconds to every page load. The destination's Core Web Vitals get measured from the moment the user clicked, not from the moment the destination started loading — so a slow redirect counts against the destination's perceived performance. If your shortener's response time is over 200ms, that's a fixable problem.
These five issues do hurt SEO, and they hurt regardless of whether you're using a short link or a direct redirect. The lesson: short links are SEO-neutral when properly configured, and the configuration mistakes that hurt them are the same mistakes that hurt any redirect.
The hidden SEO cost most people miss — click-through rate
Here's the part that gets glossed over in the technical-SEO conversation. Short links don't directly affect ranking, but they do affect click-through rate on social and email channels — and click-through rate is an indirect ranking signal in some contexts (search snippets, especially) and a direct conversion signal everywhere else.
A generic shortener (bit.ly/abc) reads as anonymous and untrusted. Multiple agency case studies — Bitly's own published research, Buffer's social-share testing — find that branded short URLs lift click-through-rate by 25–40% over generic shorteners on the same content. The mechanism is trust: a user scanning a URL preview can decide to click in milliseconds based on whether the domain looks legitimate.
For SEO, this matters in three indirect ways:
- Social shares with branded URLs get more clicks, which generates more traffic to the destination, which (over time) tends to correlate with higher ranking on the destination's target keywords. The correlation isn't algorithmic; it's behavioural.
- Email campaigns with branded URLs avoid spam filters more often, which means more deliveries to inbox, which means more clicks back to your content, which builds the same behavioural signal.
- Branded URLs in print and QR codes get scanned more often when readers recognise the domain — covered in URL vs short link QR codes — which feeds the same loop. The platform-aware variant of that pattern, QR codes for app downloads with App Store and Play Store routing, uses the same trust-by-domain effect to lift install rates from the same QR.
- Branded URLs in social bios get the same trust lift on the profile rendering, particularly on platforms with a single clickable bio link — see URL shortener for Instagram bio — beyond Linktree for the strategy side.
None of these are "SEO ranking factors" in the algorithmic sense. They're conversion factors that secondarily affect SEO because traffic begets traffic. Worth doing for the conversion reason alone; the SEO benefit is a bonus.
When short links are genuinely the SEO answer
A few cases where short links aren't just SEO-neutral but actively help:
Campaign tracking with UTMs. A short link that absorbs the UTM parameters and redirects to a clean destination URL keeps the destination URL singular in the index. Without the short link, every campaign produces a different long URL with different UTMs, and the destination might get split into multiple URL variants in Google's index. The short link consolidates them.
Affiliate-link cloaking for trust. A long affiliate URL (partner.example.com/?ref=12345&trk=affiliate) looks low-trust in search snippets and social previews. A short link masks the affiliate parameters behind a clean URL. The destination tracking still works; the user-facing surface is cleaner.
Branded domain authority for navigational queries. If you're a recognised brand, a short-link domain like gо.yourbrand.com can rank for "[brand] link" navigational queries. Niche but real.
Edge-cached redirects for performance. A short link served from a CDN edge (Cloudflare, Vercel Edge, similar) responds in 10–40ms anywhere in the world. Compared to a direct HTTP redirect from a slow origin server, the edge-cached short link is faster and that speed contributes to the destination's perceived load time. We've seen short links cut redirect latency from 400ms to 30ms by moving the redirect to an edge runtime.
For most businesses, short links are an SEO-neutral utility that helps with conversion and analytics. For a few specific cases, they're a small SEO positive. They're never an SEO negative when configured properly.
SEO myth-vs-fact quiz
Test your understanding. Each question has one correct answer; the explanation appears after you pick.
Short link SEO — myth or fact?
The quiz tracks how many of the seven you got right. Hit reset and try again if you want to test recall after reading.
Frequently asked questions about short link SEO
Do short links hurt my SEO?
No. A properly-configured short link uses a 301 or 302 redirect to send the user to the destination. Google indexes the destination, not the short URL. Multiple Google representatives — Gary Illyes, John Mueller — have confirmed both 301 and 302 redirects pass ranking signals. Short links are SEO-neutral when configured right.
Is 301 better than 302 for SEO?
For a permanent redirect, yes — 301 signals to Google that the destination is the new canonical URL. For dynamic short links where you might change the destination later, 302 is correct because 301s cache aggressively in browsers and become hard to update. Both pass equity. Pick based on whether the redirect is permanent (301) or editable (302), not on imagined SEO differences.
Will Google penalise me for using a link shortener?
No. Google ran their own URL shortener (goo.gl) from 2009 to 2018. They penalise sneaky / deceptive redirects — redirects designed to cloak destinations or trick crawlers — but standard short-link redirects are not in that category. Use a reputable shortener and you have nothing to worry about.
Can a short link rank in Google search results?
Generally no, because it's a redirect, not a destination. Search engines follow the redirect and index the target page. The exception is navigational queries about your brand specifically — a branded short-link domain can appear when someone searches for it by name, but this is rare and only relevant for established brands.
Should I use rel=canonical on shortened URLs?
Not on the short URL itself — it's a redirect, so it never gets indexed as a destination. The canonical tag belongs on the actual destination page if there are URL variants you want consolidated. The canonical question is about the destination's index handling, not about the short link.
Do short links pass less authority than direct links?
No. Inbound links pointing at your short URL pass authority through the redirect to the destination. The destination is what accumulates equity in the search index. Whether the inbound link's URL was direct or shortened doesn't change the equity flow — only the chain length matters, and one hop is invisible.
How many redirect hops is too many for SEO?
Keep it to one. Two hops is acceptable but wasteful. Three or more starts hurting crawl budget on large sites and adds measurable latency for users. Googlebot stops following chains around 5 hops on the conservative side. Audit your redirect setup and collapse chains where possible.
Sourcesshow citations
- Google Search Central: 301 redirects and ranking signals — https://developers.google.com/search/docs/crawling-indexing/301-redirects
- Google Search Central: canonicalization (rel=canonical as a hint) — https://developers.google.com/search/docs/crawling-indexing/canonicalization
- Google Search Central: link spam policies (sneaky redirects, sponsored links) — https://developers.google.com/search/docs/essentials/spam-policies
- Google Search Central: managing crawl budget — https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget
- IETF RFC 9110: HTTP Semantics (300-class status code definitions) — https://www.rfc-editor.org/rfc/rfc9110
- Mozilla Developer Network: HTTP redirections — https://developer.mozilla.org/en-US/docs/Web/HTTP/Redirections
- Cloudflare developer docs: redirect rules at the edge — https://developers.cloudflare.com/rules/url-forwarding/
Try it on your own domain
Branded short links and dynamic QR codes, on your subdomain or your own domain. One-time purchase, no per-click fees.