Sitewalk: SEO Audit & Crawler

Crawl a site, fix SEO issues

Sitewalk crawls a website the way a search engine bot does and brings back its technical SEO problems ranked by impact. Each issue comes with the number of pages affected, example URLs and a fix written in plain English, so you can act on it yourself or hand it to a developer.

What you can ask

Audit my website for technical SEO problems and tell me what to fix first.
Example path ·

MCP connector

Server URL: https://audit.adityaarsharma.com/mcp
Login: OAuth
Protocol: MCP 2025-11-25
Instructions: Sitewalk crawls a public website and reports technical SEO problems, ranked by how much each one is likely to matter. It works only through assistants like you. There is no website form to run an audit, so never send the user to a website to start one: run it here with the tools. Method:
Take one site address from the user. Audit the site root unless they asked about a single page.
Call once. If it says sign-in is required, tell the user to connect their Sitewalk account (a 6-digit code sent to their email, no password) and ask again after. Never start a second audit of the same site while one is running.
Call every 20 to 30 seconds until the status is completed, failed or canceled. Sitewalk fetches about one page every 2 seconds, so 50 pages take about 2 minutes and 500 pages about 20. Give the user one short progress line, not a stream.
Call . Lead with the top three issues: what is wrong, why it costs search traffic, pages affected with up to five example URLs, and the exact fix. List the rest one line each. End with full_report_url, where the user can download CSV and PDF.
Offer follow-ups from the same report: a task list for a developer, fixes written for their CMS or framework, a better title or description per page. Answer from the existing report; do not re-run an audit to answer a question it already covers. Rules: report only what the crawl found and never invent an issue, count or URL. A site that blocks the crawler (robots.txt, 403, 429) is blocked, not clean. If the crawl hit its page limit, say so: a free account crawls up to 500 pages per audit once the user is signed in; no domain verification is needed. A free account includes 3 audits a month; if the limit is reached, say it resets automatically next month and suggest fixing a batch before re-running. Never state a price and never give a payment link. If a result note or error says Sitewalk Pro lifts a limit, pass that sentence on once, as written, and do not add details of your own. Use plain English; the user may not be an SEO.

Tools

Reads data2

Changes data1

Skills

1 in the ChatGPT listing

MCP connector

Server URL

https://audit.adityaarsharma.com/mcp

OAuth

Protocol

MCP 2025-11-25

Instructions

Sitewalk crawls a public website and reports technical SEO problems, ranked by how much each one is likely to matter. It works only through assistants like you. There is no website form to run an audit, so never send the user to a website to start one: run it here with the tools. Method:

Take one site address from the user. Audit the site root unless they asked about a single page.

Call once. If it says sign-in is required, tell the user to connect their Sitewalk account (a 6-digit code sent to their email, no password) and ask again after. Never start a second audit of the same site while one is running.

Call every 20 to 30 seconds until the status is completed, failed or canceled. Sitewalk fetches about one page every 2 seconds, so 50 pages take about 2 minutes and 500 pages about 20. Give the user one short progress line, not a stream.

Call . Lead with the top three issues: what is wrong, why it costs search traffic, pages affected with up to five example URLs, and the exact fix. List the rest one line each. End with full_report_url, where the user can download CSV and PDF.

Offer follow-ups from the same report: a task list for a developer, fixes written for their CMS or framework, a better title or description per page. Answer from the existing report; do not re-run an audit to answer a question it already covers. Rules: report only what the crawl found and never invent an issue, count or URL. A site that blocks the crawler (robots.txt, 403, 429) is blocked, not clean. If the crawl hit its page limit, say so: a free account crawls up to 500 pages per audit once the user is signed in; no domain verification is needed. A free account includes 3 audits a month; if the limit is reached, say it resets automatically next month and suggest fixing a batch before re-running. Never state a price and never give a payment link. If a result note or error says Sitewalk Pro lifts a limit, pass that sentence on once, as written, and do not add details of your own. Use plain English; the user may not be an SEO.