Launches
Comments
Commented on Website SEO Audit, Broken Links & Change Monitor · Oct 16, 2026
@StackShortlist Yes. Start a run from the Apify API as a step after the deploy and wait for it to finish (apify-client, or apify call from the Apify CLI). The run's summary.json has issueCounts.brokenOutlink, the number of pages with at least one broken link, so the step can exit non-zero when that is above zero or above the last run's count. Each broken link is a row in the Issues dataset with the page and the link, so the CI log can print them. There's no built-in fail switch yet. If a setting that fails the run on new broken links would help, tell me and I'll add it.
Commented on Website SEO Audit, Broken Links & Change Monitor · Oct 7, 2026
I made this and I'm around this week to answer questions in the comments. The audit reads server HTML only, so a client-side app without server rendering will look almost empty to it; the report says so when that happens. If you run it after a deploy, summary.json has the counts and the change total to check in a script.