SEO

Claude SEO: plugins, skills, live data and workflows

A guide to Claude SEO: installing a plugin that brings the skills and the data together, the other Claude SEO skills worth knowing, connecting SEO servers in Claude Code and sharing them with your team, and four workflows for keyword research, SERP briefs, technical audits and Search Console quick wins.

Jesse Sibley
By , FounderPublished · Last updated · 20 min read

This guide starts with the fastest setup, a Claude plugin that installs the skills and the data together. Then it covers the other Claude SEO skills, connecting servers in Claude Code and sharing them with a team, and four workflows that also work in ChatGPT and Cursor.

Install Manifold's Claude plugin and SEO skills

Manifold's plugin installs the marketing skills and the Manifold connector together, so Claude gets a method for each SEO job and live data to run it on. In Claude Code:

Terminal
/plugin marketplace add manifoldmcp/marketing-skills
/plugin install manifold@manifold

Then run /mcp, choose manifold and sign in.

Two of the skills are for SEO:

  • seo: rankings, keyword research, content plans, briefs, quick wins, refreshes, comparison pages, rank tracking and Search Console, with dated findings on what Google's 2025 and 2026 updates rewarded and punished. The Claude SEO skill page lists them.
  • technical-seo: crawling, rendering, indexing, traffic drops and site migrations, including the false drops that come from Google's own reporting changes.

ai-search, link-building and local-seo cover AI answers, backlinks and local rankings, the last on the Google Maps MCP.

Run /manifold-get-started first: it writes down what your business sells and to whom, so every skill starts from your site rather than a blank page. After that, describe the job ("find our quick wins in Search Console") and the matching skill loads, or run one by name, such as /seo. If another plugin uses the same name, add the prefix: /manifold:seo.

In Cursor and other agents that read Agent Skills, install the skills with npx skills add manifoldmcp/marketing-skills and add the server at https://mcp.manifoldmcp.com/mcp yourself. In Claude on the web or the desktop app, add the server as a custom connector (below) and upload a skill folder as a ZIP under Customize, then Skills. The plugin's code and skills are on GitHub under the MIT license.

How to use Claude for SEO

  1. Turn on web search. In Claude on the web or in the desktop app, switch on web search in the search and tools menu in the message box so Claude can read current pages. Claude Code can search and fetch pages on its own.
  2. Add a skill for jobs you repeat. A skill is a folder with a SKILL.md file of instructions that Claude loads when a task matches, so an audit or a brief follows the same steps every time. In Claude Code, put it in ~/.claude/skills/ or install it from a plugin; in Claude on the web, upload it under Customize, then Skills. The Claude SEO skills worth installing are compared below.
  3. Connect a live data source. Add a server for search data, such as Manifold's SEO MCP server, so Claude can pull real keyword volume and difficulty, live SERPs and your own Search Console data.
  4. Ask a specific question. Name the site, market, date range and output you want, for example "find queries for oursite.com in the US where we rank 8 to 20, last 28 days, as a table".
  5. Check the numbers, then act. Ask Claude which tool and date each number came from, then make the changes, or let Claude Code edit the pages for you.

What Claude does well in SEO, and where it needs help

Claude is strongest at the analysis and writing that take time by hand:

  • Clustering keywords by intent and topic, so you can see which keywords one page could rank for
  • Reviewing SERPs and extracting the patterns across the top results
  • Writing content briefs that state what ranks now and what gaps to fill
  • Drafting schema and on-page elements like title tags and meta descriptions
  • Reading technical audits and explaining which issues matter most
  • Editing code in Claude Code to fix technical issues in templates, sitemaps and redirects

Its limits are every LLM's: it can't see current facts about search unless you give it the tools to fetch them. On its own, Claude does not know search volume, keyword difficulty, who ranks for a query today, or your Search Console data. Ask "what's the volume for X?" without a data connection and you get a plausible estimate with no basis.

Claude SEO skills: which to install

A skill tells Claude how to do a job: the steps, the checks and the shape of the output. It does not give Claude search data; an MCP server does. The two work together, and some plugins install both. For the four terms, including connector and the ChatGPT equivalents, see Claude plugins vs skills vs MCP. If you searched for "Claude SEO", you may mean the first one below, an open-source Claude Code plugin by that name. Install steps checked October 2026 on each project's own page.

Skill or pluginWhat it doesData it usesInstall in Claude Code
Claude SEO (open source, MIT)Site and page audits through /seo commands: technical, content quality, schema, local, AI searchCrawls pages itself; optional extensions and Google API credentials add live data/plugin marketplace add AgriciDaniel/claude-seo, then /plugin install claude-seo@agricidaniel-claude-seo and /seo setup
SE Ranking SEO skillsWorkflows such as content briefs, AI search visibility and backlink gaps, saved as filesThe SE Ranking MCP server/plugin marketplace add seranking/seo-skills, then /plugin install seo-skills@seranking
InfraNodus SEO analysisSearch intent and content gap analysisThe InfraNodus MCP server with a free account; falls back to web search/plugin marketplace add infranodus/skills, then /plugin install seo-analysis@infranodus-skills
Hawk Academy SEO skills, by StudioHawkFree single-file skills for tasks like title tags and auditsWhatever Claude can already reachDownload a skill's .md file into ~/.claude/skills/
Manifold's SEO skill (MIT)What Google's 2025 and 2026 updates rewarded, SEO plans, quick wins, briefs and cannibalisation fixesManifold's MCP server/plugin marketplace add manifoldmcp/marketing-skills, then /plugin install manifold@manifold

OpenSEO also publishes a Claude Code plugin that adds its server and its SEO skills in one install. Claude SEO needs Python 3.10 or later, and /seo setup installs what it needs.

In Claude on the web, skills need code execution turned on under Settings, then Capabilities; then upload a skill folder as a ZIP under Customize, then Skills (Claude's help article has the steps).

Most of these audit pages Claude can fetch. Keyword volume, difficulty and who ranks today need a data source, which is the next step.

Connect live search data

The fastest setup is a hosted MCP server. Manifold is one option: hosted, pay per call, with no SEO tool subscription or API key of your own. Every account gets 250 free credits a month, and Pro starts at $29/mo. It covers keyword research, SERP analysis, technical crawls, backlink checks, AI answer tracking, Search Console and Bing.

In Claude Desktop or claude.ai: open Customize → Connectors → Add → Add custom connector, paste https://mcp.manifoldmcp.com/mcp, connect and sign in.

In Claude Code:

Terminal
claude mcp add --transport http manifold https://mcp.manifoldmcp.com/mcp

Then run /mcp and sign in. The plugin above does this step for you.

For Search Console and Bing: open Connections in the Manifold app and sign in to Google Search Console, Bing Webmaster Tools or both. These tools cost 0 credits because the data comes from your own accounts. The Google Search Console MCP server page explains the setup, and the best Google Search Console MCP servers compares the free local servers, such as mcp-gsc, that need a Google Cloud project instead.

If you already pay for Ahrefs or Semrush, their own servers are alternatives: see our Ahrefs MCP and Semrush MCP guides. Every other option, from SE Ranking and DataForSEO to community servers, is compared with prices in the best SEO MCP servers. Manifold's advantage is one connection and one credit balance across SEO, Search Console, AI answer tracking, social, Reddit, ads and leads.

Remote and local SEO servers in Claude Code

Claude Code connects to MCP servers in two ways, and the way changes how you add a server and where it runs.

Remote HTTP servers are hosted endpoints you add with claude mcp add --transport http <name> <url>. They run on the vendor's infrastructure. You sign in with OAuth by running /mcp in Claude Code, or pass an API key with --header. Most hosted SEO servers, Manifold, Ahrefs and Semrush among them, use this method.

Local stdio servers run as processes on your machine, started with npx or uvx. You add them with claude mcp add <name> -- <command>, passing any credentials with --env before the --. They need setup on each machine and can reach your local files and environment, which suits servers that need your own Google Cloud project, or Playwright MCP for checking how JavaScript pages render:

Terminal
claude mcp add playwright -- npx @playwright/mcp@latest

Every claude mcp add command takes a --scope flag. The default, local, keeps the server private to you in the current project. user makes it available in all your projects. project writes it to a .mcp.json file at the repo root that your team can commit.

Share the setup with your team

Add servers with --scope project, or write .mcp.json at the repo root yourself, and everyone who opens the repo in Claude Code gets the same SEO servers. Claude Code asks each person to approve project servers before it uses them.

Hosted servers suit this best, because each person signs in with their own account and no secret goes in the file. For a local server that needs credentials, write ${VARIABLE} in place of the value: Claude Code expands environment variables in .mcp.json, so each teammate's own login stays out of the repo.

JSON
{
  "mcpServers": {
    "manifold": { "type": "http", "url": "https://mcp.manifoldmcp.com/mcp" },
    "playwright": { "command": "npx", "args": ["@playwright/mcp@latest"] },
    "dataforseo": {
      "command": "npx",
      "args": ["-y", "dataforseo-mcp-server"],
      "env": {
        "DATAFORSEO_USERNAME": "${DATAFORSEO_USERNAME}",
        "DATAFORSEO_PASSWORD": "${DATAFORSEO_PASSWORD}"
      }
    }
  }
}

Keep a server that points at a credentials file on your own machine, such as a local Search Console server, in the default local scope, so the path never lands in the repo.

Then tell Claude Code which server to use for what in the repo's CLAUDE.md, which it reads at the start of each session:

MD
## SEO data
- Keyword volume, difficulty and SERPs: use the manifold server. Never estimate search volume.
- Search Console: use manifold's console tools for sc-domain:example.com.
- Rendered pages: use playwright.
- Show every title or meta description change as a diff before applying it.

Workflow 1: keyword research and clustering

The goal here is a shortlist of keywords grouped into pages, with real volume and difficulty.

Step 1. Generate ideas from a seed keyword:

TEXT
Use Manifold to find keyword ideas for "project management software" in the US.
Return keyword, volume, KD, intent and CPC. Drop anything with no volume data.
Sort by volume descending and show the top 50.

Claude calls seo_search_keywords, which returns monthly volume, keyword difficulty (0 to 100), intent, CPC and a 12-month trend for each idea.

Step 2. Check metrics for a list you already have:

TEXT
Get volume, KD and intent for these keywords: [paste list].

This uses seo_get_keyword_metrics. It is useful when you have a list from customer interviews or from scraping a competitor's ranked keywords.

Step 3. Cluster and prioritise:

TEXT
Group these keywords into clusters where one page could rank for the whole group.
For each cluster: primary keyword, secondary keywords, combined volume, average KD and intent.
Rank clusters by opportunity for a site with modest authority, favouring low KD and high combined volume.

This is where Claude excels. It groups keywords by semantic similarity and intent, then explains its reasoning. Challenge any cluster that mixes intents, and ask for sub-clusters if one group is too broad.

Step 4. Find gaps against a competitor (optional):

TEXT
Show keywords competitor.com ranks for that oursite.com doesn't, sorted by volume descending, with KD.
Filter to keywords with at least 100 volume and KD under 30.

This uses seo_get_keyword_gap. It surfaces the competitor's low-hanging wins you could target. The step-by-step keyword gap analysis guide covers SERP competitors, missing vs weak keywords, clustering, and tracking the ones you write for.

Workflow 2: SERP review to content brief

The goal is a brief based on what actually ranks today, not on what Claude assumes ranks.

Step 1. Pull the live results page:

TEXT
Get the top 10 Google results for "best crm for small business" in the US, including the AI Overview and its cited sources.

Claude calls seo_get_serp with the AI Overview option. You get each ranking URL, its title and snippet, SERP features like People Also Ask boxes, and the AI Overview text with its source links.

Step 2. Analyse the top pages:

TEXT
For the top 5 organic results, fetch each page's headings, word count and schema.
Tell me: the content format that ranks (guide, listicle, comparison, tool page), the subtopics every page covers, what no page covers well, and what the AI Overview says.

Claude uses seo_get_page, which returns the title, meta description, H1 to H6 headings, word count, schema markup and basic technical signals for any URL.

Step 3. Write the brief:

TEXT
Write a content brief for a page targeting [primary keyword] and [secondary keywords].
Include: search intent, recommended format and length, a direct 2 to 3 sentence answer to open with, H2 and H3 outline with the subtopics to cover, the gaps we will fill that competitors miss, internal links to suggest, and schema markup to add.

If the SERP shows an AI Overview, ask for a short, direct answer at the top of your page. It helps readers scan quickly and gives Google a clean passage to cite.

Workflow 3: technical and on-page audit

The goal is a prioritised list of issues to fix, ideally fixed in the same session when you work in Claude Code.

Step 1. Run a technical crawl:

TEXT
Run a technical crawl of oursite.com, up to 500 pages.
Summarise broken links, non-indexable pages, duplicate titles and descriptions, pages with thin content, and the issues affecting the most pages.
Group issues by severity: blocking (prevents indexing), high (hurts rankings), medium (nice to fix).

This uses seo_run_technical_crawl, which runs in the background and returns results when done. Start with a smaller crawl if you only want a sample.

Step 2. Check AI readiness:

TEXT
Check whether AI crawlers can read oursite.com and list any failing checks.

aeo_get_site_readiness checks robots rules for AI crawlers, whether the page renders, and related signals. For the crawler behind ChatGPT search, see OAI-SearchBot: what it is and how to allow it.

Step 3. Fix issues in Claude Code:

If your site lives in a repository, open Claude Code in that folder and ask it to fix the issues the audit found. For example: missing canonical tags in a template, duplicate title tags generated by a CMS, a broken sitemap, or missing alt text on images. Review each diff before you commit.

TEXT
Run a technical crawl of oursite.com, 500 pages max. List the top 10 issues by page count, and fix what you can in this repo's templates. Show me the changes.
Claude Code's crawl of manifoldmcp.com: a table of three issues, the HTTPS redirect it added, and how it verified the fix
That prompt run on our own site, 9 October 2026. No broken links, but every page answered over plain HTTP; Claude Code fixed it in the site's Worker.

If Search Console lists pages as "Discovered" or "Crawled, currently not indexed", our guide to fixing currently not indexed pages covers the causes and what to change.

If you already crawl with Screaming Frog, its built-in server lets Claude Code run and read those crawls instead: see the Screaming Frog MCP setup guide. If you run the same audit every month, the technical-seo skill from the plugin above keeps Claude to the same steps each time, or write a skill of your own.

Workflow 4: Search Console quick wins

The goal is to find pages already close to page one and push them over. These are often the fastest wins available.

Step 1. Pull your queries:

TEXT
List my Search Console properties, then pull queries and pages for sc-domain:manifoldmcp.com for the last 28 days.
Filter to queries with an average position between 8 and 20 and at least 50 impressions.

Claude calls console_list_properties, then console_get_search_analytics.

Step 2. Prioritise by page:

TEXT
Group these by page. For each page, list its near-miss queries, total impressions and average position.
Rank pages by the clicks they could gain if they reached the top 5 for their queries.

Real example from manifoldmcp.com (8 September to 5 October 2026, pulled on 8 October 2026):

The site is young: Search Console shows its first impressions on 23 September 2026. Google returned 121 query and page rows for the 28 days, and every one had 0 clicks. The few clicks the site did get, mostly to the home page and /about, came from queries Google keeps private. The top rows:

  • "seo mcp" for /mcp/seo: 41 impressions, position 85.1
  • "mcp server seo" for /mcp/seo: 30 impressions, position 85.0
  • "best seo mcp servers" for /blog/best-seo-mcp-servers: 27 impressions, position 66.7

Most of the site's SEO queries sit between positions 60 and 90, on pages 6 to 9 of Google. The positions 8 to 20 filter with at least 50 impressions returned nothing: the only rows in that range had 6 impressions or fewer. The useful signals were elsewhere:

  • Keyword cannibalization. Seven "best SEO MCP" queries showed both /blog/best-seo-mcp-servers and /mcp/seo. The guide ranked higher for six of them, so the product page was competing with it rather than helping. On 9 October 2026 we addressed it: the guide's links to Manifold now point at /mcp/seo with the anchor "SEO MCP server", and the definition of an SEO MCP server moved to that page, so each page has its own job.
  • Question queries do better. "Is there a way to see how my competitors are being recommended by claude and chatgpt instead of us?" averaged position 27.4 for /blog/chatgpt-brand-recommendations, far above the short head terms.
Bar chart: four best SEO MCP queries split impressions between the SEO MCP guide and the /mcp/seo page
From Manifold's console_get_search_analytics for sc-domain:manifoldmcp.com, 8 September to 5 October 2026, pulled 8 October 2026. Every row had 0 clicks.

The honest lesson is that the standard "positions 8 to 20" filter returns very little on a young site. The real quick wins are (a) fixing keyword cannibalization, so one page owns each query, and (b) question queries where you already rank and could rank higher with a more direct answer.

Step 3. Plan the updates:

TEXT
For the top 3 pages by opportunity, fetch the current page and the top 5 results for its main query.
Tell me exactly what to add or change: missing subtopics, title tag wording, internal links to add, and where the query terms are weak or missing.

This combines your own data with the live SERP. For a young site, focus on the pages that already have some visibility.

Example prompts

These work in any client once live search data is connected:

  • "Which of our pages lost the most impressions this month compared with last month, and for which queries?"
  • "What does the AI Overview say for [query], and is our site cited? If not, which sites are cited and why?"
  • "Compare backlinks for oursite.com and competitor.com: referring domains, dofollow share and average domain rank."
  • "Write title tags under 60 characters and meta descriptions between 150 and 160 characters for these five pages. Use the primary keyword naturally in each title."
  • "Show the keyword difficulty trend for [keyword] over the last 12 months and explain whether now is a good time to target it."

In Claude Code the same data ends in a diff. Paste these in the repo:

  • "Pull Search Console queries for oursite.com in the US where we rank 8 to 20, last 28 days. For the top 10 by impressions, read each ranking page in the repo, suggest title and meta description improvements, and show me the edits before applying them."
  • "Get the top 10 Google results for 'best project management software for small teams' in the US, including the AI Overview. Analyze what ranks, identify content gaps our competitors miss, and draft a new page optimized for the query. Save it as content/blog/best-project-management-software-for-small-teams.md."
  • "Find 50 keyword ideas for 'email marketing automation' in the US with volume, difficulty and intent. Cluster them by intent and topic. For the top 3 clusters, generate content briefs and save them as separate files in briefs/."
  • "Pull referring domains for competitor.com with their domain rating. Show the top 20. For domains linking to them but not to us, draft outreach email templates and save them to outreach/templates.md."

The step-by-step AI backlink analysis guide covers auditing your own links, backlink gap analysis, and who to email at each target site.

Claude versus ChatGPT for SEO

Both Claude and ChatGPT work well once connected to search data, and the same Manifold server works in both. The practical differences:

  • Claude Code works inside your repository, so it can fix technical issues in templates, sitemaps or redirects in the same session as the audit.
  • Claude loads skills from a folder or a plugin, so a repeated audit or brief follows the same steps each time.
  • ChatGPT adds an MCP server as a custom app from its Plugins page, and then it works in every chat. See ChatGPT for SEO: workflows and setup for the full guide with prompts to copy.

Limits and tips

  • Verify volume and KD numbers. Different data sources give different numbers because they run separate indexes. Pick one source and stick with it when you track trends.
  • Watch cost on large requests. Bigger crawls and longer keyword lists use more credits and take longer. Start with 100 pages if you just want a sample.
  • Claude still hallucinates. If a claim about a ranking page or a backlink sounds too convenient, check it manually.
  • Check dates. When Claude cites a SERP or an AI Overview, ask when it was fetched. AI answers change from day to day.
  • Keep related questions in one chat. Claude can reuse data it already fetched, which saves credits and time.

Run this in your agent

Connect Manifold to Claude, ChatGPT or Cursor, then paste this prompt.

Get 100 keyword ideas for [topic] in the US with volume and KD. Cluster them by intent and topic. For the top 3 clusters, pull the top 10 results for the primary keyword and write a content brief.

Questions people ask

What is Claude SEO?

Two things. It is the general practice of using Claude for SEO work, which this guide covers. It is also the name of Claude SEO, an open-source Claude Code plugin (github.com/AgriciDaniel/claude-seo) that runs site and page audits through /seo commands. Either one does better with live search data from an SEO MCP server.

Is there a Claude plugin for SEO?

Several. Manifold's plugin installs SEO skills and a live data server together: /plugin marketplace add manifoldmcp/marketing-skills, then /plugin install manifold@manifold. The open-source Claude SEO plugin runs audits, and SE Ranking, InfraNodus and OpenSEO publish plugins that run on their own servers.

Can Claude do SEO?

Claude can do most SEO analysis and writing tasks well once you connect it to live search data. It can research keywords, review SERPs, audit sites, write content briefs and analyse Search Console data. Without a data connection, its search volume and difficulty numbers are guesses.

Does Claude know search volume?

No. Any volume Claude gives you without a connected data source is an estimate with no basis. Connect an SEO MCP server like Manifold, Ahrefs or Semrush to get real volume and keyword difficulty.

How do I connect Claude to SEO data?

In Claude Desktop or claude.ai, open Customize, then Connectors, add a custom connector, and paste the MCP server URL. For Manifold, paste https://mcp.manifoldmcp.com/mcp, connect and sign in. In Claude Code, run claude mcp add --transport http manifold https://mcp.manifoldmcp.com/mcp, then /mcp to sign in.

How do I add an MCP server to Claude Code?

For a hosted server, run claude mcp add --transport http <name> <url>, then /mcp in Claude Code to sign in. For a local server, run claude mcp add <name> -- <command>, passing any credentials with --env before the --, for example claude mcp add playwright -- npx @playwright/mcp@latest. /mcp shows which servers are connected.

How do I share an SEO server setup with my team?

Add servers with --scope project, and Claude Code writes them to a .mcp.json file at the repo root that your team can commit. Everyone who opens the repo gets the same servers, and Claude Code asks each person to approve them first. Hosted servers suit this best, because each person signs in with their own account.

Can Claude connect to Google Search Console?

Yes, through an MCP server. With Manifold, connect Search Console once in the app, and Claude can read clicks, impressions, CTR and positions at 0 credits per call. Community servers like AminForou/mcp-gsc run locally via Python and need a Google Cloud project.

Is Claude Code useful for SEO?

Yes, especially for technical SEO. Claude Code can read and edit your site's code in the same session as the audit, so it can fix missing canonical tags, duplicate titles in templates, broken sitemaps and missing alt text.

Claude or ChatGPT for SEO?

Both work well once connected to search data. Claude Code works inside your repository, so it suits fixing technical issues in templates or redirects in the same session as the audit. The same Manifold server works in Claude, Claude Code, ChatGPT and Cursor.

Sources

Jesse Sibley

Jesse Sibley

Founder of Manifold. A growth engineer who has worked with London startups for eight years.

All SEO guides
  • 16 min read

    Find keyword cannibalization with Claude

    Connect Search Console, group query and page rows by query, check the live SERP and both pages, pick one owner per query, then track with a weekly rank monitor that reports when a different page ranks.

  • 6 min read

    Claude plugins vs skills vs MCP

    What a Claude plugin, skill, connector and MCP each add, how those words work in ChatGPT, and one marketing job with Manifold MCP.