Back to help
17

Check before publishing

Check link readiness and simulate routing for a chosen audience without consuming clicks. Both tools appear above the tabs in a link's details. Availability depends on service settings and permission to view statistics.

Check link readiness and simulate routing for a chosen audience without consuming clicks. Both tools appear above the tabs in a link's details. Availability depends on service settings and permission to view statistics.

Enter a country, region, language, User-Agent and UTC time. See the selected destination without a visit, click consumption or notifications. Access gates still apply to real visits; fallback routing uses the latest saved health check. Check the country, region, language and User-Agent format. Test visitor: 1–254; UTC time: years 2000–2100.

Shared access requires permission to view metrics and an enabled tool for both the owner and current user. Enter one country, region and language code; the User-Agent determines the device and browser. Repeating a visitor number with the same User-Agent keeps the variant when rules are unchanged. Practice: give two ru rules the same priority and weights 1:1; test several numbers, then en and the main destination. Simulations create no visits, QR scans, conversions or destination versions. A future time does not simulate a future website outage. The JSON report contains schemaVersion, shortUrl, checkedAtUtc and findings with codes and severity levels; it contains no passwords or visitors’ personal details.

Checks the currently saved settings. It does not open the destination or guarantee availability. Resolve blocking conditions and review warnings before publishing; download the report as JSON.

There is no recent health check for the current destination. Review the health section and test the destination yourself. Some enabled routing rules have expired and are no longer selected. One priority contains both weighted and unweighted rules. When weighted rules match, unweighted options are excluded. Check audiences in the simulator.

No findings in the checked settings. Test a real visit and QR scan before publishing.

Complete user guide ยท Practical course

How to apply this section

Each topic explains a feature, the user decision behind it, and how to use it without making the link harder to manage. Read the checklist before changing a link that is already shared.

Before you publish or update

  • Start from the visitor experience: who opens the link, from where, on which device, and what should happen next.
  • Check that the destination is correct, opens quickly, and shows the expected page for the intended audience.
  • Choose only the controls that match the goal, such as expiration, password, referrer, QR design, UTM, routing, or analytics sharing.
  • Save a short note for important changes so future review, rollback, or teamwork stays clear.
  • Open the short link in a private browser session and, when relevant, test mobile, desktop, QR scan, and protected access paths.
  • Review analytics after sharing to confirm real visitors, source quality, device mix, and campaign performance.

Practical example

Example: create a test link for an internal page, add a clear slug, set a short expiration, enable preview if the destination is sensitive, scan the QR code from a phone, then check whether the visit appears in the link statistics.

Next step

After this topic is clear, combine it with one adjacent feature. For example, pair UTM with campaigns, QR with print layouts, targeting with fallback, or webhooks with conversion tracking.