Claude Desktop supports multiple MCP connectors simultaneously. When you connect both IATO and WordPress, Claude can crawl your site, analyze it, and fix issues — all in one conversation. Add scheduled crawls and Claude's Loops feature, and you have a fully automated SEO monitoring pipeline.

Here's how to set it up and what's possible.

Step 1: Connect IATO via Claude Connectors

IATO's MCP server connects through OAuth — no config files or API keys to manage.

  1. Open Claude Desktop → Settings → Connectors → Add
  2. Enter https://iato.ai/mcp
  3. Click Add → Log in to your IATO account → Authorize

That's it. Claude now has access to IATO's 105 tools: crawling, SEO auditing, sitemap management, content analysis, scheduling, webhooks, and more.

Step 2: Connect WordPress via IATO MCP Plugin

The IATO MCP plugin turns your self-hosted WordPress site into an MCP server. Install it first, then connect Claude:

  1. Install and activate the IATO MCP plugin on your WordPress site
  2. In Claude Desktop → Settings → Connectors → Add
  3. Enter your site's MCP URL (shown in Settings → IATO MCP in WordPress admin)
  4. Authorize via the OAuth flow

Claude now has access to 29 WordPress tools: reading and writing posts, managing SEO metadata, controlling menus, organizing taxonomy, and bridging to IATO's analysis.

With both connectors active, Claude can chain tools across both systems in a single conversation.

Step 3: Set Up Scheduled Crawls

Instead of manually triggering crawls, set up a recurring schedule so IATO always has fresh data about your site.

Ask Claude:

"Create a weekly crawl schedule for my-site.com that runs every Monday at 6am"

Claude will use IATO's scheduling tools:

Weekly crawls are a good default. If your site changes frequently — daily posts, product updates, seasonal content — consider daily crawls. For mostly-static sites, monthly is enough.

You can also set up webhooks to get notified when crawls complete:

"Create a webhook that sends a POST to my-slack-webhook-url when crawls complete"

Step 4: Use Claude Loops for Monitoring

Claude's Loops feature lets you run a prompt on a recurring schedule. Combined with IATO and WordPress, this creates an automated monitoring and fix pipeline.

Example loop prompt:

"Crawl my-site.com, run an SEO audit, compare the results with last week's crawl, and fix any new meta description issues in WordPress. Summarize what changed."

Set this to run weekly, and Claude will:

  1. Start a crawl via IATO
  2. Wait for the crawl to complete
  3. Run an SEO audit
  4. Compare with the previous crawl to detect regressions
  5. Use WordPress tools to fix auto-fixable issues (titles, meta descriptions, alt text)
  6. Summarize what was found and what was fixed

This turns what used to be a manual weekly task into a hands-off automated workflow.

Workflow examples

Once you have both connectors active and scheduled crawls running, here are practical workflows you can automate:

Weekly SEO regression detection

"Compare my latest two crawls. Show me any pages where SEO scores dropped, any new broken links, and any new missing meta descriptions. Fix the meta descriptions in WordPress."

Claude uses compare_crawls to diff the results, get_seo_issues to identify regressions, and WordPress's update_seo_data tool to fix what it can.

Content freshness monitoring

"Find all published pages with a word count under 300. List them with their last-modified date and suggest which ones to update first."

IATO's get_wordpress_content_gaps tool identifies thin content with WordPress slugs. Claude can then open those posts and add content, or flag them for your review.

"Check my site for broken internal links. For each broken link, find the correct replacement URL from my sitemap and update the post in WordPress."

IATO maps broken links to source posts. Claude reads the sitemap for correct URLs, then uses WordPress tools to edit the affected posts.

New content publishing workflow

"I just published 5 new blog posts. Sync them to IATO, make sure they're in the sitemap, verify their SEO metadata is complete, and add them to the Blog menu."

Claude uses the sync tools to push new content to IATO, checks SEO via the bridge tools, and adds menu items via WordPress's update_menu_item tool — all in sequence.

Full site health check

"Run a complete health check: crawl my site, run an SEO audit, find orphan pages, check for broken links, identify thin content, and give me a prioritized list of fixes."

This combines multiple IATO tools into a single comprehensive report. Claude can then ask if you want it to apply the auto-fixable items through WordPress.

Tips for production workflows

Use dry_run before making changes. Several WordPress tools support a dry_run parameter that previews what would change without actually modifying anything. Use it the first time you run an automated workflow to verify the behavior.

Set up webhooks for notifications. IATO webhooks can POST to Slack, email services, or custom endpoints when crawls complete, scores change, or new issues are detected.

Review audit history. IATO tracks every SEO audit and crawl comparison. Use get_audit_history to see trends over time and verify that automated fixes are having the expected impact.

Start with a single workflow. Don't automate everything at once. Start with one workflow — weekly SEO regression detection is a good first choice — and expand from there once you're confident in the results.

Getting started

  1. Install the IATO MCP plugin on your WordPress site
  2. Connect both IATO and WordPress to Claude Desktop via Connectors
  3. Set up a scheduled crawl
  4. Try your first automated workflow

For the full tool reference, see IATO's MCP documentation.