Technical SEO audit

Can search engines and AI crawlers actually index this page? One pass over reachability, TLS, robots policy, sitemap health, meta/OpenGraph tags, and the on-page link graph.

$0.009 per call · one payment for the whole workflow

POST /api/skill/seo-audit

Sample output + API docs →

6 tools run server-side in one request. You pay once, settle once, and get a single response - no orchestration, no per-step payments, and a partial-success envelope if any step fails. USDC over x402 on any supported chain.

When to use this pack

You shipped a page (or inherited a site) and want the technical indexability picture without opening six tools: is it up and fast, is TLS valid, does robots.txt allow the crawlers that matter (including LLM bots), does the sitemap parse, are title/description/OG tags present and sized right, and where do its links point? Distinct from a security audit (headers/SPF/CT) and an uptime snapshot - this is the 'will Google and ChatGPT see what I meant' check. Run it pre-launch, post-migration, or on a competitor.

Tools in this pack

All 6 run inside the single $0.009 call above. Each is also callable on its own if you only need one part.

HTTP check POST /api/http-check Check any public URL: status code, latency, final URL after redirects, and response headers. The uptime primitive for agent monitors.
TLS certificate POST /api/tls-cert Inspect the TLS certificate of any public host: subject, issuer, validity window, days remaining, SANs, and SHA-256 fingerprint.
Robots.txt check POST /api/robots-check Fetch a site's robots.txt and answer: may this user-agent crawl this path? Returns the matched rule and all declared sitemaps.
Sitemap reader POST /api/sitemap Fetch and parse a sitemap.xml (or sitemap index): returns up to 500 URLs with lastmod, or the child sitemaps of an index.
Page metadata GET /api/meta Fetch page metadata for a URL: title, description, OpenGraph, Twitter cards, canonical URL, favicon.
HTTP headers + security analysis POST /api/http-headers Fetch a URL and return every response header plus a security analysis: HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP/CORP/COEP. Scores 0–100 by presence, flags weak HSTS, and warns on Server/X-Powered-By identity leaks. SSRF-protected.

Bought one at a time, these 6 tools cost $0.01 together; the pack is that sum less a 10% bundle discount, rounded up to the $0.001 settlement floor, which is $0.009.

Workflow

http-check with the page URL - status, latency, redirect chain. A 200 under ~800ms is healthy; a 3xx chain longer than one hop wastes crawl budget and should be flattened.
tls-cert with the host - issuer, expiry, chain trust. daysRemaining < 21 is a renewal warning; an untrusted chain is an indexing risk (and a browser warning for humans).
robots-check with the page URL - is it fetchable by crawlers? Re-run with userAgent values you care about (Googlebot, GPTBot, ClaudeBot, PerplexityBot) - LLM crawler policy is part of modern SEO, and an accidental Disallow: / for AI bots silently removes you from answer engines.
sitemap with the site's sitemap.xml URL - type, URL count, parse errors. A sitemap that 404s or is empty means discovery depends entirely on the link graph.
meta with the page URL - title, description, canonical, OpenGraph/Twitter cards. Flag: missing description, title > 60 chars, missing og:image (kills social/link-preview CTR), missing canonical on parameterized URLs.
http-headers with the page URL - the response headers search engines act on. Flag: an X-Robots-Tag: noindex (silently removes the page from every index regardless of robots.txt), a missing/short Cache-Control on static assets, and a Content-Type without charset. Summarize as a pass/warn/fail card per check with the two highest-impact fixes on top.

Arguments

Name	Required	Description	Example
`url`	yes	The page URL to audit (https://…)	`https://example.com`

What one call returns

A JSON object with pack, args, steps, summary; steps holds one entry per tool (http-check, tls-cert, robots-check, sitemap, meta, http-headers), each with its own result or error. Full example on the API page.

Call it directly

Any x402 client pays the 402 and gets the whole workflow back in one response:

npx agent402-client call seo-audit {"url":"https://example.com"}

Run it in Claude

claude mcp add agent402 -s user -- npx -y agent402-mcp@latest

Then paste this prompt into Claude:

Run a technical SEO audit of https://example.com with Agent402: (1) http-check {url} - status + latency + redirects. (2) tls-cert {host: "example.com"} - expiry + trust. (3) robots-check {url, userAgent: "Googlebot"} and again with "GPTBot" - crawlability for search AND answer engines. (4) sitemap {url: "https://example.com/sitemap.xml"} - parses, URL count. (5) meta {url} - title/description/OG completeness, title ≤ 60 chars. (6) http-headers {url} - flag X-Robots-Tag: noindex and cache policy. Return a card: {reachability, tls, robots: {googlebot, gptbot}, sitemap, meta, headers, topFixes: [two highest-impact items]}.

← All skill packs