Automated Glitch Project Link Checks
Every Monday, WebRun signs into Glitch, lists your projects and the public links you still point people at, opens each link to see whether it loads, redirects, or fails, opens a Trello card for every dead link with the page it is published on, and sends your team a WhatsApp summary of what broke.
How do I find the published project links that no longer work?
Every Monday, WebRun signs into Glitch, lists your projects and the public links you still publish, and opens each one to see whether it loads, redirects, or fails. It raises a Trello card for every dead link with the page it sits on, and sends your team a WhatsApp summary of what broke.
- Readers stop landing on links that go nowhere
- Every dead link gets a card naming the page to fix
- Redirects are reported separately so urgency stays honest
Built for developers · technical writers · open source maintainers · developer relations teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
glitch.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Glitch - list projects and their links
glitch.com
WebRun opens Glitch to list projects and their links. - Sign into Glitch and list the projects on your account with their names
- Collect the public link for each project you still reference publicly
- Add any Glitch links from the source list you keep, such as docs pages, README files, and posts
- Open each link and record whether it loads, redirects somewhere else, or fails to resolve
- Note where the project now lives if you have recorded a replacement location
Done when Every published Glitch link has been opened and marked working, redirected, or dead.
-
2
Trello - raise a card per dead link
trello.com
WebRun opens Trello to raise a card per dead link. - Open a Trello card for each link that no longer resolves
- Put the dead link, the project name, and the page it is published on in the card
- Add the replacement location if one is known, so the fix is a copy and paste
- Skip creating a duplicate card for a link already sitting on the board
- Leave the doc edit to a person. WebRun raises the card, it never publishes a change
Done when Every dead link has a Trello card naming the page that needs editing.
-
3
WhatsApp - send the weekly link report
whatsapp.com
WebRun opens WhatsApp to send the weekly link report. - Send this week's link report to your developer group on WhatsApp
- Give the counts: links checked, still working, redirecting, and dead
- List the dead ones with the page each sits on so ownership is obvious
- Call out anything that broke since last week rather than repeating the whole list
Done when The group has this week's counts and the newly broken links.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it edit my docs or README files?
No. WebRun finds the broken links and raises a Trello card naming the page each one sits on. Editing a doc or publishing a correction stays a human action.
Where does it get the list of links to check?
From your Glitch project list, plus any source list you give it once: doc pages, README files, or posts where you still point people at a project.
What about links that redirect instead of failing?
They are reported separately from dead links. A redirect still works for readers today, so it is worth knowing about without being treated as urgent.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.