FerrymanFerryman
← All articles

Platform guides

Why links in YouTube Shorts descriptions are not clickable

Understand YouTube's link-placement rules and choose a working viewer path instead of repeatedly changing a valid URL.

By Ferryman··5 min read

The placement can be the problem even when the URL works

YouTube's link-sharing documentation explicitly says URLs in Shorts comments and descriptions are non-clickable to reduce spam and scams. If the same URL opens correctly in a browser, that does not contradict the rule. The address can be valid while the surface intentionally renders it as text. Repeatedly changing your domain or tracking parameters will not turn that surface into a clickable link.

This matters when you cross-post a caption written for another network. A call to action such as 'click the link below' may describe a path that does not exist in the Short. Adapt the invitation to the actual viewer experience. Keep the Short useful on its own, then offer a clear next step that the destination supports rather than copying the original caption unchanged.

Choose a supported route to the next step

YouTube lists channel profile links and related-video links in Shorts as clickable. These serve different purposes: a profile link can lead to an external destination, while a related video continues the journey within YouTube. Do not describe a related-video control as a direct website link. Check the channel's current eligibility and available controls before promising a particular route in the caption or video.

The same documentation says clickable external links in long-form descriptions and comments require access to advanced features. That is another reason not to generalize from one YouTube surface to another. Choose the route that matches the reader's task, then test the entire path from the Short. A valid link hidden behind a confusing instruction is still a poor handoff for a viewer.

PlacementDocumented behaviorEditorial action
Ordinary URL in Short description/commentNon-clickableDo not promise a direct tap
Channel profile linkClickableName the relevant profile link clearly
Related video in a ShortClickable YouTube continuationUse a genuinely relevant next video
Long-form external linkAdvanced-feature access requiredVerify eligibility and actual clickability

Rewrite the call to action around the real path

For an illustrative repair tutorial, replace 'Click below for the checklist' with 'The repair checklist is linked on my channel profile' only after that profile link exists and is appropriately labeled. If the next step is a longer demonstration, point viewers to the related video instead. These are wording examples, not claims that one phrase produces a higher conversion rate.

Use matching names across the spoken invitation, caption, and destination. If the video says 'the checklist,' the profile should not present several indistinguishable links called 'learn more.' Keep the promised resource accessible on mobile and verify that redirects preserve any measurement parameters you intentionally use. A functioning first tap is not enough if the final page is missing or unrelated.

Test from a viewer's perspective

Open the published Short through the surfaces your audience uses and follow the path without relying on creator-only controls. Confirm the visible wording, available link, final destination, and any account eligibility requirement. Record the test date because interfaces and policies can change. If the route is unavailable, revise the invitation rather than implying the audience is doing something wrong.

When distributing through Ferryman, review the YouTube-specific caption and final post instead of treating a successful upload as proof that an external call to action works. Keep website traffic measurement separate from publication success. A correct Short can be public and playable while offering no direct clickable URL in its description. Fixing that journey is an editorial placement decision, not necessarily an upload bug.

Sources & further reading

Written by Ferryman. Sources checked Oct 16, 2026. Platform rules can change; consult the linked documentation for current requirements.