Source: raw/I_Gave_Claude_Full_Control_of_My_Wordpress_Site_for_2_Weeks._Here_s_What_It_Did..md (main); raw/How_to_Connect_Claude_to_Google_Search_Console_and_Analytics.md and raw/5_Claude_MARKETING_Connectors_I_Can_t_Live_Without.md (connector stack and dashboard references)

Creator: Eliot Prince URL: https://www.youtube.com/watch?v=EQ0Mfpg-dnk Duration: 22:29 Platform: YouTube Published: 2026-08-15

Eliot Prince connects Claude to WordPress through an MCP plugin. He sets it up as a project-based agent with custom instructions, persistent memory and a weekly scheduled task, then tells it: “You are in charge. You are the content and SEO manager.” He reports two weeks of results on Cornish Vibes, a dormant Cornwall travel site, and then rebuilds the setup live on a second site (Cornwall Solar Company). The video was recorded before the September 2026 chat/Cowork merge, so “project with a folder” here means a local Cowork project, and its scheduled task needs the computer on. Everything below is Eliot’s reported experience, not an audited case study.

Key Takeaways

  • What Eliot says the agent did in two weeks:
    • audited 75 posts and pages, including the Yoast settings;
    • wrote and applied SEO titles and meta descriptions to all 75;
    • made “140 verified corrections” to two-year-old content — 11 businesses that no longer appeared to exist, 8 permanent closures, businesses listed in the wrong town — checking companies against Companies House;
    • published 11 new keyword-targeted posts in a voice learned from about 70 existing posts;
    • rebuilt the hub pages with 88 internal links;
    • produced an SEO strategy and an SEO dashboard. He reports a “massive impression spike” and new pages getting traffic within a week, without figures.
  • WordPress side, in order. Back up the site first (he uses “Updraft”). Upload the custom MCP plugin from his recipe vault and activate it. In its MCP settings, turn on the integration, enable “allow AI to write” (without it the agent is read-only), optionally enable “modify theme appearance” (theme and CSS edits), and scroll down and save: he hit a connection error because the toggles hadn’t been saved. Re-save permalinks. The plugin needs a non-plain permalink structure, and he warns not to switch away from “plain” unless you understand the SEO consequences. Load the plugin’s JSON endpoint in a browser: JSON means it is working, a 404 means it isn’t.
  • Give the agent its own WordPress user. Create a dedicated MCP agent user with the Editor role, not Administrator, and be logged in as that user when you authorise the connector, so OAuth links that account and not yours.
  • Claude side. Add a custom connector with the plugin’s URL, swapping in your domain. He named his CSC MCP. Connect and authorise, then leave the per-tool permissions on “needs approval” until you trust it. Test with a read-only prompt asking for post counts and media counts.
  • What turns the connector into an agent:
    • project instructions that give it ownership (“not an assistant waiting for instructions… you own the content strategy, the search performance and the email list”) and a mission (make the site the number one resource in its niche);
    • a voice file built from existing posts;
    • an index in memory of every ongoing task, so each session resumes where the last one stopped;
    • a weekly scheduled task that reads the instructions and memory, does the next block of strategy work, and writes back to memory what was done and what comes next.
  • It runs on the same connector stack as his other workflows. For the audit it uses DataForSEO, Apify (to scrape competitors), and Search Console plus Analytics through Composio. See the SEO project workflow and Connectors.
  • Escalation path. The weekly dashboard includes a “needs my attention” list of manual jobs, some of which he hands to Claude in Chrome. The scheduled-task prompt ends with “Don’t bother me unless it’s something manual that I have to go and execute.”
  • The dashboard is a live artifact with its own refresh task. It shows what needs attention, top queries, traffic quality, top pages, pages published or updated this week, upcoming actions and housekeeping, and a second scheduled task refreshes it every Monday at 9am.
  • How much autonomy is a choice. Eliot gives full autonomy on his own test sites. For client sites he suggests the alternative of “I’m going to manage the process, you’re going to execute.”

Try It

  1. Pick a low-stakes site you own and take a full backup.
  2. Install a WordPress MCP plugin (Eliot’s is distributed through his AI Recipe Vault). Enable write access, save, re-save permalinks, and check that the JSON endpoint loads.
  3. Create an Editor-role agent user, log in as it, add the custom connector in Claude and authorise it. Run a read-only check prompt.
  4. In a project, have Claude expand your instruction template (goal, autonomy level, voice file, task index in memory) and paste the result into the project instructions.
  5. Run one supervised session first: a full audit, a voice file from several posts, and a 12-month strategy executed week by week. Review what it changes.
  6. Only then add the weekly scheduled task, ending with “update memory with what’s been done and what’s next”. Keep risky tools on approval.

Implementation

Tool/Service: WordPress + a WordPress MCP plugin (custom, from the creator’s recipe vault; the video doesn’t name it) + a Claude custom connector + a project with a local folder + a scheduled task. Optional: Composio (GSC/GA), DataForSEO, Apify, Claude in Chrome. Setup: Back up → upload and activate the plugin → enable integration and write → save → re-save permalinks → verify the JSON endpoint → create an Editor user → add the custom connector while logged in as that user → write instructions → run an audit → schedule. Cost: Not stated for the plugin. Connector costs as in the SEO project article. Integration notes: In the video the scheduled task ran from a local-folder project (“we need to make sure our computer is actually switched on”). The wiki’s Cowork article records that cloud projects can now run scheduled tasks without the computer on, while local projects still need it. Moving this agent to a cloud project is untested here.

Risks worth weighing

  • Editor role still publishes. An Editor can publish and delete any post. If you want a draft-only gate, a lower role or the per-tool approval settings are the safer starting point.
  • Bulk factual edits need spot checks. “140 verified corrections” is the agent’s own count. Sample the edits before trusting a whole batch.
  • Compare with an engineered loop. WEO’s GSC Autonomous SEO Engine caps rewrites (never more than 40% of a page) and enforces crawl-aware cooldowns. Eliot’s agent has no stated guardrails beyond its instructions and the tool approvals.

Open Questions

  • Which WordPress MCP plugin is it? Its write scopes and authentication model aren’t shown beyond the toggle names.
  • Traffic outcomes: there are no Search Console figures beyond “impression spike”. A 90-day before/after would test the claim.
  • Does a local-folder agent like this survive the September 2026 merge unchanged, or does the “one-way door” for local projects (see Cowork) change the setup?