Run a WordPress Site Health check with Automatio

Ask the agent to perform a Site Health check or list your plugins. You receive a report of critical issues and site status fetched through the WordPress REST API.

What to ask

Type it in the Automatio chat. Send it as written, or change the details to fit your case.

Run a Site Health check on [my-site-url]. List the active plugins and tell me if there are any critical errors or recommended improvements reported by WordPress.

How it works

  1. 1

    Connect your site

    Go to Integrations and Apps in Automatio, select WordPress, and type in your site's address.

  2. 2

    Authorize the agent

    Sign in to your WordPress site when prompted and press Approve to grant access without installing a plugin.

  3. 3

    Request the check

    Open the chat and ask the agent to run a health check or list plugins for your connected site.

What you get

The agent sends back a text report summarizing your site's health. It includes critical alerts, recommended improvements, and site details like the active plugin list. Check these results before you head to your dashboard to make manual changes.

Good to know

  • The agent cannot update plugins or themes even if the Site Health check recommends it.
  • Your site must have application passwords enabled and cannot be behind a firewall that blocks server traffic.
  • The agent's work uses credits from your account, though the integration itself costs nothing beyond that usage.

Variations to try

Verify page rendering

Check that the homepage of [my-site-url] renders correctly and report any critical health warnings.

Audit active plugins

List all plugins installed on [my-site-url] and identify which ones are currently active.

Questions

Does this fix site errors?

The agent reports issues found by the WordPress Site Health tool but cannot edit files or run updates to fix them.

Is a plugin required?

No plugin is installed; the agent connects using the built-in WordPress REST API and application passwords.

Can it check private pages?

The agent can verify that public pages render correctly, but it cannot access pages that are restricted to logged-in users or behind a firewall.

More guides