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, it's just a few pieces stitched together.

This post walks you through building your own.

I'll cover:

The skill file (the brain).
The site setup (where content lives).
The deploy flow.
The indexing call.
The tracking sheet.

Save this as your DIY blueprint.

What You'll Build

By the end, you'll have:

A custom Claude Code skill that takes a keyword + transcript.
An automatic flow that writes 5 unique articles.
Auto-deploy to 5 sites.
Auto-submit to Omega Indexer.
Auto-update a tracking sheet.

Same workflow that took one of my sites to 12,700 clicks in 28 days.

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.
A Google Sheet for tracking.

If any of these is missing, set it up first.

Step 1 — Create The Skill File

Skills in Claude Code live in ~/.claude/skills/ (or your project's .claude/skills/).

Create a new file: seo-agent.md.

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 what the agent should ask for:

Keyword.
Video URL or transcript (optional but recommended).
Target sites (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.

Write down the exact rules you want every article to follow.

Examples:

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).
Word count (2,000+).

Be specific.

The more detail in the skill, the more consistent the output.

Step 4 — Multi-Site Logic

If you publish to multiple sites, list them in the skill:

## 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:

Different titles.
Different opening/closing lines.
Different examples and FAQs.
Not paraphrased — rewritten from scratch.

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 for each site.

If you're on Vercel, swap the deploy command.

If you use Hugo, swap the build command.

🔥 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 2,800+ members already running this. → Get the skill

Step 6 — Omega Indexer Submission

Tell the agent to submit URLs to Omega Indexer after deploy:

## 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".

This is what gets your content indexed by Google fast.

I cover indexing in detail in How To Rank In Google AI Mode.

Step 7 — Update The Tracking Sheet

After indexing, the agent updates a Google Sheet:

## 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.

Watch what the agent does.

Tweak the skill where the output isn't what you want.

Iterate 3-4 times.

This is the part that takes the longest.

It's also the part that determines content quality.

Common Build Mistakes

1. Vague rules in the skill.

The agent fills gaps with whatever it thinks is reasonable.

If you want consistency, be specific.

2. Skipping the test phase.

First skills are always rough.

Test on dummy keywords until output is clean.

3. Trying to do too much in one skill.

Keep it focused on SEO content.

Don't bundle in other workflows.

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.

Common upgrades I made:

Added internal-link logic (glob existing posts, pick relevant ones).
Added video embed checks (verify iframe in deployed page).
Added duplicate-slug protection (check for existing files).
Added retry logic for Omega Indexer submissions.
Added a "stop and confirm" step before overwriting existing posts.

Each upgrade made the skill more reliable.

Other Agents You Could Build

Once you've built one, the pattern is reusable:

A research agent.
A code-review agent.
A weekly-report agent.
A social-media-drafts agent.

Same pattern: skill file + agent + deploy logic.

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

What To Do After Build

Once your skill is working:

1. Run it on 5–10 keywords to refine.

Watch quality.

Tweak prompts.

2. Add tracking from day one.

Without tracking, you'll lose track of what's published where.

3. Scale gradually.

Don't push 50 keywords through on day one.

Start with 1 a day. 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. 2,800+ members already running their own SEO agents. → Join here

FAQ — Build Your Own Claude Code SEO Agent

How long does it take to build?

A working V1 skill: 2–3 hours.

A polished version: 2–3 weeks of iterating on real keywords.

Do I need coding experience?

Basic comfort with terminal helps.

The skill itself is plain English.

Can I use this without Claude Code?

The pattern works in OpenClaw, Hermes, or Claude direct — execution differs.

What's the most common build issue?

Vague writing rules in the skill.

The agent fills gaps inconsistently.

Can I share my skill with others?

Yes — skills are just markdown files.

How do I version control my skill?

Put the skill file in a Git repo.

Track changes the same way as code.

What if my output quality is bad?

Refine the skill rules.

Add specific examples of good output.

Iterate.