Black SEO Analyzer
Server Details
Technical SEO audits: check a page or crawl a whole site, locally or hosted. Compares crawls.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- sethblack/black-seo-analyzer
- GitHub Stars
- 60
- ChatGPT
- Black SEO Analyzer
- Claude
- Black SEO Analyzer
TDQS
Scored across 11 tools
Most tools have sharply distinct roles, and the descriptions explicitly resolve the trickiest boundaries (check_page vs start_crawl, check_page vs serp_preview, issues_summary vs query_issues). The only mild overlap is among the single-URL readers — check_page, page_report and serp_preview — which all target one page but with clearly different outputs; an agent could occasionally hesitate over which report is wanted.
All names are snake_case, so the surface reads consistently, but there are two mixed families: verb_noun actions (check_page, start_crawl, list_crawls, query_issues, search_docs, compare_crawls) and noun-first report nouns (account_status, crawl_status, issues_summary, page_report, serp_preview). Each family is internally coherent, so it is a minor deviation rather than a readability problem.
Eleven tools is well within the sweet spot and every tool maps to a real step in the audit workflow: check, crawl, poll, summarize, drill down, compare, preview snippet, read docs, check quota. Nothing looks like padding or a duplicate.
The lifecycle is well covered — single-page audit, site crawl, progress polling, session listing, summary, issue drill-down, per-page detail, regression comparison, plus account and docs. The visible gaps are housekeeping operations: there is no way to delete/expire crawl sessions, cancel a running crawl, or export results, which an agent can mostly work around.
Available Tools
11 toolsaccount_statusARead-onlyIdempotentInspect
Report this account's plan and usage live: whether hosted audits are active, the page budget used and remaining in the rolling 30 days and when it resets, how long crawl sessions are kept, and the licenses on the account. Call it when a tool returned trial_expired, no_hosted_addon or quota_exceeded, when the user says their plan has changed, or when they ask what their plan includes. Read-only: it never changes the account.
Inputs: no named parameters.
check_pageAInspect
Audit one URL immediately and return its SEO issues (schema bseoa.issue/v1: key, category, severity, message, fix_hint, docs_url). This is the fast path and the right first call for "what is wrong with this page?" - it fetches a single page and never follows links. Prefer it over start_crawl whenever the user asked about one specific page rather than a whole site, and that includes a site's homepage or bare domain ("check https://example.com/ for SEO problems") when the user did not ask for a crawl, a site audit or a number of pages. Does not count against the account's page budget; limited to 30 calls a minute. JavaScript rendering (spa) is not available on the hosted connector.
Inputs: url (required), spa.
compare_crawlsARead-onlyInspect
Compare two crawls of the same site and report which issues are new in the later crawl, which were fixed, and how many persist. Use it to answer "did my changes help?" or "what regressed since the last deploy?", and to gate a release: only the new_issues list represents a regression, so a pre-existing backlog never counts against a change. Get both session ids from list_crawls; base_session is the earlier crawl.
Inputs: base_session (required), compare_session (required).
crawl_statusARead-onlyInspect
Report the progress of a crawl started by start_crawl: state ("queued", "running", "finished" or "failed"), the crawl session_id to read results from, the pages stored so far, and the error text if it failed. Poll every few seconds; a queued crawl starts as soon as the worker is free. Do not call issues_summary or query_issues for that crawl until state is "finished", or you will read a partial result.
Inputs: job_id (required).
issues_summaryARead-onlyInspect
Summarize a crawl: total issue count, counts by severity and by category, and every distinct issue key with how many pages it affects plus up to five example URLs. Always call this before query_issues - it is small, it tells you which keys are worth drilling into, and it is what you should base a prioritized fix plan on. Omit session_id to summarize the account's most recent crawl.
Inputs: session_id.
list_crawlsARead-onlyInspect
List the crawl sessions stored for this account, newest last, with their session_id, start URL, start and end times, and page count. Single-page checks made with check_page are not crawls and are not listed. Call this first when the user refers to "the last crawl" or when you need a session_id for issues_summary, query_issues, page_report or compare_crawls. A session with no end time is still running or was interrupted.
Inputs: no named parameters.
page_reportARead-onlyInspect
Report everything recorded about one crawled URL: status code, redirect target, title and meta description, Open Graph tags, word count, link and asset counts, headings, TTFB, Web Vitals score, and the full issue list for that page. Use it after query_issues or issues_summary when you need the context behind a specific page's issues. It never returns the page's HTML source; to inspect markup, fetch the URL yourself.
Inputs: url (required), session_id.
query_issuesARead-onlyInspect
List individual issues from a crawl, filtered by severity, issue key, category or URL prefix, as bseoa.issue/v1 records with the affected URL, the localized message, a fix hint and a docs link. Returns at most 100 issues per call: when the response has a non-null next_offset there are more, so call again with offset set to that value. Narrow with min_severity or key from issues_summary rather than paging through everything.
Inputs: key, limit, offset, category, +3 more.
search_docsARead-onlyIdempotentInspect
Search Black SEO Analyzer's own documentation and return the matching sections with their URLs. Use it for questions about bseoa itself: what a tool, command, flag or setting does, crawl limits and the page budget, licenses and the hosted plan, installing or configuring the CLI, GUI or connector, or what an issue key means (pass issue_key for that issue's reference page with its fix). Pass query for a question, issue_key for one issue, or neither to list the documentation pages. Works whatever the account's hosted status; does not count against the page budget; limited to 30 calls a minute.
Inputs: query, issue_key, max_results.
serp_previewARead-onlyIdempotentInspect
Fetch each URL and report how its title and meta description will look in a search result: character length, pixel width, whether the engine will truncate it, and the Open Graph and Twitter Card fallbacks. Use it when the user asks how a page "looks in Google" or is rewriting titles and descriptions - it is about the snippet, not the page's other SEO problems, which check_page covers. At most 50 URLs per call; does not count against the page budget; limited to 30 calls a minute.
Inputs: urls (required), engine.
start_crawlAInspect
Queue a crawl of a whole site and return a job_id immediately; a worker runs the crawl and the pages count against the account's rolling 30-day page budget. Use it only when the user asks to crawl or audit a site, or names a number of pages; a request to check a single URL, even a homepage, is check_page, and never start a crawl alongside check_page unasked. Pass the max_pages the user named. One crawl per account runs at a time. Poll crawl_status with the job_id until state is "finished", then read the results with issues_summary and query_issues. max_pages defaults to 500 and is capped at 2000 and at the pages remaining in the budget. JavaScript rendering (spa) is not available on the hosted connector.
Inputs: url (required), spa, max_pages, audit_profile.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Technical SEO audit crawler: broken links, 404s, redirects, titles, canonicals. Runs on Apify.
Technical SEO + GEO (AI-search) site audits: hosted crawls, prioritized fixes, report diffs.
SEO, broken links, Lighthouse, sitemaps, Open Graph tags and SSL expiry for any list of URLs.
Crawls a website for broken links, redirects and SEO issues, and lists changes since the last run
Related MCP Servers
- AlicenseAqualityBmaintenanceRead-only static SEO audits and bounded crawling; runs locally with no API keys or telemetry.368 npmMIT
- AlicenseAqualityDmaintenanceEnables SEO auditing and site analysis by crawling websites, identifying issues, and generating reports like sitemaps and markdown exports.54MIT
- AlicenseNot gradedqualityDmaintenanceAnalyzes any webpage for SEO scores, issues, and actionable recommendations. Supports side-by-side comparison of two URLs.MIT
- AlicenseAqualityDmaintenanceEnables auditing of a live website's technical SEO, including sitemap coverage, per-page issues, and redirect chains.4MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.