Skip to main content

AI Jobs: maintenance that asks first

Jobs are the recurring maintenance you would rather not remember. You add one from a card, run it now or put it on a schedule, and read the result in plain English. Four jobs run end to end today.

  • Find broken links — collects the links from your recent posts and pages, checks each one with a real request, and reports what is broken with its status code, marking internal and external separately. Read-only.
  • Security scan — checks the things that quietly stay wrong: debug output exposed to visitors, a stray debug.log, the built-in file editor left enabled, a user called "admin", open registration handing out a privileged role, a site URL still on HTTP, and outdated core, plugins or themes. Read-only.
  • Check for updates — lists every pending plugin, theme and core update with its current and new version, read from WordPress's own check, so there is no network wait.
  • Clean up the database — scans for old revisions, auto-drafts, spam, trash, expired transients and orphaned meta, then stops and waits for you.

How the safety and the schedule work:

  1. Anything that changes your site goes to Approvals first. The job pauses, shows what it found, and applies nothing until you approve. Deny it and the run closes with the reason recorded.
  2. Set each job to Manual, Daily or Weekly. Scheduled runs go through WP-Cron and drop their results into Reports on their own.
  3. Activity is a live timeline of every step, newest first, and Reports keeps the plain-English result of every run — what was checked, what passed, what needs attention.

Full guide: Jobs