Skip to content

FeaturesBuild

Know it works before your users do

Most broken deep links are a file Apple or Google can't read. The checks fetch those files the way the phones do, on a schedule, and say what they found.

Health

Your link addresses, tested the way Apple and Google test them.

90%set up: 9 of 10 steps done

Next: Release the app update that adds go.runclub.app.

apple-app-site-association is served

200 · application/json · no redirect

go.runclub.appPass

The file lists your app

ABCDE12345.app.runclub.ios

go.runclub.appPass

assetlinks.json matches the signing key

sha256 7C:1A:…:9E, Play App Signing

go.runclub.appPass

The alternate address opens the app

Listed in the app's associated domains

runclub-alt.dl2.appPass

Apple's copy of the file is current

Apple's CDN last fetched it 26 hours ago

go.runclub.appCheck
The real dashboard, with example data.

How it works

  1. 01

    The setup guide lists each step

    With a score, and the next thing to do.

  2. 02

    Checks run on every link address

    Including apple-app-site-association and assetlinks.json, on your dl2.app hosts and your custom domains.

  3. 03

    You are told when something breaks

    An alert when a check that passed starts failing.

What is included

  • Scheduled checks from once a day on the Free plan to every 15 minutes.
  • Test links that last an hour and show what each kind of device would do, without changing anything for real visitors.
  • A public link checker: paste any app link, yours or someone else’s. No account needed.
  • A list of what to try in each in-app browser.

Where it stops

  • Scheduled checks and their alerts stop while a team is read-only for non-payment. Links keep redirecting.
  • A check can read the files, not your installed app. An app update that drops a domain still has to be tested on a phone.

The detail

Start with one link

The free plan has no time limit and needs no card. Create a project, add your app, and send yourself the link.

Setup health checks · DL2App