This website gets 90,000 clicks a month from organic traffic alone.
No ads. No agency. No paid promotion.
Just four Claude Code systems running practically on autopilot.
And two other websites started getting organic traffic from the day they launched.
Most people think SEO requires a team, expensive tools, and months of manual work. It does not. It requires the right system. A system that does keyword research, writes content, audits your site health, and refreshes old content all connected under one roof, all feeding into each other, all running automatically.
Here are the complete Claude Code SEO system that ranks website 👇🏻👇🏻
Step 1 — Set up your business information folder as the foundation
Everything this system produces — keywords, blog posts, audit reports, refresh recommendations — is only as good as the business context Claude Code starts with.
Create a folder on your local machine. Name it after the business.
Inside it, put every piece of business information you have:
✅ The website URL
✅ List of all services with descriptions
✅ Target audience (who the ideal customer is, their pain points, their language)
✅ Business location (important for local SEO)
✅ The business story and any unique experience or expertise worth mentioning
✅ A list of all internal pages and their URLs (so Claude can internally link correctly)
✅ Any existing blog posts or content already published
✅ Competitors you are aware of
✅ Any keywords you already know you want to target
Why this matters more than most people realize:
When the content writer system runs, it injects real business context into every blog post. If the business owner has 15 years of experience in therapeutic gardening, that gets mentioned. If the business serves a specific city or region, that gets woven in naturally. If the business has a unique methodology, that becomes the differentiator in the content.
Generic AI content that anyone could write does not rank well in 2026. Specific, experience-driven content that only this business could authentically produce does rank. The business folder is where that specificity lives.
Step 2 — Clone the four-system GitHub repo and install everything in one prompt
All four systems are pre-built and available in a GitHub repo. You do not need to set each one up individually.
How to do it:
✅ Open Claude Code (Desktop application or CLI)
✅ Set the working directory to your business folder
✅ Copy the GitHub repo link (linked in the description)
✅ Paste this prompt:
"I want to set this up for this business that I am doing work for in this folder. Can you read all the business information in this directory, clone this GitHub repo [paste repo link], install all required dependencies, and extract as much business context as possible so you are ready to run all four SEO systems?"
✅ Enable auto mode (the equivalent of dangerously skip permissions)
Why auto mode matters:
Without auto mode, Claude Code stops and asks for permission at every step. "Can I access this repo? Can I install this package? Can I read this file?" Each pause breaks the momentum and turns a 10-minute setup into 45 minutes of clicking approve.
With auto mode, Claude Code reads your business folder, clones the repo, installs the four systems, and reports back with a summary of the business context it extracted.
Wait 8–10 minutes. Come back to a fully installed four-system SEO operation ready to run.
What Claude installs:
✅ Keyword researcher with DataForSEO connection
✅ Content writer with business context loaded
✅ On-site auditor
✅ Content refresher with Google Search Console connection
✅ The unified dashboard that tracks everything
Step 3 — Run the keyword research system first — it powers everything else
Type: "Research keywords for [your target service or topic]."
Example: "Research keywords for therapeutic gardening."
What happens:
✅ The keyword research system connects to DataForSEO
✅ It pulls every relevant keyword variation for the topic
✅ It scores each keyword by search volume, keyword difficulty, and opportunity
✅ It identifies the primary keyword to target
✅ It identifies the fan-out cluster — the related H2 keywords that should appear in the blog post
✅ It saves everything to a CSV file
✅ It updates the dashboard with the full keyword bank
What the dashboard shows after running:
✅ Total keywords identified (the example run found 31 keywords)
✅ Keywords in queue (not yet written about)
✅ Keywords covered (already have a blog post targeting them)
✅ Keywords in progress (currently being written)
✅ Fan-out clusters for each primary keyword
The fan-out cluster is what most content writers miss:
When you target "therapeutic gardening," the H2 questions inside that blog post should cover the related keywords people also search for — "benefits of gardening for mental health," "therapeutic gardening programs," "how to start therapeutic gardening." These are not separate blog posts. They are sections inside the primary blog post. The keyword research system identifies all of them automatically.
When to run this system:
Once a month or when you run out of keywords in the content queue. Not every week. The dashboard manages the queue automatically so you know exactly when you need to refill it.
Step 4 — Understand content cannibalization and how the system solves it
Content cannibalization is one of the most common SEO mistakes and almost nobody catches it until the damage is done.
What it is:
You write a blog post about "therapeutic gardening benefits." Three months later you write another one about "benefits of therapeutic gardening." Both posts target essentially the same keyword. Google sees two pages on your website competing for the same search query. Instead of one strong page ranking in position 3, you have two weak pages ranking in positions 14 and 22. Neither wins.
Most websites doing regular content production have multiple cases of this and do not know it.
How the dashboard prevents it:
Every keyword the system identifies gets one of three statuses:
Queued: not yet written, available for the content writer to pick
In progress: currently being written
Covered: a blog post has been published targeting this keyword
When the content writer runs, it reads the dashboard first. It will only pick keywords with "queued" status. It cannot accidentally write about a covered topic because the dashboard explicitly marks it as done.
The dashboard also shows the fan-out cluster for each primary keyword — the related questions covered inside each blog post. This means even subtopics are tracked, not just primary keywords.
After you publish the example blog post on therapeutic gardening, the dashboard updates automatically to show it as covered. The next time the content writer runs, it skips that keyword entirely and moves to the next queued one.
This is the difference between a system and just using Claude as a writing tool. The system remembers. Claude alone does not.
Step 5 — Run the content writer system to publish SEO-optimized blog posts
Type: "Write the next blog post."
The system checks the dashboard, picks the top queued keyword, and begins writing.
What it does during the writing process:
✅ Selects the primary keyword from the queue
✅ Identifies the fan-out cluster keywords to include as H2s
✅ Fetches information from authoritative sources (government websites, academic sources, established industry authorities) — not from AI imagination
✅ Writes using the content capsule technique
✅ Adds a key takeaways block at the top
✅ Injects the business experience and expertise from your business folder
✅ Internally links to relevant existing pages on the website
✅ Cites every factual claim with a real source
What the content capsule technique is:
Every H2 in the blog post is written as a question. The answer to that question appears immediately below it in 2–4 short paragraphs. This structure is specifically optimized for how search engines parse content and how readers scan. It is also the format most likely to get your content cited in AI overviews and featured snippets.
What the key takeaways block does:
A TLDR summary at the top of the blog post. Search engines read this first. It signals clearly what the content is about. It increases the chance of being cited by Google AI overviews. It also reduces bounce rate because readers know immediately whether the content answers their question.
Why this content ranks when generic AI content does not:
The content knows the business. It knows the website's existing pages. It cites real sources. It follows a proven structure. It is not a generic article about therapeutic gardening — it is an article about this specific business's approach to therapeutic gardening written for their specific audience.
Step 6 — Publish directly to your website or export as a formatted file
Two paths depending on your website setup:
Path A — Astro or framework-based websites:
If your website runs on Astro (or a similar framework that Claude Code can directly edit), type: "Publish this to the website."
Claude Code writes the markdown file with the correct frontmatter, drops it into the content directory of your website, and the post goes live. No logging into a CMS. No copy-pasting. No formatting adjustments.
This is the cleanest version of the workflow and the one that enables full automation.
Path B — WordPress or any other CMS:
The system outputs a formatted markdown file with all correct metadata, headings, internal links, and citations. Copy it into WordPress (the block editor accepts markdown) or paste it into your preferred CMS.
The important step: tell Claude the format once:
The first time you generate a blog post, check the output format. If it needs any adjustment (different metadata structure, different heading format, different file naming), tell Claude exactly what you need.
Then say: "Remember this output format for every blog post from now on."
Every subsequent blog post matches exactly. You never adjust the format manually again.
For WordPress users specifically:
The system understands WordPress parameters. If it needs additional information to format correctly for your WordPress setup, it will ask exactly the right questions the first time. Answer them once. Every future post comes out correctly formatted.
Step 7 — Schedule the content writing workflow to run automatically every week
Once the first blog post publishes successfully and you have confirmed the format is correct, tell Claude:
"Turn this entire content writing workflow into a routine and run it every Monday at 9:00 a.m."
Three ways to run scheduled automation depending on your setup:
Option 1 — Claude Desktop routine (simplest):
Claude Code Desktop has a built-in routine feature. Set the time and frequency. Claude runs the workflow at the scheduled time. The only requirement: your computer must be on and the Desktop application must be open.
Best for: people who have their computer on during work hours and want the simplest setup.
Option 2 — Cron job (most reliable):
Tell Claude Code: "Set this up as a cron job running every Monday at 9:00 a.m."
A cron job is a scheduled task that runs at the operating system level. Claude Code runs headless — meaning it works in the background without the application window needing to be visible. More reliable than the Desktop routine because it does not depend on the application being open.
Best for: developers or anyone comfortable with the Claude CLI.
Option 3 — Cloud deployment (fully autonomous):
Deploy the entire workflow to a cloud server. Google Search Console connection, DataForSEO connection, and website publishing all happen in the cloud. Nothing runs on your local machine. The workflow fires every Monday regardless of whether your computer is on or not.
Best for: agency operators running this for multiple clients simultaneously.
Regardless of which option you choose, the result is the same:
Every Monday at 9 a.m., the system checks the keyword queue, picks the next uncovered keyword, writes a complete blog post, publishes it to the website, and updates the dashboard. You review it when you have time. You change nothing unless something is wrong.
Step 8 — Run the on-site audit system every month to catch technical problems
Type: "Run an on-site audit."
The system connects to DataForSEO and runs a complete technical and on-page audit of your website. The example audit scored 97 out of 100 for technical health, 6 out of 100 for a specific issue that needed fixing, and 99 for SEO. Total cost for that audit: 48 cents.
What the audit checks:
✅ Site speed and Core Web Vitals
✅ Missing or duplicate meta titles and descriptions
✅ Broken internal and external links
✅ Missing alt text on images
✅ Crawl errors and blocked pages
✅ Duplicate content issues
✅ Mobile usability problems
✅ Missing structured data (schema markup)
✅ Redirect chains and redirect loops
✅ Page depth (pages too many clicks from the homepage)
What the audit returns:
A prioritised action list. Not a dump of 200 technical issues ranked equally. A clear hierarchy: fix this first because it is hurting rankings the most, then fix this, then this.
How to act on the audit:
If your website runs on Astro or a framework Claude Code can edit directly: tell it "Fix the issues you found." It makes the changes automatically.
If you run WordPress: the audit gives you an exact manual fix list. Most WordPress issues can be fixed with a plugin (Rank Math, Yoast) or by editing a page in your CMS. The audit tells you exactly which pages and exactly what to change.
How often to run this:
Minimum once a month. If you are publishing new content weekly, run it every two weeks. New pages can introduce new technical issues. Broken links appear as other websites change their URLs. Speed can degrade as you add new images or plugins.
Step 9 — Run the content refresher to rescue de-indexed and underperforming content
Most people think about SEO as publishing more content. This is half the job.
The other half is rescuing content that Google has already decided it does not want to index.
The signal to watch for:
"Crawled currently not indexed" in Google Search Console. This means Google visited your page, read the content, and decided not to store it in its database. The page is invisible to anyone searching. It gets zero traffic. It might as well not exist.
This happens more than most people know. On average only 60% of the content a website publishes stays indexed long-term. The other 40% gets quietly removed from Google's database — usually because Google decided the content was not high enough quality or useful enough to serve to searchers.
Type: "Run refresh recommender."
What it does:
✅ Connects to Google Search Console
✅ Identifies every page with "crawled currently not indexed" status
✅ Identifies every page that was indexed but ranking too low to get meaningful traffic
✅ Analyzes what is wrong with each piece of content
✅ Returns a prioritised list of which pages to refresh and what to improve on each one
How to use the output:
Take the pages the refresh recommender identifies. Run the content writer system on each one: "Rewrite the content for [page URL] using the content writer system."
The rewrite now includes business context, the content capsule technique, authoritative citations, and internal linking — everything the original version was probably missing. The rewritten version is good enough that Google will index it and keep it indexed.
This is not just about maintaining rankings. Content refreshing is often where the biggest traffic gains come from. A page sitting at position 15 with a rewrite can jump to position 4. A de-indexed page with a rewrite can suddenly start generating 500 clicks per month.
How often to run this:
Once a month alongside the on-site audit. Identify, rewrite, republish, wait three to four weeks, check Google Search Console, repeat.
Step 10 — Connect all four systems into one complete automated SEO operation
Each system is useful alone. Together they replace what a four-person SEO team does.
The full monthly workflow:
Week 1 — Content (automated):
Monday 9am: content writer runs automatically, picks next keyword from queue, writes and publishes blog post, updates dashboard.
Week 2 — Content + Audit:
Monday 9am: content writer runs again, second post published.
Mid-week: run on-site audit, fix any critical issues found.
Week 3 — Content + Refresh:
Monday 9am: content writer runs again, third post published.
Mid-week: run refresh recommender, identify pages to update.
Week 4 — Content + Refresh + Keyword Research:
Monday 9am: content writer runs again, fourth post published.
End of week: if keyword queue is running low, run keyword research to refill it. Check if any refreshed pages have been re-indexed in Google Search Console.
What you personally do each month:
✅ Approve the keyword research output (5 minutes)
✅ Glance at each published blog post before it goes out (2 minutes each)
✅ Review the on-site audit and fix anything critical (30 minutes)
✅ Review the refresh recommender report (10 minutes)
✅ Trigger the rewrites for de-indexed pages (5 minutes to prompt)
Total personal time per month: approximately 2–3 hours.
The system handles the rest.
What this replaces:
A content strategist who does keyword research: $3,000–$5,000 per month.
A content writer producing 4 posts per month: $2,000–$4,000 per month.
A technical SEO specialist running monthly audits: $2,000–$3,000 per month.
A content editor running refresh campaigns: $1,500–$3,000 per month.
Total team cost: $8,500–$15,000 per month.
Total system cost: under $50 per month in API and tool costs.
The websites using this system are not doing anything complicated. They are doing the right things consistently using a system that does not forget, does not get tired, does not skip the content refresher because it is tedious, and does not miss technical issues because nobody had time to audit this month.
They publish consistently. They fix technical issues immediately. They rescue lost content before it permanently disappears from Google. They never duplicate a keyword. Over 12 months that consistency compounds into rankings that no competitor spending bucks 5,000 per month on an agency can easily displace.
Start with System 1 this week. Get keyword research done.
Run System 2 next Monday. Get the first blog post published.
Run System 3 at the end of the month. Fix anything broken.
Run System 4 next month. Rescue what is not working.
That is the complete SEO system.
