A plain-text version of this site for AI assistants is at https://contengi.com/llms.txt, with the full product documentation in one file at https://contengi.com/llms-full.txt. Every page is also available as markdown by adding .md to its URL.

··6 min read

Claude Code for SEO: the site-wide jobs it handles well, and the guardrails to put around it

Claude Code makes good SEO faster, and every bulk change still goes through a pull request you read.

A plain-text version of this site for AI assistants is at https://contengi.com/llms.txt, with the full product documentation in one file at https://contengi.com/llms-full.txt. Every page is also available as markdown by adding .md to its URL.

TL;DR

  • Claude Code is Anthropic's agentic coding tool, and for SEO it shines on site-wide jobs: auditing templates, fixing metadata in bulk, generating schema, adding internal links, and building redirect maps.
  • It works best when your site or content lives in files it can read, such as a Next.js repo or a folder of markdown posts, with Search Console connected through MCP.
  • Put your SEO rules in CLAUDE.md, turn weekly jobs into skills, and use hooks to run checks after every edit.
  • Google wants AI-generated titles, meta descriptions, structured data, and alt text reviewed by a person before publishing, so every bulk change goes through a pull request you read.
  • Ignore the "rank #1 in 24 hours" videos. Claude Code makes good SEO faster, and thin pages stay thin however quickly you ship them.

The results page for this topic is wall-to-wall videos promising first place on Google by tomorrow. Claude Code is a remarkable tool for SEO, and none of those thumbnails describe what it's good at.

This guide covers the SEO jobs Claude Code handles well, how to set it up for anyone who's site lives in a repo, the guardrails that keep bulk changes safe, and where the hype runs ahead of the tool. For Claude in general, including chat and connectors, start with Claude SEO.

What is Claude Code, and why use it for SEO?

Claude Code is an agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools. It runs in the terminal, an IDE, a desktop app, and the browser.

That makes it the right tool for SEO work that touches many files at once. Chat is great for rewriting one title. Claude Code is what you reach for when 300 titles live in a template and a CMS export, and they all need the same fix.

Think of chat as a skilled editor sitting next to you, and Claude Code as the same editor with keys to the building.

Which SEO jobs does Claude Code handle well?

SEO jobWhat you ask forWhat you check
Template auditList every page type and where it sets title, description, canonical, and robots tagsMissing or duplicated tags per template
Bulk metadataRewrite descriptions under 155 characters for every post missing oneEvery line in the diff, for accuracy
SchemaGenerate Article or Organization markup from the template's real fieldsMarkup matches what's visible on the page
Internal linksFind posts that mention a topic another post covers and propose anchorsAnchors read naturally in context
Redirect mapMatch old URLs to new ones after a migrationEvery row, before it goes live
Search Console analysisGroup striking-distance queries by page through the MCP connectionWhich suggestions fit the strategy

Links deserve a special mention. Google can generally only crawl a link if it's an a element with an href attribute, and Claude Code is very good at spotting menus and cards built from click handlers instead. On a JavaScript site, that check alone can be worth the setup. The Next.js SEO checklist covers what to look for.

How to set up Claude Code for SEO

  1. Open your site repo or content folder. If your site isn't in code yet, building a website with Claude Code walks through getting there.
  2. Write an SEO section in CLAUDE.md. Claude Code reads CLAUDE.md at the start of every session, so put your title format, canonical rules, schema types, and link policy there.
  3. Connect Search Console through MCP. Without it, Claude Code knows your files but not your rankings.
  4. Turn weekly jobs into skills. A /meta-check or /striking-distance skill runs the same way every time.
  5. Add hooks for checks. Run a schema validator or banned-word linter after every edit so nothing slips through.
  6. Review every change as a pull request. Claude Code works with git, so let it branch and commit, and you merge.

Two commands cover a surprising amount of day-to-day work:

claude "list every page template, where it sets the title and canonical, and any page type missing either"

git diff main --name-only | claude -p "check these changed files for missing titles, canonicals, alt text, or links built without an href"

The second one uses the pipe-friendly CLI to review only what changed, which makes it a cheap pre-deploy SEO check. If you want to go further and turn this into a full AI SEO agent with subagents and a schedule, follow the SEO agent build.

What guardrails does Claude Code need for SEO?

A person reads every change before it reaches Google. AI-generated content needs a manual fact-check before publishing, and that includes title elements, meta descriptions, structured data, and image alt text. Bulk edits are where confident mistakes multiply fastest.

Structured data is the classic trap. Structured data has to match the visible text on the page, and a model filling in schema fields will happily invent a rating or an author bio. Point it at real template fields only.

Then check what a bot receives after your changes with the AI bot view, because a clean diff can still render badly.

How we check facts before anything ships

While writing the SEO engineer post in this cluster, the agent found two different average salaries for the same job title on the same salary site, depending on which version of the page it could read. It left the number out.

That's the habit worth copying in Claude Code. Write it into CLAUDE.md that any number, price, or claim needs a source fetched in the same session, and that an unverifiable figure gets dropped. It costs you a sentence now and then. It saves you from publishing 300 meta descriptions with the wrong price in every one.

Where does the hype run ahead?

Speed. Claude Code can draft 50 posts before lunch, and generating many pages without adding value for users can breach Google's scaled content abuse policy. Fast, thin, and identical is still thin. Use the speed on the boring structural work and spend the saved hours on posts with a point of view.

If you've never opened a terminal, start smaller with Claude Code for marketers.

Frequently asked questions

Can Claude Code do SEO?

Yes, especially site-wide technical work: auditing templates, fixing metadata in bulk, generating schema, adding internal links, and building redirect maps. Connect Search Console through MCP so it works from your real rankings.

Is Claude Code only for coding?

No. It reads, edits, and organises any files, so a folder of markdown posts or a CSV of URLs works as well as a code repo. For SEO, the files are your templates, content, and data exports.

Do I need to know how to code to use Claude Code for SEO?

You need to be comfortable with folders, a terminal or the desktop app, and reading a diff. You don't need to write code yourself, but you should understand what a change does before you merge it.

Can Claude Code rank a page in 24 hours?

No tool controls how fast Google ranks a page. Claude Code speeds up the work around a page, from metadata to schema to links, and the page still has to earn its place.

What's the difference between Claude Code and Claude for SEO?

Claude chat with connectors suits analysis, briefs, and writing one page at a time. Claude Code suits jobs that touch many files at once, such as templates, bulk metadata, and site-wide link fixes.

Content like this, in your own voice

The workflows behind this blog run inside Contengi. A strategist sets up your knowledge base, and the agents write to your rules.