Claude Code for SEO: reports, new pages and technical fixes

What Claude Code does for SEO

• A daily report from Search Console and your analytics: impressions, clicks, the queries and pages behind them, and the gap to your goal.
• New pages for queries that are starting to work, written in your site's repository with titles, meta descriptions and internal links.
• Technical checks on every page it touches: titles, canonical tags, hreflang, structured data, sitemap entries and broken links.
• Translations of pages that already get traffic, and an indexing request when a page ships.

Claude Code features for SEO

How to set up Claude Code for SEO

1. Connect the tools

   Give it read-only access to the numbers and a browser to check pages as visitors see them. For Search Console, use the API with a read-only service account or an MCP server; for analytics, your tool's CLI or MCP server.

   # A browser for checking rendered pages, titles and links
   claude mcp add playwright npx @playwright/mcp@latest
   
   # See what's connected
   claude mcp list

2. Write the rules in CLAUDE.md

   Claude Code reads CLAUDE.md at the start of every session, claude -p runs included. Put the job's rules there, or in a skill under .claude/skills/ if they're long. See the CLAUDE.md guide.

   ## SEO rules
   Goal: 10,000 impressions, 500 clicks and 2,000 visitors a week.
   
   Every day
   1. Read the last 7 days in Search Console and analytics.
   2. Pick one query or page that is starting to work and do one
      thing for it: a related page, an FAQ, internal links or a
      translation.
   3. Run the build and check the page's title, description,
      canonical and structured data before you commit.
   4. Post the report and what you changed. Ask before anything
      that can't be undone.
   
   Never
   - Buy links, stuff keywords or publish a page you haven't built.
   - Change robots.txt or redirects without asking.

3. Run it without the interactive interface

   claude -p runs one task and exits, so cron, CI or another tool can start it. Choose what it may do without asking with --allowedTools or --permission-mode; --output-format json returns the result with its cost.

   # Today's routine without the interactive interface
   claude -p "Do today's SEO routine from CLAUDE.md and list what you changed" \
     --permission-mode acceptEdits --allowedTools "Bash(npm run build)" \
     --output-format json

4. Put it on a schedule

   Make it a cloud scheduled task with /schedule (Pro, Max, Ultra, Team and Enterprise), a desktop scheduled task, or /loop while a session stays open. See how to make Claude Code proactive.

Source: Claude Code documentation

Limits and safety

• It can't see Search Console or analytics until you connect them. Give it read-only access.
• Rankings take weeks. Judge it on pages shipped and impressions, not on yesterday's clicks.
• A person approves anything public: deploys, redirects, robots.txt and removals.
• Since Claude Code v2.1.302, claude -p starts in Manual mode: an action that needs approval is denied unless a rule allows it. Allow only the tools the job needs.

Claude Code or Codex for SEO?

The rules carry over. Write them once in AGENTS.md and put @AGENTS.md in CLAUDE.md, and both agents read the same file.

Step by step for the other agent: SEO with Codex.

Make SEO someone's job

Commands run when someone remembers to run them. Crewmark turns your own Claude Code into an AI employee with a role, a goal in numbers, working hours and a heartbeat, so the work happens on schedule and shows up on a board.

1. Start from the role

   The AI SEO specialist, with these rules in its brief.

2. Put the work on its board

   Add the job as a recurring issue. The employee wakes on its heartbeat, does it and reports in a comment.

3. Related

   The daily SEO report has the full report brief, and the SEO skills cover keywords, writing and indexing.

FAQ