Content use case
Scheduled WordPress audits, that run while nobody is connected.
An audit only helps when someone remembers to ask for it. A routine in GoBuildWP Free asks for you: the accessibility, content and alt-text audits run on WP-Cron at an hour you choose, each run is compared with the one before, and the administrators you pick get a short email saying what is new and what was fixed.
GoBuildWP Free, Works in Claude Code, Runs under Production Safe, Pricing
Illustrative ability sequence for GoBuildWP Free 1.18.6. IDs, results and recovery outcomes are examples, not a recorded client or WordPress test. Select Read Only explicitly for the initial reads; Production Safe is the default. Connection management requires manage_options on a single site or superadmin on multisite.
The problem
Why the audit you run by hand finds problems late
A broken link does not announce itself. A page is renamed, an image is replaced by one with no alt text, a plugin update changes a heading level, and nothing on the site says so. The first person to notice is usually a visitor, a screen-reader user or a search console report weeks later.
GoBuildWP Free performs bounded accessibility checks, scans media for missing alt text and audits content for broken links, orphans and missing descriptions. These checks do not establish WCAG conformance. Free also supports scheduled audit routines and several basic fixes, including media metadata and basic per-post SEO; Pro adds deeper plugin-aware and planned repair workflows. Routines persist configuration and reports, can send email, and depend on WP-Cron execution.
What Claude Code can do here
- Run audit-accessibility on up to ten pages: named URLs, the front page and the top pages from the menus
- Run audit-content over the whole site as a background job, with checks such as broken_links, orphans, seo_meta and schema
- Run audit-media-alt over up to 500 library images
- Compare each run with the previous one, audit by audit: new, resolved and changed issues
- Email a plain-text summary with a link to the report to administrators chosen by user id
- Show every routine's schedule, next run and last result on a Routines screen under Activity
What it cannot do
- Rewrite site content or apply repairs. The routine stores configuration/reports and can send notifications; its audit allowlist does not authorize content fixes
- Email an address an agent types. Recipients are administrators picked by user id, re-checked when the email is sent
- Rank pages by traffic. Top pages means menu pages first, then pages by menu order, because the site has no traffic data to rank by
- Fix what it finds. That is content fixes, the alt-text abilities or a person
- Run on time on a site with no visitors if WP-Cron waits for traffic. A real cron job calling wp-cron.php fixes that
The prompt
The prompt to paste into Claude Code
Paste this into Claude Code with GoBuildWP connected. It sets up one weekly routine, runs it once, and reads the first report back so you know it works before Monday.
- Step 2 names users, not addresses: a routine cannot email anyone who is not an administrator.
- Step 4 matters because the content audit is a background job that finishes over several cron ticks.
- The first report has nothing to compare against; the diff starts with the second run.
Create only this weekly WordPress audit routine; do not modify content or settings outside it.
1. Run routines-list and show me the administrators and the site timezone.
2. Save a routine called "Monday site check": weekly on Monday at 07:00 site time.
- audit-accessibility on the front page and the top 5 pages
- audit-content with checks broken_links, orphans and seo_meta
- audit-media-alt
Email only the administrators I name, by user id.
3. Run it once now with routines-run-now.
4. Poll routines-list until the run has finished, then read routines-report.
5. Summarise the findings by severity. Do not fix anything.Under the prompt
The abilities Claude Code will call
Registered GoBuildWP abilities, each with its own schema and permission check. The live ability list on your site is the final word; the tool map lists every group.
routines-listRoutines with schedule, next run, run in progress and last result, plus the administrators to choose from
routines-saveCreates or updates a routine: audits, daily or weekly schedule, recipients and run-as user
routines-run-nowQueues one run outside the schedule; refused while one is running
routines-reportThe last runs, each with a diff against the one before
routines-deleteRemoves a routine, its schedule and its reports; undoable
audit-accessibilityWCAG 2.2 checks on the HTML a logged-out visitor receives
audit-contentBroken links, orphans, thin content, missing descriptions and schema problems
audit-media-altImages with missing or file-name alt text
Safety and recovery
A schedule that can only read
- Safety profile
- Saving a routine is a write, so Production Safe. The runs themselves go through the site's safety profile and every gate as the administrator the routine names, because WP-Cron runs as nobody.
- Change ledger
- Saving, deleting and running a routine now are recorded in the change ledger. The audit calls a routine makes are not, because they only read.
- Rollback
- Undoing a save restores the routine's previous definition; undoing a delete brings the routine and its reports back and reschedules it. A run has nothing to undo.
- #3120Routine "Monday site check" savedRollback available
- #3121Run now queued for "Monday site check"Recorded
- #3187Routine "Old weekly check" deletedRollback available
What a routine keeps, and for how long
- The last 20 runs are kept per routine, and only the newest keeps its full issue list.
- Each audit stores at most 300 issues; a comparison that hit the cap is marked approximate.
- A run advances 20 seconds per cron tick and saves its place. One still unfinished after three hours is closed with its open audits failed.
- The email is plain text with counts and a link: no page content, titles or personal data.
- Run now is refused while a run is queued or in progress, and for 10 minutes after the last one started by hand.
How profiles, confirmations and rollback fit together: safety profiles and the change ledger.
Setup
Set up routines from Claude Code
Claude Code configures the routine once. After that the site runs it on its own, with Claude Code closed.
GoBuildWP Free runs every audit a routine uses and the routines themselves: the schedule, the stored reports and their comparison, the email and the Routines screen.
Pro adds the next step: content fixes for what a run finds, safe updates behind a fresh backup, and an approval queue.
Install GoBuildWP Free
The audits, routines, reports and the email all ship in the free plugin, with nothing else to install. Routines saved earlier with Pro keep running unchanged.
Check WP-Cron
routines-list says whether WP-Cron is disabled. On a quiet site, point a real cron job at wp-cron.php so a run starts on time.
Connect Claude Code
Add the server with the command from GoBuildWP's Connect screen, then run /mcp to sign in.
Save and run once
Use the prompt above, then read the first report before trusting the schedule.
Watch the Routines screen
Under Activity in wp-admin: each routine's next run, last result and a Run now button.
Reading the report after setup
A saved schedule is not evidence that an audit ran
Check the site timezone and selected administrator recipients before saving the routine. Then queue a first run and inspect its final report. A next-run timestamp only describes the schedule: WP-Cron still has to execute, the audit has to finish and the chosen mailbox has to receive the notification.
Keep the first completed report as a baseline. On later runs, distinguish newly found issues, resolved issues and unchanged findings. A smaller issue count is meaningful only when the audited scope stayed comparable; a skipped page should not look like a repaired page.
- If a run is late, inspect WP-Cron configuration and execution with the host. Do not repeatedly queue work while a run is still in progress.
- If the report exists but no email arrives, confirm the selected recipient and check mail delivery separately. The report and its notification are different results.
- If the report flags missing alt text, review informative and decorative uses with the image alt-text workflow. Accessibility findings need context, not automatic rewriting.
- Keep repairs in a separately reviewed session. These scheduled accessibility, content and media-alt checks are not a complete security review or an automatic repair service.
FAQ
Questions about how to run scheduled WordPress audits
Can WordPress run an accessibility audit automatically?
With GoBuildWP Free, yes. A routine runs the WCAG 2.2 check on up to ten pages, plus the content and alt-text audits, daily or weekly at an hour in the site's timezone, and emails what changed since the last run.
Does a routine need an AI client connected?
No. An agent sets it up, or anyone who can call routines-save, and after that WP-Cron runs it on the server with no AI provider involved. The run sends the email to the administrators you chose and requests the site's own pages for the accessibility and schema checks. If you add the optional external_links check to the content audit, it also sends HEAD requests to the other sites your posts link to.
Can a routine fix the problems it finds?
No, deliberately. It can only run the three read-only audits, so it never meets an approval hold or the fresh-backup requirement and cannot change a page. Fixing is a separate, reviewed step, such as content fixes for broken links.
Is this the only WordPress MCP server with scheduled tasks?
No. Flex MCP, for one, documents scheduled AI tasks from hourly to monthly (as of 29 September 2026). GoBuildWP's routines are narrower on purpose: fixed read-only audits with a comparison against the last run, rather than arbitrary prompts on a timer.
Try it on staging first.
Install the free plugin, connect Claude Code, and run the read-only half of this prompt before anything on the site changes.