Four Claude Code systems run my entire SEO workflow under one roof: keyword research, a content writer, a site health audit, and a content refresher. They feed each other like an SEO team would, ship blog posts that follow the capsule content method, and run on a Monday 9am cron. One repo, four prompts, free organic traffic.
Why bother building an SEO system inside Claude Code?
Because most SEO tools force you to bounce between five tabs to ship one blog post, and the boring tasks (the ones that actually move rankings) are the ones you skip. I built four systems that connect under one roof and feed each other like an actual SEO team would. The result on one site was 14.4M impressions and 90,000 organic clicks. Two newer sites started pulling organic traffic the week they launched.
No ads, no agency, no five-tool stack. Just Claude Code running the work.
And this matters more in 2026 than ever, because AI search engines now convert roughly five times better than traditional organic traffic, but only if your content is structured to be cited. These systems are what get you there without burning a weekend.
What are the 4 Claude Code SEO systems?
The four systems are keyword research, a content writer, an on-site audit, and a content refresher. Each one is a skill Claude Code can run on command, and each one outputs into a shared dashboard so the next system knows what the previous one did.
- System 1 — Keyword research: Builds a keyword bank + fan-out cluster + content queue. Run once a month.
- System 2 — Content writer: Drafts ranking-ready blog posts using the capsule method. Run weekly.
- System 3 — On-site audit: Pulls a full health report via DataForSEO. Run fortnightly.
- System 4 — Content refresher: Flags decaying or de-indexed posts to rewrite. Run monthly.
The trick is they share state. The keyword researcher knows what's already been covered, so the content writer can't cannibalise itself. The audit knows which pages exist. The refresher knows which ones are dying.
What do you need before you start?
You need a project folder, Claude Code, and a DataForSEO key. That's it.
- A project folder on your local machine with your business info inside (services, locations, brand voice, USPs)
- Claude Code installed (desktop app or CLI, which I prefer for SEO automations)
- A free DataForSEO account (this link gives you $5 free credit instead of $1, pay-as-you-go after that)
- The GitHub repo with all four systems pre-built: github.com/NicoSKOOL/the-four-systems
Hand Claude Code the repo link and tell it to install the systems for this business. Eight to ten minutes later, all four skills are wired up and pulling your business context. Auto-mode helps here so it stops asking permission every 30 seconds.
If you've never connected Claude Code to MCP servers before, watch my SEO Command Center setup video first, then come back.
How does System 1 (keyword research) work?
You type a service or topic, and Claude Code runs the keyword research skill, builds a fan-out cluster, and saves it to a dashboard.
In my example I ran it for “therapeutic gardening”. A couple of minutes later I had 31 keywords, a CSV file, and a live HTML dashboard. The dashboard has two things that matter:
- A keyword bank of every keyword in the cluster, with status flags so Claude knows which ones it's already targeted (this is what stops content cannibalisation)
- A fan-out cluster of supporting keywords that should appear as H2s or H3s inside the eventual blog post
So by the time System 1 is done, System 2 already knows exactly what to write and which headings to use. You only need to run keyword research once a month, or whenever you run out of content.
This is the same fan-out logic Google's AI uses to decide what to cite, which is why fan-out queries are the unlock for ChatGPT citations too.
How does System 2 (the content writer) write ranking blog posts?
You tell Claude Code “write the next blog post”. It pulls from the keyword bank, drafts a post using the capsule content method, and outputs an MD file or publishes directly to your site.
Specifically, the content writer does six things automatically:
- Injects your experience from the business files (first-person stories, real numbers, anything that smells like E-E-A-T)
- Targets the primary keyword in the title and an H1, and the fan-out keywords in H2s and H3s
- Writes ~70% in the capsule method (H2s phrased as questions, answered in the first one or two sentences)
- Cites high-trust sources like government domains, official health bodies, primary research
- Internally links across the site because it reads your sitemap
- Adds a TL;DR block at the top, which is now best practice for getting cited by AI search
If your site is built on Astro, the post publishes itself to the live site without you ever opening a CMS. If you're on WordPress, you get a clean MD file to paste in, and the WordPress REST API can automate that part too.
Community win: Inside the AI Ranking community, Steven used a version of this exact workflow to index more than 800 local service pages, which generated 105 booked appointments in a single month from organic traffic alone. No ads.
Don't worry about making posts longer. Worry about making them better. The content writer was tuned for citation-readiness, not word count.
How does System 3 (the on-site audit) work?
You run “audit the site”, Claude Code calls DataForSEO, and you get a full health report inside the dashboard with prioritised fixes.
On the test site, it returned an on-page score of 97/100 and an SEO score of 99/100, plus a list of broken links and slow pages to fix. Total DataForSEO cost: about 48 cents. With the $5 free credit, you can run this 10 times before paying anything.
The audit also tells you exactly which fixes to do first. If your site is on Astro and Claude Code can edit it directly, you can tell Claude to fix them for you. If you're on WordPress, you do the fixes manually but at least you know what to fix.
Run this once a fortnight, definitely once a month. Most people skip on-page audits because the data is overwhelming. Claude's job is to do the distilling for you.
How does System 4 (the content refresher) work and why does nobody run it?
The content refresher reads your Google Search Console data, finds blog posts that are decaying or de-indexed, and tells you exactly which ones to rewrite. Almost nobody runs this, and it's the highest-ROI system of the four.
Here's why it matters: only around 60% of the blog posts you publish stay indexed. Google has been getting much stricter about what it keeps in its index, and “crawled, currently not indexed” is Google's passive-aggressive way of saying it read your content and didn't think it was worth keeping.
When you run run refresh recommender, Claude:
- Pulls your Search Console coverage data
- Flags pages that are decaying in rank or dropped from the index
- Tells you whether to rewrite, merge, or kill each one
- Optionally rewrites the page using System 2 so the new draft inherits your business context and the capsule method
This is the half of the job most people skip. Generating new content is only 50% of SEO. The other 50% is keeping the content you already have alive.
How do you put all four systems on a schedule?
You tell Claude Code to turn the workflow into a routine, and it sets it as a local automation.
The simplest version is one sentence:
“Set this workflow to run every Monday at 9:00 AM.”
Claude Code registers it as a routine. If you're using the desktop app, the catch is that your computer has to be on at run time. If you're using the CLI, you can run it as a cron job in headless mode, which is what I do across multiple sites.
If you want this fully cloud-based, you'd need to move the MCP connections (Search Console, DataForSEO) to the cloud too, which is more setup than most people want. Local cron is the 80/20.
And yes, before you ask, this all works in Codex with GPT-5.5 too. Same architecture, different runtime.
Frequently Asked Questions
Do I have to use Astro for this to work?
No. Astro just lets Claude publish posts directly without touching a CMS. WordPress, Webflow, Framer, all work, you just plug into their APIs or paste the MD file manually.
How much does DataForSEO cost to run all four systems?
The on-site audit was 48 cents per run on a small site. Keyword research is a few cents per cluster. Even if you ran the full stack weekly, you'd burn through the free $5 credit in a couple of months.
Can I run this in Codex instead of Claude Code?
Yes. I have a full walkthrough on running the same workflow with Codex and GPT-5.5. The systems are agnostic, the runtime isn't.
What's the capsule content method?
A blog structure where every H2 is a question and the first sentence answers it directly, so AI search engines can lift the answer cleanly. Full breakdown here.
Will the content writer trigger an AI penalty?
No. Google has publicly said AI content is fine when it's helpful. The reason this workflow doesn't trip penalties is the business context injection, the source citations, and the capsule structure. That's what “helpful” looks like.
Want me to set this up for you?
If you'd rather skip the wiring step and learn this inside a community of people running it in production, AI Ranking is where the full workflow lives. Live SEO audits every Thursday, weekly tutorials on systems like these, and a private repo of the agents, skills, and prompts I use across every site.
Resources
