Link in bio not working? A checklist to narrow down the cause

First identify the symptom: is the link missing, untappable, rejected, opening the wrong page, or failing after the page loads? Those are different problems. The order below starts with straightforward checks; it is not a ranking of how frequently each cause occurs.

1. Check that the published link is clickable

Use the platform's current link-editing controls rather than assuming a URL typed into ordinary profile text becomes a link. Save the change, leave the editor and inspect the profile as a visitor. Check the actual link placement and account configuration you are using.

If the link is missing or untappable, investigate the profile field and any displayed platform message first. A destination website cannot fix a link that the source app has not made available.

2. Compare the saved URL with the intended destination

• Check the scheme, domain, path and query parameters. Look for pasted whitespace, duplicated prefixes or a link to the editor instead of the public page.
• Open the exact saved address in a fresh browser window and note the final URL after any redirects.
• Then tap the actual profile link. If the result differs, record both addresses rather than assuming the app changed the destination.

3. Record any platform warning

If the app rejects the link or displays a warning, record its exact wording and the address involved. Check the platform's current support or review process. Do not assume that a shortener, new domain or previous report is the cause without evidence, and do not rotate domains to evade a warning.

Opening the destination separately can help determine whether it is reachable outside the app, but that does not explain or resolve the platform warning. A DM is a different entry point and is not a definitive test of what happens in a profile.

4. Check public access and link rules

A page that works while you are signed in may not be available to visitors. Check publication status, active links, password requirements, audience restrictions, schedules and expiry settings. In OpenOut, also check that you are sharing the public page you intended rather than a preview or another page's handle.

5. Separate stale previews from wrong destinations

An outdated share-card title or image is not the same as a redirect to an old page. Check the final address and loaded content separately. If the address is wrong, inspect the saved link and redirect configuration. If the address is right but content is stale, investigate the site's caching and deployment state.

MDN's HTTP caching guide explains how stored responses are reused and how browser and managed caches differ. It does not establish a social platform's preview refresh time. Use available site or platform refresh tools where appropriate rather than assuming waiting will fix every case.

6. Reproduce the step that fails after loading

If the page loads but sign-in, a form, a download or checkout fails, test that exact action. The cause may involve the website, account, network, device or browser context. An in-app browser is one possibility, not an automatic diagnosis.

1. 1

   Start from the real source

   Tap the profile, Story or campaign link your audience uses. Record the destination and any error before changing settings.

2. 2

   Repeat the same action in your regular browser

   Use the same device and destination. Note differences in login state, cart contents, permissions and payment options; they can affect the comparison.

3. 3

   Narrow the difference

   If only one context fails, investigate that context and the failing website feature. This is evidence of a reproducible difference, not proof that all in-app browsing is broken.

4. 4

   Retest the whole journey after a change

   Check the original entry point, the final destination and the completed action. For browser guidance, also test unavailable menu actions, denied clipboard access and manual copying.

For the technical distinctions, read in-app browsers explained. Practical menu and copy options are covered in the Instagram guide and TikTok guide.

What to include in a useful bug report

• The public source and destination URLs, with private tokens or credentials removed.
• The device, OS and app version, whether you were signed in, and the date of the test.
• The expected result, exact failing step, visible message and final address.
• Whether the same action worked in a regular browser, and any differences in account state or permissions.

OpenOut browser guidance can provide opening attempts, copy and manual instructions, but does not repair an unavailable destination or guarantee a completed checkout. Free includes a linkpage; guidance requires Pro. See pricing for plan details.