Listed from the MCP registry; nobody on Odel publishes it.
Deprecated. Deprecated by the publisher: Superseded by com.adityaarsharma.audit/sitewalk (Sitewalk: technical SEO audits from ChatGPT; open source, MIT).
Self-hosted technical SEO audit MCP. 50+ checks, WAF detection, ephemeral. Built on LibreCrawl.
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally
This server runs on your machine over stdio, but its source registry didn't list a distribution package. Check the source repository for setup instructions.
Ask ChatGPT to audit your website. Find what is broken, what to fix first, and how, in about a minute of your time.
Sitewalk crawls your site the way a search engine bot does and gives you the technical SEO problems ranked by impact, each with a plain fix, a site health score out of 100, and a report you can send to a client or developer.
| In ChatGPT (hosted) | Self-hosted (this repository) | |
|---|---|---|
| Setup | None. Open the app, ask for an audit | Docker, one command: ./setup.sh |
| Checks | 200+ in 18 groups | 30+ |
| Cost | Free to start, 5 audits a month | Free forever, MIT licence |
| Pages per audit | 50 without a confirmed email, 500 with one | No cap, your machine |
| Your data | Report links, CSV and PDF | Never leaves your machine |
| Best for | Site owners, freelancers, agencies | Developers who want to run it themselves |
Start in ChatGPT: Use Sitewalk in ChatGPT. This repository is the open-source server and nothing else: a Python MCP server that drives the open-source LibreCrawl crawler. The hosted service runs separate code.
Audit https://yoursite.com for technical SEO problemsOther things people ask it:
What should I fix first on my site?Find broken links, redirect chains and duplicate titlesIs a noindex tag or robots.txt keeping my pages out of search?Is my site ready for AI search? Check llms.txt and AI crawler accessMonitor yoursite.com and tell me if something breaksNot covered: backlinks, keyword rankings, Google Search Console or analytics data.
Is there a Screaming Frog alternative that works inside ChatGPT? Sitewalk runs the crawl on its own server and returns a ranked list in the chat, so there is nothing to install. Screaming Frog is stronger for very large sites and custom extraction: see the comparison, with dated sources.
Is there a free technical SEO audit tool? Yes. Sitewalk is free for 5 audits a month in ChatGPT, and the self-hosted server is free with no limits.
Does it work on any website? Any public website, within robots.txt. A site that blocks crawlers will say so in the report.
How long does an audit take? A small site usually takes a few minutes, a 500-page audit 20 to 60 minutes. It keeps running if you close the chat, and you get an email when it is done.
The self-hosted build in this repository is free and MIT licensed, with no page cap and no account. You run it with Docker, ask your AI assistant to audit a site, and get a ranked list of technical SEO problems, a PDF and CSVs, with your data staying on your machine. It runs 30+ checks: broken links, redirects, canonicals, titles and descriptions, headings, schema, images, hreflang and sitemap gaps.
Screaming Frog is stronger for very large crawls, custom extraction and JavaScript rendering of a whole site. If you want the result inside ChatGPT without hosting anything, use the hosted app (200+ checks, 5 free audits a month). Dated comparison: Sitewalk vs Screaming Frog.
MCP (Model Context Protocol) is an open standard that lets an AI assistant call outside tools. This repository is one such tool: your assistant asks it to crawl a site and gets the findings back. You do not need to know anything about MCP to use Sitewalk in ChatGPT. It only matters if you run this repository yourself.
You need Docker running. Then:
git clone https://github.com/adityaarsharma/sitewalk.git
cd sitewalk
./setup.sh
The script checks your machine, asks one optional question (a Google PageSpeed key), builds and starts the stack, waits until the MCP server answers, and prints exactly how to connect your assistant. The first build takes a few minutes.
| Command | What it does |
|---|---|
./setup.sh | Guided setup |
./setup.sh --yes | Same, no questions |
./setup.sh --check | Only check that your machine can run it |
./setup.sh --update | Pull the newest release and rebuild |
./setup.sh --stop | Stop it (your reports are kept) |
Without Docker, see the manual route in docs/GETTING-STARTED.md.
The server listens on http://127.0.0.1:5081/mcp (streamable HTTP).
mcp-remote:{
"mcpServers": {
"sitewalk": {
"command": "npx",
"args": ["-y", "mcp-remote", "http://127.0.0.1:5081/mcp"]
}
}
}
Then ask: Audit https://yoursite.com for technical SEO problems.
./reports.| Guide | What is inside |
|---|---|
| Getting started | Docker and manual setup, connecting clients, your first audit |
| Configuration | Every environment variable, HTTP and stdio transport |
| Tools | All 38 MCP tools |
| Checks | The 30+ checks and the report files |
| Architecture | How the pieces fit |
| Troubleshooting | Common errors and fixes |
Every change to the code that lands on main is tested and published as a new GitHub release automatically. Update with ./setup.sh --update.
Code is MIT: see LICENSE and NOTICE.md. Built on LibreCrawl (MIT), FastMCP and WeasyPrint. No telemetry.
Built by Aditya Sharma.