Choose theme
AI Resources
Claude SEO
Claude SEO is a public, third-party Claude Code plugin for running website and page audits through a collection of focused SEO skills and specialist agents.
A full audit can crawl up to 500 pages, send different parts of the review to specialist agents, and write a report with a prioritized action plan. Narrower commands cover technical SEO, content, schema, AI search, sitemaps, local search, e-commerce, and international sites. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
An SEO workspace inside Claude Code
The plugin combines focused SEO skills and specialist agents. You can run a broad site audit or call a narrower workflow for one page, schema, content quality, Core Web Vitals, local SEO, keyword planning, or AI-search visibility.
Why it stands out
Start without data-service accounts
The core audit works without optional third-party APIs. You can later connect Google data or extensions for services such as Ahrefs, DataForSEO, SE Ranking, Profound, or Bing when their live data is useful and you have the required account.
Availability
Public plugin with a managed Python setup
The public repository documents Claude Code plugin installation and manual Windows, macOS, and Linux paths. Setup creates an isolated Python environment, with Playwright Chromium added for rendered-page and screenshot work.
Why it matters
What makes it useful
A site review can scatter crawl problems, structured-data errors, content gaps, performance signals, and search-console evidence across several tools. Claude SEO gives that work one command surface and turns the findings into files you can question, edit, and rerun inside the same coding workspace.
What to know
Where it fits
Start with a single-page audit when you need to investigate one landing page; use the full-site audit to collect findings across a crawl of up to 500 pages. Both produce editable reports in your Claude Code workspace. Connect live search or performance data when the question needs it, then verify the findings before changing production content or markup.
Notable points
What stands out
The project documents two important limits. Heavily interactive pages can still produce noisy findings even with its Playwright renderer. Without Google credentials or optional data services, Core Web Vitals rely on lab estimates and indexation is inferred from page-level signals rather than confirmed with live account data.
Before using
What to review
Run the documented setup and doctor commands before the first audit. The managed environment installs Python packages and may add Playwright Chromium for rendered pages.
Inspect the repository and installer before running it, especially on a client or work machine. The Windows documentation deliberately uses a cloned script instead of piping remote PowerShell directly into execution.
Use the crawler only on sites you are allowed to assess, and choose a scope that will not create unnecessary load or pull private pages into the working context.
Treat scores and recommendations as leads to verify. Check the underlying page, Search Console, analytics, schema rules, and current Google documentation before making a consequential change.
Local report files do not make the whole workflow offline. Claude Code still handles the model interaction, so review the data controls for your Claude account before using private site, customer, or analytics material.
Optional Google and MCP integrations require their own accounts, credentials, quotas, and terms. Add only the services needed for the question you are answering.
Reader fit
Who may find it relevant
SEO practitioners and site owners who already use Claude Code and want repeatable audit files rather than a closed dashboard.
Developers who want technical, content, schema, and AI-search checks in the same workspace as implementation.
Teams that prefer to begin without optional data-service accounts and add live sources selectively.
Less relevant if you need a non-technical hosted dashboard, guaranteed ranking advice, deep proprietary backlink data without another service, or an offline-only workflow.
Editorial note
Why LifeHubber lists it
Claude SEO is useful for site owners deciding the order of recommended changes and what to monitor after each one. Its recommendation instructions ask for dependencies, failure checks and early signals, giving an action plan more to work with than a priority label. Before acting on one recommendation, check four things: the observation behind it, what must change first, how you would know the change failed, and which early signal you can monitor without another full audit. The project instructs its agents to include these in recommendations. If your report is missing one, ask for it before treating a priority label as a reason to make the change.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
More in AI Agents
Keep browsing this category
Explore more AI agent projects.
Paperclip
paperclipai/paperclip
A self-hosted server and dashboard for coordinating agent teams through companies, goals, roles, issues, heartbeats, budgets, approvals, and persistent activity records.
Octop
TencentCloud/Octop
A self-hosted assistant platform with multiple users and experts, shared knowledge bases, messaging channels, scheduled tasks, workspace memory, and configurable model providers.
LiveKit Agents
livekit/agents
A realtime framework for voice, video, and physical AI agents, with Python and Node.js paths, LiveKit room participants, WebRTC clients, telephony support, tools, testing, and deployment options.
For project maintainers
Listed here? You can use the badge.
If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.
