Technical SEO · compact evidence
Find the fixes.
Keep HTML out of your model context.
A bounded same-site crawl and deterministic checks turn static pages into a short, prioritized fix list. Inspect the evidence when you need it. No model or paid API is required.
This free first release checks HTTP failures, observed broken links, titles, index directives, canonical conflicts and JSON-LD syntax. It does not measure rankings, keyword volume, backlinks, rendered JavaScript or rich-result eligibility.
1. Try the supplied snapshot
Run the fictional two-page example, or load a local crawl snapshot. Your HTML stays in this browser; the same audit is also available over HTTP and hosted MCP. Use public or sanitized snapshots.
No audit run yet.
2. Review priorities and evidence
Select an issue group after the audit.
3. Crawl your public site
The local crawler pins validated public DNS addresses, stays on one HTTPS origin, respects robots.txt and waits at least one second between requests. It follows no off-site canonical or sitemap URLs. Limit: 20 pages, 100 KB per response, 2 MB total and 60 seconds. Missing, blocked, failed and unvisited pages remain unknown. Only run on sites you own or have permission to inspect.
Download Node.js 22+ crawler · SHA-256 checksum · Dependency licenses
shasum -a 256 -c agent-utilities-seo.mjs.sha256
node agent-utilities-seo.mjs crawl https://YOUR-SITE/ --out crawl.json --max-pages 10
node agent-utilities-seo.mjs report crawl.json
node agent-utilities-seo.mjs details crawl.json --group noindex --offset 0 --limit 20The crawl snapshot contains raw HTML. Keep that file out of model prompts; give your agent the compact report and bounded details. Summary and detail output are measured in bytes here, not tokens. Small inputs may produce larger reports.
Use the same audit from your agent
Free HTTP: POST /v1/seo/audit, JSON snapshot up to 128 KiB. Hosted MCP: agent_utilities_seo_audit at /mcp/remote?category=web. The free audit does not call paid utilities, purchase credits or crawl URLs remotely. Supplying full snapshots in an MCP request adds input tokens; the local crawler/report path keeps HTML outside the model.
Schema, example and detail pagination · MCP setup · Other metered utilities