Every growing web agency hits the same ceiling. The work that keeps client sites healthy, writing meta descriptions, adding alt text, proofreading pages, checking that SEO basics are in place, grows with every client you sign. Ten clients is manageable. Forty is a full-time job nobody wants. We wanted to take on more clients without hiring for more of the same repetitive maintenance, so we spent a week working out how much of it AI content automation could actually handle. Here is what we built and how you can copy it.
The Short Version: What AI Content Automation Covers
Yes, you can hand most recurring WordPress content maintenance to an AI assistant. Using Claude Cowork, we built five reusable skills that draft SEO metadata, image alt text, readability edits, proofreading fixes, and meta-tag QA. Each one reads a client site, then produces a review document a person approves before anything changes. Nothing publishes on its own.
Start by Sorting the Work, Not Automating It
The mistake is to grab the first task you think of and try to automate it. We started by listing every recurring job we do for clients and sorting it into four buckets by how ready it was for automation.
The first bucket was pure content and reasoning work that needs no special tools: SEO optimization, alt text for images, readability passes, proofreading, and confirming meta tags are present. The second needed a data connector, like pulling monthly Google Analytics or Ads figures. The third needed an extra tool, such as a page-speed API or a link checker. The fourth was judgment-heavy work like full website audits, where the AI drafts and a human makes the call.
We started with bucket one. It carries the most repetitive volume, and none of it requires anything beyond reading a page and thinking about the words on it. If you only automate one category this quarter, make it this one.
The Five Skills We Built
A skill in Cowork is a saved set of instructions the assistant follows every time you trigger it. Build it once, and it runs the same way forever, manually or on a schedule. We wrote five, each mapped to one recurring task.
SEO and meta optimizer. Drafts title tags, meta descriptions, and target keywords for a page.
Alt text writer. Views each image and writes descriptive alt text, marking purely decorative images as empty so screen readers skip them.
Readability pass. Improves clarity, tone, and structure without changing meaning.
Proofreader. Runs a final spelling, grammar, and consistency check.
Meta presence check. A fast audit that flags any page missing a title, meta description, single H1, or canonical tag.
Two design choices matter more than the skills themselves. First, every skill is read-only and draft-only. It reads the site and writes a document. It never touches the live pages. Second, the output is always a marked-up review file that shows the original, the proposed change, and a short reason. A person approves it. That keeps a human in the loop on everything a client will actually see, which is where you want the judgment to live.
Step 1: Give the Assistant Read-Only Access
The skills read content straight from WordPress using the REST API and an Application Password, which is built into WordPress core. You set it up once per site.
Create a user with the least privilege that can still read your content. An Editor role is plenty. Under that user's profile, generate an Application Password and name it something obvious like "content-readonly." Store it wherever you keep client secrets, not in any document the assistant produces.
You can confirm it works with a single authenticated request to the WordPress REST API, hitting an endpoint like /wp-json/wp/v2/pages with your username and application password. If you get JSON back, you are connected. If the request is blocked, a security plugin or server rule is probably filtering the REST API, and you can either allow it or fall back to a browser-based reading method.
One note on roles: never hand over an administrator account for this. Read access to published content is all these skills need, and scoping the credential down is the difference between a safe automation and a liability.
The Divi Wrinkle Worth Knowing
Many client sites run a page-builder theme like Divi, which stores page content as builder shortcodes. Pull a page raw and you get a wall of et_pb_section tags instead of clean copy. We wrote each skill to work from the rendered, visible text rather than the shortcode source, and to note which section an edit belongs to so the team can find it in the builder. If you use a builder theme, account for this or your first drafts will be full of markup.
Step 2: Run Each Skill by Hand First
Before automating anything, run every skill manually on two or three real client pages. This is where you tune it: adjust the tone, set your keyword rules, decide how aggressive the readability edits should be. You are teaching the skill your standards on cheap, low-stakes runs before you let it work unattended. Skip this and you will schedule a skill that produces confident, consistent, slightly wrong output.
A sensible order for a single page is to run the meta presence check to find gaps, optimize the metadata, improve readability, then proofread last.
Step 3: Put It on a Schedule
Scheduled tasks in Cowork use the same skills, so once a skill is tuned, a schedule runs it for you. Each run starts fresh, so the instruction has to name the site, the scope, and the output on its own.
The meta presence check is the best one to schedule first. Run it weekly per client as an early-warning monitor. It is cheap, and it surfaces the pages that need real work. The optimizer and alt-text skills fit a monthly cadence, or you trigger them whenever a client adds pages or images. Readability and proofreading are better run per deliverable than on a clock, since they respond to new content rather than the calendar.
One practical limit: scheduled tasks run while the app is open, and a missed run fires the next time you open it. Plan cadences around a machine that is actually on.
What We Left Out on Purpose
We stopped at drafts. None of these skills write back to the live site yet. Auto-publishing changes through the API is a real option, but it is a bigger risk and a later project, something you add only after months of trusting the review docs, and even then with a dry run and an approval step. Start with drafts. The time you save reviewing a good draft instead of writing from scratch is already most of the win. It pairs naturally with an ongoing website maintenance retainer, where the review-and-approve step already lives.
Was It Worth It?
The repetitive first-draft work is the bulk of the recurring hours across a client roster. Moving it to "the assistant drafts on a schedule, we approve" turned an hour of doing into a few minutes of reviewing per page. That recovered time is exactly the capacity you need to sign the next client without hiring for the same maintenance you just automated.
If you run a WordPress agency and you have felt that ceiling, this is a weekend of setup that pays back every month. Start with one skill, one site, and one manual run. If you would rather have us set the system up around your sites, book a free consultation and we will walk you through it.
Is It Safe to Give an AI Access to Client WordPress Sites?
It is as safe as the credential you give it. Use a read-only Application Password on a least-privilege user, never an administrator login, and the assistant can read content but cannot change or break anything.
Does This Publish Changes Automatically?
No. Every skill produces a review document showing the original and the proposed change. A person approves and applies it. Nothing goes live without a human.
Will This Work With a Page Builder Like Divi or Elementor?
Yes, as long as the skills read the rendered page text rather than the builder's raw shortcodes. Account for that when you set them up and the drafts come back clean.
Do I Need to Know How to Code?
No. The skills are written in plain instructions, and the only technical step is generating an Application Password in WordPress, which is a few clicks.
Related reading: What a Real Website Audit Covers · Content Marketing That Compounds · See also Website Maintenance and Website Audits.
