Documentation

SEO Loop answers SEO questions about any public URL, over plain HTTP. No signup, no API key.

Quick start

curl seoloop.in/audit/example.com
curl -fsSL https://seoloop.in/install | sh   # optional CLI
seoloop audit example.com

Targets

A target is a domain or URL: example.com, https://example.com/pricing. If you leave out the scheme, https:// is assumed. Only http and https on ports 80 and 443 are allowed, and the host must resolve to a public address. Anything else is refused with HTTP 422.

Endpoints

Every endpoint is GET /<endpoint>/<target>. The answer is short plain text by default.

Output options

Audits return an X-SeoLoop-Score header. Machine-readable descriptions: /openapi.json and /llms.txt.

The audit

Each check is weighted by importance (high 10, medium 5, low 2). The score is the weighted share of checks that pass; grades are A 90+, B 80+, C 70+, D 60+, otherwise F.

CLI

curl -fsSL https://seoloop.in/install | sh

seoloop audit example.com
seoloop audit example.com --only seo --format md
seoloop audit example.com --min 80          # exit code 3 below 80
seoloop audit example.com --diff            # what changed since last run
seoloop compare a.com b.com
seoloop ssl example.com --field days_left
seoloop indexable example.com --json

Exit codes: 0 success, 1 error, 2 bad usage, 3 audit score below --min, 4 rate limited. --diff keeps its state in ~/.cache/seoloop. Set SEOLOOP_URL to use your own server.

GitHub Action

- uses: mehranshahmiri/seoloop-action@v1
  with:
    url: https://staging.example.com
    min-score: 80
    skip: sitemap          # optional
    only: seo,security     # optional

Listed on the GitHub Marketplace. Outputs score and grade, writes the Markdown report to the job summary, and fails the job below min-score. The target must be publicly reachable from the internet, so use a deployed preview or staging URL.

MCP server

A remote MCP server (Streamable HTTP, stateless, JSON responses) exposes every endpoint as a tool, so AI agents can run the checks themselves.

claude mcp add --transport http seoloop https://seoloop.in/mcp

Most other MCP clients that support remote servers take a URL: https://seoloop.in/mcp. Tools: audit, compare, indexable, links, schema, status, title, meta, headers, redirects, ttfb, ssl, robots, sitemap. All are read-only. Results include both text and structured content.

Limits & errors

• Rate limits are per IP: 30 requests a minute in general, 6 a minute for /audit and /compare, 20 a minute for /mcp. Over the limit you get HTTP 429.
• Results are cached for 5 minutes (10 for audits), so repeating a request is fast. Look for X-Cache: HIT.
• Each request has a 25 second budget, at most 6 redirects, and a 1.5 MB response cap.

Errors are plain text (error: ...) or {"error": "...", "status": 422} as JSON.

Self-hosting

PHP 8.2+ with curl, dom, openssl, mbstring and intl, plus nginx and PHP-FPM. The repository includes example configs for nginx, a dedicated PHP-FPM pool and rate limits, and a Dockerfile.

git clone https://github.com/mehranshahmiri/seoloop
php -S 127.0.0.1:8099 -t public public/index.php    # try it locally

Environment: SEOLOOP_BASE_URL (public URL), SEOLOOP_CACHE_DIR. Full steps are in the README.

Security model

The service fetches URLs that strangers type in, so all outbound requests go through one hardened function: public IPs only (every address a name resolves to is checked), the validated IP is pinned into the connection, redirects are followed manually and re-validated at every hop, ports are limited to 80 and 443, and size, time and redirect counts are capped. Found a problem? See the security policy.