Build Your Own Claude Code SEO Agent (Step-By-Step)

A Claude Code SEO agent looks complicated from the outside, but when you build your own you realise it's just a few pieces stitched together with markdown. Most people pay for tools that wrap this exact pattern, but building it yourself takes a couple of hours and gives you a custom system you can extend forever.

This post walks you through building your own Claude Code SEO agent from scratch. I'll cover the skill file (which is the brain), the site setup (where content lives), the deploy flow, the indexing call, and the tracking sheet. Save this as your DIY blueprint and you'll have a working V1 by the end of the day.

What Your Claude Code SEO Agent Will Build

By the end of this guide you'll have a custom Claude Code skill that takes a keyword and a transcript, an automatic flow that writes 5 unique articles, auto-deploy to 5 sites, auto-submission to Omega Indexer, and an auto-update on a tracking sheet.

This is the same workflow that took one of my sites to 12,700 clicks in 28 days, so it's not a toy.

Prerequisites

Before you start, you need Claude Code installed (Desktop or CLI), one website you can deploy to (Netlify is easiest), an Omega Indexer account, and a Google Sheet for tracking. If any of these is missing, set it up first or you'll hit walls in the build.

Step 1 — Create The Skill File

Skills in Claude Code live in ~/.claude/skills/ (or your project's .claude/skills/). Create a new file called seo-agent.md and the header looks like this:

---
name: seo-agent
description: Write SEO articles for a keyword and deploy across multiple sites
user_invocable: true
---

Below the header you write the workflow in plain English. That's literally it. Claude Code reads your markdown and follows the steps.

Step 2 — Define The Inputs

In the skill, write down what the agent should ask for. The keyword is mandatory, the video URL or transcript is optional but recommended, and the target sites tell the agent where to publish.

Example:

## Step 1: Get the keyword and transcript

Ask the user: "What keyword do you want to target?"

Wait for their answer before proceeding.

If they have a related video, ask for the URL and transcript.

Step 3 — Article Writing Rules

This is the most important part of the whole build. Write down the exact rules you want every article to follow because the agent fills in any gap with whatever it thinks is reasonable, which is not what you want.

Be specific about tone (Hormozi-style, direct, no fluff), voice (1st person, UK grammar), structure (sentence per line, headers, bullet points), SEO requirements (keyword in first/last line, H2/H3, FAQs, internal links), CTA placement (3-4 throughout, personalised to topic), and word count (2,000+).

The more detail in the skill, the more consistent the output. Skimping here is where most agents fail.

Step 4 — Multi-Site Logic

If you publish to multiple sites, list them in the skill so the agent knows where each version goes:

## Sites

- Site 1: example1.com → /path/to/site1/posts/
- Site 2: example2.com → /path/to/site2/posts/

Tell the agent each article must be unique with different titles, different opening and closing lines, different examples and FAQs, and rewritten from scratch rather than paraphrased. If you've followed Claude Code AI SEO, this is the same approach scaled.

Step 5 — Deploy Commands

For each site, tell the agent exactly how to deploy:

### Site 1 deploy
1. Save markdown to /path/to/site1/posts/<slug>.md
2. Run: `cd /path/to/site1 && npx @11ty/eleventy && netlify deploy --prod --dir=_site`
3. Confirm deploy succeeded.

Repeat the pattern for each site. If you're on Vercel, swap the deploy command. If you use Hugo, swap the build command. The agent doesn't care what stack you're on as long as the commands are clear.

🔥 Want my full Claude Code SEO agent skill? Inside the AI Profit Boardroom, I share my exact skill file with all the rules pre-written. Plus an AI SEO course, weekly live coaching where I'll set up YOUR custom skill on a screen-share, and 3,000+ members already running this. → Get the skill

Step 6 — Omega Indexer Submission

Tell the agent to submit URLs to Omega Indexer after deploy because that's what gets your content indexed by Google fast:

## Step: Submit to Omega Indexer

After all sites deployed, navigate to https://app.omegaindexer.com/campaigns/create

Click "Copy & Paste Links"

Set Campaign Name: <keyword> - <month> <year>

Paste all 5 URLs (one per line) into the Links field.

Click "Create and Run".

I cover indexing in detail in How To Rank In Google AI Mode if you want the deeper background.

Step 7 — Update The Tracking Sheet

After indexing, the agent updates a Google Sheet so you don't lose track of what was published where:

## Step: Update Sheet

Open https://docs.google.com/spreadsheets/d/<your-sheet-id>

Find or insert a row with the keyword.

Fill columns: keyword, video URL, status=DONE, then 5 site URLs.

If you want a faster method, use the clipboard paste approach with a TSV row.

Step 8 — Test The Whole Skill

Don't just build it and run it on a real keyword. Test it first with a fake one and watch what the agent does step by step.

Tweak the skill wherever the output isn't what you want, and iterate 3 or 4 times before you trust it on real keywords. This is the part that takes the longest, and it's also the part that determines your content quality forever.

Four Common Build Mistakes

These are the mistakes I see people make on their first build.

1. Vague rules in the skill. The agent fills gaps with whatever it thinks is reasonable. If you want consistency, be specific about every rule.

2. Skipping the test phase. First skills are always rough. Test on dummy keywords until output is clean before letting it touch real work.

3. Trying to do too much in one skill. Keep it focused on SEO content. Don't bundle in other workflows or you'll end up with a skill that does several things badly.

4. Hard-coding paths. Use variables where possible so the skill is portable across machines.

Iterating On Your Skill

Once it's running, you'll find things to improve. The common upgrades I made over time were adding internal-link logic (glob existing posts, pick relevant ones), adding video embed checks (verify iframe in deployed page), adding duplicate-slug protection (check for existing files), adding retry logic for Omega Indexer submissions, and adding a "stop and confirm" step before overwriting existing posts.

Each upgrade made the skill more reliable, and the iteration cycle compounds across keywords.

Other Claude Code SEO Agent Variants You Could Build

Once you've built one skill, the pattern is reusable for almost any workflow. A research agent, a code-review agent, a weekly-report agent, a social-media-drafts agent — all use the same skill file plus agent plus deploy logic pattern.

I cover OpenClaw versions of similar agents in OpenClaw AI SEO.

What To Do After The Build Is Working

Once your skill is working, three actions to lock in the value.

1. Run it on 5 to 10 keywords to refine. Watch quality and tweak prompts based on real output rather than imagined output.

2. Add tracking from day one. Without tracking you'll lose track of what's published where, and the system breaks down.

3. Scale gradually. Don't push 50 keywords through on day one. Start with one a day and increase as confidence grows.

🚀 Want a guided Claude Code SEO agent build? The AI Profit Boardroom has the full skill template, weekly live coaching where we'll build YOUR version together, and an AI SEO course. 3,000+ members already running their own SEO agents. → Join here