SEO Audit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_pageA | Analyze a single web page for SEO factors including:
Use this for detailed analysis of specific pages like job detail pages, landing pages, or homepage. |
| crawl_siteA | Crawl multiple pages of a website starting from a URL. Discovers internal links and analyzes each page. Returns:
Use this for comprehensive site audits. Respects crawl limits and delays. |
| run_lighthouseA | Run a Lighthouse performance audit on a URL. Returns:
Use this for performance analysis. Run separately for mobile and desktop if both matter. Note: Requires Lighthouse CLI to be installed (npm install -g lighthouse). |
| analyze_sitemapA | Analyze a site's robots.txt and XML sitemaps. Returns:
Use this as a first step to understand site structure before crawling. |
| check_urlsA | Check HTTP status codes for a list of URLs. Returns status code, redirect destination (if redirected), and response time for each URL. Use this to:
|
| plan_auditA | RECOMMENDED FIRST STEP - Analyze sitemaps and create an intelligent sampling strategy for large sites. This tool is essential for job boards and large sites with 100k+ pages. Instead of crawling everything, it:
Returns:
Use this BEFORE crawl_site or sample_pages to understand site structure. |
| sample_pagesA | Intelligently sample and analyze pages based on an audit plan. Use this AFTER plan_audit to analyze representative pages from each route type. For a site with 500k job pages, instead of crawling all of them, this will:
Returns:
This approach finds template-level issues that affect all pages of that type. |
| run_auditA | FULL AUDIT - Run a complete SEO audit with automatic sampling, caching, and report generation. This is the main audit tool that orchestrates the entire workflow:
The audit captures pages ONCE and stores:
Returns comprehensive findings and prioritized fix recommendations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes, but there is some overlap between crawl_site, run_audit, and sample_pages. crawl_site performs comprehensive crawling and analysis, run_audit orchestrates a full audit including sampling, and sample_pages focuses on intelligent sampling after planning. While their descriptions clarify differences, an agent might initially confuse when to use crawl_site versus run_audit, as both involve crawling and analysis, though run_audit is more automated and includes caching and reporting.
Tool names follow a consistent verb_noun pattern (e.g., analyze_page, check_urls, crawl_site), with minor deviations. The main inconsistency is run_lighthouse, which uses 'run' instead of 'analyze' or 'check', and run_audit, which also uses 'run' but fits the pattern. Overall, the naming is predictable and readable, with only slight variations in verb choice.
With 8 tools, the count is well-scoped for an SEO audit server. Each tool serves a specific function in the audit workflow, from initial planning (plan_audit) to detailed analysis (analyze_page) and comprehensive auditing (run_audit). The tools cover a range of tasks without being overwhelming, and none feel redundant or unnecessary given the domain's complexity.
The tool set provides complete coverage for SEO auditing, including planning (plan_audit), crawling (crawl_site), sampling (sample_pages), detailed analysis (analyze_page, run_lighthouse), sitemap handling (analyze_sitemap), URL checking (check_urls), and full automation (run_audit). There are no obvious gaps; the tools support a full lifecycle from initial assessment to report generation, with clear workflows and no dead ends for agents.