Website audits and SEO fixes inside Claude Code
Run squirrelscan as a skill or a hosted MCP server, and let Claude Code find what's broken and fix it.
Claude Code is already in your terminal, so it might as well run your SEO audits too. squirrelscan gives it two ways in: a thin CLI skill for quick local checks, or the hosted MCP server for cloud audits, browser rendering, and a shared issue tracker your whole team can see.
Either path gets you the same 249+ audit rules across SEO, performance, security, accessibility, and agent experience, minus the meta tag guessing games. Claude Code reads the output, tells you what's wrong, and if you ask nicely, fixes it.
Start with the CLI if you want something running in the next thirty seconds. Reach for the MCP server once you want Claude Code polling live audits, reading the issue tracker, or working across an organization instead of just your laptop.
Setup
- 1
Install the squirrelscan CLI
One line, no account needed. Local audits are free and run entirely on your machine.
bashcurl -fsSL https://install.squirrelscan.com | sh - 2
Run an audit in agent-friendly format
Point it at a URL and ask Claude Code to read the result. The llm format is compact and structured, built for exactly this.
bashsquirrel audit https://example.com --format llm - 3
Or install the audit-website skill
Gives Claude Code a /audit-website slash command so it can run audits on its own, without you typing the CLI invocation each time. Works in plan mode too, so it can draft a fix plan before touching any code.
bashnpx skills install squirrelscan/skills - 4
For cloud audits, connect the hosted MCP server
This is the deeper integration: cloud audits with browser rendering, the per-website issue tracker, and the rule catalog, all as native tools. Add the server, then run /mcp inside a session, select squirrelscan, and choose Authenticate to sign in and pick your organization.
bashclaude mcp add --transport http squirrelscan https://mcp.squirrelscan.com/mcp
Frequently asked questions
- Does this cost anything?
- Local CLI audits are free, no account required. Cloud audits over the hosted MCP server are pay-as-you-go credits, and every account gets 500 free per month, so most day-to-day use doesn't touch a card.
- Can Claude Code actually fix the issues it finds, or just list them?
- Both. Point Claude Code at the audit output, or use the skill in plan mode, and it will group issues by category and implement fixes across your codebase, not just describe them.
- Does it work on localhost or a staging site behind auth?
- The local CLI and skill audit anything Claude Code's machine can reach, including localhost. The hosted MCP server crawls from squirrelscan's cloud, so it needs a publicly reachable URL; use the CLI or the local squirrel mcp server for private networks.
- Should I use the skill or the MCP server?
- The skill is a thin wrapper around the free local CLI, good for quick one-off audits. The MCP server is the fuller integration: cloud audits, a shared issue tracker, and the rule catalog as native tools, worth it once you want state that persists across sessions and teammates.
Get started
Follow the docs quickstart, or see what a finished audit looks like.