Next.js SEO Audit
Local read-only MCP server that audits a deployed site for SEO and indexing problems
- Pricing
- Open source
- Platforms
- CLI, self-hosted
- Runs
- Locally
- Version
- 0.1.2
- Listing updated
- today
Similar MCP servers
About Next.js SEO Audit
Next.js SEO Audit is an open-source MCP server for marketing and seo. It runs locally on your machine and is started by your AI client.
Aimed at Next.js sites, this server wraps the vercel-seo-audit CLI so a coding agent can check a deployed URL and read back the CLI's agent-format JSON. Checks cover redirects, robots.txt, sitemap, canonicals, noindex, metadata streamed into the body and preview deployments left indexable, across 17 modules. It does not run JavaScript, so it sees what the deployment serves, not what a browser renders.
Three tools exist on stdio only. One audit runs at a time with a 120-second cap, plus two seconds per crawled page. Findings are labelled as untrusted page content, with control and format characters stripped. Private and loopback addresses are refused to limit server-side request forgery, with an environment flag to audit a local dev server; DNS rebinding is noted as not covered. It never writes files, and fix text is only a suggestion. Node 22 or newer is required.
Install
Run in a terminal
claude mcp add nextjs-seo-audit -- npx -y nextjs-seo-audit-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"nextjs-seo-audit": {
"command": "npx",
"args": [
"-y",
"nextjs-seo-audit-mcp"
]
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"nextjs-seo-audit": {
"command": "npx",
"args": [
"-y",
"nextjs-seo-audit-mcp"
]
}
}
}Add to .vscode/mcp.json
{
"servers": {
"nextjs-seo-audit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nextjs-seo-audit-mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"nextjs-seo-audit": {
"command": "npx",
"args": [
"-y",
"nextjs-seo-audit-mcp"
]
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"nextjs-seo-audit": {
"command": "npx",
"args": [
"-y",
"nextjs-seo-audit-mcp"
]
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
NEXTJS_SEO_AUDIT_MCP_ALLOW_PRIVATESet to 1 to let audit_site reach private and local addresses, for a local dev server
Tools this server provides (3)
Taken from the project documentation; the running server may differ.
- audit_site
- Audits one URL and returns findings sorted error, warning, info.
- explain_finding
- Explains an issue code, its module and category.
- list_checks
- Lists every module id with the codes it can report.
What it does
- Site audit
- Audits one URL and returns findings sorted by severity.
- Issue explanations
- Explains what an issue code means and which module reports it.
- Check listing
- Lists every module id and the codes it can report.
- Sitemap crawl
- Optionally audits 1 to 50 pages from the sitemap.
- Diff against earlier run
- Passing a previous result returns new, resolved and unchanged findings.
- SSRF protection
- Refuses private addresses unless explicitly allowed.
Good for
- Audit a preview deployment before launch
- Find pages accidentally set to noindex
- Check robots.txt and sitemap health
- Re-run an audit and see what was fixed
- Audit a local dev server with the private-address flag
Pricing
Open source
Open source; free
Next.js SEO Audit FAQ
Does it change my project?
No. It is read-only and never writes files.
Does it run JavaScript?
No. It reads what the deployment serves.
Why was my local URL refused?
Private addresses are blocked unless NEXTJS_SEO_AUDIT_MCP_ALLOW_PRIVATE is set to 1.
What Node version is needed?
Node 22 or newer.
Is Next.js SEO Audit free?
Yes. Next.js SEO Audit is open source, so you can use and self-host it for free.
How do I add Next.js SEO Audit to Claude Code?
Run this command in your terminal: claude mcp add nextjs-seo-audit -- npx -y nextjs-seo-audit-mcp
What are the best alternatives to Next.js SEO Audit?
The closest alternatives to Next.js SEO Audit are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


