Automate a weekly broken link check for your website

Links break quietly as pages move and other sites change. A scheduled agent reads your sitemap each week, checks the status of pages and their links, and drafts a list of broken ones that its department head reviews and you approve.

What you’ll set up

Connections

Works from public sources: Your public sitemap.xml and the pages it lists

Upgrades

Delivery (channel or inbox)

Delivers the approved report to your channel or inbox.

Inputs

Site address · Required

Text, no default

Domains to skip · Optional

List, no default

Ready by · Required

Time, default 09:00

Brief · Required

Text, prefilled and editable during setup.

Runs

Runs every Monday at 08:00

Done by Market researcher

You approve before anything goes out.

Set up this job

You approve every report · Free to start

How it runs

One agent does the work. Its department head reviews it, then you approve.

  1. 1Market researcher

    Runs every Monday at 08:00 and prepares the report from your connected sources.

  2. 2CMO · Review

    The department head reviews the report before it reaches you.

  3. 3You

    You approve before anything goes out.

What you get

Sample, not live dataSample broken link report (Sample, not live data)

Sample, not live data. The site, pages and links are invented.

Link check, week of 26 Oct (sample)

212 pages checked, 5 broken links, 3 redirects.

Found onLinkStatus
/blog/invoicing-tipsexample.org/old-guide404
/pricingexample.org/terms301 to /legal/terms

Fixes to consider (need your approval)

  1. Replace the 404 link with a current source or remove it.

Why links break without anyone noticing

Pages get renamed, other sites reorganise, and a link you added two years ago now ends on an error page. Visitors lose trust, and crawlers spend time on dead ends. Google documents how it handles status codes: a 404 means the content is gone, and a page that returns 200 while showing an error message may be reported as a soft 404. A regular check catches both before readers do.

How the scheduled job works

You add the job with your site address. Each week a scheduled agent reads your public sitemap, requests each page, and records its status code. It then reads the links on each page and requests those too, at a gentle rate, noting 404s, server errors, timeouts and redirects. It reports where each bad link sits so the fix is quick. Redirects are listed apart from errors, since the HTTP standard defines them as a different class of response. It reads public pages and changes nothing.

Review and approval

The CMO agent, as department head, reviews the report before it goes out: is a reported failure real or a one-off timeout, are redirects separated from errors, is each suggested fix sensible. Then you approve, edit or skip it, and nothing is sent until you do. Some sites block automated requests, so expect a few false alarms early on and note them in the brief.

Fixing what it finds

Start with broken links on your own pages that point to your own pages, because they are entirely yours to fix. Then update outbound links to current sources, or remove them if the source is gone. Redirecting links work but are worth updating when you next edit the page. Re-run the job after a site move or redesign, and keep an eye on the count: a sudden jump usually means one removed section or a changed address.

Questions

Start with one report

Set up this job

You approve every report · Free to start