Claude SEO is using Anthropic's Claude model to research and write content that ranks in search. Claude is one of the best writers you can put on the job, but raw output rarely ranks on its own. The model writes fluent prose with no idea what people search for, what already ranks, or what your business does differently. The fix is a workflow: feed Claude real search demand, your business context, and quality checks every draft must pass before it ships. Done right in 2026, you get content that reads like a person wrote it and can actually rank.
If your blog is markdown in a repo and you already code with Claude Code, you are most of the way there. This post gives you the workflow, then shows how to run it so Claude leaves a checked markdown file in your repo.
Why does Claude struggle with SEO by default?
Claude is trained to be helpful and fluent. It is not trained to rank. Out of the box, it cannot see search volume, the live results page, or your positioning. So it fills the gap with safe, generic writing. That is the exact thing search engines try to filter out.
This is not a small problem. Google said its March 2024 core update aimed to cut low-quality, unoriginal content by around 40 percent, per Google Search Central. Generic AI writing sits right in that blast radius.
It also explains a common worry. Founders keep asking whether AI blogs can rank at all. They have watched thin AI posts get ignored. The problem is rarely that Claude wrote the post. The problem is that nothing told Claude what would make it worth ranking.
What does Claude do well and badly for SEO?
Claude is strong at the writing itself. The weakness is everything around the draft. Knowing this split lets you build a process to cover the gaps.
Claude does these things well:
- Drafting a full article quickly from a clear brief
- Matching a specific voice when you give it examples
- Restructuring and tightening messy notes
- Summarising research you hand it
Claude does these things badly on its own:
- Knowing what people search for and how often
- Seeing the live results page and what already ranks
- Staying specific to your product instead of generic advice
- Catching its own tells, the phrasing that screams AI
None of these gaps are fixable by a better prompt alone. They need real data and a checking step.
How do you build a Claude SEO workflow that ranks?
Treat Claude as the writer inside a bigger pipeline, not the whole pipeline. A workflow that ranks looks like this:
- Start from real search demand. Pull a keyword with its volume and difficulty before you write a word. A tool like Ahrefs shows both. Do not let Claude invent topics from memory.
- Give Claude your business context: who you serve, the real problems they have, and what only you can say. This is where generic turns specific.
- Write to one clear intent and structure. Match what the searcher wants. Lead with the answer. Use headings that map to real questions.
- Run the draft through checks before publishing. Readability, structure, internal links, and anti-slop checks catch the weak spots in any first draft.
- Publish as markdown you control. Then track whether it ranks and improve it.
You can wire this by hand. Paste the keyword numbers into the chat, keep a business brief in a doc, and eyeball every draft. It works, it is just slow.
How do you run a Claude SEO workflow from your repo with Claude Code?
Claude Code works inside your repo, so it can write the article file itself:
- Connect the MCP. Paste the one connect prompt into Claude Code. It registers the server and confirms the handshake.
- Ask Claude to research your keyword, for example "Research 'claude code seo' for my site". It pulls volume, difficulty and the live Google results.
- Ask for the brief: intent, headings, related terms and internal links.
- Tell it to write
content/blog/claude-code-seo.mdwith frontmatter at the top. Claude Code creates the file in your repo. - Claude runs the quality gates on the file. Anything that fails is blocked, so it fixes the draft and runs them again.
- Run
git diff, edit, commit, and open the pull request.
A generated file starts with frontmatter like this:
---
title: "Claude Code for SEO: A Repo-First Workflow"
description: "How to use Claude Code to research a keyword, write a blog post into your repo and check it before you merge."
slug: claude-code-seo
canonical: /blog/claude-code-seo
keyword: claude code seo
secondaryKeywords: ["claude for seo", "use claude to write seo content"]
intent: informational
dateGenerated: 2026-10-18
---
You can do this without our product. Put your business profile and banned words in CLAUDE.md, paste keyword numbers from any tool, and add a script that checks title length, headings and links. Tell Claude to run it before every commit.
If you'd rather not do this by hand, Jack's SEO MCP does it from inside your repo. Connect it to Claude Code and your agent gets live keyword data, your saved business profile, a brief and 60+ checks built on Google's published guidance. It writes each article as a markdown file, frontmatter and schema included, straight into your content folder, and only the drafts that pass get counted. See the pricing page.
Have your agent do this for your site
Written into your repo, checked against Google's guidance. First one free.
What are the most common mistakes using Claude for SEO?
Most failures come from skipping the steps around the draft, not from the draft itself. Watch for these:
- Letting Claude invent statistics or sources. Always give it real numbers and check every claim.
- Publishing the first draft. The first pass is a starting point, not a finished article.
- Ignoring search intent. A great essay that answers the wrong question still will not rank.
- Stuffing the keyword. Repeating the exact phrase reads worse and can work against you.
- Shipping thin posts at volume. One developer added 12,000 AI blog posts in a single commit. It became a textbook example of what not to do, as covered on Hacker News.
Where should you start with Claude SEO?
Stop letting Claude pick topics blind. Ground every article in a real keyword and your real business, and check the draft before it ships. What lands in your repo is a markdown file you review like any other pull request. The summary:
- Claude writes well but does not know what ranks, so give it the missing inputs.
- Start from search demand, not imagination.
- Feed it your business context so the content is specific, not generic.
- Always run a quality and anti-slop pass before publishing.
- Publish content you own and track what happens next.
Frequently Asked Questions
Can Claude write SEO content that ranks on Google?
Claude can write content that ranks, but not on its own. Claude gives you fast, fluent drafting. Ranking still depends on three things: a real keyword, the right search intent, and being more useful than what already ranks. Give Claude search data and a clear brief, and its output competes with human writing. Leave it to guess, and it produces generic posts that struggle.
Is Claude or ChatGPT better for SEO writing?
Claude and ChatGPT are both capable writers. The gap for SEO comes from your process, not the model. Claude is often praised for natural, less robotic prose, which helps it avoid obvious AI tells. Either model still needs real keyword data, your business context, and a quality check to rank. Pick the writing you prefer, then build the workflow around it.
Does Google penalize content written with Claude?
Google does not penalize content for being written with Claude. Google judges content by quality and helpfulness, not the tool that made it. What gets demoted is unoriginal, low-value content, which AI makes easy to mass-produce. Content written with Claude is fine when it is accurate, specific, and useful. It is at risk when it is thin and generic.
How do you give Claude real keyword data?
You give Claude keyword data by pulling it from an SEO tool and putting it in front of the model. The manual way is to copy volume and difficulty from a keyword tool into the chat. The connected way is an MCP server. It hands Claude the data directly, so the model researches and writes in one flow with no copy and paste.
What is an SEO MCP and how does it help Claude?
An SEO MCP is a server that connects Claude to SEO data using the Model Context Protocol. Instead of pasting keyword numbers and a brief each time, the MCP gives Claude live search data, your saved business profile, and quality gates inside the chat. The result is simple. Claude researches, writes, and checks its own work against real inputs rather than guessing. That is the whole point of connecting Claude to real data.
Get found on Google without taking on a second job in SEO.
An agent wrote this post straight into our repo. Yours can too. First article free, no card.
Write my first article free