Test the shared address, public page, and final destination separately. In Links2, saved drafts and published content are separate, so publish your correction before retesting as a visitor.
‘The link is broken’ can describe several problems: a social profile opens the wrong address, the public page shows old content, one button fails, or a music player refuses to play. Start by identifying the first failing step. Changing several things at once can hide the cause and make a working part of the journey harder to verify.
2. Check whether the intended content is published
Links2 saves drafts separately from the published page. Draft saved means the editor has retained your changes; it does not mean visitors can see those changes. Check the published status, select Publish when the page is ready, and reopen the public address. An unpublished page is not available to visitors.
If one block is missing, check its visibility and any schedule you configured. Confirm the dates and timezone rather than assuming a scheduled item should be visible now. Look at the public page as well as the editor preview, because the preview is not proof of the current published result.
A simple publish check
- Editor: make one identifiable correction to the affected label or destination.
- Save: confirm the draft has saved successfully.
- Publish: publish the corrected version.
- Visitor: reopen the public address and confirm the correction appears.
3. Test a failing button’s destination on its own
Copy the destination from the editor and open it while signed out of the destination service. A private document, organizer dashboard, expired ticket page, or deleted product can work for the owner and fail for everyone else. Replace it with the intended public destination, publish, and test the real button again.
For booking links, confirm the correct service and location. For music, check the recording and version. For email or phone actions, the visitor’s device needs an appropriate app to handle the action; opening that app does not prove that a message was sent or a call completed. A web address, email action, and phone action should be configured as the matching type.
4. Separate player problems from QR and address problems
If the page loads but a player fails, open the media on its original service. Check that it is public and that the page uses a supported URL and any required player field. YouTube notes that age-restricted videos cannot play on most third-party websites. Keep a direct destination available when the provider requires visitors to continue there.
If a QR code will not scan, test the image or physical proof at the intended size and distance. If it scans but opens the wrong destination, the problem is the encoded address or redirect. Links2’s downloaded profile QR uses a stable profile identifier, while a code you create from a handle URL contains that address. Do not assume all QR codes will follow a handle change.
Check music-card interaction and supported player URLs ↗
5. Send a reproducible report if the issue remains
Write down the first step that fails and whether it happens consistently. Include the public page address, affected button, expected result, and what actually appears. Add your browser and device and the approximate time with timezone. For a custom hostname, note whether the Links2 address works while the custom address does not.
Send Links2 issues to support@links2.link. Never include passwords, login links, payment details, or private access tokens. A clear report such as ‘the public page loads, but the workshop button opens a deleted event’ is much easier to investigate than ‘everything is broken.’ Recheck the original shared link once the correction is complete.
- Exact public page and affected button.
- First failing step and visible error text.
- Expected destination or behavior.
- Device, browser, and approximate time with timezone.
- Whether the same link works signed out or in another browser.