Automated Moz Crawl Issue Triage
Every Monday, WebRun opens your Moz campaign, reads the latest site crawl issues, groups them by issue type and cross-checks the affected pages against your tracked rankings, posts a ranked fix list to Microsoft Teams for the developers, and sends you a short Telegram summary of what changed since last week.
How do I turn Moz crawl issues into a weekly fix list?
WebRun triages your Moz crawl issues every Monday. It reads the latest site crawl, groups issues by type, checks which affected pages carry tracked rankings, and posts a ranked fix list to Microsoft Teams with example URLs, then sends you a Telegram summary of what is newly broken and what was fixed.
- Developers get a ranked fix list instead of a raw issue count
- Issues on ranking pages are worked first
- You can see week over week whether crawl health is improving
Built for SEO specialists · digital marketing agencies · content teams · web developers
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
moz.comin a real browser with your saved login - no setup, no API keys. -
1
Moz - read the week's crawl issues
moz.com
WebRun opens Moz to read the week's crawl issues. - Open your Moz campaign and go to the latest site crawl
- Group the issues by type, keeping critical crawler errors separate from warnings and notices
- Record the affected pages for each issue type and how many there are
- Check which of those pages carry tracked rankings or sit in your priority page list
- Compare against last week's crawl to see which issues are new, which were fixed and which are growing
Done when Every crawl issue is grouped by type, matched to its pages, and marked as new, fixed or ongoing.
-
2
Microsoft Teams - post the ranked fix list
microsoft.com
WebRun opens Microsoft Teams to post the ranked fix list. - Post a ranked fix list to your SEO and web development channel
- Put issues affecting ranking pages at the top, then issues by how many pages they hit
- For each item give the issue type, the page count, two or three example URLs and what the fix involves
- Keep it to the top items a developer can realistically pick up this week rather than the full issue dump
Done when The development channel has a ranked, page-level fix list for the week.
-
3
Telegram - summarise what changed
telegram.org
WebRun opens Telegram to summarise what changed. - Send yourself a short summary of the week's crawl
- Give the total issue count and how it moved against last week
- Name what is newly broken and what was fixed since the previous crawl
- Flag any issue type that is growing week over week
Done when You have this week's crawl movement summarised in Telegram.
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 change anything on my website?
No. WebRun only reads the crawl results in Moz and writes a fix list into Teams. It never edits a page, a redirect, a tag or a robots file, so every fix is made by your developers in your own codebase.
How does it decide which issues matter most?
It ranks by whether the affected pages carry tracked rankings or sit in your priority page list, then by how many pages each issue type hits, so a broken title on a ranking page outranks a notice spread across low value pages.
Will it repost the same issues every week?
No. Each run compares the new crawl against the previous one and marks issues as new, fixed or ongoing, so the Teams list leads with what actually changed rather than repeating a static backlog.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.